You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@openjpa.apache.org by Donald Woods <dw...@apache.org> on 2010/03/04 17:28:59 UTC
[DISCUSS] Upcoming OpenJPA 2.0.0 release plans
As we're winding down the changes for the 2.0.0 release, I wanted to
alert everyone to the proposed release dates.
3/19 - Cut 2.0 branch
4/12 - Start release candidate vote
Once the branch is created, only changes approved by myself or Kevin
will be accepted into the branch. Trunk (probably renamed to 2.1) will
still be open for any changes.
Also, please use this email thread to discuss any critical patches that
you would like to see considered for 2.0.0.
Thanks,
Donald
Re: [DISCUSS] Upcoming OpenJPA 2.0.0 release plans
Posted by Craig L Russell <Cr...@Sun.COM>.
Hi Donald,
I'd like to get OPENJPA-1530 into the 2.0.0 release. It allows schema
generation for non-innodb MySQL storage engines (needed to test MySQL
cluster for example).
It would be great if someone could review the patch...
Thanks,
Craig
On Mar 4, 2010, at 8:28 AM, Donald Woods wrote:
> As we're winding down the changes for the 2.0.0 release, I wanted to
> alert everyone to the proposed release dates.
>
> 3/19 - Cut 2.0 branch
> 4/12 - Start release candidate vote
>
> Once the branch is created, only changes approved by myself or Kevin
> will be accepted into the branch. Trunk (probably renamed to 2.1)
> will
> still be open for any changes.
>
> Also, please use this email thread to discuss any critical patches
> that
> you would like to see considered for 2.0.0.
>
>
> Thanks,
> Donald
Craig L Russell
Architect, Sun Java Enterprise System http://db.apache.org/jdo
408 276-5638 mailto:Craig.Russell@sun.com
P.S. A good JDO? O, Gasp!
Re: [DISCUSS] Upcoming OpenJPA 2.0.0 release plans
Posted by Craig L Russell <Cr...@Sun.COM>.
Hi Donald,
I'd like to get OPENJPA-1530 into the 2.0.0 release. It allows schema
generation for non-innodb MySQL storage engines (needed to test MySQL
cluster for example).
It would be great if someone could review the patch...
Thanks,
Craig
On Mar 4, 2010, at 8:28 AM, Donald Woods wrote:
> As we're winding down the changes for the 2.0.0 release, I wanted to
> alert everyone to the proposed release dates.
>
> 3/19 - Cut 2.0 branch
> 4/12 - Start release candidate vote
>
> Once the branch is created, only changes approved by myself or Kevin
> will be accepted into the branch. Trunk (probably renamed to 2.1)
> will
> still be open for any changes.
>
> Also, please use this email thread to discuss any critical patches
> that
> you would like to see considered for 2.0.0.
>
>
> Thanks,
> Donald
Craig L Russell
Architect, Sun Java Enterprise System http://db.apache.org/jdo
408 276-5638 mailto:Craig.Russell@sun.com
P.S. A good JDO? O, Gasp!
Re: [DISCUSS] Upcoming OpenJPA 2.0.0 release plans
Posted by Donald Woods <dw...@apache.org>.
Everyone, please review the JIRAs you have assigned to you today and
either unassign yourself if you are not going to work on them, move them
to 2.1.0 (soon to be trunk) or remove the Fix Version so they'll be
placed in the backlog. There are currently 43 issues assigned to the
2.0.0 release, which only a handful will be resolved before the 2.0.0
release.
I plan on cutting the 2.0.x branch later today and will start moving any
JIRAs left in 2.0.0 to either 2.1.0 or backlog as part of preparing the
branch for a beta3 release.
Thanks,
Donald
On 3/4/10 11:28 AM, Donald Woods wrote:
> As we're winding down the changes for the 2.0.0 release, I wanted to
> alert everyone to the proposed release dates.
>
> 3/19 - Cut 2.0 branch
> 4/12 - Start release candidate vote
>
> Once the branch is created, only changes approved by myself or Kevin
> will be accepted into the branch. Trunk (probably renamed to 2.1) will
> still be open for any changes.
>
> Also, please use this email thread to discuss any critical patches that
> you would like to see considered for 2.0.0.
>
>
> Thanks,
> Donald
>
Re: [DISCUSS] Upcoming OpenJPA 2.0.0 release plans
Posted by Kevin Sutter <kw...@gmail.com>.
+1
On Fri, Mar 19, 2010 at 11:26 AM, No1UNo <je...@jerrycarter.org> wrote:
>
>
> DWoods wrote:
> > Also, I'm toying with the idea of creating a 2.0.0-beta3 once the branch
> > is cut, as there are still some maven-release-plugin issues I'd like to
> > work through again before we get to cutting our final 2.0.0 release and
> > we've had great feedback and testing on beta and beta2 with several new
> > bugs reported, so it'd be nice to have another round of real world
> > testing from users, too.
>
> I must second the idea of publishing beta3. This nicely fills the gap
> between beta2 and the 2.0.0 release.
> --
> View this message in context:
> http://n2.nabble.com/DISCUSS-Upcoming-OpenJPA-2-0-0-release-plans-tp4675401p4764045.html
> Sent from the OpenJPA Developers mailing list archive at Nabble.com.
>
Re: [DISCUSS] Upcoming OpenJPA 2.0.0 release plans
Posted by No1UNo <je...@jerrycarter.org>.
DWoods wrote:
> Also, I'm toying with the idea of creating a 2.0.0-beta3 once the branch
> is cut, as there are still some maven-release-plugin issues I'd like to
> work through again before we get to cutting our final 2.0.0 release and
> we've had great feedback and testing on beta and beta2 with several new
> bugs reported, so it'd be nice to have another round of real world
> testing from users, too.
I must second the idea of publishing beta3. This nicely fills the gap
between beta2 and the 2.0.0 release.
--
View this message in context: http://n2.nabble.com/DISCUSS-Upcoming-OpenJPA-2-0-0-release-plans-tp4675401p4764045.html
Sent from the OpenJPA Developers mailing list archive at Nabble.com.
Re: [DISCUSS] Upcoming OpenJPA 2.0.0 release plans
Posted by Donald Woods <dw...@apache.org>.
I've got a few last minute JIRAs that I'm working on (1097, 1524, 1550,
1571, ...) as several others like Jeremy, Pinaki, Rick, .... do.
So in reality, it looks like the target for creating the 2.0 branch and
moving trunk to 2.1-SNAPSHOT will be end-of-day Monday, March 22. But
please, don't see this as an open invitation to flood 2.0 with a lot of
last minute code patches (docs and junit updates are more than welcome),
as we still need to keep trunk stable and ready for a release. If there
are any questions about a patch, please discuss on this thread before
committing.
Also, I'm toying with the idea of creating a 2.0.0-beta3 once the branch
is cut, as there are still some maven-release-plugin issues I'd like to
work through again before we get to cutting our final 2.0.0 release and
we've had great feedback and testing on beta and beta2 with several new
bugs reported, so it'd be nice to have another round of real world
testing from users, too.
Thanks,
-Donald
On 3/4/10 11:28 AM, Donald Woods wrote:
> As we're winding down the changes for the 2.0.0 release, I wanted to
> alert everyone to the proposed release dates.
>
> 3/19 - Cut 2.0 branch
> 4/12 - Start release candidate vote
>
> Once the branch is created, only changes approved by myself or Kevin
> will be accepted into the branch. Trunk (probably renamed to 2.1) will
> still be open for any changes.
>
> Also, please use this email thread to discuss any critical patches that
> you would like to see considered for 2.0.0.
>
>
> Thanks,
> Donald
>
Re: Re: [DISCUSS] Upcoming OpenJPA 2.0.0 release plans
Posted by Kevin Sutter <kw...@gmail.com>.
Hi Milosz,
I actually thought we were doing a pretty good job of updating the
documentation for the new JPA 2 level of functionality as we were
integrating the code changes. Not sure what aspect of lock modes you are
referring to. I can see where we have defined the new JPA 2 lock mode as
well as kept the old openjpa lock modes.
So, personally, I don't think we're too far off. Of course, with enough
examples, I can be educated... :-) I know that we have your general doc
update JIRA. But, maybe we need to open subtasks for the larger areas of
the documentation that still need some work.
Thoughts?
Kevin
On Mon, Mar 15, 2010 at 4:30 PM, Miłosz <mt...@o2.pl> wrote:
> Hi All,
>
> What worries me is that our documentation is still a JPA 1 documentation in
> many places. For example we say only two lock modes are available,
> subqueries are possible only in WHERE clause, etc. That is confusing,
> especially for JPA new-comers and might turn into quite a big job. I am
> currently correcting the user manual in small steps but not able by any
> chance to fix all the scattered inaccuracies before 2.0 time.
>
> Regards,
> Milosz
>
> > As we approach the March 19 branch creation for 2.0.0, please take time
> > to review JIRA issues that either you have opened or are assigned to
> > where the Fix Version is 2.0.0 or 2.0.1 and start reassigning to:
> >
> > 2.0.1 - maintenance release, which will not be open to just any patch
> > 2.1.0 - next trunk release, which will be open to any patches
> > None - you have no intention of working on the issue in the foreseeable
> > future
> >
> >
> > Thanks,
> > Donald
> >
> >
> > On 3/4/10 11:28 AM, Donald Woods wrote:
> > > As we're winding down the changes for the 2.0.0 release, I wanted to
> > > alert everyone to the proposed release dates.
> > >
> > > 3/19 - Cut 2.0 branch
> > > 4/12 - Start release candidate vote
> > >
> > > Once the branch is created, only changes approved by myself or Kevin
> > > will be accepted into the branch. Trunk (probably renamed to 2.1) will
> > > still be open for any changes.
> > >
> > > Also, please use this email thread to discuss any critical patches that
> > > you would like to see considered for 2.0.0.
> > >
> > >
> > > Thanks,
> > > Donald
> > >
>
>
Re: Re: [DISCUSS] Upcoming OpenJPA 2.0.0 release plans
Posted by Miłosz <mt...@o2.pl>.
Hi All,
What worries me is that our documentation is still a JPA 1 documentation in many places. For example we say only two lock modes are available, subqueries are possible only in WHERE clause, etc. That is confusing, especially for JPA new-comers and might turn into quite a big job. I am currently correcting the user manual in small steps but not able by any chance to fix all the scattered inaccuracies before 2.0 time.
Regards,
Milosz
> As we approach the March 19 branch creation for 2.0.0, please take time
> to review JIRA issues that either you have opened or are assigned to
> where the Fix Version is 2.0.0 or 2.0.1 and start reassigning to:
>
> 2.0.1 - maintenance release, which will not be open to just any patch
> 2.1.0 - next trunk release, which will be open to any patches
> None - you have no intention of working on the issue in the foreseeable
> future
>
>
> Thanks,
> Donald
>
>
> On 3/4/10 11:28 AM, Donald Woods wrote:
> > As we're winding down the changes for the 2.0.0 release, I wanted to
> > alert everyone to the proposed release dates.
> >
> > 3/19 - Cut 2.0 branch
> > 4/12 - Start release candidate vote
> >
> > Once the branch is created, only changes approved by myself or Kevin
> > will be accepted into the branch. Trunk (probably renamed to 2.1) will
> > still be open for any changes.
> >
> > Also, please use this email thread to discuss any critical patches that
> > you would like to see considered for 2.0.0.
> >
> >
> > Thanks,
> > Donald
> >
Re: [DISCUSS] Upcoming OpenJPA 2.0.0 release plans
Posted by Donald Woods <dw...@apache.org>.
As we approach the March 19 branch creation for 2.0.0, please take time
to review JIRA issues that either you have opened or are assigned to
where the Fix Version is 2.0.0 or 2.0.1 and start reassigning to:
2.0.1 - maintenance release, which will not be open to just any patch
2.1.0 - next trunk release, which will be open to any patches
None - you have no intention of working on the issue in the foreseeable
future
Thanks,
Donald
On 3/4/10 11:28 AM, Donald Woods wrote:
> As we're winding down the changes for the 2.0.0 release, I wanted to
> alert everyone to the proposed release dates.
>
> 3/19 - Cut 2.0 branch
> 4/12 - Start release candidate vote
>
> Once the branch is created, only changes approved by myself or Kevin
> will be accepted into the branch. Trunk (probably renamed to 2.1) will
> still be open for any changes.
>
> Also, please use this email thread to discuss any critical patches that
> you would like to see considered for 2.0.0.
>
>
> Thanks,
> Donald
>
Re: [DISCUSS] Upcoming OpenJPA 2.0.0 release plans
Posted by Donald Woods <dw...@apache.org>.
OK, all issues that I've heard about are in 2.0.0, so unless someone
speaks up in the next hour, I'll start creating the release candidate.
-Donald
On 4/10/10 4:15 PM, Donald Woods wrote:
> OK, due to the JIRA outage yesterday and some last minute fixes, the
> latest ETA for creating a release candidate build is Sunday.
>
> We still need to get OPENJPA-1625 integrated and I'm working on
> OPENJPA-1179.
>
>
> -Donald
>
>
> On 4/9/10 4:12 PM, Donald Woods wrote:
>> OK, we're in the final countdown to cutting a 2.0.0 release candidate.
>> Once JIRA and cwiki are back up, I'll finish updating the release notes
>> and start cutting a RC for a vote.
>>
>>
>> -Donald
>>
>>
>> On 3/4/10 11:28 AM, Donald Woods wrote:
>>> As we're winding down the changes for the 2.0.0 release, I wanted to
>>> alert everyone to the proposed release dates.
>>>
>>> 3/19 - Cut 2.0 branch
>>> 4/12 - Start release candidate vote
>>>
>>> Once the branch is created, only changes approved by myself or Kevin
>>> will be accepted into the branch. Trunk (probably renamed to 2.1) will
>>> still be open for any changes.
>>>
>>> Also, please use this email thread to discuss any critical patches that
>>> you would like to see considered for 2.0.0.
>>>
>>>
>>> Thanks,
>>> Donald
>>>
>>
>
Re: [DISCUSS] Upcoming OpenJPA 2.0.0 release plans
Posted by Donald Woods <dw...@apache.org>.
OK, due to the JIRA outage yesterday and some last minute fixes, the
latest ETA for creating a release candidate build is Sunday.
We still need to get OPENJPA-1625 integrated and I'm working on
OPENJPA-1179.
-Donald
On 4/9/10 4:12 PM, Donald Woods wrote:
> OK, we're in the final countdown to cutting a 2.0.0 release candidate.
> Once JIRA and cwiki are back up, I'll finish updating the release notes
> and start cutting a RC for a vote.
>
>
> -Donald
>
>
> On 3/4/10 11:28 AM, Donald Woods wrote:
>> As we're winding down the changes for the 2.0.0 release, I wanted to
>> alert everyone to the proposed release dates.
>>
>> 3/19 - Cut 2.0 branch
>> 4/12 - Start release candidate vote
>>
>> Once the branch is created, only changes approved by myself or Kevin
>> will be accepted into the branch. Trunk (probably renamed to 2.1) will
>> still be open for any changes.
>>
>> Also, please use this email thread to discuss any critical patches that
>> you would like to see considered for 2.0.0.
>>
>>
>> Thanks,
>> Donald
>>
>
Re: [DISCUSS] Upcoming OpenJPA 2.0.0 release plans
Posted by Donald Woods <dw...@apache.org>.
OK, we're in the final countdown to cutting a 2.0.0 release candidate.
Once JIRA and cwiki are back up, I'll finish updating the release notes
and start cutting a RC for a vote.
-Donald
On 3/4/10 11:28 AM, Donald Woods wrote:
> As we're winding down the changes for the 2.0.0 release, I wanted to
> alert everyone to the proposed release dates.
>
> 3/19 - Cut 2.0 branch
> 4/12 - Start release candidate vote
>
> Once the branch is created, only changes approved by myself or Kevin
> will be accepted into the branch. Trunk (probably renamed to 2.1) will
> still be open for any changes.
>
> Also, please use this email thread to discuss any critical patches that
> you would like to see considered for 2.0.0.
>
>
> Thanks,
> Donald
>
Re: [DISCUSS] Upcoming OpenJPA 2.0.0 release plans
Posted by Donald Woods <dw...@apache.org>.
I've got a few last minute JIRAs that I'm working on (1097, 1524, 1550,
1571, ...) as several others like Jeremy, Pinaki, Rick, .... do.
So in reality, it looks like the target for creating the 2.0 branch and
moving trunk to 2.1-SNAPSHOT will be end-of-day Monday, March 22. But
please, don't see this as an open invitation to flood 2.0 with a lot of
last minute code patches (docs and junit updates are more than welcome),
as we still need to keep trunk stable and ready for a release. If there
are any questions about a patch, please discuss on this thread before
committing.
Also, I'm toying with the idea of creating a 2.0.0-beta3 once the branch
is cut, as there are still some maven-release-plugin issues I'd like to
work through again before we get to cutting our final 2.0.0 release and
we've had great feedback and testing on beta and beta2 with several new
bugs reported, so it'd be nice to have another round of real world
testing from users, too.
Thanks,
-Donald
On 3/4/10 11:28 AM, Donald Woods wrote:
> As we're winding down the changes for the 2.0.0 release, I wanted to
> alert everyone to the proposed release dates.
>
> 3/19 - Cut 2.0 branch
> 4/12 - Start release candidate vote
>
> Once the branch is created, only changes approved by myself or Kevin
> will be accepted into the branch. Trunk (probably renamed to 2.1) will
> still be open for any changes.
>
> Also, please use this email thread to discuss any critical patches that
> you would like to see considered for 2.0.0.
>
>
> Thanks,
> Donald
>
Re: [DISCUSS] Upcoming OpenJPA 2.0.0 release plans
Posted by Donald Woods <dw...@apache.org>.
One minor clarification - Doc and junit updates can be made to the 2.0.x
branch w/o prior RTC approval. Just verify that the new tests work on
more than Derby before committing...
-Donald
On 3/22/10 10:42 PM, Donald Woods wrote:
> Branch for 2.0 has been created -
> https://svn.apache.org/repos/asf/openjpa/branches/2.0.x/
> Please remember that 2.0.x branch is now under RTC (Review Then Commit)
> and any changes should be reviewed in a JIRA and then approved by
> myself, Mike Dick or Kevin Sutter before committing.
>
> Trunk is now 2.1.0-SNAPSHOT and open for business under the normal CTR
> (Commit Then Review) process.
>
>
> -Donald
>
>
> On 3/4/10 11:28 AM, Donald Woods wrote:
>> As we're winding down the changes for the 2.0.0 release, I wanted to
>> alert everyone to the proposed release dates.
>>
>> 3/19 - Cut 2.0 branch
>> 4/12 - Start release candidate vote
>>
>> Once the branch is created, only changes approved by myself or Kevin
>> will be accepted into the branch. Trunk (probably renamed to 2.1) will
>> still be open for any changes.
>>
>> Also, please use this email thread to discuss any critical patches that
>> you would like to see considered for 2.0.0.
>>
>>
>> Thanks,
>> Donald
>>
>
Re: [DISCUSS] Upcoming OpenJPA 2.0.0 release plans
Posted by Donald Woods <dw...@apache.org>.
Branch for 2.0 has been created -
https://svn.apache.org/repos/asf/openjpa/branches/2.0.x/
Please remember that 2.0.x branch is now under RTC (Review Then Commit)
and any changes should be reviewed in a JIRA and then approved by
myself, Mike Dick or Kevin Sutter before committing.
Trunk is now 2.1.0-SNAPSHOT and open for business under the normal CTR
(Commit Then Review) process.
-Donald
On 3/4/10 11:28 AM, Donald Woods wrote:
> As we're winding down the changes for the 2.0.0 release, I wanted to
> alert everyone to the proposed release dates.
>
> 3/19 - Cut 2.0 branch
> 4/12 - Start release candidate vote
>
> Once the branch is created, only changes approved by myself or Kevin
> will be accepted into the branch. Trunk (probably renamed to 2.1) will
> still be open for any changes.
>
> Also, please use this email thread to discuss any critical patches that
> you would like to see considered for 2.0.0.
>
>
> Thanks,
> Donald
>
Re: [DISCUSS] Upcoming OpenJPA 2.0.0 release plans
Posted by Donald Woods <dw...@apache.org>.
Branch for 2.0 has been created -
https://svn.apache.org/repos/asf/openjpa/branches/2.0.x/
Please remember that 2.0.x branch is now under RTC (Review Then Commit)
and any changes should be reviewed in a JIRA and then approved by
myself, Mike Dick or Kevin Sutter before committing.
Trunk is now 2.1.0-SNAPSHOT and open for business under the normal CTR
(Commit Then Review) process.
-Donald
On 3/4/10 11:28 AM, Donald Woods wrote:
> As we're winding down the changes for the 2.0.0 release, I wanted to
> alert everyone to the proposed release dates.
>
> 3/19 - Cut 2.0 branch
> 4/12 - Start release candidate vote
>
> Once the branch is created, only changes approved by myself or Kevin
> will be accepted into the branch. Trunk (probably renamed to 2.1) will
> still be open for any changes.
>
> Also, please use this email thread to discuss any critical patches that
> you would like to see considered for 2.0.0.
>
>
> Thanks,
> Donald
>
Re: [DISCUSS] Upcoming OpenJPA 2.0.0 release plans
Posted by Michael Dick <mi...@gmail.com>.
I'll second OPENJPA-1604.
I'd also vote for including OPENJPA-1609 which I think is a minor fix and
the potential for regression is similarly small. I've also spoken with Jody
and I think he has a fix nearly ready.
-mike
On Wed, Apr 7, 2010 at 11:16 AM, Jeremy Bauer <te...@gmail.com> wrote:
> I think we should try to get the basic OpenJPA 1.x compatibility issue
> described in OpenJPA-1604 fixed in the base release. (There's a larger
> issued defined in the JIRA, but if possible, that could/should be queued
> for
> a future release.) The lack of pessimistic locking may result in data
> integrity issues in certain scenarios.
>
> -Jeremy
>
> On Tue, Apr 6, 2010 at 9:20 PM, Donald Woods <dw...@apache.org> wrote:
>
> > Just a reminder, we're less than a week away from a 2.0.0 release
> > candidate..... Are there any show stoppers or critical bugs that anyone
> > knows of that need to be addressed before we cut a RC build?
> >
> >
> > -Donald
> >
> >
> > On 3/4/10 11:28 AM, Donald Woods wrote:
> > > As we're winding down the changes for the 2.0.0 release, I wanted to
> > > alert everyone to the proposed release dates.
> > >
> > > 3/19 - Cut 2.0 branch
> > > 4/12 - Start release candidate vote
> > >
> > > Once the branch is created, only changes approved by myself or Kevin
> > > will be accepted into the branch. Trunk (probably renamed to 2.1) will
> > > still be open for any changes.
> > >
> > > Also, please use this email thread to discuss any critical patches that
> > > you would like to see considered for 2.0.0.
> > >
> > >
> > > Thanks,
> > > Donald
> > >
> >
>
Re: [DISCUSS] Upcoming OpenJPA 2.0.0 release plans
Posted by Jeremy Bauer <te...@gmail.com>.
I think we should try to get the basic OpenJPA 1.x compatibility issue
described in OpenJPA-1604 fixed in the base release. (There's a larger
issued defined in the JIRA, but if possible, that could/should be queued for
a future release.) The lack of pessimistic locking may result in data
integrity issues in certain scenarios.
-Jeremy
On Tue, Apr 6, 2010 at 9:20 PM, Donald Woods <dw...@apache.org> wrote:
> Just a reminder, we're less than a week away from a 2.0.0 release
> candidate..... Are there any show stoppers or critical bugs that anyone
> knows of that need to be addressed before we cut a RC build?
>
>
> -Donald
>
>
> On 3/4/10 11:28 AM, Donald Woods wrote:
> > As we're winding down the changes for the 2.0.0 release, I wanted to
> > alert everyone to the proposed release dates.
> >
> > 3/19 - Cut 2.0 branch
> > 4/12 - Start release candidate vote
> >
> > Once the branch is created, only changes approved by myself or Kevin
> > will be accepted into the branch. Trunk (probably renamed to 2.1) will
> > still be open for any changes.
> >
> > Also, please use this email thread to discuss any critical patches that
> > you would like to see considered for 2.0.0.
> >
> >
> > Thanks,
> > Donald
> >
>
Re: [DISCUSS] Upcoming OpenJPA 2.0.0 release plans
Posted by Donald Woods <dw...@apache.org>.
Just a reminder, we're less than a week away from a 2.0.0 release
candidate..... Are there any show stoppers or critical bugs that anyone
knows of that need to be addressed before we cut a RC build?
-Donald
On 3/4/10 11:28 AM, Donald Woods wrote:
> As we're winding down the changes for the 2.0.0 release, I wanted to
> alert everyone to the proposed release dates.
>
> 3/19 - Cut 2.0 branch
> 4/12 - Start release candidate vote
>
> Once the branch is created, only changes approved by myself or Kevin
> will be accepted into the branch. Trunk (probably renamed to 2.1) will
> still be open for any changes.
>
> Also, please use this email thread to discuss any critical patches that
> you would like to see considered for 2.0.0.
>
>
> Thanks,
> Donald
>