Hi Tuong, I'm not familiar with the 2 weeks notice for releases you mentioned. But in any case, I'm only talking about branching the code, not doing a release, and I don't know of any rules against branching. I'm totally content with waiting 2 weeks to initiate the actual release process.
On the patch you mentioned, we aren't talking about the same thing and I apologize that my message above wasn't clearer. You are talking about what to do to a project that is dependent on Sentry. I need to update Sentry's dependency on another project (solr-sentry-handlers) and I want to do that for sentry version 1.5-SNAPSHOT, not 1.4. If we don't branch, all the patches that shouldn't go into 1.4, like this one, are basically left in limbo for two weeks. Greg On Thu, Jul 24, 2014 at 1:58 PM, Tuong Tr. <[email protected]> wrote: > Hi Greg, > > The process of bumping release number will be done as part of the release > subtasks. The official Apache release process calls for 2 weeks notice. > It may not be needed for Sentry, but I am also out of the office next week > :)) So we decided to stick to the recommended wait-out. > > For your patch, Sravya's recent commit (5862bbe) has updated the version > to 1.4.0-incubating-SNAPSHOT. If you update your dependency to that, it > will keep you stable and up-to-date until 1.4.0 is released. > > Respectfully, > Tuong > > > On Thursday, July 24, 2014 1:12 PM, Gregory Chanan <[email protected]> > wrote: > > > > Hi Tuong, > > Thanks for taking this on, we definitely appreciate all the effort! > > One thing I haven't seen discussed is what to do about dependency versions > -- are we planning to bump to released versions for 1.4.0, like we did in > 1.3.0 (https://issues.apache.org/jira/browse/SENTRY-171)? > One reason I'm asking is because of SENTRY-354 ( > https://issues.apache.org/jira/browse/SENTRY-354) -- I need to bump a > version number for that patch, but don't think it's appropriate until after > 1.4.0 is brached. To avoid these sorts of issues where trunk progress is > stalled while we "help keep trunk stable", I generally prefer to branch > sooner rather than later. Could you describe why you want to wait 2 > weeks? > > Thanks, > Greg > > > > > On Tue, Jul 22, 2014 at 6:21 PM, Tuong Tr. <[email protected]> > wrote: > > > Hi Sentry Community, > > > > As you may know, we are getting ready to release Sentry 1.4.0. > > Our plan is to branch on Tuesday, August 5th. > > > > There are currently about 24 unresolved JIRAs that have > > fix-version as 1.4.0. By EOD today, I will move all those to the next > > release. > > If you would like to commit > > any of these JIRAs into 1.4.0 release, you will need to change the > > fix-version back to > > 1.4.0. > > > > Please help keep trunk > > stable in the next 2 weeks so we can have a smooth release. > > > > SENTRY-365 (https://issues.apache.org/jira/browse/SENTRY-356) has been > > created to track the release activity. > > > > > > Let me know if you any question or > > suggestion. > > > > Respectfully, > > Tuong >
