[VOTE] Create Release Branch 2009.04

[David E Jones-3]

Today is the day we have discussed for a while! A lot of improvements  
and fixes have gone in over the last few weeks, but it is important to  
remember that the release branch is primarily time-based and is a  
"line in the sand" as it were to begin the effort of stabilizing a  
specific code base so that end-users who want stability over features  
have that option. Some things make it in, and other things don't make  
it, and that is true no matter when we draw the line (but we don't  
want to delay it forever). What we have in place it a HUGE improvement  
over the release4.0 branch, and that is the most important point to  
keep in mind.

Along with that there is a planned press release coordinated with the  
Apache Software Foundation Public Relations Committee (that's a  
mouthful! no wonder we use acronyms like: ASF PRC) for tomorrow  
morning (Wed 15 April).

That said, the target date/time for the release branch is later  
tonight (and when I say tonight I mean according to USA time, just to  
clarify). To follow the date pattern we have discussed and make it  
clearly a date I'm thinking of the actual name for the branch  
directory to be "release200904" (and please feel free to comment on  
that if you think something else is better).

However, that I will only do that IFF we have a positive vote for the  
release, hence this message!

Please vote:

[+1] Create the release branch tonight, April 14th (it will be April  
15th for GMT-0)
[+0] Abstain
[-1] Do not create the release branch tonight

Please remember that everyone is free to (and encouraged to!) vote,  
but only the PMC votes are binding.

Thanks to everyone who has made this possible with amazing  
contributions over the last 2 years, and a heightened activity in  
recent weeks and months to make this a spectacular release.

-David

[Adrian Crum]

+1

-Adrian

David E Jones wrote:

>
> Today is the day we have discussed for a while! A lot of improvements
> and fixes have gone in over the last few weeks, but it is important to
> remember that the release branch is primarily time-based and is a "line
> in the sand" as it were to begin the effort of stabilizing a specific
> code base so that end-users who want stability over features have that
> option. Some things make it in, and other things don't make it, and that
> is true no matter when we draw the line (but we don't want to delay it
> forever). What we have in place it a HUGE improvement over the
> release4.0 branch, and that is the most important point to keep in mind.
>
> Along with that there is a planned press release coordinated with the
> Apache Software Foundation Public Relations Committee (that's a
> mouthful! no wonder we use acronyms like: ASF PRC) for tomorrow morning
> (Wed 15 April).
>
> That said, the target date/time for the release branch is later tonight
> (and when I say tonight I mean according to USA time, just to clarify).
> To follow the date pattern we have discussed and make it clearly a date
> I'm thinking of the actual name for the branch directory to be
> "release200904" (and please feel free to comment on that if you think
> something else is better).
>
> However, that I will only do that IFF we have a positive vote for the
> release, hence this message!
>
> Please vote:
>
> [+1] Create the release branch tonight, April 14th (it will be April
> 15th for GMT-0)
> [+0] Abstain
> [-1] Do not create the release branch tonight
>
> Please remember that everyone is free to (and encouraged to!) vote, but
> only the PMC votes are binding.
>
> Thanks to everyone who has made this possible with amazing contributions
> over the last 2 years, and a heightened activity in recent weeks and
> months to make this a spectacular release.
>
> -David
>
>

[hans_bakker]

David , to start a vote and give the opportunity to vote in 6-12 hours
is rather short....

I would favor a week delay and release next week, still april and still
9.04 also like sally suggests.

regards,
Hans

On Tue, 2009-04-14 at 15:14 -0600, David E Jones wrote:

> Today is the day we have discussed for a while! A lot of improvements  
> and fixes have gone in over the last few weeks, but it is important to  
> remember that the release branch is primarily time-based and is a  
> "line in the sand" as it were to begin the effort of stabilizing a  
> specific code base so that end-users who want stability over features  
> have that option. Some things make it in, and other things don't make  
> it, and that is true no matter when we draw the line (but we don't  
> want to delay it forever). What we have in place it a HUGE improvement  
> over the release4.0 branch, and that is the most important point to  
> keep in mind.
>
> Along with that there is a planned press release coordinated with the  
> Apache Software Foundation Public Relations Committee (that's a  
> mouthful! no wonder we use acronyms like: ASF PRC) for tomorrow  
> morning (Wed 15 April).
>
> That said, the target date/time for the release branch is later  
> tonight (and when I say tonight I mean according to USA time, just to  
> clarify). To follow the date pattern we have discussed and make it  
> clearly a date I'm thinking of the actual name for the branch  
> directory to be "release200904" (and please feel free to comment on  
> that if you think something else is better).
>
> However, that I will only do that IFF we have a positive vote for the  
> release, hence this message!
>
> Please vote:
>
> [+1] Create the release branch tonight, April 14th (it will be April  
> 15th for GMT-0)
> [+0] Abstain
> [-1] Do not create the release branch tonight
>
> Please remember that everyone is free to (and encouraged to!) vote,  
> but only the PMC votes are binding.
>
> Thanks to everyone who has made this possible with amazing  
> contributions over the last 2 years, and a heightened activity in  
> recent weeks and months to make this a spectacular release.
>
> -David
>

--
Antwebsystems.com: Quality OFBiz services for competitive rates

[Scott Gray-2]

Hi Hans

Do you have an actual reason for wanting to delay the branch?  Haven't we all known this was coming?  In my mind you would need to justify a delay rather than just request one.

Regards

Scott

HotWax Media

http://www.hotwaxmedia.com

On 15/04/2009, at 12:15 PM, Hans Bakker wrote:

David , to start a vote and give the opportunity to vote in 6-12 hours
is rather short....

I would favor a week delay and release next week, still april and still
9.04 also like sally suggests.

regards,
Hans

On Tue, 2009-04-14 at 15:14 -0600, David E Jones wrote:

Today is the day we have discussed for a while! A lot of improvements  

and fixes have gone in over the last few weeks, but it is important to  

remember that the release branch is primarily time-based and is a  

"line in the sand" as it were to begin the effort of stabilizing a  

specific code base so that end-users who want stability over features  

have that option. Some things make it in, and other things don't make  

it, and that is true no matter when we draw the line (but we don't  

want to delay it forever). What we have in place it a HUGE improvement  

over the release4.0 branch, and that is the most important point to  

keep in mind.

Along with that there is a planned press release coordinated with the  

Apache Software Foundation Public Relations Committee (that's a  

mouthful! no wonder we use acronyms like: ASF PRC) for tomorrow  

morning (Wed 15 April).

That said, the target date/time for the release branch is later  

tonight (and when I say tonight I mean according to USA time, just to  

clarify). To follow the date pattern we have discussed and make it  

clearly a date I'm thinking of the actual name for the branch  

directory to be "release200904" (and please feel free to comment on  

that if you think something else is better).

However, that I will only do that IFF we have a positive vote for the  

release, hence this message!

Please vote:

[+1] Create the release branch tonight, April 14th (it will be April  

15th for GMT-0)

[+0] Abstain

[-1] Do not create the release branch tonight

Please remember that everyone is free to (and encouraged to!) vote,  

but only the PMC votes are binding.

Thanks to everyone who has made this possible with amazing  

contributions over the last 2 years, and a heightened activity in  

recent weeks and months to make this a spectacular release.

-David

--
Antwebsystems.com: Quality OFBiz services for competitive rates

[Adrian Crum-2]

I agree with Scott. This has been discussed for months. At first we discussed a March release, but then we delayed it until April to get a few more things in.

-Adrian


--- On Tue, 4/14/09, Scott Gray <[hidden email]> wrote:

> From: Scott Gray <[hidden email]>
> Subject: Re: [VOTE] Create Release Branch 2009.04
> To: [hidden email]
> Date: Tuesday, April 14, 2009, 5:40 PM
> Hi Hans
>
> Do you have an actual reason for wanting to delay the
> branch?  Haven't we all known this was coming?  In my
> mind you would need to justify a delay rather than just
> request one.
>
> Regards
> Scott
>
> HotWax Media
> http://www.hotwaxmedia.com
>
> On 15/04/2009, at 12:15 PM, Hans Bakker wrote:
>
> > David , to start a vote and give the opportunity to
> vote in 6-12 hours
> > is rather short....
> >
> > I would favor a week delay and release next week,
> still april and still
> > 9.04 also like sally suggests.
> >
> > regards,
> > Hans
> >
> > On Tue, 2009-04-14 at 15:14 -0600, David E Jones
> wrote:
> >> Today is the day we have discussed for a while! A
> lot of improvements
> >> and fixes have gone in over the last few weeks,
> but it is important to
> >> remember that the release branch is primarily
> time-based and is a
> >> "line in the sand" as it were to begin
> the effort of stabilizing a
> >> specific code base so that end-users who want
> stability over features
> >> have that option. Some things make it in, and
> other things don't make
> >> it, and that is true no matter when we draw the
> line (but we don't
> >> want to delay it forever). What we have in place
> it a HUGE improvement
> >> over the release4.0 branch, and that is the most
> important point to
> >> keep in mind.
> >>
> >> Along with that there is a planned press release
> coordinated with the
> >> Apache Software Foundation Public Relations
> Committee (that's a
> >> mouthful! no wonder we use acronyms like: ASF PRC)
> for tomorrow
> >> morning (Wed 15 April).
> >>
> >> That said, the target date/time for the release
> branch is later
> >> tonight (and when I say tonight I mean according
> to USA time, just to
> >> clarify). To follow the date pattern we have
> discussed and make it
> >> clearly a date I'm thinking of the actual name
> for the branch
> >> directory to be "release200904" (and
> please feel free to comment on
> >> that if you think something else is better).
> >>
> >> However, that I will only do that IFF we have a
> positive vote for the
> >> release, hence this message!
> >>
> >> Please vote:
> >>
> >> [+1] Create the release branch tonight, April 14th
> (it will be April
> >> 15th for GMT-0)
> >> [+0] Abstain
> >> [-1] Do not create the release branch tonight
> >>
> >> Please remember that everyone is free to (and
> encouraged to!) vote,
> >> but only the PMC votes are binding.
> >>
> >> Thanks to everyone who has made this possible with
> amazing
> >> contributions over the last 2 years, and a
> heightened activity in
> >> recent weeks and months to make this a spectacular
> release.
> >>
> >> -David
> >>
> > --Antwebsystems.com: Quality OFBiz services for
> competitive rates
> >

     

[porkiey]

+1

Sam


On 15/04/2009 05:14, "David Jones" <[hidden email]> wrote:



Today is the day we have discussed for a while! A lot of improvements
and fixes have gone in over the last few weeks, but it is important to
remember that the release branch is primarily time-based and is a
"line in the sand" as it were to begin the effort of stabilizing a
specific code base so that end-users who want stability over features
have that option. Some things make it in, and other things don't make
it, and that is true no matter when we draw the line (but we don't
want to delay it forever). What we have in place it a HUGE improvement
over the release4.0 branch, and that is the most important point to
keep in mind.

