You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hbase.apache.org by Andrew Purtell <ap...@apache.org> on 2017/06/30 21:37:18 UTC

Branching branch-1.4, volunteering to RM branch-1.4

Greeting HBasers,

It's my intention to create a new release branch, branch-1.4, as seed for a
new 1.4.x code line, with a 1.4.0 release coming within the next two months.

I would like to volunteer to RM this branch.

I would like to create the new branch in ASF git, branch-1.4, as early as
next week.

There are a number of contributions from my colleagues and others that have
been sitting in branch-1 for about a year. As time goes on it will be more
and more difficult to stabilize the current head of branch-1 for release.
There is no time like the present to begin, so let's begin next week!

If you have concerns, please, let's discuss. (smile)


-- 
Best regards,
Andrew

Re: Branching branch-1.4, volunteering to RM branch-1.4

Posted by Stack <st...@duboce.net>.
On Fri, Jun 30, 2017 at 2:37 PM, Andrew Purtell <ap...@apache.org> wrote:

> Greeting HBasers,
>
> It's my intention to create a new release branch, branch-1.4, as seed for a
> new 1.4.x code line, with a 1.4.0 release coming within the next two
> months.
>
> I would like to volunteer to RM this branch.
>
> I would like to create the new branch in ASF git, branch-1.4, as early as
> next week.
>
> There are a number of contributions from my colleagues and others that have
> been sitting in branch-1 for about a year. As time goes on it will be more
> and more difficult to stabilize the current head of branch-1 for release.
> There is no time like the present to begin, so let's begin next week!
>
> If you have concerns, please, let's discuss. (smile)
>
>
>
Good on you Andrew,
St.Ack



> --
> Best regards,
> Andrew
>

Re: Branching branch-1.4, volunteering to RM branch-1.4

Posted by Andrew Purtell <ap...@apache.org>.
Sure thing.

I branched branch-1.4 today. Sent a separate announcement.

On Sat, Jul 1, 2017 at 12:38 PM, Yu Li <ca...@gmail.com> wrote:

> Yes, IMHO this will be more instructive and it will be great if we could do
> this from 1.4, thanks!
>
> Best Regards,
> Yu
>
> On 2 July 2017 at 02:24, Andrew Purtell <an...@gmail.com> wrote:
>
> > You mean something more digestible than JIRA release notes, prose not
> > bullet lists of JIRA descriptions. We could start doing that with 1.4.
> Some
> > RMs have done this before but in the release announcement emails. We can
> go
> > back and pull out that text for the book.
> >
> >
> > > On Jul 1, 2017, at 10:36 AM, Yu Li <ca...@gmail.com> wrote:
> > >
> > > +1 on branching branch-1.4
> > >
> > > One naive question here: from the book
> > > <http://hbase.apache.org/book.html#hbase.versioning> we will add
> > > functionality (in a backwards-compatible manner) in minor versions, but
> > it
> > > seems we don't have any one-line description on the differences (what
> > main
> > > functionalities have been added) between branch-1.1/1.2/1.3/1.4 so user
> > > could better decide which version to choose/upgrade. Should we add some
> > > explicit document on this? Or release note of the first release for
> each
> > > branch is enough? Thanks.
> > >
> > > Best Regards,
> > > Yu
> > >
> > >> On 1 July 2017 at 09:10, Mike Drob <md...@apache.org> wrote:
> > >>
> > >> Not at all. I missed Sean's earlier comment, my email client was being
> > slow
> > >> to fetch updates it seems.
> > >>
> > >> Give a shout out on list if you need more hands for any part of this,
> > and
> > >> thanks for volunteering!
> > >>
> > >> On Fri, Jun 30, 2017 at 5:31 PM, Andrew Purtell <ap...@apache.org>
> > >> wrote:
> > >>
> > >>> If it makes it to branch-1 before a release of 1.4.0 I don't see why
> it
> > >>> can't get in. Any objections to that?
> > >>>
> > >>>
> > >>>> On Fri, Jun 30, 2017 at 3:29 PM, Mike Drob <md...@apache.org>
> wrote:
> > >>>>
> > >>>> Do you want the hbase-spark module in, or will that eventual
> backport
> > >> go
> > >>> to
> > >>>> 1.5 if it makes it into branch-1?
> > >>>>
> > >>>> On Fri, Jun 30, 2017 at 4:37 PM, Andrew Purtell <
> apurtell@apache.org>
> > >>>> wrote:
> > >>>>
> > >>>>> Greeting HBasers,
> > >>>>>
> > >>>>> It's my intention to create a new release branch, branch-1.4, as
> seed
> > >>>> for a
> > >>>>> new 1.4.x code line, with a 1.4.0 release coming within the next
> two
> > >>>>> months.
> > >>>>>
> > >>>>> I would like to volunteer to RM this branch.
> > >>>>>
> > >>>>> I would like to create the new branch in ASF git, branch-1.4, as
> > >> early
> > >>> as
> > >>>>> next week.
> > >>>>>
> > >>>>> There are a number of contributions from my colleagues and others
> > >> that
> > >>>> have
> > >>>>> been sitting in branch-1 for about a year. As time goes on it will
> be
> > >>>> more
> > >>>>> and more difficult to stabilize the current head of branch-1 for
> > >>> release.
> > >>>>> There is no time like the present to begin, so let's begin next
> week!
> > >>>>>
> > >>>>> If you have concerns, please, let's discuss. (smile)
> > >>>>>
> > >>>>>
> > >>>>> --
> > >>>>> Best regards,
> > >>>>> Andrew
> > >>>>>
> > >>>>
> > >>>
> > >>>
> > >>>
> > >>> --
> > >>> Best regards,
> > >>> Andrew
> > >>>
> > >>> Words like orphans lost among the crosstalk, meaning torn from
> truth's
> > >>> decrepit hands
> > >>>   - A23, Crosstalk
> > >>>
> > >>
> >
>



