i would really like to get 3.3.3 out because of the fixes that just went in.
there are quite a few bugs that are marked for 3.3.3, but i think they
can all be pushed to 3.4.0.
i would really like to push everything to 3.4.0 and then work on getting
the 3.4.0 release out. we haven't done a
On Wed, Jan 26, 2011 at 10:27 AM, Benjamin Reed br...@yahoo-inc.com wrote:
i would really like to get 3.3.3 out because of the fixes that just went in.
there are quite a few bugs that are marked for 3.3.3, but i think they can
all be pushed to 3.4.0.
Any non-blocker jiras are always pushed
On Wed, Jan 26, 2011 at 10:38 AM, Flavio Junqueira f...@yahoo-inc.comwrote:
Ben, Your proposal in general sounds reasonable to me with the exception of
do a release from just a branch if it is something that pops up quickly
right after a
release. I don't see a reason for binding it to time,
One other thing to keep in mind with this model. The RM is responsible for
backporting (or working with the author to backport) any issues that go into
a fix release. Today we require authors to provide patches for both the fix
branch and the trunk (for fixes). If changes are committed to the
this is an interesting read. i'm not a big fan of the even odd numbering
scheme. i'm also unclear how it work. for example, lets say i signed up
to be the RM for 3.4.0. i branch, stabilize the code, and then do a
release. would i also be in charge of 3.4.1? i would hope the answer
would be
sorry, i read your messages backwards. i like your idea.
ben
On 01/26/2011 11:15 AM, Patrick Hunt wrote:
On Wed, Jan 26, 2011 at 10:38 AM, Flavio Junqueiraf...@yahoo-inc.comwrote:
Ben, Your proposal in general sounds reasonable to me with the exception of
do a release from just a branch if
On Wed, Jan 26, 2011 at 12:39 PM, Benjamin Reed br...@yahoo-inc.com wrote:
this is an interesting read. i'm not a big fan of the even odd numbering
scheme. i'm also unclear how it work. for example, lets say i signed up to
be the RM for 3.4.0. i branch, stabilize the code, and then do a
