Mailing-List: contact dev-help@accumulo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@accumulo.apache.org
MIME-Version: 1.0
Reply-To: vines@apache.org
In-Reply-To: <DAD2663B-A5B4-49AC-B728-F21AE0E83FD3@bbn.com>
References: 
 <CAGHyZ6JH=JBnA9K+QjeFtNinYEuPPu7LDNc8CrQiKD_2K2oBSw@mail.gmail.com>
 <CAGHyZ6JSUxdjHUJAZiaxOebjTdqZ=NWb0x0f4Fw=tDCHFMCTJg@mail.gmail.com>
 <DAD2663B-A5B4-49AC-B728-F21AE0E83FD3@bbn.com>
From: John Vines <vines@apache.org>
Date: Tue, 6 May 2014 13:26:26 -0400
Message-ID: 
 <CADczPYQstwuwkoM9zfnBFhni4UQ58UZYK9QmEb-ncFOvLbcR+w@mail.gmail.com>
Subject: Re: [VOTE] end of life plan for 1.4 branch
To: Accumulo Dev List <dev@accumulo.apache.org>
Content-Type: multipart/alternative; boundary=001a113476de9456e404f8be8ebe

--001a113476de9456e404f8be8ebe
Content-Type: text/plain; charset=UTF-8

+0

I want to EOL 1.4.x but I am having difficulties following this discussion.
If someone could provide a tldr; I will probably change my vote.


On Tue, May 6, 2014 at 12:31 PM, Ryan Leary <ryan@bbn.com> wrote:

> +1
>
> Thanks for encouraging votes from non-committers. I think having three
> major versions simultaneously encourages fragmentation that this project
> does not need.
>
> -Ryan
>
> On May 6, 2014, at 11:47 AM, Sean Busbey <busbey@cloudera.com> wrote:
>
> > This is friendly reminder to everyone that this vote closes today at
> 20:40
> > UTC (about 5 hours from now).
> >
> > Please vote, especially if you are not a committer / PMC member. Ending
> > support for a major branch is something I'd really like as much community
> > input on as possible.
> >
> > For reference, the vote right now is: +3, -2
> >
> > +1: David M., Josh E., Bill H.
> > -1: Christopher T., Keith T.
> >
> > I have seen statements about support or disagreement with different
> > actions, but these are the only clearly stated votes.
> >
> >
> > On Sat, May 3, 2014 at 3:41 PM, Sean Busbey <busbey@cloudera.com> wrote:
> >
> >> Accumulo Folks,
> >>
> >> I would like to declare end of life for the 1.4 branch of development.
> >> It's been active for a little over two years and the release of 1.6.0
> means
> >> we now have three active releases.
> >>
> >> Declaring end of life would mean
> >>
> >> * Posting an ANNOUNCE message to the user list
> >> * No longer accepting issue fix version targets for future 1.4 releases
> >> * Removing fix version targets of 1.4.x for existing open issues
> >> * The end of having a long lived 1.4 related branch in git
> >> * Removing direct references to 1.4.x releases on our download page
> >> * No longer linking to the 1.4 related documentation from the main
> >> navigation area
> >>
> >> Our issue tracker shows that candidate version 1.4.6 currently has:
> >>
> >> * 9 closed issues, none of which are blockers or critical.
> >> * 1 issue in patch available status, marked critical
> >> * 18 open issues with a target fix version of 1.4.6, four of which are
> >> marked critical.
> >>
> >> Because there is existing work, but not yet enough to warrant a
> release, I
> >> propose
> >> that on successful passing of this vote we create a "1.4.6-eol" tag with
> >> the then
> >> current state of the development branch.
> >>
> >> Please vote
> >>
> >> [ ] +1 I am in favor of announcing End of Life according to the above
> plan
> >> [ ] +-0 I am indifferent
> >> [ ] -1 I am opposed to the above End of Life plan because...
> >>
> >> I'm treating this like a release vote. Thus, it will be handled with
> >> Majority Approval:
> >> to pass it will need 3 committers to +1 and more committers voting +1
> than
> >> -1.
> >>
> >> Vote will remain open for 72 hours, until Tuesday, May 6 2014, 20:40 UTC
> >>
> >> --
> >> Sean
> >>
> >
> >
> >
> > --
> > Sean
>
>

--001a113476de9456e404f8be8ebe--