[VOTE] Create Release Branch 2009.04

[Jacques Le Roux]

Well tried digression :o)
* 1st point obviously a bug
* 2d too
* I'd like to discuss this point, do you agree we should do it too (I did not look into code yet)
* Not a bug but IMPO should be in release 9.04 too

BTW I thought about your branch name propostion (200904). Could we not use a such name for our releases. Microsoft marketing used 95
and 98 then 2000. Obviously 2009-04 or whatever form is less cryptice than 9.04. I know we, IT people, like crytic things ;o) but
making it clearer for eveyrone is all about marketing, isn'it ? The next release could be OFBiz 2009-04

Jacques


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

> 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
>>
>>
>

[Adrian Crum-2]

lol wut?

I thought you were the one who suggested Ubuntu revision conventions. Let's keep it at 9.04 please. There are more important things to consider.

-Adrian


--- On Wed, 4/15/09, Jacques Le Roux <[hidden email]> wrote:

> From: Jacques Le Roux <[hidden email]>
> Subject: Re: [VOTE] Create Release Branch 2009.04
> To: [hidden email]
> Date: Wednesday, April 15, 2009, 12:27 AM
> Well tried digression :o)
> * 1st point obviously a bug
> * 2d too
> * I'd like to discuss this point, do you agree we
> should do it too (I did not look into code yet)
> * Not a bug but IMPO should be in release 9.04 too
>
> BTW I thought about your branch name propostion (200904).
> Could we not use a such name for our releases. Microsoft
> marketing used 95 and 98 then 2000. Obviously 2009-04 or
> whatever form is less cryptice than 9.04. I know we, IT
> people, like crytic things ;o) but making it clearer for
> eveyrone is all about marketing, isn'it ? The next
> release could be OFBiz 2009-04
>
> Jacques
>
>
> From: "David E Jones"
> <[hidden email]>
> > 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
> >>
> >>
> >

     

[Jacopo Cappellato-4]

+1

On Apr 14, 2009, at 11: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
>

[Jacques Le Roux]

From: "Adrian Crum" <[hidden email]>
> lol wut?

I knew lol not lol wut, I learn everyday :o)
 
> I thought you were the one who suggested Ubuntu revision conventions.

Yes I'm, only fools don't change their mind ;o)

>Let's keep it at 9.04 please.

OK too late, anyway not a big deal

There are more important things to consider.

Yes, like the 4 other points...

Jacques
 

> -Adrian
>
>
> --- On Wed, 4/15/09, Jacques Le Roux <[hidden email]> wrote:
>
>> From: Jacques Le Roux <[hidden email]>
>> Subject: Re: [VOTE] Create Release Branch 2009.04
>> To: [hidden email]
>> Date: Wednesday, April 15, 2009, 12:27 AM
>> Well tried digression :o)
>> * 1st point obviously a bug
>> * 2d too
>> * I'd like to discuss this point, do you agree we
>> should do it too (I did not look into code yet)
>> * Not a bug but IMPO should be in release 9.04 too
>>
>> BTW I thought about your branch name propostion (200904).
>> Could we not use a such name for our releases. Microsoft
>> marketing used 95 and 98 then 2000. Obviously 2009-04 or
>> whatever form is less cryptice than 9.04. I know we, IT
>> people, like crytic things ;o) but making it clearer for
>> eveyrone is all about marketing, isn'it ? The next
>> release could be OFBiz 2009-04
>>
>> Jacques
>>
>>
>> From: "David E Jones"
>> <[hidden email]>
>> > 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
>> >>
>> >>
>> >
>
>
>      
>

[Ravindra Mandre]

+1

Regards
Ravindra Mandre

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]

[+1] Binding: David, Adrian, Anil, Scott, Jacopo
[+1] Non-binding: Sam, Tim, Ashish, Vikas, Bruno, Pranay, Shi, Marco,  
Ravindra
[+0]: 0
[-1]: 0

Based on this result (more than 3 binding +1 votes and more +1 than -1  
votes) the vote has passed.