-- 
Best regards,
Andrew

Words like orphans lost among the crosstalk, meaning torn from truth's
decrepit hands
   - A23, Crosstalk

Re: Branching branch-1.4, volunteering to RM branch-1.4

Posted by Yu Li <ca...@gmail.com>.
Yes, IMHO this will be more instructive and it will be great if we could do
this from 1.4, thanks!

Best Regards,
Yu

On 2 July 2017 at 02:24, Andrew Purtell <an...@gmail.com> wrote:

> You mean something more digestible than JIRA release notes, prose not
> bullet lists of JIRA descriptions. We could start doing that with 1.4. Some
> RMs have done this before but in the release announcement emails. We can go
> back and pull out that text for the book.
>
>
> > On Jul 1, 2017, at 10:36 AM, Yu Li <ca...@gmail.com> wrote:
> >
> > +1 on branching branch-1.4
> >
> > One naive question here: from the book
> > <http://hbase.apache.org/book.html#hbase.versioning> we will add
> > functionality (in a backwards-compatible manner) in minor versions, but
> it
> > seems we don't have any one-line description on the differences (what
> main
> > functionalities have been added) between branch-1.1/1.2/1.3/1.4 so user
> > could better decide which version to choose/upgrade. Should we add some
> > explicit document on this? Or release note of the first release for each
> > branch is enough? Thanks.
> >
> > Best Regards,
> > Yu
> >
> >> On 1 July 2017 at 09:10, Mike Drob <md...@apache.org> wrote:
> >>
> >> Not at all. I missed Sean's earlier comment, my email client was being
> slow
> >> to fetch updates it seems.
> >>
> >> Give a shout out on list if you need more hands for any part of this,
> and
> >> thanks for volunteering!
> >>
> >> On Fri, Jun 30, 2017 at 5:31 PM, Andrew Purtell <ap...@apache.org>
> >> wrote:
> >>
> >>> If it makes it to branch-1 before a release of 1.4.0 I don't see why it
> >>> can't get in. Any objections to that?
> >>>
> >>>
> >>>> On Fri, Jun 30, 2017 at 3:29 PM, Mike Drob <md...@apache.org> wrote:
> >>>>
> >>>> Do you want the hbase-spark module in, or will that eventual backport
> >> go
> >>> to
> >>>> 1.5 if it makes it into branch-1?
> >>>>
> >>>> On Fri, Jun 30, 2017 at 4:37 PM, Andrew Purtell <ap...@apache.org>
> >>>> wrote:
> >>>>
> >>>>> Greeting HBasers,
> >>>>>
> >>>>> It's my intention to create a new release branch, branch-1.4, as seed
> >>>> for a
> >>>>> new 1.4.x code line, with a 1.4.0 release coming within the next two
> >>>>> months.
> >>>>>
> >>>>> I would like to volunteer to RM this branch.
> >>>>>
> >>>>> I would like to create the new branch in ASF git, branch-1.4, as
> >> early
> >>> as
> >>>>> next week.
> >>>>>
> >>>>> There are a number of contributions from my colleagues and others
> >> that
> >>>> have
> >>>>> been sitting in branch-1 for about a year. As time goes on it will be
> >>>> more
> >>>>> and more difficult to stabilize the current head of branch-1 for
> >>> release.
> >>>>> There is no time like the present to begin, so let's begin next week!
> >>>>>
> >>>>> If you have concerns, please, let's discuss. (smile)
> >>>>>
> >>>>>
> >>>>> --
> >>>>> Best regards,
> >>>>> Andrew
> >>>>>
> >>>>
> >>>
> >>>
> >>>
> >>> --
> >>> Best regards,
> >>> Andrew
> >>>
> >>> Words like orphans lost among the crosstalk, meaning torn from truth's
> >>> decrepit hands
> >>>   - A23, Crosstalk
> >>>
> >>
>

