To whom it may engage...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at [EMAIL PROTECTED]
Project jakarta-poi has an issue affecting its community integration.
This issue affects
To whom it may engage...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at [EMAIL PROTECTED]
Project jakarta-poi has an issue affecting its community integration.
This issue affects
On Fri, 1 Dec 2006, Rainer Klute wrote:
However, a beta should be only a step on the way to a full release. This
is something we really need to have. There are probably many users out
there who don't trust in any beta or alpha releases - not to speak about
a nighly build. They just grab the
+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
On Mon, 4 Dec 2006, Yegor Kozlov wrote:
Does the full release mean that HSLF will be moved out of the scratchpad
area?
No, that'd need another vote. I think we have some way to go before that'd
be approved (based on past discussion), in terms of functionality,
documentation, examples etc
Fine code freeze for 5 minutes. Create a branch. Tag releases from
said branch.
-Andy
Rainer Klute wrote:
Andrew C. Oliver schrieb:
-1 to any kind of code freeze that lasts more than the time it takes
to create a branch.
I can accept any -1 that eventually leads to creating a
