sorry, i meant to say open bugs. the plan is to cut a release based on
the current 3.3 branch.
ben
On 02/17/2011 12:26 AM, Flavio Junqueira wrote:
-1. Your original proposal didn't suggest to discard all currently
marked 3.3.3. In fact, I'm not even sure how you'd do it given that I
think some have already been committed.
-Flavio
On Feb 17, 2011, at 6:21 AM, Benjamin Reed wrote:
ok, we have a lazy majority. i'll declare the vote as passed :)
i want to get this release out right away to get out the fix for the
major bug we resolved recently, so all of the bugs currently marked for
3.3.3 will not be included, although i really would like to get
ZOOKEEPER-960 in, but i don't really want to hold up the release. i'll
try to package something up by tomorrow.
ben
On 02/09/2011 11:55 PM, Henry Robinson wrote:
+1, thanks for taking the lead.
On 8 February 2011 13:31, Mahadev Konar<[email protected]
<mailto:[email protected]>> wrote:
+1. You could have used some phrases with your +1 so that folks
understood that you +1'ed your own proposal :).
thanks
mahadev
On Tue, Feb 8, 2011 at 1:14 PM, Benjamin Reed<[email protected]
<mailto:[email protected]>> wrote:
i would like to propose that we do a 3.3.3 release based on the
current
3.3
branch with myself, benjamin reed, as the release manager. that branch
has a
critical bug fix (ZOOKEEPER-962) that we need to get out asap. as
per the
bylaws, this vote will conclude in the next three days, and if
accepted,
i
plan to build the 3.3.3 release to be ready for a vote on 2/14.
+1
ben
*flavio*
*junqueira*
research scientist
[email protected] <mailto:[email protected]>
direct +34 93-183-8828
avinguda diagonal 177, 8th floor, barcelona, 08018, es
phone (408) 349 3300fax (408) 349 3301