Re: Branching branch-1.4, volunteering to RM branch-1.4

Posted by Andrew Purtell <an...@gmail.com>.
You mean something more digestible than JIRA release notes, prose not bullet lists of JIRA descriptions. We could start doing that with 1.4. Some RMs have done this before but in the release announcement emails. We can go back and pull out that text for the book. 


> On Jul 1, 2017, at 10:36 AM, Yu Li <ca...@gmail.com> wrote:
> 
> +1 on branching branch-1.4
> 
> One naive question here: from the book
> <http://hbase.apache.org/book.html#hbase.versioning> we will add
> functionality (in a backwards-compatible manner) in minor versions, but it
> seems we don't have any one-line description on the differences (what main
> functionalities have been added) between branch-1.1/1.2/1.3/1.4 so user
> could better decide which version to choose/upgrade. Should we add some
> explicit document on this? Or release note of the first release for each
> branch is enough? Thanks.
> 
> Best Regards,
> Yu
> 
>> On 1 July 2017 at 09:10, Mike Drob <md...@apache.org> wrote:
>> 
>> Not at all. I missed Sean's earlier comment, my email client was being slow
>> to fetch updates it seems.
>> 
>> Give a shout out on list if you need more hands for any part of this, and
>> thanks for volunteering!
>> 
>> On Fri, Jun 30, 2017 at 5:31 PM, Andrew Purtell <ap...@apache.org>
>> wrote:
>> 
>>> If it makes it to branch-1 before a release of 1.4.0 I don't see why it
>>> can't get in. Any objections to that?
>>> 
>>> 
>>>> On Fri, Jun 30, 2017 at 3:29 PM, Mike Drob <md...@apache.org> wrote:
>>>> 
>>>> Do you want the hbase-spark module in, or will that eventual backport
>> go
>>> to
>>>> 1.5 if it makes it into branch-1?
>>>> 
>>>> On Fri, Jun 30, 2017 at 4:37 PM, Andrew Purtell <ap...@apache.org>
>>>> wrote:
>>>> 
>>>>> Greeting HBasers,
>>>>> 
>>>>> It's my intention to create a new release branch, branch-1.4, as seed
>>>> for a
>>>>> new 1.4.x code line, with a 1.4.0 release coming within the next two
>>>>> months.
>>>>> 
>>>>> I would like to volunteer to RM this branch.
>>>>> 
>>>>> I would like to create the new branch in ASF git, branch-1.4, as
>> early
>>> as
>>>>> next week.
>>>>> 
>>>>> There are a number of contributions from my colleagues and others
>> that
>>>> have
>>>>> been sitting in branch-1 for about a year. As time goes on it will be
>>>> more
>>>>> and more difficult to stabilize the current head of branch-1 for
>>> release.
>>>>> There is no time like the present to begin, so let's begin next week!
>>>>> 
>>>>> If you have concerns, please, let's discuss. (smile)
>>>>> 
>>>>> 
>>>>> --
>>>>> Best regards,
>>>>> Andrew
>>>>> 
>>>> 
>>> 
>>> 
>>> 
>>> --
>>> Best regards,
>>> Andrew
>>> 
>>> Words like orphans lost among the crosstalk, meaning torn from truth's
>>> decrepit hands
>>>   - A23, Crosstalk
>>> 
>> 

