You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@poi.apache.org by Nick Burch <ni...@torchbox.com> on 2006/12/01 12:16:24 UTC

[VOTE] Another alpha release?

Hi All

It's now about 6 months since our last alpha release, 3.0-alpha2. There's 
been quite a bit of new functionality added to HSLF, and bug fixes to HSSF 
and HWPF. So, I think a new release is probably in order.

Asking around, it seems that people are planning some new features early 
in the new year, and a bit refactoring too (mainly in HSLF). Based on 
that, I think we should probably make this release another alpha one, then 
give serious thought to doing a beta release in Feb / March, when the new 
features are in. However, I wouldn't object to calling this one a beta, if 
people think that'd be better.


So, could people vote, and include any thoughts they might have too? The 
options are:

+1a - release as alpha
+1b - release as beta
  0  - I don't have a strong opinion either way
-1  - I don't think we should do a release now

I'm voting [+1a]. Voting will last for 1 week.

(As with all Apache release votes, the votes of everyone are taken account 
of, but only PMC members have binding votes)

Nick

---------------------------------------------------------------------
To unsubscribe, e-mail: poi-dev-unsubscribe@jakarta.apache.org
Mailing List:    http://jakarta.apache.org/site/mail2.html#poi
The Apache Jakarta POI Project: http://jakarta.apache.org/poi/


Re: [VOTE] Another alpha release?

Posted by "Andrew C. Oliver" <ac...@apache.org>.
+1 for alpha.

Nick Burch wrote:
> Hi All
>
> It's now about 6 months since our last alpha release, 3.0-alpha2. 
> There's been quite a bit of new functionality added to HSLF, and bug 
> fixes to HSSF and HWPF. So, I think a new release is probably in order.
>
> Asking around, it seems that people are planning some new features 
> early in the new year, and a bit refactoring too (mainly in HSLF). 
> Based on that, I think we should probably make this release another 
> alpha one, then give serious thought to doing a beta release in Feb / 
> March, when the new features are in. However, I wouldn't object to 
> calling this one a beta, if people think that'd be better.
>
>
> So, could people vote, and include any thoughts they might have too? 
> The options are:
>
> +1a - release as alpha
> +1b - release as beta
>  0  - I don't have a strong opinion either way
> -1  - I don't think we should do a release now
>
> I'm voting [+1a]. Voting will last for 1 week.
>
> (As with all Apache release votes, the votes of everyone are taken 
> account of, but only PMC members have binding votes)
>
> Nick
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: poi-dev-unsubscribe@jakarta.apache.org
> Mailing List:    http://jakarta.apache.org/site/mail2.html#poi
> The Apache Jakarta POI Project: http://jakarta.apache.org/poi/
>



---------------------------------------------------------------------
To unsubscribe, e-mail: poi-dev-unsubscribe@jakarta.apache.org
Mailing List:    http://jakarta.apache.org/site/mail2.html#poi
The Apache Jakarta POI Project: http://jakarta.apache.org/poi/


Re: [VOTE] Another alpha release?

Posted by Eric Ladner <er...@gmail.com>.
+1b

On 12/1/06, Nick Burch <ni...@torchbox.com> wrote:
> Hi All
>
> It's now about 6 months since our last alpha release, 3.0-alpha2. There's
> been quite a bit of new functionality added to HSLF, and bug fixes to HSSF
> and HWPF. So, I think a new release is probably in order.
>
> Asking around, it seems that people are planning some new features early
> in the new year, and a bit refactoring too (mainly in HSLF). Based on
> that, I think we should probably make this release another alpha one, then
> give serious thought to doing a beta release in Feb / March, when the new
> features are in. However, I wouldn't object to calling this one a beta, if
> people think that'd be better.
>
>
> So, could people vote, and include any thoughts they might have too? The
> options are:
>
> +1a - release as alpha
> +1b - release as beta
>   0  - I don't have a strong opinion either way
> -1  - I don't think we should do a release now
>
> I'm voting [+1a]. Voting will last for 1 week.
>
> (As with all Apache release votes, the votes of everyone are taken account
> of, but only PMC members have binding votes)
>
> Nick
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: poi-dev-unsubscribe@jakarta.apache.org
> Mailing List:    http://jakarta.apache.org/site/mail2.html#poi
> The Apache Jakarta POI Project: http://jakarta.apache.org/poi/
>
>


