Hello,
Let's keep it simple.
2.3.build, build being incremented everytime a new feature or bug fix is
built in, seems like a reasonable plan
The only difficulty with the "build" is when people are doing stuff in
parallel. I guess there will be a "file not up to date" thing ... so it
would work.
Ok, so 2.1 is out... let's branch for new development... As I asked let's
not commit new stuff in 2.1.
Can someone more knowledgeable than me in "branches" take care of tagging
2.1 and branching for the new development with 2.3.1
Again numbering:
major, minor, build is tried and true. build in our case is the
responsability of every developer that commits something, meaning a patch or
a feature.
Regards
marc
|-----Original Message-----
|From: [EMAIL PROTECTED]
|[mailto:[EMAIL PROTECTED]]On Behalf Of Filip Hanik
|Sent: Tuesday, March 06, 2001 11:48 AM
|To: JBoss-Dev
|Subject: RE: [jBoss-Dev] Version numbering
|
|
|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.
|>
|>
|>
|>
|
|