Re: Branching branch-1.4, volunteering to RM branch-1.4

Posted by Yu Li <ca...@gmail.com>.
+1 on branching branch-1.4

One naive question here: from the book
<http://hbase.apache.org/book.html#hbase.versioning> we will add
functionality (in a backwards-compatible manner) in minor versions, but it
seems we don't have any one-line description on the differences (what main
functionalities have been added) between branch-1.1/1.2/1.3/1.4 so user
could better decide which version to choose/upgrade. Should we add some
explicit document on this? Or release note of the first release for each
branch is enough? Thanks.

Best Regards,
Yu

On 1 July 2017 at 09:10, Mike Drob <md...@apache.org> wrote:

> Not at all. I missed Sean's earlier comment, my email client was being slow
> to fetch updates it seems.
>
> Give a shout out on list if you need more hands for any part of this, and
> thanks for volunteering!
>
> On Fri, Jun 30, 2017 at 5:31 PM, Andrew Purtell <ap...@apache.org>
> wrote:
>
> > If it makes it to branch-1 before a release of 1.4.0 I don't see why it
> > can't get in. Any objections to that?
> >
> >
> > On Fri, Jun 30, 2017 at 3:29 PM, Mike Drob <md...@apache.org> wrote:
> >
> > > Do you want the hbase-spark module in, or will that eventual backport
> go
> > to
> > > 1.5 if it makes it into branch-1?
> > >
> > > On Fri, Jun 30, 2017 at 4:37 PM, Andrew Purtell <ap...@apache.org>
> > > wrote:
> > >
> > > > Greeting HBasers,
> > > >
> > > > It's my intention to create a new release branch, branch-1.4, as seed
> > > for a
> > > > new 1.4.x code line, with a 1.4.0 release coming within the next two
> > > > months.
> > > >
> > > > I would like to volunteer to RM this branch.
> > > >
> > > > I would like to create the new branch in ASF git, branch-1.4, as
> early
> > as
> > > > next week.
> > > >
> > > > There are a number of contributions from my colleagues and others
> that
> > > have
> > > > been sitting in branch-1 for about a year. As time goes on it will be
> > > more
> > > > and more difficult to stabilize the current head of branch-1 for
> > release.
> > > > There is no time like the present to begin, so let's begin next week!
> > > >
> > > > If you have concerns, please, let's discuss. (smile)
> > > >
> > > >
> > > > --
> > > > Best regards,
> > > > Andrew
> > > >
> > >
> >
> >
> >
> > --
> > Best regards,
> > Andrew
> >
> > Words like orphans lost among the crosstalk, meaning torn from truth's
> > decrepit hands
> >    - A23, Crosstalk
> >
>

Re: Branching branch-1.4, volunteering to RM branch-1.4

Posted by Mike Drob <md...@apache.org>.
Not at all. I missed Sean's earlier comment, my email client was being slow
to fetch updates it seems.

Give a shout out on list if you need more hands for any part of this, and
thanks for volunteering!

On Fri, Jun 30, 2017 at 5:31 PM, Andrew Purtell <ap...@apache.org> wrote:

> If it makes it to branch-1 before a release of 1.4.0 I don't see why it
> can't get in. Any objections to that?
>
>
> On Fri, Jun 30, 2017 at 3:29 PM, Mike Drob <md...@apache.org> wrote:
>
> > Do you want the hbase-spark module in, or will that eventual backport go
> to
> > 1.5 if it makes it into branch-1?
> >
> > On Fri, Jun 30, 2017 at 4:37 PM, Andrew Purtell <ap...@apache.org>
> > wrote:
> >
> > > Greeting HBasers,
> > >
> > > It's my intention to create a new release branch, branch-1.4, as seed
> > for a
> > > new 1.4.x code line, with a 1.4.0 release coming within the next two
> > > months.
> > >
> > > I would like to volunteer to RM this branch.
> > >
> > > I would like to create the new branch in ASF git, branch-1.4, as early
> as
> > > next week.
> > >
> > > There are a number of contributions from my colleagues and others that
> > have
> > > been sitting in branch-1 for about a year. As time goes on it will be
> > more
> > > and more difficult to stabilize the current head of branch-1 for
> release.
> > > There is no time like the present to begin, so let's begin next week!
> > >
> > > If you have concerns, please, let's discuss. (smile)
> > >
> > >
> > > --
> > > Best regards,
> > > Andrew
> > >
> >
>
>
>
> --
> Best regards,
> Andrew
>
> Words like orphans lost among the crosstalk, meaning torn from truth's
> decrepit hands
>    - A23, Crosstalk
>