-- 
Eric Ladner

---------------------------------------------------------------------
To unsubscribe, e-mail: poi-dev-unsubscribe@jakarta.apache.org
Mailing List:    http://jakarta.apache.org/site/mail2.html#poi
The Apache Jakarta POI Project: http://jakarta.apache.org/poi/


Re: [VOTE] Another alpha release?

Posted by Broadus Jones <bj...@tiv.com>.
+1b

Broadus Jones


On 12/1/2006 5:16 AM, Nick Burch wrote:
> Hi All
>
> It's now about 6 months since our last alpha release, 3.0-alpha2. 
> There's been quite a bit of new functionality added to HSLF, and bug 
> fixes to HSSF and HWPF. So, I think a new release is probably in order.
>
> Asking around, it seems that people are planning some new features 
> early in the new year, and a bit refactoring too (mainly in HSLF). 
> Based on that, I think we should probably make this release another 
> alpha one, then give serious thought to doing a beta release in Feb / 
> March, when the new features are in. However, I wouldn't object to 
> calling this one a beta, if people think that'd be better.
>
>
> So, could people vote, and include any thoughts they might have too? 
> The options are:
>
> +1a - release as alpha
> +1b - release as beta
>  0  - I don't have a strong opinion either way
> -1  - I don't think we should do a release now
>
> I'm voting [+1a]. Voting will last for 1 week.
>
> (As with all Apache release votes, the votes of everyone are taken 
> account of, but only PMC members have binding votes)
>
> Nick

Re[2]: [VOTE] Another alpha release?

Posted by Nick Burch <ni...@torchbox.com>.
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

Nick

---------------------------------------------------------------------
To unsubscribe, e-mail: poi-dev-unsubscribe@jakarta.apache.org
Mailing List:    http://jakarta.apache.org/site/mail2.html#poi
The Apache Jakarta POI Project: http://jakarta.apache.org/poi/


Re[2]: [VOTE] Another alpha release?

Posted by Yegor Kozlov <ye...@dinom.ru>.
+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: poi-dev-unsubscribe@jakarta.apache.org
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: poi-dev-unsubscribe@jakarta.apache.org
Mailing List:    http://jakarta.apache.org/site/mail2.html#poi
The Apache Jakarta POI Project: http://jakarta.apache.org/poi/


Re: [VOTE] Another alpha release?

Posted by Nick Burch <ni...@torchbox.com>.
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 latest full release and use that. How 
> many years have passed since we release it? We really need one!

I think the question should be:

* should we do a release now, freeze, work to a release now, release with
    some HSLF apis that are about to change, without excel comment support
    etc, then do another release in the new year once we have that code?

or

* alpha/beta now, beta when we've got the HSLF api tweaks + excel comment
    support in the new year, then freeze and release then?

My main reason for suggesting an alpha was the HSLF api tweaks. If we're 
happy with doing a release where we're planning to change some (admitedly
scratchpad) APIs just after, then I don't see why we can't then move to a 
speedy release.

As for the freeze, once we've done this release (be it alpha or beta), we 
can do an SVN branch for the release candidate (if we decide we want one 
now). That can be frozen, and all bug fixes applied to it and trunk (new 
work only to trunk). The final release can be from there.


I think that whatever happens, we should do a release in a few days time 
(be it alpha or beta, based on voting). Between now and then, we should 
decide if we want this to flow straight into a release candidate process 
(for a -final in late December / early January), with another -final once 
we have comments support etc, or if we want to hold off the -final until 
we have that code in.

