either way is fine with me, whatever is easier to understand.
as long as everybody is on the same page :)
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 Tom Cook
> Sent: Tuesday, March 06, 2001 5:38 PM
> To: JBoss-Dev
> Subject: RE: [jBoss-Dev] Version numbering
>
>
> AFAIK there are no nightly builds - just nightly source snapshots. So how
> do we know when to increment the last number? This is particularly
> problematic since there is no real central project control, so anyone
> might do a build any time, to test, whatever, and then do they increment
> the number? The three digit system seems fairly well tried and accepted
> in OS circles...
>
> Tom
>
> On Tue, 6 Mar 2001, Filip Hanik wrote:
>
> > I have another recommendation
> >
> > 4 digits separated by dots like this
> >
> > 2.3.C.23
> >
> > what does this mean?
> >
> > 2 = major version
> > 3 = minor version
> > C = Candidate Release (Final) (other options A=Alpha, B=Beta)
> > 23= Build number
> >
> > so this number is indentifying:
> >
> > We are building towards the candidate release of version 2.3,
> and we have
> > done 23 builds already.
> > If we have nightly builds the last number will increase.
> >
> > if anyone thinks this is a good idea, just let me know and I
> can give more
> > details how this can work very well.
> >
> > 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 Kimpton,C (Chris)
> > > Sent: Tuesday, March 06, 2001 1:06 AM
> > > To: 'JBoss-Dev'
> > > Subject: [jBoss-Dev] RE: Version numbering
> > >
> > >
> > > Hi,
> > >
> > > >
> > > > Instead of doing 2.1-BETA, 2.1-FINAL
> > > > etc., why not just go with a three-
> > > > digit version number.
> > > > For example, 2.1-BETA has version
> > > > number 2.1.0. When we fix the bugs
> > > > in 2.1.0, we get 2.1.1. If 2.1.1 is
> > > > ok, we release that as 2.2.0,
> > > > otherwise a 2.1.2 could be done first.
> > >
> > > +1
> > >
> > > >
> > > >
> > > > > I am no cvs guru so clear instruction on how to do this
> > > > would be very
> > > > > welcome
> > > >
> > > > Me too...
> > > >
> > >
> > > Create a tag, and then branch from it - although you could
> delay creating
> > > the branch - its only needed if you want to patch it...
> > >
> > > See http://www.cvshome.org/docs/manual/cvs_5.html#SEC54
> > >
> > > Basically, create a tag for 2.1.0 and a branch 2.1.0-patches,
> > > then when your
> > > happy to do a release of this patched version, create a new tag on the
> > > branch - 2.1.1 - or if final 2.2.0.
> > >
> > > HTH,
> > > Chris
> > >
> > > ==================================================================
> > > ==============================
> > > This electronic message (email) and any attachments to it are
> > > subject to copyright and are sent for the personal attention of
> > > the addressee. Although you may be the named recipient, it may
> > > become apparent that this email and its contents are not intended
> > > for you and an addressing error has been made. This email may
> > > include information that is legally privileged and exempt from
> > > disclosure. If you have received this email in error, please
> > > advise us immediately and delete this email and any attachments
> > > from your computer system.Rabobank International is the trading
> > > name of Coöperatieve Centrale Raiffeisen-Boerenleenbank B.A.
> > > which is incorporated in the Netherlands. Registered with the
> > > Registrar of Companies for England & Wales No. BR002630 and
> > > regulated by the SFA for the conduct of investment business in the UK.
> > >
> > > The presence of this footnote also confirms that this email has
> > > been automatically checked by Rabobank International for the
> > > presence of computer viruses prior to it being sent, however, no
> > > guarantee is given or implied that this email is virus free
> upon delivery.
> > >
> > >
> > >
> > >
> >
> >
> >
>
> --
> "If you mess with something for long enough it will break." - Schmidt
>
>
>