Re: Branching branch-1.4, volunteering to RM branch-1.4

Posted by Andrew Purtell <ap...@apache.org>.
If it makes it to branch-1 before a release of 1.4.0 I don't see why it
can't get in. Any objections to that?


On Fri, Jun 30, 2017 at 3:29 PM, Mike Drob <md...@apache.org> wrote:

> Do you want the hbase-spark module in, or will that eventual backport go to
> 1.5 if it makes it into branch-1?
>
> On Fri, Jun 30, 2017 at 4:37 PM, Andrew Purtell <ap...@apache.org>
> wrote:
>
> > Greeting HBasers,
> >
> > It's my intention to create a new release branch, branch-1.4, as seed
> for a
> > new 1.4.x code line, with a 1.4.0 release coming within the next two
> > months.
> >
> > I would like to volunteer to RM this branch.
> >
> > I would like to create the new branch in ASF git, branch-1.4, as early as
> > next week.
> >
> > There are a number of contributions from my colleagues and others that
> have
> > been sitting in branch-1 for about a year. As time goes on it will be
> more
> > and more difficult to stabilize the current head of branch-1 for release.
> > There is no time like the present to begin, so let's begin next week!
> >
> > If you have concerns, please, let's discuss. (smile)
> >
> >
> > --
> > Best regards,
> > Andrew
> >
>



-- 
Best regards,
Andrew

Words like orphans lost among the crosstalk, meaning torn from truth's
decrepit hands
   - A23, Crosstalk

Re: Branching branch-1.4, volunteering to RM branch-1.4

Posted by Mike Drob <md...@apache.org>.
Do you want the hbase-spark module in, or will that eventual backport go to
1.5 if it makes it into branch-1?

On Fri, Jun 30, 2017 at 4:37 PM, Andrew Purtell <ap...@apache.org> wrote:

> Greeting HBasers,
>
> It's my intention to create a new release branch, branch-1.4, as seed for a
> new 1.4.x code line, with a 1.4.0 release coming within the next two
> months.
>
> I would like to volunteer to RM this branch.
>
> I would like to create the new branch in ASF git, branch-1.4, as early as
> next week.
>
> There are a number of contributions from my colleagues and others that have
> been sitting in branch-1 for about a year. As time goes on it will be more
> and more difficult to stabilize the current head of branch-1 for release.
> There is no time like the present to begin, so let's begin next week!
>
> If you have concerns, please, let's discuss. (smile)
>
>
> --
> Best regards,
> Andrew
>

Re: Branching branch-1.4, volunteering to RM branch-1.4

Posted by Sean Busbey <bu...@apache.org>.
HBASE-15631 would be great.

On Fri, Jun 30, 2017 at 4:55 PM, Andrew Purtell <ap...@apache.org> wrote:

> Hi Sean,
>
> Yes please, a summary document would be helpful.
>
> Although we should assess stability under load and chaos at moderate scale
> as soon as we branch, and I intend to do this in earnest, I don't
> anticipate we would freeze the branch for features for a few weeks after
> that.
>
> My big wish list item for a branch-1.4 would be HBASE-15631. I have a
> backport of RSGroups along with all of the subsequent improvements from
> master on an internal branch based on 1.3, exercised under chaos, but with
> as yet IMHO insufficient coverage, and am planning to upstream into
> branch-1, if the consensus is that is ok.
>
>
> On Fri, Jun 30, 2017 at 2:46 PM, Sean Busbey <bu...@apache.org> wrote:
>
> > yay! what are you looking for in terms of done-ness for inclusion in
> > feature freeze? I think we've got consensus on spark support, for
> instance,
> > and AFAICT there's only 1-2 issues to close out before it's code
> complete,
> > both of which have patches.
> >
> > I was planning to make a summary document of the consensus week after
> next.
> > Do I need to step that up to get this included in a 1.4 release? It's
> > pretty isolated in the code base.
> >
> > On Fri, Jun 30, 2017 at 4:37 PM, Andrew Purtell <ap...@apache.org>
> > wrote:
> >
> > > Greeting HBasers,
> > >
> > > It's my intention to create a new release branch, branch-1.4, as seed
> > for a
> > > new 1.4.x code line, with a 1.4.0 release coming within the next two
> > > months.
> > >
> > > I would like to volunteer to RM this branch.
> > >
> > > I would like to create the new branch in ASF git, branch-1.4, as early
> as
> > > next week.
> > >
> > > There are a number of contributions from my colleagues and others that
> > have
> > > been sitting in branch-1 for about a year. As time goes on it will be
> > more
> > > and more difficult to stabilize the current head of branch-1 for
> release.
> > > There is no time like the present to begin, so let's begin next week!
> > >
> > > If you have concerns, please, let's discuss. (smile)
> > >
> > >
> > > --
> > > Best regards,
> > > Andrew
> > >
> >
>
>
>
> --
> Best regards,
> Andrew
>
> Words like orphans lost among the crosstalk, meaning torn from truth's
> decrepit hands
>    - A23, Crosstalk
>

