I have one thing I want to commit before we do a release but can't
realistically promise to do it in the next few days (I'm hellatired from
working till 4am every night and talking to proprietary vendors about my
lack of open sourciness). However lets start planning and I'll probably
commit it in a fit of rage during some late night caffeine binge just
before some deadline. Nick said he has the relevant signed key. anyone
else have pieces to put in? Any major show stoppers? Are we all caught
up on doubling our Line count with headers?
-Andy
Martin van den Bemt wrote:
Hi everyone,
Since we need a release to replace the 2 previous releases, I was wondering if
there are still open
issues to be resolved so that legally the release is covered.
If the current release branch (or trunk) is equally stable or more stable than
the previous release,
I would prefer cutting a release as soon as possible, so we can report that the
release is fixed and
move to the next items on the list that Andy proposed on general in December.
Mvgr,
Martin
---------------------------------------------------------------------
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/
--
No PST Files Ever Again
Buni Meldware Communication Suite
Email, Calendaring, ease of configuration/administration
http://buni.org
---------------------------------------------------------------------
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/