I'm not too bothered either way, but then I tend to use nightlies in 
production :)  Do other people want to weigh in?

Nick

---------------------------------------------------------------------
To unsubscribe, e-mail: poi-dev-unsubscribe@jakarta.apache.org
Mailing List:    http://jakarta.apache.org/site/mail2.html#poi
The Apache Jakarta POI Project: http://jakarta.apache.org/poi/


Re: [VOTE] Another alpha release?

Posted by David Fisher <df...@jmlafferty.com>.
My concern with a release cycle NOW is that there has been no warning  
giving contributers a chance to finish.

I think that two cycles a year is appropriate. If that schedule is  
followed then these dates should be published. Having regular,  
predictable release dates and then following them will increase POI's  
reputation and acceptance.

Sounds to me like a slightly different vote than Nick's.

Regards,
Dave

On Dec 1, 2006, at 2:40 PM, Rainer Klute wrote:

> David Fisher schrieb:
>> Sounds like a description of a release cycle to me.
>
> Yep.
>
>
>> Before a code freeze is called you should ask about planned
>> contributions and decide if they should be included and set a
>> reasonable plan for a contribution deadline.
>>
>> Keep in mind that contributions are made by people who are working on
>> commercial projects with real deadlines and are made at times that  
>> are
>> "convenient" to those times. ALL of Yegor Kozlov's recent
>> contributions fit this category.
>>
>> So, if the decision becomes have a code freeze then I very much hope
>> that it is no earlier than January 15th.
>
> This is all quite right, but I'd rather like to make a code freeze  
> NOW,
> make sure there aren't any show stoppers, quickly roll out the release
> and then continue development. There are always plans for new features
> that should go into the software. And yes, they really should and  
> will.
> However, it has been years since the last release! I prefer to have
> releases much more often, say, twice a year or so.
>
> Best regards
> Rainer Klute
>
>                            Rainer Klute IT-Consulting GmbH
>   Dipl.-Inform.
>   Rainer Klute             E-Mail:  klute@rainer-klute.de
>   Körner Grund 24          Telefon: +49 172 2324824
> D-44143 Dortmund           Telefax: +49 231 5349423
>
> OpenPGP fingerprint: E4E4386515EE0BED5C162FBB5343461584B5A42E
>
>


---------------------------------------------------------------------
To unsubscribe, e-mail: poi-dev-unsubscribe@jakarta.apache.org
Mailing List:    http://jakarta.apache.org/site/mail2.html#poi
The Apache Jakarta POI Project: http://jakarta.apache.org/poi/


Re: [VOTE] Another alpha release?

Posted by "Andrew C. Oliver" <ac...@apache.org>.
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 release.
> However, through the last years (!) that hasn't been possible. So please
> don't just -1 my proposal, but make a better one.
>
> Best regards
> Rainer Klute
>
>                            Rainer Klute IT-Consulting GmbH
>   Dipl.-Inform.
>   Rainer Klute             E-Mail:  klute@rainer-klute.de
>   Körner Grund 24          Telefon: +49 172 2324824
> D-44143 Dortmund           Telefax: +49 231 5349423
>
> OpenPGP fingerprint: E4E4386515EE0BED5C162FBB5343461584B5A42E
>
>
>   



---------------------------------------------------------------------
To unsubscribe, e-mail: poi-dev-unsubscribe@jakarta.apache.org
Mailing List:    http://jakarta.apache.org/site/mail2.html#poi
The Apache Jakarta POI Project: http://jakarta.apache.org/poi/


Re: [VOTE] Another alpha release?

Posted by Rainer Klute <kl...@rainer-klute.de>.
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 release.
However, through the last years (!) that hasn't been possible. So please
don't just -1 my proposal, but make a better one.

Best regards
Rainer Klute

                           Rainer Klute IT-Consulting GmbH
  Dipl.-Inform.
  Rainer Klute             E-Mail:  klute@rainer-klute.de
  Körner Grund 24          Telefon: +49 172 2324824
