It doesn't matter whether they are public or not, versions and releases have
to be tracked as well.
I actually recommended a more detailed versioning scheme that would have
easily taken care of this problem earlier on, but the developers of JBoss
felt strongly that 3 digits would be enough to take care of all the
versioning.
So, I'm not the one arguing against Toby's point, I'm just notifying you and
other listeners that this has been discussed before, and it was shut down.
I'm all for Toby's point, but I also feel like, before making a decision
again, please consider all the scenarios that could happen, and create a
release cycle too.
Using a versioning scheme without a release goal, makes it almost useless,
irregardless of how sophisticated or simple the scheme is.
Filip
~
Namaste - I bow to the divine in you
~
Filip Hanik
Software Architect
[EMAIL PROTECTED]
www.filip.net
> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of Scott
> M Stark
> Sent: Thursday, April 12, 2001 4:39 PM
> To: [EMAIL PROTECTED]
> Subject: Re: [JBoss-dev] Added Rel_2_2_1 tag to Branch_2_2
>
>
> But Toby is talking about the "internal" patch versions which are
> not public releases.
> So how would the version tags go for the 2.2.0 -> 2.2.1 -> 2.2.2
> JBoss releases?
>
> JBoss_2_2_0
> + Rel_2_2_1
> + Rel_2_2_2
> + Rel_2_2_3
> |
> JBoss_2_2_1
> + Rel_2_2_? (Rel_2_2_4 ?)
> ...
> JBoss_2_2_2
>
> ----- Original Message -----
> From: "Filip Hanik" <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Sent: Thursday, April 12, 2001 4:04 PM
> Subject: RE: [JBoss-dev] Added Rel_2_2_1 tag to Branch_2_2
>
>
> > > Wouldn't it make more sense to call these tags Rel_2_2_0_a,
> Rel_2_2_0_b,
> > > then, after JBoss_2_2_1, Rel_2_2_1_a, Rel_2_2_1_b, etc?
> >
> > well, this discussion was brought up earlier, and it was
> determined to use a
> > three digit version number.
> > hence when you create a new release of version 2.2 (release 2.2.x), it
> > becomes 2.2.++x
> >
> > Filip
> >
>
>
>
> _______________________________________________
> Jboss-development mailing list
> [EMAIL PROTECTED]
> http://lists.sourceforge.net/lists/listinfo/jboss-development
>
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-development
