I briefly stopped watching the commits and am not absolutely certain: is the tip of TORQUE_3_0_BRANCH in a state where I could throw a TORQUE_3_0_2 tag on it and call it a release, or is there absolutely necessary outstanding work that would interfere with normal operation?
- Dan Martin Poeschl <[EMAIL PROTECTED]> writes: > +1 > > martin > > Daniel Rall wrote: > > >Scott Eade <[EMAIL PROTECTED]> writes: > > > > > > >>Shouldn't the TORQUE_3_0_BRANCH have had a TORQUE_3_0_1 > >>tag added with the release of 3.0.1? > >> > >>I guess there is little point if there is not likely to > >>be a 3.0.2 (i.e. efforts are now focused on 3.1). > >> > > > > >What do people think about putting this to get this deadlock fix into > >a 3.0.2? I ask because I have seen it fatal to an entire web > >application. ... --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
