RE: NUnit Version Numbering

I think I answered this earlier, via the copy I received. Since it's just
now posting, I'll reply with my latest info.

The ymmdd pattern will stop working in 2006. I've been using the uddd
pattern that I described for a short while and I tend to agree with Jamie
that it's annoying to have to calculate the day. Sequential numbers are
another option.

There is one other issue: what should the version number be in
CommonAssemblyInfo.cs if you check the code out of sourceforge? My thought
is to use 2.3.*.* there, since any number kept in the repository can
potentially duplicate a release - even though the code has changed. For our
release builds, we would substitute actual numbers, of course.

Charlie

> -----Original Message-----
> From: nunit-developer-admin@xxxxxxxxxxxxxxxxxxxxx [mailto:nunit-developer-
> admin@xxxxxxxxxxxxxxxxxxxxx] On Behalf Of Jamie Cansdale
> Sent: Monday, November 28, 2005 4:09 PM
> To: Charlie Poole; nunit-developer@xxxxxxxxxxxxxxxxxxxxx
> Subject: Re: [nunit-developer] NUnit Version Numbering
> 
> Hi Charlie,
> 
> > 3. The build number (third digit) for development builds will be in the
> form
> > yddd, representing the date of the build. For example, a development
> build
> > issued today would be 2.3.5322, one a week from now would be 2.3.5329.
> >
> How about using ymmdd for the build number rather than yddd. This
> would be a lot easier on my brain.  ;o)
> 
> Jamie.
> 
> 
> 
> On 28/11/05, Charlie Poole <charlie@xxxxxxxxxxxxxxxxxxx> wrote:
> > Hi All,
> >
> > Following up on the version numbering issue, here's what's happening...
> >
> > 1. NUnit 2.2.3 was released in two builds, one using .Net 1.1 and the
> other
> > using .Net 2.0. The same version number was used for both versions and
> this
> > seems to cause no problems. Please let me know if any are encountered.
> >
> > 2. NUnit will go to the traditional odd/even numbering used in many open
> > source projects. For example: 2.3.x is a development build and 2.4.x is
> a
> > stable production build.
> >
> > 3. The build number (third digit) for development builds will be in the
> form
> > yddd, representing the date of the build. For example, a development
> build
> > issued today would be 2.3.5322, one a week from now would be 2.3.5329.
> >
> > 4. The build number for stable builds will be sequential within each
> minor
> > version: 2.4.1, 2.4.2, etc.
> >
> > 5. The CVS mainline will always contain the version number of the last
> > development drop. We'll use a release branch for stable releases and
> will
> > begin doing bug fixes on those releases, separate from the ongoing
> > development of new features.
> >
> > 6. If it becomes necessary to distinguish versions built with .Net 1.1
> and
> > .Net 2.0, we'll do so. But at the moment, there seems to be no need.
> >
> > That's how it looks now, anyway.
> >
> > Charlie
> >
> >
> >
> >
> > -------------------------------------------------------
> > This SF.net email is sponsored by: Splunk Inc. Do you grep through log
> files
> > for problems?  Stop!  Download the new AJAX search engine that makes
> > searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
> > http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
> > _______________________________________________
> > nunit-developer mailing list
> > nunit-developer@xxxxxxxxxxxxxxxxxxxxx
> > https://lists.sourceforge.net/lists/listinfo/nunit-developer
> >
> 
> 
> -------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc. Do you grep through log
> files
> for problems?  Stop!  Download the new AJAX search engine that makes
> searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
> http://ads.osdn.com/?ad_idv37&alloc_id865&op=ick
> _______________________________________________
> nunit-developer mailing list
> nunit-developer@xxxxxxxxxxxxxxxxxxxxx
> https://lists.sourceforge.net/lists/listinfo/nunit-developer




-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_idv37&alloc_id865&op=click