Hi,
I am in doubt regarding what version numbers I should use for my
product. There are two schemes I can think of right now:
1) 1.0-m1-SNAPSHOT - 1.0-m1 - 1.0-m2-SNAPSHOT - 1.0-m2 -
1.0-rc1-SNAPSHOT - 1.0-rc1 ...
2) 1.0-SNAPSHOT - 1.0-m1 - 1.0-SNAPSHOT - 1.0-m2 - 1.0-SNAPSHOT -
1.0-rc1 ...
If
Hello.
In my projects I use second variant.
It's makes only one trouble for me, when I have to remember the name of the
last milestone version I have released already and what will be the next :)
By my logic, you always develop snapshot of version 1.0 (for example). Not
1.0-m1, not 1.0-m2.
Thanks, this is what I was thinking, too. Can I also get an official
nod that this won't backfire at some point which I cannot think about
right now, please?
Lóránt
On Tue, Mar 23, 2010 at 10:40, Aleksey Didik
di...@magenta-technology.ru wrote:
Hello.
In my projects I use second variant.
Hi Lóránt,
Lóránt Pintér wrote at Dienstag, 23. März 2010 10:21:
Hi,
I am in doubt regarding what version numbers I should use for my
product. There are two schemes I can think of right now:
1) 1.0-m1-SNAPSHOT - 1.0-m1 - 1.0-m2-SNAPSHOT - 1.0-m2 -
1.0-rc1-SNAPSHOT - 1.0-rc1 ...
2)
At this point I cannot see why I would mix SNAPSHOT and final versions
of my artifacts as dependencies. (This is a standalone product, the
only things depending on it are our tools that create test databases
etc.)
Apart from this, is there any danger in using the 2) scheme, i.e.
always having
Another question: what should be service releases be called?
1.0.sr1? 1.0-sr1? 1.0.1?
Lóránt
2010/3/23 Lóránt Pintér lorant.pin...@gmail.com:
At this point I cannot see why I would mix SNAPSHOT and final versions
of my artifacts as dependencies. (This is a standalone product, the
only things
