[torquedev] Re: what happened to 2.4.0?
glen.beane at gmail.com
Fri Mar 27 20:44:20 MDT 2009
If CRI is going to have people running 2.4.x on production systems, we
probably should release a real 2.4.0 official release, other than the
2.4.0b1 in the download folder. Then we we should make a 2.4-fixes
branch in subversion to continue 2.4.x development and start working
on 2.5.0 in trunk.
The release process is completely messed up for 2.4 now.
On Fri, Mar 27, 2009 at 10:33 PM, Glen Beane <glen.beane at gmail.com> wrote:
> ok, so it looks like configure.ac was changed in some other check in
> than the change to the configure script, so if we rerun autoconf
> configure.ac and configure will have the same torque version... but
> still I think it should have been changed to 2.4.0b2 not 2.4.1b1
> On Fri, Mar 27, 2009 at 10:30 PM, Glen Beane <glen.beane at gmail.com> wrote:
>> I see that in trunk the version in configure got changed from 2.4.0b1 to 2.4.1b1
>> First, the version *should* be changed in configure.ac, and then a
>> new configure should be generated from that. configure should never
>> be edited by hand, since those changes will be lost as soon as someone
>> runs autoconf again.
>> Second, as far as I know there never was an official 2.4.0 release,
>> just snapshots and a beta release. Why go from 2.4.0b1 to 2.4.1b1?
>> The next logical version number would be 2.4.0b2 (2.4.0 beta 2), since
>> we still haven't released 2.4.0 yet.
More information about the torquedev