In respect for comments about the time, I'll wait for about 12 hours  
more from the time of this email (that makes it mid-day Thursday my  
time) to do the actual branch. If anyone would like to vote after this  
that's fine, but unless something major comes up we'll consider this  
vote binding and do the release branch as has been planned for (though  
~1.5 days after). With that timing the press release should go out  
early (probably Monday) of next week, for those interested in such  
things.

-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
>

[Jacques Le Roux]

+1 for the branche with the points below taken into account...

Maybe I did not make it clear but each * just below refer to each * in my 1st message.

Jacques

From: "Jacques Le Roux" <[hidden email]>

> Well tried digression :o)
> * 1st point obviously a bug
> * 2d too
> * I'd like to discuss this point, do you agree we should do it too (I did not look into code yet)
> * Not a bug but IMPO should be in release 9.04 too
>
> BTW I thought about your branch name propostion (200904). Could we not use a such name for our releases. Microsoft marketing used
> 95 and 98 then 2000. Obviously 2009-04 or whatever form is less cryptice than 9.04. I know we, IT people, like crytic things ;o)
> but making it clearer for eveyrone is all about marketing, isn'it ? The next release could be OFBiz 2009-04
>
> Jacques
>
>
> From: "David E Jones" <[hidden email]>
>> 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
>>>
>>>
>>
>
>

[David E Jones-3]

Jacques,

Please keep in mind that everyone has a list of things they'd like to  
see done before the release. If we waited for all of it to get done we  
would NEVER ever do any releases, especially because as one person's  
list made progress other people would add more things to their list...  
and on and on and on it would go. Fortunately we have the trunk for  
those sorts of things, and it does go on and on and on.

For the release branch, we have to draw the line somewhere, and we've  
been discussing this for months and delayed it a few weeks ago and  
then delayed it again a couple of days ago... and THAT'S IT! We're not  
delaying this forever, otherwise we might as well not even try to do  
it...

-David


On Apr 16, 2009, at 1:32 AM, Jacques Le Roux wrote:

> +1 for the branche with the points below taken into account...
>
> Maybe I did not make it clear but each * just below refer to each *  
> in my 1st message.
>
> Jacques
>
> From: "Jacques Le Roux" <[hidden email]>
>> Well tried digression :o)
>> * 1st point obviously a bug
>> * 2d too
>> * I'd like to discuss this point, do you agree we should do it too  
>> (I did not look into code yet)
>> * Not a bug but IMPO should be in release 9.04 too
>>
>> BTW I thought about your branch name propostion (200904). Could we  
>> not use a such name for our releases. Microsoft marketing used 95  
>> and 98 then 2000. Obviously 2009-04 or whatever form is less  
>> cryptice than 9.04. I know we, IT people, like crytic things ;o)  
>> but making it clearer for eveyrone is all about marketing, isn'it ?  
>> The next release could be OFBiz 2009-04
>>
>> Jacques
>>
>>
>> From: "David E Jones" <[hidden email]>
>>> 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
>>>>
>>>>
>>>
>>
>
>

[Erwan de FERRIERES-3]

David,

i'm trying to make a JIRA to update the poi.jar library in OFBiz, just
before creating the branch.

Hope that could be integrated before the creation !

Cheers

David E Jones a écrit :

>
> [+1] Binding: David, Adrian, Anil, Scott, Jacopo
> [+1] Non-binding: Sam, Tim, Ashish, Vikas, Bruno, Pranay, Shi, Marco,
> Ravindra
> [+0]: 0
> [-1]: 0
>
> Based on this result (more than 3 binding +1 votes and more +1 than -1
> votes) the vote has passed.
>
> In respect for comments about the time, I'll wait for about 12 hours
> more from the time of this email (that makes it mid-day Thursday my
> time) to do the actual branch. If anyone would like to vote after this
> that's fine, but unless something major comes up we'll consider this
> vote binding and do the release branch as has been planned for (though
> ~1.5 days after). With that timing the press release should go out early
> (probably Monday) of next week, for those interested in such things.
>
> -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
>>
>
>

--
- Erwan -

[Jacques Le Roux]