D-44143 Dortmund           Telefax: +49 231 5349423

OpenPGP fingerprint: E4E4386515EE0BED5C162FBB5343461584B5A42E



Re: [VOTE] Another alpha release?

Posted by "Andrew C. Oliver" <ac...@apache.org>.
-1 to any kind of code freeze that lasts more than the time it takes to 
create a branch.

Rainer Klute wrote:
> David Fisher schrieb:
>   
>> Sounds like a description of a release cycle to me.
>>     
>
> Yep.
>
>
>   
>> Before a code freeze is called you should ask about planned
>> contributions and decide if they should be included and set a
>> reasonable plan for a contribution deadline.
>>
>> Keep in mind that contributions are made by people who are working on
>> commercial projects with real deadlines and are made at times that are
>> "convenient" to those times. ALL of Yegor Kozlov's recent
>> contributions fit this category.
>>
>> So, if the decision becomes have a code freeze then I very much hope
>> that it is no earlier than January 15th.
>>     
>
> This is all quite right, but I'd rather like to make a code freeze NOW,
> make sure there aren't any show stoppers, quickly roll out the release
> and then continue development. There are always plans for new features
> that should go into the software. And yes, they really should and will.
> However, it has been years since the last release! I prefer to have
> releases much more often, say, twice a year or so.
>
> Best regards
> Rainer Klute
>
>                            Rainer Klute IT-Consulting GmbH
>   Dipl.-Inform.
>   Rainer Klute             E-Mail:  klute@rainer-klute.de
>   Körner Grund 24          Telefon: +49 172 2324824
> D-44143 Dortmund           Telefax: +49 231 5349423
>
> OpenPGP fingerprint: E4E4386515EE0BED5C162FBB5343461584B5A42E
>
>
>   



---------------------------------------------------------------------
To unsubscribe, e-mail: poi-dev-unsubscribe@jakarta.apache.org
Mailing List:    http://jakarta.apache.org/site/mail2.html#poi
The Apache Jakarta POI Project: http://jakarta.apache.org/poi/


Re: [VOTE] Another alpha release?

Posted by Rainer Klute <kl...@rainer-klute.de>.
David Fisher schrieb:
> Sounds like a description of a release cycle to me.

Yep.


> Before a code freeze is called you should ask about planned
> contributions and decide if they should be included and set a
> reasonable plan for a contribution deadline.
>
> Keep in mind that contributions are made by people who are working on
> commercial projects with real deadlines and are made at times that are
> "convenient" to those times. ALL of Yegor Kozlov's recent
> contributions fit this category.
>
> So, if the decision becomes have a code freeze then I very much hope
> that it is no earlier than January 15th.

This is all quite right, but I'd rather like to make a code freeze NOW,
make sure there aren't any show stoppers, quickly roll out the release
and then continue development. There are always plans for new features
that should go into the software. And yes, they really should and will.
However, it has been years since the last release! I prefer to have
releases much more often, say, twice a year or so.

Best regards
Rainer Klute

                           Rainer Klute IT-Consulting GmbH
  Dipl.-Inform.
  Rainer Klute             E-Mail:  klute@rainer-klute.de
  Körner Grund 24          Telefon: +49 172 2324824
D-44143 Dortmund           Telefax: +49 231 5349423

OpenPGP fingerprint: E4E4386515EE0BED5C162FBB5343461584B5A42E



Re: [VOTE] Another alpha release?

Posted by David Fisher <df...@jmlafferty.com>.
Sounds like a description of a release cycle to me.

Before a code freeze is called you should ask about planned  
contributions and decide if they should be included and set a  
reasonable plan for a contribution deadline.

Keep in mind that contributions are made by people who are working on  
commercial projects with real deadlines and are made at times that  
are "convenient" to those times. ALL of Yegor Kozlov's recent  
contributions fit this category.

So, if the decision becomes have a code freeze then I very much hope  
that it is no earlier than January 15th.