Re: Branching branch-1.4, volunteering to RM branch-1.4

Posted by Andrew Purtell <ap...@apache.org>.
Hi Sean,

Yes please, a summary document would be helpful.

Although we should assess stability under load and chaos at moderate scale
as soon as we branch, and I intend to do this in earnest, I don't
anticipate we would freeze the branch for features for a few weeks after
that.

My big wish list item for a branch-1.4 would be HBASE-15631. I have a
backport of RSGroups along with all of the subsequent improvements from
master on an internal branch based on 1.3, exercised under chaos, but with
as yet IMHO insufficient coverage, and am planning to upstream into
branch-1, if the consensus is that is ok.


On Fri, Jun 30, 2017 at 2:46 PM, Sean Busbey <bu...@apache.org> wrote:

> yay! what are you looking for in terms of done-ness for inclusion in
> feature freeze? I think we've got consensus on spark support, for instance,
> and AFAICT there's only 1-2 issues to close out before it's code complete,
> both of which have patches.
>
> I was planning to make a summary document of the consensus week after next.
> Do I need to step that up to get this included in a 1.4 release? It's
> pretty isolated in the code base.
>
> On Fri, Jun 30, 2017 at 4:37 PM, Andrew Purtell <ap...@apache.org>
> wrote:
>
> > Greeting HBasers,
> >
> > It's my intention to create a new release branch, branch-1.4, as seed
> for a
> > new 1.4.x code line, with a 1.4.0 release coming within the next two
> > months.
> >
> > I would like to volunteer to RM this branch.
> >
> > I would like to create the new branch in ASF git, branch-1.4, as early as
> > next week.
> >
> > There are a number of contributions from my colleagues and others that
> have
> > been sitting in branch-1 for about a year. As time goes on it will be
> more
> > and more difficult to stabilize the current head of branch-1 for release.
> > There is no time like the present to begin, so let's begin next week!
> >
> > If you have concerns, please, let's discuss. (smile)
> >
> >
> > --
> > Best regards,
> > Andrew
> >
>



-- 
Best regards,
Andrew

Words like orphans lost among the crosstalk, meaning torn from truth's
decrepit hands
   - A23, Crosstalk

Re: Branching branch-1.4, volunteering to RM branch-1.4

Posted by Sean Busbey <bu...@apache.org>.
yay! what are you looking for in terms of done-ness for inclusion in
feature freeze? I think we've got consensus on spark support, for instance,
and AFAICT there's only 1-2 issues to close out before it's code complete,
both of which have patches.

I was planning to make a summary document of the consensus week after next.
Do I need to step that up to get this included in a 1.4 release? It's
pretty isolated in the code base.

On Fri, Jun 30, 2017 at 4:37 PM, Andrew Purtell <ap...@apache.org> wrote:

> Greeting HBasers,
>
> It's my intention to create a new release branch, branch-1.4, as seed for a
> new 1.4.x code line, with a 1.4.0 release coming within the next two
> months.
>
> I would like to volunteer to RM this branch.
>
> I would like to create the new branch in ASF git, branch-1.4, as early as
> next week.
>
> There are a number of contributions from my colleagues and others that have
> been sitting in branch-1 for about a year. As time goes on it will be more
> and more difficult to stabilize the current head of branch-1 for release.
> There is no time like the present to begin, so let's begin next week!
>
> If you have concerns, please, let's discuss. (smile)
>
>
> --
> Best regards,
> Andrew
>