[Poll] Next release?

[Dain Sundstrom <da...@iq80.com>]

In an attempt to quantify our expectation about the next release from  
trunk, please rank the following items in importance to you:

[ ] Release Date
[ ] Feature Set
[ ] Release Name
[ ] Certification

Re: [Poll] Next release?

[Gianny Damour <gi...@optusnet.com.au>]

On 09/09/2006, at 11:55 AM, Dain Sundstrom wrote:

> In an attempt to quantify our expectation about the next release  
> from trunk, please rank the following items in importance to you:
>
> [ 2] Release Date
> [ 1] Feature Set
> [ 4] Release Name
> [ 3] Certification
>

It seems that the baton on Release Manager has already been handed  
off :)

Thanks,
Gianny

Re: [Poll] Next release?

[Matt Hogstrom <ma...@hogstrom.org>]

First off Dain, thanks for pulling all the info together.  I didn't realize how much stuff was in 
trunk right now.  Now, to the topic at hand.

Dain Sundstrom wrote:
> In an attempt to quantify our expectation about the next release from 
> trunk, please rank the following items in importance to you:
> 
> [2] Release Date
> [1] Feature Set
> [3] Release Name
> [2] Certification
> 
> 
> 
> 
> 

I'm not sure how to rank certification.  I think its important to have a certified release on the 
actual release date.  I expect its not as critical for interim releases.  I think I'm still using 
Maven-1.1-beta-2 :)

-- 


Matt Hogstrom

Re: [Poll] Next release?

[Jacek Laskowski <ja...@laskowski.net.pl>]

On 9/9/06, Dain Sundstrom <da...@iq80.com> wrote:

> [1] Release Date
> [2] Feature Set
> [3] Release Name
> [ALWAYS] Certification

where:

- Release Date (RD): It's the first item for it sets a final date so
people can add new features and fixes. The very first though was to
put Feature Set (FS) as the first, but then realized that having FS
without RD would not be beneficial.

- Release Notes can't be 5 until Geronimo doesn't support JEE 5 fully
(it should be easy to achieve, though ;-))

- Certifiaction is always a must - I'd vote against a release if it's
not j2ee 1.4 (or jee 5) certified.

Jacek

-- 
Jacek Laskowski
http://www.laskowski.net.pl

Re: [Poll] Next release?

[Hernan Cunico <hc...@gmail.com>]

I'm gonna cheat a bit as I think that both release date and feature set 
are equally important and one affects the other. Certification however 
is a strong "1"

What do you mean by release name, _numbering_ ?


[2] Release Date
[2] Feature Set
[3] Release Name
[1] Certification

Cheers!
Hernan

Dain Sundstrom wrote:
> In an attempt to quantify our expectation about the next release from 
> trunk, please rank the following items in importance to you:
> 
> [ ] Release Date
> [ ] Feature Set
> [ ] Release Name
> [ ] Certification
> 
> 
> 

Re: [Poll] Next release?

[Kevan Miller <ke...@gmail.com>]

On Sep 8, 2006, at 9:55 PM, Dain Sundstrom wrote:

> In an attempt to quantify our expectation about the next release  
> from trunk, please rank the following items in importance to you:
>
> [3 ] Release Date
> [2 ] Feature Set
> [4 ] Release Name
> [1] Certification

I don't view certification of a "release" as optional. I'd be  
hesitant to deliver a non-certified milestone...

I do think that working to get trunk up to "releasable" standards is  
a good thing. We're going to need to do that regardless... BTW, part  
of this work should include the new Apache source header and  
copyright notice policy -- http://www.apache.org/legal/src-headers.html.

Would be great to have an automated test for checking source headers,  
LICENSE, and NOTICE files. Would hopefully avoid some of those last  
minute release vote respins...

--kevan

Re: [Poll] Next release?

[David Blevins <da...@visi.com>]

On Sep 19, 2006, at 5:07 PM, David Jencks wrote:

> Oops, I missed replying.
>
> For me,
>
> 1- cert
> 2- release date
> 3- feature set
> 4- name
>
> I could probably be talked out of the release date priority if we  
> are producing weekly certifiable builds and our build/tck process  
> is working really smoothly.
>
> I'm really really really worried about the amount of development on  
> trunk that has not had the tck run against it.

That pretty much echos my thoughts exactly.