Thanks everyone. And, yes I understand that some people won't use  
beta libraries.

Regards,
Dave Fisher

On Dec 1, 2006, at 1:37 PM, Cheenu wrote:

> Well put Rainer.
>
> Can we please get a full release in the near future - pleease!
>
> On 12/1/06, Rainer Klute <kl...@rainer-klute.de> wrote:
>>
>> +1b
>>
>> 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 latest full release and use  
>> that. How
>> many years have passed since we release it? We really need one!
>>
>> Therefore I suggest to
>>
>>    1. release the beta,
>>    2. make a code freeze where only bugs are fixed,
>>    3. make one or more (if needed) release candidates with bug fixing
>>       cycles, and
>>    4. make a full release.
>>    5. Only after that submit new code.
>>
>>
>> Best regards
>>
>> Rainer Klute
>>
>>                            Rainer Klute IT-Consulting GmbH
>>   Dipl.-Inform.
>>   Rainer Klute             E-Mail:  klute@rainer-klute.de
>>   Körner Grund 24          Telefon: +49 172 2324824
>> D-44143 Dortmund           Telefax: +49 231 5349423
>>
>>   http://www.glaube24.de/
>>
>> OpenPGP-Fingerprint: E4E4386515EE0BED5C162FBB5343461584B5A42E
>>
>>
>>
>>
>>


---------------------------------------------------------------------
To unsubscribe, e-mail: poi-dev-unsubscribe@jakarta.apache.org
Mailing List:    http://jakarta.apache.org/site/mail2.html#poi
The Apache Jakarta POI Project: http://jakarta.apache.org/poi/


Re: [VOTE] Another alpha release?

Posted by Cheenu <ch...@users.sourceforge.net>.
Well put Rainer.

Can we please get a full release in the near future - pleease!

On 12/1/06, Rainer Klute <kl...@rainer-klute.de> wrote:
>
> +1b
>
> 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 latest full release and use that. How
> many years have passed since we release it? We really need one!
>
> Therefore I suggest to
>
>    1. release the beta,
>    2. make a code freeze where only bugs are fixed,
>    3. make one or more (if needed) release candidates with bug fixing
>       cycles, and
>    4. make a full release.
>    5. Only after that submit new code.
>
>
> Best regards
>
> Rainer Klute
>
>                            Rainer Klute IT-Consulting GmbH
>   Dipl.-Inform.
>   Rainer Klute             E-Mail:  klute@rainer-klute.de
>   Körner Grund 24          Telefon: +49 172 2324824
> D-44143 Dortmund           Telefax: +49 231 5349423
>
>   http://www.glaube24.de/
>
> OpenPGP-Fingerprint: E4E4386515EE0BED5C162FBB5343461584B5A42E
>
>
>
>
>

Re: [VOTE] Another alpha release?

Posted by Rainer Klute <kl...@rainer-klute.de>.
+1b

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 latest full release and use that. How
many years have passed since we release it? We really need one!

Therefore I suggest to

   1. release the beta,
   2. make a code freeze where only bugs are fixed,
   3. make one or more (if needed) release candidates with bug fixing
      cycles, and
   4. make a full release.
   5. Only after that submit new code.


Best regards

Rainer Klute

                           Rainer Klute IT-Consulting GmbH
  Dipl.-Inform.
  Rainer Klute             E-Mail:  klute@rainer-klute.de
  Körner Grund 24          Telefon: +49 172 2324824
D-44143 Dortmund           Telefax: +49 231 5349423

  http://www.glaube24.de/

OpenPGP-Fingerprint: E4E4386515EE0BED5C162FBB5343461584B5A42E



Re: [VOTE] Another alpha release?

Posted by Henri Yandell <fl...@gmail.com>.
Plus there's been a release already. alpha-3 in:

http://people.apache.org/repo/m1-ibiblio-rsync-repository/poi/jars/

I suspect that the alpha-2 release was dodgy too.

Hen

