Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [tycho-user] Meaningless to increase version number of projects when tagging/releasing?

On Sat, Jun 23, 2012 at 4:58 AM, Johannes Serup <johs.serup@xxxxxxxxx> wrote:
[del]
> c) There is no distrubtion system. So there is no way of depending on
> previously build binaries. To my understanding even nexus pro does not have
> full support for osgi/p2 repositories that can be integrated with maven SCM
> and the maven-deploy-plugin.

So you are supplying your users with you app already bundled, e.g. as
a zip file.

What happens in a months time when bugs are reported?
Do you give them another zip that contains the same named artefacts?
What about in a further months time when more bugs are reported?
How will you tell which versions they were using?
How will you be able to reproduce the problem on your desktop with the
same install base and compare that against the code?

The standard best practice is whenever you give something to someone
outside of your dev team you want released versions that never change.


Back to the top