-David


> thanks
> david jencks
>
> On Sep 19, 2006, at 4:58 PM, Dain Sundstrom wrote:
>
>> I only got a few responses, but we the results were almost unanimous
>> so I'm going to take this as a sign that most people agree with what
>> was already posted.  If you do disagree with the poll results, please
>> speak up.
>>
>> RESULTS:
>>
>> [1] Certification
>> [2] Feature Set
>> [3] Release Date
>> [4] Release Name
>>
>> Certification is a requirement and timeline will be pushed to achieve
>> a desired feature set and no one seems to care what the release are
>> named :)
>>
>>
>> Based on this feed back, I will start another thread where we can
>> discuss the feature requirements for the next release.  Again if you
>> disagree, please jump in now.
>>
>> Thanks for the feed back,
>>
>> -dain
>>
>> On 9/8/06, Dain Sundstrom <da...@iq80.com> wrote:
>>> In an attempt to quantify our expectation about the next release  
>>> from
>>> trunk, please rank the following items in importance to you:
>>>
>>> [ ] Release Date
>>> [ ] Feature Set
>>> [ ] Release Name
>>> [ ] Certification
>>>
>>>
>>>
>

Re: [Poll] Next release?

[David Jencks <da...@yahoo.com>]

Oops, I missed replying.

For me,

1- cert
2- release date
3- feature set
4- name

I could probably be talked out of the release date priority if we are  
producing weekly certifiable builds and our build/tck process is  
working really smoothly.

I'm really really really worried about the amount of development on  
trunk that has not had the tck run against it.

thanks
david jencks

On Sep 19, 2006, at 4:58 PM, Dain Sundstrom wrote:

> I only got a few responses, but we the results were almost unanimous
> so I'm going to take this as a sign that most people agree with what
> was already posted.  If you do disagree with the poll results, please
> speak up.
>
> RESULTS:
>
> [1] Certification
> [2] Feature Set
> [3] Release Date
> [4] Release Name
>
> Certification is a requirement and timeline will be pushed to achieve
> a desired feature set and no one seems to care what the release are
> named :)
>
>
> Based on this feed back, I will start another thread where we can
> discuss the feature requirements for the next release.  Again if you
> disagree, please jump in now.
>
> Thanks for the feed back,
>
> -dain
>
> On 9/8/06, Dain Sundstrom <da...@iq80.com> wrote:
>> In an attempt to quantify our expectation about the next release from
>> trunk, please rank the following items in importance to you:
>>
>> [ ] Release Date
>> [ ] Feature Set
>> [ ] Release Name
>> [ ] Certification
>>
>>
>>

Re: [Poll] Next release?

[Dain Sundstrom <ds...@gmail.com>]

I only got a few responses, but we the results were almost unanimous
so I'm going to take this as a sign that most people agree with what
was already posted.  If you do disagree with the poll results, please
speak up.

RESULTS:

[1] Certification
[2] Feature Set
[3] Release Date
[4] Release Name

Certification is a requirement and timeline will be pushed to achieve
a desired feature set and no one seems to care what the release are
named :)


Based on this feed back, I will start another thread where we can
discuss the feature requirements for the next release.  Again if you
disagree, please jump in now.

Thanks for the feed back,

-dain

On 9/8/06, Dain Sundstrom <da...@iq80.com> wrote:
> In an attempt to quantify our expectation about the next release from
> trunk, please rank the following items in importance to you:
>
> [ ] Release Date
> [ ] Feature Set
> [ ] Release Name
> [ ] Certification
>
>
>

Re: [Poll] Next release?

[Joe Bohn <jo...@earthlink.net>]

Dain Sundstrom wrote:
> In an attempt to quantify our expectation about the next release from  
> trunk, please rank the following items in importance to you:
> 
> [3] Release Date
> [2] Feature Set
> [4] Release Name
> [1] Certification
> 

I agree with Kevan that we can't ship a release now that isn't certified 
so that isn't optional).  I ranked these with that in mind.  In other 
words, I expect that we would remove/add function and possibly 
compromise the date in order to ship a certified release.

Second to that I think we need to focus on what we need to be 
competitive with a close second (3rd over all) on the date.  Function 
vs. date is always trade off depending upon the urgency of one or the 
other with regard to our competitors.  Finally, "what's in a name".

Joe