You've had a great track record on keeping 1.4 releases going and I'd hate to hold up things while I try to dig out branch-1.2. Let me get 1.2 to a releasable state and after that I'd be up for scheduling when releases on both branches happen.
On Wed, Aug 15, 2018 at 2:54 PM, Andrew Purtell <andrew.purt...@gmail.com> wrote: > If we want to lock step 1.2 and 1.4 releases for a little while we can do > that. I mean approximately, like within a week or two of each other. We could > agree on a release calendar and then do the RM things when needed. I'd be up > for that. > > >> On Aug 15, 2018, at 12:42 PM, Sean Busbey <bus...@apache.org> wrote: >> >> My hope is that in restarting I'll get the incremental cost of >> maintenance releases down enough that I can be strict on the monthly >> cadence. I don't think the 1.2 -> 1.4 upgrade path is well tested, and >> I anticipate that some changes to 1.2 might be needed to make sure it >> goes smoothly. regular releases make that easier. >> >> >> >>> On Wed, Aug 15, 2018 at 2:19 PM, Mike Drob <md...@apache.org> wrote: >>> How strict do you plan to be with the monthly release cadence? If there's >>> only a few Jira issues resolved on 1.2.x do you still plan to spin those >>> out? I don't understand how doing more releases on the old stable line will >>> incentivize adopters to move to the new stable line. >>> >>> Other than that, announcement seems fine. >>> >>>> On Wed, Aug 15, 2018 at 2:16 PM, Sean Busbey <bus...@apache.org> wrote: >>>> >>>> If anyone has feedback before I send this, please let me know. I've >>>> already updated dist.a.o for the stable line change. I'd like to send >>>> this announcement tomorrow once the mirrors are updated. >>>> >>>> --- >>>> >>>> Hi HBase Community! >>>> >>>> The HBase developers would like you to know that we have updated the >>>> "stable" release pointer to the 1.4.6 release. As future 1.4.z >>>> releases are made the stable pointer will track them. All users of >>>> releases prior to 1.4.6 are advised to upgrade to the new stable >>>> release line. >>>> >>>> The prior stable release line was 1.2.z. I'm in the process of getting >>>> releases on that branch going again. Users of that release line are >>>> advised that once releases start again they will continue monthly for >>>> a period of about 6 months before the branch moves to end-of-life. >>>> >>>> If you are currently a user of a release line older than 1.4 and >>>> there's anything that would make your transition to the stable release >>>> line easier please let us know either via email or JIRAs. >>>>