David,

From: "David E Jones" <[hidden email]>
> Jacques,
>
> Please keep in mind that everyone has a list of things they'd like to  see done before the release. If we waited for all of it to
> get done we  would NEVER ever do any releases, especially because as one person's  list made progress other people would add more
> things to their list...  and on and on and on it would go. Fortunately we have the trunk for  those sorts of things, and it does
> go on and on and on.

As we already discusses, it's not about specific features I'd like to be in this release but about *security*. I thought we already
agree that we will put them in the branche after it will be freezed. Did you change your mind ?

> For the release branch, we have to draw the line somewhere, and we've  been discussing this for months and delayed it a few weeks
> ago and  then delayed it again a couple of days ago... and THAT'S IT! We're not  delaying this forever, otherwise we might as well
> not even try to do  it...

I don't want to delay anything, just be sure that at least security fixes and maybe related things like the location component://
stuff in controllers will be in the release. That's all I say below. BTW I did not find the time yet to look at the 3d point, but I
guess it's a security issue too.

Believe me, it's not whim (an new english word for me),  security  is an important argument for users !

Jacques

> -David
>
>
> On Apr 16, 2009, at 1:32 AM, Jacques Le Roux wrote:
>
>> +1 for the branche with the points below taken into account...
>>
>> Maybe I did not make it clear but each * just below refer to each *  in my 1st message.
>>
>> Jacques
>>
>> From: "Jacques Le Roux" <[hidden email]>
>>> Well tried digression :o)
>>> * 1st point obviously a bug
>>> * 2d too
>>> * I'd like to discuss this point, do you agree we should do it too  (I did not look into code yet)
>>> * Not a bug but IMPO should be in release 9.04 too
>>>
>>> BTW I thought about your branch name propostion (200904). Could we  not use a such name for our releases. Microsoft marketing
>>> used 95  and 98 then 2000. Obviously 2009-04 or whatever form is less  cryptice than 9.04. I know we, IT people, like crytic
>>> things ;o)  but making it clearer for eveyrone is all about marketing, isn'it ?  The next release could be OFBiz 2009-04
>>>
>>> Jacques
>>>
>>>
>>> From: "David E Jones" <[hidden email]>
>>>> 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
>>>>>
>>>>>
>>>>
>>>
>>
>>
>

[David E Jones-3]

Okay, at long last the release branch is created. The URL for it is:

https://svn.apache.org/repos/asf/ofbiz/branches/release09.04

Tim Ruppert will be heading up build and demo resources for this in  
the near future, and for now it is in SVN.

Just as with the release4.0 branch this now means as contributors to  
the trunk we should watch out for fixes that should also go into the  
branch and apply them there as well.

Thanks to everyone who has helped, and everyone who is continuing to  
help, with this.

-David


On Apr 15, 2009, at 11:59 PM, David E Jones wrote:

>
> [+1] Binding: David, Adrian, Anil, Scott, Jacopo
> [+1] Non-binding: Sam, Tim, Ashish, Vikas, Bruno, Pranay, Shi,  
> Marco, Ravindra
> [+0]: 0
> [-1]: 0
>
> Based on this result (more than 3 binding +1 votes and more +1 than  
> -1 votes) the vote has passed.
>
> In respect for comments about the time, I'll wait for about 12 hours  
> more from the time of this email (that makes it mid-day Thursday my  
> time) to do the actual branch. If anyone would like to vote after  
> this that's fine, but unless something major comes up we'll consider  
> this vote binding and do the release branch as has been planned for  
> (though ~1.5 days after). With that timing the press release should  
> go out early (probably Monday) of next week, for those interested in  
> such things.
>
> -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]

David,

Thank you so much for your work on this! Combined with the forthcoming press release, I believe OFBiz will be entering a new era.

-Adrian


--- On Fri, 4/17/09, David E Jones <[hidden email]> wrote:

