On Sat, Jul 20, 2013 at 8:05 PM, Leif Hedstrom <zw...@apache.org> wrote:
> On 7/15/13 2:28 PM, Leif Hedstrom wrote: > >> I'd like to prepare the v3.3.5 release on Friday this week. Anything left >> in v3.3.5 by the end of business day Friday would then be moved out to >> v3.3.6 (and probably therefore, v3.5.0). This puts us at a release date for >> v3.3.5 for 7/24, and hopefully v4.0 about 2 weeks after that. For the >> records, this is over 2 months later than planned. >> > > So, seems I was overly optimistic, we need another 2 weeks to get v3.3.5 > ready. Here's the new plan: > > 1. v3.3.5 is branched / cut on Friday 8/2. Please lets make sure there are > no show stoppers left in v3.3.x by this time. I will also cut the v3.4.0 > branch on this day. > > 2. We call the vote for v3.3.5 on Wednesday 8/7. > > 3. People test v3.3.5 thoroughly for the next 2 weeks. Documentation and > other trivial changes can also be committed, but anything major would cause > us to have to prepare a new developer release. > > 4. Assuming there are no showstoppers, v3.3.5 + docs/trivial changes > becomes the v3.4.0 release candidate on Thursday 8/22. > > 5. We call the vote for v3.4.0 on Monday 8/26 (this is a shorter release > cycle than the 5 days we agreed on, but there should be no major changes > here). > > > This is roughly 10 weeks delayed. I will make a better schedule next > release (assuming we keep our yearly stable release cycles), such that we > can release 3.6 (or v4.0 or whatever) in June 2014. > > Cheers, > > -- Leif > > The following bugs are currently marked blockers, and needs to be resolved > for v3.3.5: > > https://issues.apache.org/**jira/browse/TS-2051<https://issues.apache.org/jira/browse/TS-2051> > https://issues.apache.org/**jira/browse/TS-2052<https://issues.apache.org/jira/browse/TS-2052> > https://issues.apache.org/**jira/browse/TS-2021<https://issues.apache.org/jira/browse/TS-2021> > https://issues.apache.org/**jira/browse/TS-2053<https://issues.apache.org/jira/browse/TS-2053> > > > A few of these don't have an owner, we need people to help out here to get > SSL into releasable shape. > > Also https://issues.apache.org/jira/browse/TS-2054 Leif was not able to reproduce this, but I was able to verify it with a few versions and verify that it works in an older but recent version of master.
