Hi Kohei, On Fri, Aug 19, 2005 at 22:50:21 -0400, Kohei Yoshida wrote:
> Now my question is: do we know for sure that we will have a 2.1 > release, or do we skip that version number and go straight to 3.0? Unfortunately there is no decision yet. > If yes, could someone create a new target milestone for 2.1/3.0 > (whichever)? I think every developer would prefer to have a target for the next non-micro release, whatever it be, next minor or next major.. > I have an issue that I want to assign a target milestone > for, but since it's a feature/enhancement, neither 2.0.1 nor 2.0.2 > will be appropriate. Any advice from someone who makes the call on > this matter would be appreciated. A target of OOoLater may of course always be retargeted to some release milestone when ready, which is how most of these issues are handled. You could also use the target milestone "not determined" if you needed to distinguish it from issues that are set to OOoLater. That's what I use sometimes if it isn't clarified exactly when an implementation should go in but OOoLater doesn't fit, for example when there are missing pieces like a signed JCA for a patch. However, one should only use that target temporary, keep an eye on it, retarget as soon as appropriate and not overstress its use. Eike -- OOo/SO Calc core developer. Number formatter bedevilled I18N transpositionizer. GnuPG key 0x293C05FD: 997A 4C60 CE41 0149 0DB3 9E96 2F1A D073 293C 05FD --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