On 12/14/06, Martin van den Bemt <ml...@mvdb.net> wrote:
> Hi everyone,
>
> I miss a couple of things here :
> 1) A VOTE RESULT (with cc to private@jakarta.apache.org) which contains an overview who voted and
> who has binding votes.
> 2) The ability to check the release before it was released (to see all is in place the way it should)
> - To increase visibility a release, you can also send a mail to  announcements@jakarta.apache.org
>
> Although I will not moderate through 3 until 1 has happened and I had time for 2.
>
> If you need any help, let me know.
>
> Mvgr,
> Martin
>
> Nick Burch wrote:
> > Hi All
> >
> > It's now about 6 months since our last alpha release, 3.0-alpha2.
> > There's been quite a bit of new functionality added to HSLF, and bug
> > fixes to HSSF and HWPF. So, I think a new release is probably in order.
> >
> > Asking around, it seems that people are planning some new features early
> > in the new year, and a bit refactoring too (mainly in HSLF). Based on
> > that, I think we should probably make this release another alpha one,
> > then give serious thought to doing a beta release in Feb / March, when
> > the new features are in. However, I wouldn't object to calling this one
> > a beta, if people think that'd be better.
> >
> >
> > So, could people vote, and include any thoughts they might have too? The
> > options are:
> >
> > +1a - release as alpha
> > +1b - release as beta
> >  0  - I don't have a strong opinion either way
> > -1  - I don't think we should do a release now
> >
> > I'm voting [+1a]. Voting will last for 1 week.
> >
> > (As with all Apache release votes, the votes of everyone are taken
> > account of, but only PMC members have binding votes)
> >
> > Nick
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: poi-dev-unsubscribe@jakarta.apache.org
> > Mailing List:    http://jakarta.apache.org/site/mail2.html#poi
> > The Apache Jakarta POI Project: http://jakarta.apache.org/poi/
> >
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: poi-dev-unsubscribe@jakarta.apache.org
> Mailing List:    http://jakarta.apache.org/site/mail2.html#poi
> The Apache Jakarta POI Project: http://jakarta.apache.org/poi/
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: poi-dev-unsubscribe@jakarta.apache.org
Mailing List:    http://jakarta.apache.org/site/mail2.html#poi
The Apache Jakarta POI Project: http://jakarta.apache.org/poi/


Re: [VOTE] Another alpha release?

Posted by Martin van den Bemt <ml...@mvdb.net>.
Hi everyone,

I miss a couple of things here :
1) A VOTE RESULT (with cc to private@jakarta.apache.org) which contains an overview who voted and
who has binding votes.
2) The ability to check the release before it was released (to see all is in place the way it should)
- To increase visibility a release, you can also send a mail to  announcements@jakarta.apache.org

Although I will not moderate through 3 until 1 has happened and I had time for 2.

If you need any help, let me know.

Mvgr,
Martin

Nick Burch wrote:
> Hi All
> 
> It's now about 6 months since our last alpha release, 3.0-alpha2.
> There's been quite a bit of new functionality added to HSLF, and bug
> fixes to HSSF and HWPF. So, I think a new release is probably in order.
> 
> Asking around, it seems that people are planning some new features early
> in the new year, and a bit refactoring too (mainly in HSLF). Based on
> that, I think we should probably make this release another alpha one,
> then give serious thought to doing a beta release in Feb / March, when
> the new features are in. However, I wouldn't object to calling this one
> a beta, if people think that'd be better.
> 
> 
> So, could people vote, and include any thoughts they might have too? The
> options are:
> 
> +1a - release as alpha
> +1b - release as beta
>  0  - I don't have a strong opinion either way
> -1  - I don't think we should do a release now
> 
> I'm voting [+1a]. Voting will last for 1 week.
> 
> (As with all Apache release votes, the votes of everyone are taken
> account of, but only PMC members have binding votes)
> 
> Nick
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: poi-dev-unsubscribe@jakarta.apache.org
> Mailing List:    http://jakarta.apache.org/site/mail2.html#poi
> The Apache Jakarta POI Project: http://jakarta.apache.org/poi/
> 
> 
> 