> From: David E Jones <[hidden email]>
> Subject: Re: [VOTE][RESULT] Create Release Branch 2009.04
> To: [hidden email]
> Date: Friday, April 17, 2009, 2:08 AM
> Okay, at long last the release branch is created. The URL
> for it is:
>
> https://svn.apache.org/repos/asf/ofbiz/branches/release09.04
>
> Tim Ruppert will be heading up build and demo resources for
> this in the near future, and for now it is in SVN.
>
> Just as with the release4.0 branch this now means as
> contributors to the trunk we should watch out for fixes that
> should also go into the branch and apply them there as well.
>
> Thanks to everyone who has helped, and everyone who is
> continuing to help, with this.
>
> -David
>
>
> On Apr 15, 2009, at 11:59 PM, David E Jones wrote:
>
> >
> > [+1] Binding: David, Adrian, Anil, Scott, Jacopo
> > [+1] Non-binding: Sam, Tim, Ashish, Vikas, Bruno,
> Pranay, Shi, Marco, Ravindra
> > [+0]: 0
> > [-1]: 0
> >
> > Based on this result (more than 3 binding +1 votes and
> more +1 than -1 votes) the vote has passed.
> >
> > In respect for comments about the time, I'll wait
> for about 12 hours more from the time of this email (that
> makes it mid-day Thursday my time) to do the actual branch.
> If anyone would like to vote after this that's fine, but
> unless something major comes up we'll consider this vote
> binding and do the release branch as has been planned for
> (though ~1.5 days after). With that timing the press release
> should go out early (probably Monday) of next week, for
> those interested in such things.
> >
> > -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
> >>
> >

     

[Jacques Le Roux]

Yes, thank you David, and thank you also to all the people that made this new step for OFBiz possible!

Jacques

From: "Adrian Crum" <[hidden email]>

> David,
>
> Thank you so much for your work on this! Combined with the forthcoming press release, I believe OFBiz will be entering a new era.
>
> -Adrian
>
>
> --- On Fri, 4/17/09, David E Jones <[hidden email]> wrote:
>
>> From: David E Jones <[hidden email]>
>> Subject: Re: [VOTE][RESULT] Create Release Branch 2009.04
>> To: [hidden email]
>> Date: Friday, April 17, 2009, 2:08 AM
>> Okay, at long last the release branch is created. The URL
>> for it is:
>>
>> https://svn.apache.org/repos/asf/ofbiz/branches/release09.04
>>
>> Tim Ruppert will be heading up build and demo resources for
>> this in the near future, and for now it is in SVN.
>>
>> Just as with the release4.0 branch this now means as
>> contributors to the trunk we should watch out for fixes that
>> should also go into the branch and apply them there as well.
>>
>> Thanks to everyone who has helped, and everyone who is
>> continuing to help, with this.
>>
>> -David
>>
>>
>> On Apr 15, 2009, at 11:59 PM, David E Jones wrote:
>>
>> >
>> > [+1] Binding: David, Adrian, Anil, Scott, Jacopo
>> > [+1] Non-binding: Sam, Tim, Ashish, Vikas, Bruno,
>> Pranay, Shi, Marco, Ravindra
>> > [+0]: 0
>> > [-1]: 0
>> >
>> > Based on this result (more than 3 binding +1 votes and
>> more +1 than -1 votes) the vote has passed.
>> >
>> > In respect for comments about the time, I'll wait
>> for about 12 hours more from the time of this email (that
>> makes it mid-day Thursday my time) to do the actual branch.
>> If anyone would like to vote after this that's fine, but
>> unless something major comes up we'll consider this vote
>> binding and do the release branch as has been planned for
>> (though ~1.5 days after). With that timing the press release
>> should go out early (probably Monday) of next week, for
>> those interested in such things.
>> >
>> > -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
>> >>
>> >
>
>
>      
>

[Ashish Vijaywargiya]

Thanks David for creating the branch release.

Thanks to everybody who is involved directly / indirectly in the project !

--
Ashish Vijaywargiya

On Fri, Apr 17, 2009 at 3:10 PM, Jacques Le Roux <
[hidden email]> wrote:

> Yes, thank you David, and thank you also to all the people that made this
> new step for OFBiz possible!
>
> Jacques
>
> From: "Adrian Crum" <[hidden email]>
>
>> David,
>>
>>
>> Thank you so much for your work on this! Combined with the forthcoming
>> press release, I believe OFBiz will be entering a new era.
>>
>> -Adrian
>>
>>
>>

[Pranay Pandey-2]

Thanks David.

This is another milestone achieved by OFBiz community. Congratulations  
to all involved in the project.

Regards
--
Pranay Pandey




On Apr 17, 2009, at 3:49 PM, Ashish Vijaywargiya wrote:

> Thanks David for creating the branch release.
>
> Thanks to everybody who is involved directly / indirectly in the  
> project !
>
> --
> Ashish Vijaywargiya
>
> On Fri, Apr 17, 2009 at 3:10 PM, Jacques Le Roux <
> [hidden email]> wrote:
>
>> Yes, thank you David, and thank you also to all the people that  
>> made this
>> new step for OFBiz possible!
>>
>> Jacques
>>
>> From: "Adrian Crum" <[hidden email]>
>>
>>> David,
>>>
>>>
>>> Thank you so much for your work on this! Combined with the  
>>> forthcoming
>>> press release, I believe OFBiz will be entering a new era.
>>>
>>> -Adrian
>>>
>>>
>>>

[Bruno Busco]

Best wishes to OFBiz 9.4 !!!!!
Many thanks to everyone !!!!
-Bruno

2009/4/17 Pranay Pandey <[hidden email]>

> Thanks David.
>
> This is another milestone achieved by OFBiz community. Congratulations to
> all involved in the project.
>
> Regards
> --
> Pranay Pandey
>
>
>
>
>
> On Apr 17, 2009, at 3:49 PM, Ashish Vijaywargiya wrote:
>
>  Thanks David for creating the branch release.
>>
>> Thanks to everybody who is involved directly / indirectly in the project !
>>
>> --
>> Ashish Vijaywargiya
>>
>> On Fri, Apr 17, 2009 at 3:10 PM, Jacques Le Roux <
>> [hidden email]> wrote:
>>
>>  Yes, thank you David, and thank you also to all the people that made this
>>> new step for OFBiz possible!
>>>
>>> Jacques
>>>
>>> From: "Adrian Crum" <[hidden email]>
>>>
>>>  David,
>>>>
>>>>
>>>> Thank you so much for your work on this! Combined with the forthcoming
>>>> press release, I believe OFBiz will be entering a new era.
>>>>
>>>> -Adrian
>>>>
>>>>
>>>>
>>>>
>

[guo weizhan]

I miss this list before :(

Congratulations!

Thanks to everyone.
Weizhan Guo
2009/4/18 Bruno Busco <[hidden email]>

> Best wishes to OFBiz 9.4 !!!!!
> Many thanks to everyone !!!!
> -Bruno
>
> 2009/4/17 Pranay Pandey <[hidden email]>
>
> > Thanks David.
> >
> > This is another milestone achieved by OFBiz community. Congratulations to
> > all involved in the project.
> >
> > Regards
> > --
> > Pranay Pandey
> >
> >
> >
> >
> >
> > On Apr 17, 2009, at 3:49 PM, Ashish Vijaywargiya wrote:
> >
> >  Thanks David for creating the branch release.
> >>
> >> Thanks to everybody who is involved directly / indirectly in the project
> !
> >>
> >> --
> >> Ashish Vijaywargiya
> >>
> >> On Fri, Apr 17, 2009 at 3:10 PM, Jacques Le Roux <
> >> [hidden email]> wrote:
> >>
> >>  Yes, thank you David, and thank you also to all the people that made
> this
> >>> new step for OFBiz possible!
> >>>
> >>> Jacques
> >>>
> >>> From: "Adrian Crum" <[hidden email]>
> >>>
> >>>  David,
> >>>>
> >>>>
> >>>> Thank you so much for your work on this! Combined with the forthcoming
> >>>> press release, I believe OFBiz will be entering a new era.
> >>>>
> >>>> -Adrian
> >>>>
> >>>>
> >>>>
> >>>>
> >
>