You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hbase.apache.org by Nick Dimiduk <nd...@apache.org> on 2016/01/05 08:26:31 UTC
1.1.3RC1 next week
Happy New Year!
I'd like to pick back up the branch-1.1 release. Since we're already busy
with 1.2 and 0.98 is eminent, I'll let the dust settle on at least one of
those releases before posting RC1; probably next week though possibly the
week following, depending on how the votes go.
As always, let me know if you have any concerns.
Thanks,
Nick
Re: 1.1.3RC1 next week
Posted by Nick Dimiduk <nd...@apache.org>.
Thanks for taking a look Jon.
On Fri, Jan 15, 2016 at 9:05 AM, Jonathan Hsieh <jo...@cloudera.com> wrote:
> Nick,
>
> I looked at the three reports look good to me. Usually I'm most concerned
> about removals but HMaster is LimitedPrivate.
>
> Jon
>
> On Thu, Jan 14, 2016 at 10:49 PM, Nick Dimiduk <nd...@apache.org>
> wrote:
>
> > For the curious, I've run the compatibility script on branch-1.1, against
> > both 1.1.0 [0] and 1.1.3RC0 [1] tags. Since the resolution on HBASE-14944
> > was that the incompatible changes [2] were acceptable given their
> security
> > nature and limited scope, I've focused my attention on the changes that
> > have happened since 1.1.3RC0.
> >
> > The changes introduced for controlling additional operations with ProcV2
> > are showing up in the latest reports. However, these too look limited in
> > scope to LimitedPrivate and/or Evolving classes, so they are acceptable
> by
> > my understanding of our compatibility guidelines.
> >
> > I'd appreciate another pair of eyes on these reports to make sure I
> didn't
> > miss anything. I'd hate to sink another RC due to things we should be
> aware
> > of well in advance.
> >
> > Thanks,
> > -n
> >
> > [0]:
> http://home.apache.org/~ndimiduk/1.1.0_branch-1.1_compat_report.html
> > [1]:
> > http://home.apache.org/~ndimiduk/1.1.3RC0_branch-1.1_compat_report.html
> > [2]: http://home.apache.org/~ndimiduk/1.1.0_1.1.3RC0_compat_report.html
> >
> > On Mon, Jan 4, 2016 at 11:26 PM, Nick Dimiduk <nd...@apache.org>
> wrote:
> >
> > > Happy New Year!
> > >
> > > I'd like to pick back up the branch-1.1 release. Since we're already
> busy
> > > with 1.2 and 0.98 is eminent, I'll let the dust settle on at least one
> of
> > > those releases before posting RC1; probably next week though possibly
> the
> > > week following, depending on how the votes go.
> > >
> > > As always, let me know if you have any concerns.
> > >
> > > Thanks,
> > > Nick
> > >
> >
>
>
>
> --
> // Jonathan Hsieh (shay)
> // HBase Tech Lead, Software Engineer, Cloudera
> // jon@cloudera.com // @jmhsieh
>
Re: 1.1.3RC1 next week
Posted by Jonathan Hsieh <jo...@cloudera.com>.
Nick,
I looked at the three reports look good to me. Usually I'm most concerned
about removals but HMaster is LimitedPrivate.
Jon
On Thu, Jan 14, 2016 at 10:49 PM, Nick Dimiduk <nd...@apache.org> wrote:
> For the curious, I've run the compatibility script on branch-1.1, against
> both 1.1.0 [0] and 1.1.3RC0 [1] tags. Since the resolution on HBASE-14944
> was that the incompatible changes [2] were acceptable given their security
> nature and limited scope, I've focused my attention on the changes that
> have happened since 1.1.3RC0.
>
> The changes introduced for controlling additional operations with ProcV2
> are showing up in the latest reports. However, these too look limited in
> scope to LimitedPrivate and/or Evolving classes, so they are acceptable by
> my understanding of our compatibility guidelines.
>
> I'd appreciate another pair of eyes on these reports to make sure I didn't
> miss anything. I'd hate to sink another RC due to things we should be aware
> of well in advance.
>
> Thanks,
> -n
>
> [0]: http://home.apache.org/~ndimiduk/1.1.0_branch-1.1_compat_report.html
> [1]:
> http://home.apache.org/~ndimiduk/1.1.3RC0_branch-1.1_compat_report.html
> [2]: http://home.apache.org/~ndimiduk/1.1.0_1.1.3RC0_compat_report.html
>
> On Mon, Jan 4, 2016 at 11:26 PM, Nick Dimiduk <nd...@apache.org> wrote:
>
> > Happy New Year!
> >
> > I'd like to pick back up the branch-1.1 release. Since we're already busy
> > with 1.2 and 0.98 is eminent, I'll let the dust settle on at least one of
> > those releases before posting RC1; probably next week though possibly the
> > week following, depending on how the votes go.
> >
> > As always, let me know if you have any concerns.
> >
> > Thanks,
> > Nick
> >
>
--
// Jonathan Hsieh (shay)
// HBase Tech Lead, Software Engineer, Cloudera
// jon@cloudera.com // @jmhsieh
Re: 1.1.3RC1 next week
Posted by Nick Dimiduk <nd...@apache.org>.
For the curious, I've run the compatibility script on branch-1.1, against
both 1.1.0 [0] and 1.1.3RC0 [1] tags. Since the resolution on HBASE-14944
was that the incompatible changes [2] were acceptable given their security
nature and limited scope, I've focused my attention on the changes that
have happened since 1.1.3RC0.
The changes introduced for controlling additional operations with ProcV2
are showing up in the latest reports. However, these too look limited in
scope to LimitedPrivate and/or Evolving classes, so they are acceptable by
my understanding of our compatibility guidelines.
I'd appreciate another pair of eyes on these reports to make sure I didn't
miss anything. I'd hate to sink another RC due to things we should be aware
of well in advance.
Thanks,
-n
[0]: http://home.apache.org/~ndimiduk/1.1.0_branch-1.1_compat_report.html
[1]: http://home.apache.org/~ndimiduk/1.1.3RC0_branch-1.1_compat_report.html
[2]: http://home.apache.org/~ndimiduk/1.1.0_1.1.3RC0_compat_report.html
On Mon, Jan 4, 2016 at 11:26 PM, Nick Dimiduk <nd...@apache.org> wrote:
> Happy New Year!
>
> I'd like to pick back up the branch-1.1 release. Since we're already busy
> with 1.2 and 0.98 is eminent, I'll let the dust settle on at least one of
> those releases before posting RC1; probably next week though possibly the
> week following, depending on how the votes go.
>
> As always, let me know if you have any concerns.
>
> Thanks,
> Nick
>