Hi Camille, unfortunately there's a blocker on 3.3.2 at the moment.
http://bit.ly/asOSNl I just updated that patch to fix a build issue,
hopefully one of the committers can review asap.
Additionally there are a number of other "patch available" patches attached
to 3.3.2. I'd like to get those included give everyone's done a bunch of
work on them. Again, committers need to review/commit/reject appropriately.
What do ppl think, are we pretty close? Ben/Flavio/Henry/Mahadev please
review some of the outstanding patches. Coordinate with me if you have
On Mon, Oct 18, 2010 at 7:56 AM, Fournier, Camille F. [Tech] <
> Hi guys,
> Any updates on the 3.3.2 release schedule? Trying to plan a release myself
> and wondering if I'll have to go to production with patched 3.3.1 or have
> time to QA with the 3.3.2 release.
> -----Original Message-----
> From: Patrick Hunt [mailto:ph...@apache.org]
> Sent: Thursday, September 23, 2010 12:45 PM
> To: firstname.lastname@example.org
> Subject: Fix release 3.3.2 planning, status.
> Looking at the JIRA queue for 3.3.2 I see that there are two blockers, one
> is currently PA and the other is pretty close (it has a patch that should
> in soon).
> There are a few JIRAs that already went into the branch that are important
> to get out there ASAP, esp ZOOKEEPER-846 (fix close issue found by hbase).
> One issue that's been slowing us down is hudson. The trunk was not passing
> it's hudson validation, which was causing a slow down in patch review.
> Mahadev and I fixed this. However with recent changes to the hudson
> hw/security environment the patch testing process (automated) is broken.
> Giri is working on this. In the mean time we'll have to test ourselves.
> Committers -- be sure to verify RAT, Findbugs, etc... in addition to
> verifying via test. I've setup an additional Hudson environment inside
> Cloudera that also verifies the trunk/branch. If issues are found I will
> report them (unfortunately I can't provide access to cloudera's hudson env
> to non-cloudera employees at this time).
> I'd like to clear out the PAs asap and get a release candidate built.
> see a problem with shooting for an RC mid next week?