---------------------------------------------------------------------
To unsubscribe, e-mail: poi-dev-unsubscribe@jakarta.apache.org
Mailing List:    http://jakarta.apache.org/site/mail2.html#poi
The Apache Jakarta POI Project: http://jakarta.apache.org/poi/


Re: [VOTE] Another alpha release?

Posted by Sean Sullivan <se...@seansullivan.com>.
+1a

Nick Burch wrote:
> Hi All
>
> It's now about 6 months since our last alpha release, 3.0-alpha2.
> There's been quite a bit of new functionality added to HSLF, and bug
> fixes to HSSF and HWPF. So, I think a new release is probably in order.
>
> Asking around, it seems that people are planning some new features
> early in the new year, and a bit refactoring too (mainly in HSLF).
> Based on that, I think we should probably make this release another
> alpha one, then give serious thought to doing a beta release in Feb /
> March, when the new features are in. However, I wouldn't object to
> calling this one a beta, if people think that'd be better.
>
>
> So, could people vote, and include any thoughts they might have too?
> The options are:
>
> +1a - release as alpha
> +1b - release as beta
>  0  - I don't have a strong opinion either way
> -1  - I don't think we should do a release now
>
> I'm voting [+1a]. Voting will last for 1 week.
>
> (As with all Apache release votes, the votes of everyone are taken
> account of, but only PMC members have binding votes)
>
> Nick
>

---------------------------------------------------------------------
To unsubscribe, e-mail: poi-dev-unsubscribe@jakarta.apache.org
Mailing List:    http://jakarta.apache.org/site/mail2.html#poi
The Apache Jakarta POI Project: http://jakarta.apache.org/poi/


Re: [VOTE] Another alpha release?

Posted by David Fisher <df...@jmlafferty.com>.
Thanks Nick.

I vote a non-binding +1a.

I want to see a beta have Yegor's full style enhancements to HSLF and  
cell comments in HSSF. The community seems to want these and I know  
they are within reach.

Regards,
Dave Fisher
PS. I'm Yegor's "project manager"

On Dec 1, 2006, at 5:16 AM, Nick Burch wrote:

> Hi All
>
> It's now about 6 months since our last alpha release, 3.0-alpha2.  
> There's been quite a bit of new functionality added to HSLF, and  
> bug fixes to HSSF and HWPF. So, I think a new release is probably  
> in order.
>
> Asking around, it seems that people are planning some new features  
> early in the new year, and a bit refactoring too (mainly in HSLF).  
> Based on that, I think we should probably make this release another  
> alpha one, then give serious thought to doing a beta release in  
> Feb / March, when the new features are in. However, I wouldn't  
> object to calling this one a beta, if people think that'd be better.
>
>
> So, could people vote, and include any thoughts they might have  
> too? The options are:
>
> +1a - release as alpha
> +1b - release as beta
>  0  - I don't have a strong opinion either way
> -1  - I don't think we should do a release now
>
> I'm voting [+1a]. Voting will last for 1 week.
>
> (As with all Apache release votes, the votes of everyone are taken  
> account of, but only PMC members have binding votes)
>
> Nick
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: poi-dev-unsubscribe@jakarta.apache.org
> Mailing List:    http://jakarta.apache.org/site/mail2.html#poi
> The Apache Jakarta POI Project: http://jakarta.apache.org/poi/
>
>


---------------------------------------------------------------------
To unsubscribe, e-mail: poi-dev-unsubscribe@jakarta.apache.org
Mailing List:    http://jakarta.apache.org/site/mail2.html#poi
The Apache Jakarta POI Project: http://jakarta.apache.org/poi/


Re: [VOTE] Another alpha release?

Posted by Avik Sengupta <av...@itellix.com>.
+1a

Quoting Amol Deshmukh <am...@yahoo.com>:

> +1a
>
> ~ amol
>
> --- Nick Burch <ni...@torchbox.com> wrote:
>
>> Hi All
>>
>> It's now about 6 months since our last alpha
>> release, 3.0-alpha2. There's
>> been quite a bit of new functionality added to HSLF,
>> and bug fixes to HSSF
>> and HWPF. So, I think a new release is probably in
>> order.
>>
>> Asking around, it seems that people are planning
>> some new features early
>> in the new year, and a bit refactoring too (mainly
>> in HSLF). Based on
>> that, I think we should probably make this release
>> another alpha one, then
>> give serious thought to doing a beta release in Feb
>> / March, when the new
>> features are in. However, I wouldn't object to
>> calling this one a beta, if
>> people think that'd be better.
>>
>>
>> So, could people vote, and include any thoughts they
>> might have too? The
>> options are:
>>
>> +1a - release as alpha
>> +1b - release as beta
>>   0  - I don't have a strong opinion either way
>> -1  - I don't think we should do a release now
>>
>> I'm voting [+1a]. Voting will last for 1 week.
>>
>> (As with all Apache release votes, the votes of
>> everyone are taken account
>> of, but only PMC members have binding votes)
>>
>> Nick
>>
>>
> ---------------------------------------------------------------------
>> To unsubscribe, e-mail:
>> poi-dev-unsubscribe@jakarta.apache.org
>> Mailing List:
>> http://jakarta.apache.org/site/mail2.html#poi
>> The Apache Jakarta POI Project:
>> http://jakarta.apache.org/poi/
>>
>>
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: poi-dev-unsubscribe@jakarta.apache.org
> Mailing List:    http://jakarta.apache.org/site/mail2.html#poi
> The Apache Jakarta POI Project: http://jakarta.apache.org/poi/
>
>



----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.


---------------------------------------------------------------------
To unsubscribe, e-mail: poi-dev-unsubscribe@jakarta.apache.org
Mailing List:    http://jakarta.apache.org/site/mail2.html#poi
The Apache Jakarta POI Project: http://jakarta.apache.org/poi/


Re: [VOTE] Another alpha release?

Posted by Amol Deshmukh <am...@yahoo.com>.
+1a

~ amol

--- Nick Burch <ni...@torchbox.com> wrote:

> Hi All
> 
> It's now about 6 months since our last alpha
> release, 3.0-alpha2. There's 
> been quite a bit of new functionality added to HSLF,
> and bug fixes to HSSF 
> and HWPF. So, I think a new release is probably in
> order.
> 
> Asking around, it seems that people are planning
> some new features early 
> in the new year, and a bit refactoring too (mainly
> in HSLF). Based on 
> that, I think we should probably make this release
> another alpha one, then 
> give serious thought to doing a beta release in Feb
> / March, when the new 
> features are in. However, I wouldn't object to
> calling this one a beta, if 
> people think that'd be better.
> 
> 
> So, could people vote, and include any thoughts they
> might have too? The 
> options are:
> 
> +1a - release as alpha
> +1b - release as beta
>   0  - I don't have a strong opinion either way
> -1  - I don't think we should do a release now
> 
> I'm voting [+1a]. Voting will last for 1 week.
> 
> (As with all Apache release votes, the votes of
> everyone are taken account 
> of, but only PMC members have binding votes)
> 
> Nick
> 
>
---------------------------------------------------------------------
> To unsubscribe, e-mail:
> poi-dev-unsubscribe@jakarta.apache.org
> Mailing List:   
> http://jakarta.apache.org/site/mail2.html#poi
> The Apache Jakarta POI Project:
> http://jakarta.apache.org/poi/
> 
> 




---------------------------------------------------------------------
To unsubscribe, e-mail: poi-dev-unsubscribe@jakarta.apache.org
Mailing List:    http://jakarta.apache.org/site/mail2.html#poi
The Apache Jakarta POI Project: http://jakarta.apache.org/poi/