Along with that there is a planned press release coordinated with the
Apache Software Foundation Public Relations Committee (that's a
mouthful! no wonder we use acronyms like: ASF PRC) for tomorrow
morning (Wed 15 April).

That said, the target date/time for the release branch is later
tonight (and when I say tonight I mean according to USA time, just to
clarify). To follow the date pattern we have discussed and make it
clearly a date I'm thinking of the actual name for the branch
directory to be "release200904" (and please feel free to comment on
that if you think something else is better).

However, that I will only do that IFF we have a positive vote for the
release, hence this message!

Please vote:

[+1] Create the release branch tonight, April 14th (it will be April
15th for GMT-0)
[+0] Abstain
[-1] Do not create the release branch tonight

Please remember that everyone is free to (and encouraged to!) vote,
but only the PMC votes are binding.

Thanks to everyone who has made this possible with amazing
contributions over the last 2 years, and a heightened activity in
recent weeks and months to make this a spectacular release.

-David





Sam Hamilton
CTO
Virtual Village

Tel: [phone]
Fax: [phone]
Mobile: [phone]
E-mail: [hidden email]

[Tim Ruppert]

+1

Cheers,
Tim
--
Tim Ruppert
HotWax Media
http://www.hotwaxmedia.com

o:801.649.6594
f:801.649.6595

----- "Sam Hamilton" <[hidden email]> wrote:

> +1
>
> Sam
>
>
> On 15/04/2009 05:14, "David Jones" <[hidden email]>
> wrote:
>
>
>
> Today is the day we have discussed for a while! A lot of improvements
> and fixes have gone in over the last few weeks, but it is important
> to
> remember that the release branch is primarily time-based and is a
> "line in the sand" as it were to begin the effort of stabilizing a
> specific code base so that end-users who want stability over features
> have that option. Some things make it in, and other things don't make
> it, and that is true no matter when we draw the line (but we don't
> want to delay it forever). What we have in place it a HUGE
> improvement
> over the release4.0 branch, and that is the most important point to
> keep in mind.
>
> Along with that there is a planned press release coordinated with the
> Apache Software Foundation Public Relations Committee (that's a
> mouthful! no wonder we use acronyms like: ASF PRC) for tomorrow
> morning (Wed 15 April).
>
> That said, the target date/time for the release branch is later
> tonight (and when I say tonight I mean according to USA time, just to
> clarify). To follow the date pattern we have discussed and make it
> clearly a date I'm thinking of the actual name for the branch
> directory to be "release200904" (and please feel free to comment on
> that if you think something else is better).
>
> However, that I will only do that IFF we have a positive vote for the
> release, hence this message!
>
> Please vote:
>
> [+1] Create the release branch tonight, April 14th (it will be April
> 15th for GMT-0)
> [+0] Abstain
> [-1] Do not create the release branch tonight
>
> Please remember that everyone is free to (and encouraged to!) vote,
> but only the PMC votes are binding.
>
> Thanks to everyone who has made this possible with amazing
> contributions over the last 2 years, and a heightened activity in
> recent weeks and months to make this a spectacular release.
>
> -David
>
>
>
>
>
> Sam Hamilton
> CTO
> Virtual Village
>
> Tel: [phone]
> Fax: [phone]
> Mobile: [phone]
> E-mail: [hidden email]

[Ashish Vijaywargiya-5]

+1

--
Ashish Vijaywargiya

David E Jones wrote:

>
> Today is the day we have discussed for a while! A lot of improvements
> and fixes have gone in over the last few weeks, but it is important to
> remember that the release branch is primarily time-based and is a
> "line in the sand" as it were to begin the effort of stabilizing a
> specific code base so that end-users who want stability over features
> have that option. Some things make it in, and other things don't make
> it, and that is true no matter when we draw the line (but we don't
> want to delay it forever). What we have in place it a HUGE improvement
> over the release4.0 branch, and that is the most important point to
> keep in mind.
>
> Along with that there is a planned press release coordinated with the
> Apache Software Foundation Public Relations Committee (that's a
> mouthful! no wonder we use acronyms like: ASF PRC) for tomorrow
> morning (Wed 15 April).
>
> That said, the target date/time for the release branch is later
> tonight (and when I say tonight I mean according to USA time, just to
> clarify). To follow the date pattern we have discussed and make it
> clearly a date I'm thinking of the actual name for the branch
> directory to be "release200904" (and please feel free to comment on
> that if you think something else is better).
>
> However, that I will only do that IFF we have a positive vote for the
> release, hence this message!
>
> Please vote:
>
> [+1] Create the release branch tonight, April 14th (it will be April
> 15th for GMT-0)
> [+0] Abstain
> [-1] Do not create the release branch tonight
>
> Please remember that everyone is free to (and encouraged to!) vote,
> but only the PMC votes are binding.
>
> Thanks to everyone who has made this possible with amazing
> contributions over the last 2 years, and a heightened activity in
> recent weeks and months to make this a spectacular release.
>
> -David
>

[Vikas Mayur-3]

+1

Vikas

On Apr 15, 2009, at 8:18 AM, Tim Ruppert wrote:

> +1
>
> Cheers,
> Tim
> --
> Tim Ruppert
> HotWax Media
> http://www.hotwaxmedia.com
>
> o:801.649.6594
> f:801.649.6595
>
> ----- "Sam Hamilton" <[hidden email]> wrote:
>
>> +1
>>
>> Sam
>>
>>
>> On 15/04/2009 05:14, "David Jones" <[hidden email]>
>> wrote:
>>
>>
>>
>> Today is the day we have discussed for a while! A lot of improvements
>> and fixes have gone in over the last few weeks, but it is important
>> to
>> remember that the release branch is primarily time-based and is a
>> "line in the sand" as it were to begin the effort of stabilizing a
>> specific code base so that end-users who want stability over features
>> have that option. Some things make it in, and other things don't make
>> it, and that is true no matter when we draw the line (but we don't
>> want to delay it forever). What we have in place it a HUGE
>> improvement
>> over the release4.0 branch, and that is the most important point to
>> keep in mind.
>>
>> Along with that there is a planned press release coordinated with the
>> Apache Software Foundation Public Relations Committee (that's a
>> mouthful! no wonder we use acronyms like: ASF PRC) for tomorrow
>> morning (Wed 15 April).
>>
>> That said, the target date/time for the release branch is later
>> tonight (and when I say tonight I mean according to USA time, just to
>> clarify). To follow the date pattern we have discussed and make it
>> clearly a date I'm thinking of the actual name for the branch
>> directory to be "release200904" (and please feel free to comment on
>> that if you think something else is better).
>>
>> However, that I will only do that IFF we have a positive vote for the
>> release, hence this message!
>>
>> Please vote:
>>
>> [+1] Create the release branch tonight, April 14th (it will be April
>> 15th for GMT-0)
>> [+0] Abstain
>> [-1] Do not create the release branch tonight
>>
>> Please remember that everyone is free to (and encouraged to!) vote,
>> but only the PMC votes are binding.
>>
>> Thanks to everyone who has made this possible with amazing
>> contributions over the last 2 years, and a heightened activity in
>> recent weeks and months to make this a spectacular release.
>>
>> -David
>>
>>
>>
>>
>>
>> Sam Hamilton
>> CTO
>> Virtual Village
>>
>> Tel: [phone]
>> Fax: [phone]
>> Mobile: [phone]
>> E-mail: [hidden email]

[Anil Patel-3]

+1

Regards
Anil Patel

On Apr 15, 2009, at 2:44 AM, David E Jones wrote:

>
> Today is the day we have discussed for a while! A lot of  
> improvements and fixes have gone in over the last few weeks, but it  
> is important to remember that the release branch is primarily time-
> based and is a "line in the sand" as it were to begin the effort of  
> stabilizing a specific code base so that end-users who want  
> stability over features have that option. Some things make it in,  
> and other things don't make it, and that is true no matter when we  
> draw the line (but we don't want to delay it forever). What we have  
> in place it a HUGE improvement over the release4.0 branch, and that  
> is the most important point to keep in mind.
>
> Along with that there is a planned press release coordinated with  
> the Apache Software Foundation Public Relations Committee (that's a  
> mouthful! no wonder we use acronyms like: ASF PRC) for tomorrow  
> morning (Wed 15 April).
>
> That said, the target date/time for the release branch is later  
> tonight (and when I say tonight I mean according to USA time, just  
> to clarify). To follow the date pattern we have discussed and make  
> it clearly a date I'm thinking of the actual name for the branch  
> directory to be "release200904" (and please feel free to comment on  
> that if you think something else is better).
>
> However, that I will only do that IFF we have a positive vote for  
> the release, hence this message!
>
> Please vote:
>
> [+1] Create the release branch tonight, April 14th (it will be April  
> 15th for GMT-0)
> [+0] Abstain
> [-1] Do not create the release branch tonight
>
> Please remember that everyone is free to (and encouraged to!) vote,  
> but only the PMC votes are binding.
>
> Thanks to everyone who has made this possible with amazing  
> contributions over the last 2 years, and a heightened activity in  
> recent weeks and months to make this a spectacular release.
>
> -David
>

[David E Jones-3]

Hans,

Do you mean for this to be a -1, or are you just saying you'd like  
more time to consider your vote?

It is customary to allow 48 hours for voting, and if that is needed  
(ie insufficient responses before that) there's no reason not to do  
that.

-David


On Apr 14, 2009, at 6:15 PM, Hans Bakker wrote:

> David , to start a vote and give the opportunity to vote in 6-12 hours
> is rather short....
>
> I would favor a week delay and release next week, still april and  
> still
> 9.04 also like sally suggests.
>
> regards,
> Hans
>
> On Tue, 2009-04-14 at 15:14 -0600, David E Jones wrote:
>> Today is the day we have discussed for a while! A lot of improvements
>> and fixes have gone in over the last few weeks, but it is important  
>> to
>> remember that the release branch is primarily time-based and is a
>> "line in the sand" as it were to begin the effort of stabilizing a
>> specific code base so that end-users who want stability over features
>> have that option. Some things make it in, and other things don't make
>> it, and that is true no matter when we draw the line (but we don't
>> want to delay it forever). What we have in place it a HUGE  
>> improvement
>> over the release4.0 branch, and that is the most important point to
>> keep in mind.
>>
>> Along with that there is a planned press release coordinated with the
>> Apache Software Foundation Public Relations Committee (that's a
>> mouthful! no wonder we use acronyms like: ASF PRC) for tomorrow
>> morning (Wed 15 April).
>>
>> That said, the target date/time for the release branch is later
>> tonight (and when I say tonight I mean according to USA time, just to
>> clarify). To follow the date pattern we have discussed and make it
>> clearly a date I'm thinking of the actual name for the branch
>> directory to be "release200904" (and please feel free to comment on
>> that if you think something else is better).
>>
>> However, that I will only do that IFF we have a positive vote for the
>> release, hence this message!
>>
>> Please vote:
>>
>> [+1] Create the release branch tonight, April 14th (it will be April
>> 15th for GMT-0)
>> [+0] Abstain
>> [-1] Do not create the release branch tonight
>>
>> Please remember that everyone is free to (and encouraged to!) vote,
>> but only the PMC votes are binding.
>>
>> Thanks to everyone who has made this possible with amazing
>> contributions over the last 2 years, and a heightened activity in
>> recent weeks and months to make this a spectacular release.
>>
>> -David
>>
> --
> Antwebsystems.com: Quality OFBiz services for competitive rates
>

[David E Jones-3]

Thanks for your comments Scott.

BTW, did you mean for this to be a +1 vote for you?

-David


On Apr 14, 2009, at 6:40 PM, Scott Gray wrote:

> Hi Hans
>
> Do you have an actual reason for wanting to delay the branch?  
> Haven't we all known this was coming?  In my mind you would need to  
> justify a delay rather than just request one.
>
> Regards
> Scott
>
> HotWax Media
> http://www.hotwaxmedia.com
>
> On 15/04/2009, at 12:15 PM, Hans Bakker wrote:
>
>> David , to start a vote and give the opportunity to vote in 6-12  
>> hours
>> is rather short....
>>
>> I would favor a week delay and release next week, still april and  
>> still
>> 9.04 also like sally suggests.
>>
>> regards,
>> Hans
>>
>> On Tue, 2009-04-14 at 15:14 -0600, David E Jones wrote:
>>> Today is the day we have discussed for a while! A lot of  
>>> improvements
>>> and fixes have gone in over the last few weeks, but it is  
>>> important to
>>> remember that the release branch is primarily time-based and is a
>>> "line in the sand" as it were to begin the effort of stabilizing a
>>> specific code base so that end-users who want stability over  
>>> features
>>> have that option. Some things make it in, and other things don't  
>>> make
>>> it, and that is true no matter when we draw the line (but we don't
>>> want to delay it forever). What we have in place it a HUGE  
>>> improvement
>>> over the release4.0 branch, and that is the most important point to
>>> keep in mind.
>>>
>>> Along with that there is a planned press release coordinated with  
>>> the
>>> Apache Software Foundation Public Relations Committee (that's a
>>> mouthful! no wonder we use acronyms like: ASF PRC) for tomorrow
>>> morning (Wed 15 April).
>>>
>>> That said, the target date/time for the release branch is later
>>> tonight (and when I say tonight I mean according to USA time, just  
>>> to
>>> clarify). To follow the date pattern we have discussed and make it
>>> clearly a date I'm thinking of the actual name for the branch
>>> directory to be "release200904" (and please feel free to comment on
>>> that if you think something else is better).
>>>
>>> However, that I will only do that IFF we have a positive vote for  
>>> the
>>> release, hence this message!
>>>
>>> Please vote:
>>>
>>> [+1] Create the release branch tonight, April 14th (it will be April
>>> 15th for GMT-0)
>>> [+0] Abstain
>>> [-1] Do not create the release branch tonight
>>>
>>> Please remember that everyone is free to (and encouraged to!) vote,
>>> but only the PMC votes are binding.
>>>
>>> Thanks to everyone who has made this possible with amazing
>>> contributions over the last 2 years, and a heightened activity in
>>> recent weeks and months to make this a spectacular release.
>>>
>>> -David
>>>
>> --
>> Antwebsystems.com: Quality OFBiz services for competitive rates
>>
>

[Scott Gray-2]

Oh yeah sorry, +1

Regards

Scott

HotWax Media

http://www.hotwaxmedia.com

On 15/04/2009, at 5:22 PM, David E Jones wrote:

Thanks for your comments Scott.

BTW, did you mean for this to be a +1 vote for you?

-David


On Apr 14, 2009, at 6:40 PM, Scott Gray wrote:

Hi Hans

Do you have an actual reason for wanting to delay the branch?  Haven't we all known this was coming?  In my mind you would need to justify a delay rather than just request one.

Regards

Scott

HotWax Media

http://www.hotwaxmedia.com

On 15/04/2009, at 12:15 PM, Hans Bakker wrote:

David , to start a vote and give the opportunity to vote in 6-12 hours

is rather short....

I would favor a week delay and release next week, still april and still

9.04 also like sally suggests.

regards,

Hans

On Tue, 2009-04-14 at 15:14 -0600, David E Jones wrote:

Today is the day we have discussed for a while! A lot of improvements

and fixes have gone in over the last few weeks, but it is important to

remember that the release branch is primarily time-based and is a

"line in the sand" as it were to begin the effort of stabilizing a

specific code base so that end-users who want stability over features

have that option. Some things make it in, and other things don't make

it, and that is true no matter when we draw the line (but we don't

want to delay it forever). What we have in place it a HUGE improvement

over the release4.0 branch, and that is the most important point to

keep in mind.

Along with that there is a planned press release coordinated with the

Apache Software Foundation Public Relations Committee (that's a

mouthful! no wonder we use acronyms like: ASF PRC) for tomorrow

morning (Wed 15 April).

That said, the target date/time for the release branch is later

tonight (and when I say tonight I mean according to USA time, just to

clarify). To follow the date pattern we have discussed and make it

clearly a date I'm thinking of the actual name for the branch

directory to be "release200904" (and please feel free to comment on

that if you think something else is better).

However, that I will only do that IFF we have a positive vote for the

release, hence this message!

Please vote:

[+1] Create the release branch tonight, April 14th (it will be April

15th for GMT-0)

[+0] Abstain

[-1] Do not create the release branch tonight

Please remember that everyone is free to (and encouraged to!) vote,

but only the PMC votes are binding.

Thanks to everyone who has made this possible with amazing

contributions over the last 2 years, and a heightened activity in

recent weeks and months to make this a spectacular release.

-David

--

Antwebsystems.com: Quality OFBiz services for competitive rates

[Bruno Busco]

+1
Bruno

2009/4/15, Scott Gray <[hidden email]>:

> Oh yeah sorry, +1
>
> Regards
> Scott
>
> HotWax Media
> http://www.hotwaxmedia.com
>
>
>
> On 15/04/2009, at 5:22 PM, David E Jones wrote:
>
>>
>> Thanks for your comments Scott.
>>
>> BTW, did you mean for this to be a +1 vote for you?
>>
>> -David
>>
>>
>> On Apr 14, 2009, at 6:40 PM, Scott Gray wrote:
>>
>>> Hi Hans
>>>
>>> Do you have an actual reason for wanting to delay the branch?
>>> Haven't we all known this was coming?  In my mind you would need to
>>> justify a delay rather than just request one.
>>>
>>> Regards
>>> Scott
>>>
>>> HotWax Media
>>> http://www.hotwaxmedia.com
>>>
>>> On 15/04/2009, at 12:15 PM, Hans Bakker wrote:
>>>
>>>> David , to start a vote and give the opportunity to vote in 6-12
>>>> hours
>>>> is rather short....
>>>>
>>>> I would favor a week delay and release next week, still april and
>>>> still
>>>> 9.04 also like sally suggests.
>>>>
>>>> regards,
>>>> Hans
>>>>
>>>> On Tue, 2009-04-14 at 15:14 -0600, David E Jones wrote:
>>>>> Today is the day we have discussed for a while! A lot of
>>>>> improvements
>>>>> and fixes have gone in over the last few weeks, but it is
>>>>> important to
>>>>> remember that the release branch is primarily time-based and is a
>>>>> "line in the sand" as it were to begin the effort of stabilizing a
>>>>> specific code base so that end-users who want stability over
>>>>> features
>>>>> have that option. Some things make it in, and other things don't
>>>>> make
>>>>> it, and that is true no matter when we draw the line (but we don't
>>>>> want to delay it forever). What we have in place it a HUGE
>>>>> improvement
>>>>> over the release4.0 branch, and that is the most important point to
>>>>> keep in mind.
>>>>>
>>>>> Along with that there is a planned press release coordinated with
>>>>> the
>>>>> Apache Software Foundation Public Relations Committee (that's a
>>>>> mouthful! no wonder we use acronyms like: ASF PRC) for tomorrow
>>>>> morning (Wed 15 April).
>>>>>
>>>>> That said, the target date/time for the release branch is later
>>>>> tonight (and when I say tonight I mean according to USA time,
>>>>> just to
>>>>> clarify). To follow the date pattern we have discussed and make it
>>>>> clearly a date I'm thinking of the actual name for the branch
>>>>> directory to be "release200904" (and please feel free to comment on
>>>>> that if you think something else is better).
>>>>>
>>>>> However, that I will only do that IFF we have a positive vote for
>>>>> the
>>>>> release, hence this message!
>>>>>
>>>>> Please vote:
>>>>>
>>>>> [+1] Create the release branch tonight, April 14th (it will be
>>>>> April
>>>>> 15th for GMT-0)
>>>>> [+0] Abstain
>>>>> [-1] Do not create the release branch tonight
>>>>>
>>>>> Please remember that everyone is free to (and encouraged to!) vote,
>>>>> but only the PMC votes are binding.
>>>>>
>>>>> Thanks to everyone who has made this possible with amazing
>>>>> contributions over the last 2 years, and a heightened activity in
>>>>> recent weeks and months to make this a spectacular release.
>>>>>
>>>>> -David
>>>>>
>>>> --
>>>> Antwebsystems.com: Quality OFBiz services for competitive rates
>>>>
>>>
>>
>
>

--
Inviato dal mio dispositivo mobile

[Pranay Pandey-2]

+1

Thanks & Regards
--
Pranay Pandey



On Apr 15, 2009, at 2:44 AM, David E Jones wrote:

>
> Today is the day we have discussed for a while! A lot of  
> improvements and fixes have gone in over the last few weeks, but it  
> is important to remember that the release branch is primarily time-
> based and is a "line in the sand" as it were to begin the effort of  
> stabilizing a specific code base so that end-users who want  
> stability over features have that option. Some things make it in,  
> and other things don't make it, and that is true no matter when we  
> draw the line (but we don't want to delay it forever). What we have  
> in place it a HUGE improvement over the release4.0 branch, and that  
> is the most important point to keep in mind.
>
> Along with that there is a planned press release coordinated with  
> the Apache Software Foundation Public Relations Committee (that's a  
> mouthful! no wonder we use acronyms like: ASF PRC) for tomorrow  
> morning (Wed 15 April).
>
> That said, the target date/time for the release branch is later  
> tonight (and when I say tonight I mean according to USA time, just  
> to clarify). To follow the date pattern we have discussed and make  
> it clearly a date I'm thinking of the actual name for the branch  
> directory to be "release200904" (and please feel free to comment on  
> that if you think something else is better).
>
> However, that I will only do that IFF we have a positive vote for  
> the release, hence this message!
>
> Please vote:
>
> [+1] Create the release branch tonight, April 14th (it will be April  
> 15th for GMT-0)
> [+0] Abstain
> [-1] Do not create the release branch tonight
>
> Please remember that everyone is free to (and encouraged to!) vote,  
> but only the PMC votes are binding.
>
> Thanks to everyone who has made this possible with amazing  
> contributions over the last 2 years, and a heightened activity in  
> recent weeks and months to make this a spectacular release.
>
> -David
>

[Shi Yusen]

+1

Great work!

Cheers

在 2009-04-14二的 15:14 -0600，David E Jones写道：

> Today is the day we have discussed for a while! A lot of improvements  
> and fixes have gone in over the last few weeks, but it is important to  
> remember that the release branch is primarily time-based and is a  
> "line in the sand" as it were to begin the effort of stabilizing a  
> specific code base so that end-users who want stability over features  
> have that option. Some things make it in, and other things don't make  
> it, and that is true no matter when we draw the line (but we don't  
> want to delay it forever). What we have in place it a HUGE improvement  
> over the release4.0 branch, and that is the most important point to  
> keep in mind.
>
> Along with that there is a planned press release coordinated with the  
> Apache Software Foundation Public Relations Committee (that's a  
> mouthful! no wonder we use acronyms like: ASF PRC) for tomorrow  
> morning (Wed 15 April).
>
> That said, the target date/time for the release branch is later  
> tonight (and when I say tonight I mean according to USA time, just to  
> clarify). To follow the date pattern we have discussed and make it  
> clearly a date I'm thinking of the actual name for the branch  
> directory to be "release200904" (and please feel free to comment on  
> that if you think something else is better).
>
> However, that I will only do that IFF we have a positive vote for the  
> release, hence this message!
>
> Please vote:
>
> [+1] Create the release branch tonight, April 14th (it will be April  
> 15th for GMT-0)
> [+0] Abstain
> [-1] Do not create the release branch tonight
>
> Please remember that everyone is free to (and encouraged to!) vote,  
> but only the PMC votes are binding.
>
> Thanks to everyone who has made this possible with amazing  
> contributions over the last 2 years, and a heightened activity in  
> recent weeks and months to make this a spectacular release.
>
> -David
>

[David E Jones-3]

Just an FYI: it appears that due to some other things going on with  
the PRC that the press release will NOT be ready for tomorrow, and  
instead will be going out on Monday.

I don't think we have any reason to delay the release branch itself  
(and it'll be great to have a few days for binary builds to get going  
and people to play with it before the press release anyway), but this  
does mean there is no reason to rush to get it in during the next few  
hours as no press release will be going out (and it we delay we don't  
have to ask them to hold the press release).

Just so everyone knows, creating and coordinating this press release  
has been going for about 3 weeks now and is a significant  effort  
overall with over 20 people involved (on the OFBiz side as well as on  
the ASF PRC side), not to mention the hundreds of people it will go to  
after it is finally released.

Anyway, I apologize for this further delay, but I don't think we're in  
any hurry here... I like the think of setting a specific date as a way  
to coordinate all of the many things that need to happen for an effort  
like this. As long as an early pre-requisite of other complex things  
doesn't slip then it's not such a huge deal (and this isn't a  
commercial effort with thousands of financially at-risk stakeholders  
or something... or is it? ;) ).

-David


On Apr 14, 2009, at 3:14 PM, David E Jones wrote:

>
> Today is the day we have discussed for a while! A lot of  
> improvements and fixes have gone in over the last few weeks, but it  
> is important to remember that the release branch is primarily time-
> based and is a "line in the sand" as it were to begin the effort of  
> stabilizing a specific code base so that end-users who want  
> stability over features have that option. Some things make it in,  
> and other things don't make it, and that is true no matter when we  
> draw the line (but we don't want to delay it forever). What we have  
> in place it a HUGE improvement over the release4.0 branch, and that  
> is the most important point to keep in mind.
>
> Along with that there is a planned press release coordinated with  
> the Apache Software Foundation Public Relations Committee (that's a  
> mouthful! no wonder we use acronyms like: ASF PRC) for tomorrow  
> morning (Wed 15 April).
>
> That said, the target date/time for the release branch is later  
> tonight (and when I say tonight I mean according to USA time, just  
> to clarify). To follow the date pattern we have discussed and make  
> it clearly a date I'm thinking of the actual name for the branch  
> directory to be "release200904" (and please feel free to comment on  
> that if you think something else is better).
>
> However, that I will only do that IFF we have a positive vote for  
> the release, hence this message!
>
> Please vote:
>
> [+1] Create the release branch tonight, April 14th (it will be April  
> 15th for GMT-0)
> [+0] Abstain
> [-1] Do not create the release branch tonight
>
> Please remember that everyone is free to (and encouraged to!) vote,  
> but only the PMC votes are binding.
>
> Thanks to everyone who has made this possible with amazing  
> contributions over the last 2 years, and a heightened activity in  
> recent weeks and months to make this a spectacular release.
>
> -David
>

[Adrian Crum-2]

--- On Tue, 4/14/09, David E Jones <[hidden email]> wrote:
> Anyway, I apologize for this further delay, but I don't
> think we're in any hurry here... I like the think of
> setting a specific date as a way to coordinate all of the
> many things that need to happen for an effort like this. As
> long as an early pre-requisite of other complex things
> doesn't slip then it's not such a huge deal (and
> this isn't a commercial effort with thousands of
> financially at-risk stakeholders or something... or is it?
> ;) ).

Aaaaahhhhh!!!!!

*Companies crashing and burning, mass devastation*

Just kidding.

Like you said, a line has to be drawn somewhere.

-Adrian



     

[Jacques Le Roux]

Before voting I'd like to clarify some points. As we previously agreed we should not put anything but bugs fixes in a freezed
branches.
But I think that we need to finish the secured URLs job. For me this means to :
* Fix the URL calling services in FTL files (I will open a Jira issue for this as soons as I will come with a tool to make all
references clear, we can't rely on chance here)
* Treat the secured URLs exception https://issues.apache.org/jira/browse/OFBIZ-2272
* I suggested to process targets with params in forms : look for <<form(.*)target=(.*)\?(.*)=(.*)>> and
<<form.(*)\R(.*)target=(.*)\?(.*)=(.*)>>, what about this ?
* Not related to securing URL but as we already discussed, I'd like to test, and if OK, replace location="org.ofbiz. by
location="component:// in controllers

That's all I see for the moment. So my opinion is that we need to commit this changes in the new branche, before or after its
creation. Then I will vote.

Jacques

From: "David E Jones" <[hidden email]>

> Today is the day we have discussed for a while! A lot of improvements  and fixes have gone in over the last few weeks, but it is
> important to  remember that the release branch is primarily time-based and is a  "line in the sand" as it were to begin the effort
> of stabilizing a  specific code base so that end-users who want stability over features  have that option. Some things make it in,
> and other things don't make  it, and that is true no matter when we draw the line (but we don't  want to delay it forever). What
> we have in place it a HUGE improvement  over the release4.0 branch, and that is the most important point to  keep in mind.
>
> Along with that there is a planned press release coordinated with the  Apache Software Foundation Public Relations Committee
> (that's a  mouthful! no wonder we use acronyms like: ASF PRC) for tomorrow  morning (Wed 15 April).
>
> That said, the target date/time for the release branch is later  tonight (and when I say tonight I mean according to USA time,
> just to  clarify). To follow the date pattern we have discussed and make it  clearly a date I'm thinking of the actual name for
> the branch  directory to be "release200904" (and please feel free to comment on  that if you think something else is better).
>
> However, that I will only do that IFF we have a positive vote for the  release, hence this message!
>
> Please vote:
>
> [+1] Create the release branch tonight, April 14th (it will be April  15th for GMT-0)
> [+0] Abstain
> [-1] Do not create the release branch tonight
>
> Please remember that everyone is free to (and encouraged to!) vote,  but only the PMC votes are binding.
>
> Thanks to everyone who has made this possible with amazing  contributions over the last 2 years, and a heightened activity in
> recent weeks and months to make this a spectacular release.
>
> -David
>

[David E Jones-3]

Well, what do you think Jacques? Are each of these appropriate things  
to put in a release branch? Are any of them things that you'd like  
done but that aren't really bug fixes (IMO a security hole is a bug  
fix of sorts)?

-David


On Apr 15, 2009, at 12:32 AM, Jacques Le Roux wrote:

> Before voting I'd like to clarify some points. As we previously  
> agreed we should not put anything but bugs fixes in a freezed  
> branches.
> But I think that we need to finish the secured URLs job. For me this  
> means to :
> * Fix the URL calling services in FTL files (I will open a Jira  
> issue for this as soons as I will come with a tool to make all  
> references clear, we can't rely on chance here)
> * Treat the secured URLs exception https://issues.apache.org/jira/browse/OFBIZ-2272
> * I suggested to process targets with params in forms : look for  
> <<form(.*)target=(.*)\?(.*)=(.*)>> and <<form.(*)\R(.*)target=(.*)\?
> (.*)=(.*)>>, what about this ?
> * Not related to securing URL but as we already discussed, I'd like  
> to test, and if OK, replace location="org.ofbiz. by  
> location="component:// in controllers
>
> That's all I see for the moment. So my opinion is that we need to  
> commit this changes in the new branche, before or after its  
> creation. Then I will vote.
>
> Jacques
>
> From: "David E Jones" <[hidden email]>
>> Today is the day we have discussed for a while! A lot of  
>> improvements  and fixes have gone in over the last few weeks, but  
>> it is important to  remember that the release branch is primarily  
>> time-based and is a  "line in the sand" as it were to begin the  
>> effort of stabilizing a  specific code base so that end-users who  
>> want stability over features  have that option. Some things make it  
>> in, and other things don't make  it, and that is true no matter  
>> when we draw the line (but we don't  want to delay it forever).  
>> What we have in place it a HUGE improvement  over the release4.0  
>> branch, and that is the most important point to  keep in mind.
>>
>> Along with that there is a planned press release coordinated with  
>> the  Apache Software Foundation Public Relations Committee (that's  
>> a  mouthful! no wonder we use acronyms like: ASF PRC) for tomorrow  
>> morning (Wed 15 April).
>>
>> That said, the target date/time for the release branch is later  
>> tonight (and when I say tonight I mean according to USA time, just  
>> to  clarify). To follow the date pattern we have discussed and make  
>> it  clearly a date I'm thinking of the actual name for the branch  
>> directory to be "release200904" (and please feel free to comment  
>> on  that if you think something else is better).
>>
>> However, that I will only do that IFF we have a positive vote for  
>> the  release, hence this message!
>>
>> Please vote:
>>
>> [+1] Create the release branch tonight, April 14th (it will be  
>> April  15th for GMT-0)
>> [+0] Abstain
>> [-1] Do not create the release branch tonight
>>
>> Please remember that everyone is free to (and encouraged to!)  
>> vote,  but only the PMC votes are binding.
>>
>> Thanks to everyone who has made this possible with amazing  
>> contributions over the last 2 years, and a heightened activity in  
>> recent weeks and months to make this a spectacular release.
>>
>> -David
>
>