+1a. Does the full release mean that HSLF will be moved out of the scratchpad area?
Yegor NB> * should we do a release now, freeze, work to a release now, release with NB> some HSLF apis that are about to change, without excel comment support NB> etc, then do another release in the new year once we have that code? NB> or NB> * alpha/beta now, beta when we've got the HSLF api tweaks + excel comment NB> support in the new year, then freeze and release then? NB> My main reason for suggesting an alpha was the HSLF api tweaks. If we're NB> happy with doing a release where we're planning to change some (admitedly NB> scratchpad) APIs just after, then I don't see why we can't then move to a NB> speedy release. NB> As for the freeze, once we've done this release (be it alpha or beta), we NB> can do an SVN branch for the release candidate (if we decide we want one NB> now). That can be frozen, and all bug fixes applied to it and trunk (new NB> work only to trunk). The final release can be from there. NB> I think that whatever happens, we should do a release in a few days time NB> (be it alpha or beta, based on voting). Between now and then, we should NB> decide if we want this to flow straight into a release candidate process NB> (for a -final in late December / early January), with another -final once NB> we have comments support etc, or if we want to hold off the -final until NB> we have that code in. NB> I'm not too bothered either way, but then I tend to use nightlies in NB> production :) Do other people want to weigh in? NB> Nick NB> --------------------------------------------------------------------- NB> To unsubscribe, e-mail: [EMAIL PROTECTED] NB> Mailing List: http://jakarta.apache.org/site/mail2.html#poi NB> The Apache Jakarta POI Project: http://jakarta.apache.org/poi/ --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] Mailing List: http://jakarta.apache.org/site/mail2.html#poi The Apache Jakarta POI Project: http://jakarta.apache.org/poi/