I’m counting 6 binding PMC +1s, 4 non-binding +1s, and no -1s of any kind.
From now on, please skip merging into the 3.X branch on the way to trunk.
The new merge order: 2.1 -> 2.2 -> 3.0 -> 3.11 -> trunk.
I will take care of what’s currently in 3.X branch, NEWS, CHANGES, and JIRA
fixversions
w
+1
Thanks for bringing this up.
On Sat, Jan 14, 2017 at 6:21 AM, Aleksey Yeschenko wrote:
> Hi all!
>
> It seems like we have a general consensus on ending tick-tock at 3.11, and
> moving
> on to stabilisation-only for 3.11.x series.
>
> In light of this, I suggest immediate feature freeze in th
+1
On Fri, Jan 13, 2017 at 10:52 AM, Josh McKenzie
wrote:
> +1
>
> On Fri, Jan 13, 2017 at 1:43 PM, Blake Eggleston
> wrote:
>
> > +1
> >
> >
> > On January 13, 2017 at 12:38:55 PM, Michael Shuler (
> mich...@pbandjelly.org)
> > wrote:
> >
> > +1 to freeze with this clarified branch situation.
+1
On Fri, Jan 13, 2017 at 1:43 PM, Blake Eggleston
wrote:
> +1
>
>
> On January 13, 2017 at 12:38:55 PM, Michael Shuler (mich...@pbandjelly.org)
> wrote:
>
> +1 to freeze with this clarified branch situation.
>
> --
> Michael
>
> On 01/13/2017 11:53 AM, Aleksey Yeschenko wrote:
> > To elaborate
+1
On January 13, 2017 at 12:38:55 PM, Michael Shuler (mich...@pbandjelly.org)
wrote:
+1 to freeze with this clarified branch situation.
--
Michael
On 01/13/2017 11:53 AM, Aleksey Yeschenko wrote:
> To elaborate further, under the current consensus there would be no 3.12
> release.
+1 to freeze with this clarified branch situation.
--
Michael
On 01/13/2017 11:53 AM, Aleksey Yeschenko wrote:
> To elaborate further, under the current consensus there would be no 3.12
> release.
>
> Meaning that there are a few features that already made it to 3.X (3.12) that
> would
> eith
+1
On Fri, Jan 13, 2017 at 10:16 AM, Benjamin Roth
wrote:
> Progress:
> Yes and no. I made a patch that made our cluster stable performance wise
> but introduces a consistency issue I am aware of. We can deal with it and I
> prefer this over severe performance problems. But this is nothing you c
Progress:
Yes and no. I made a patch that made our cluster stable performance wise
but introduces a consistency issue I am aware of. We can deal with it and I
prefer this over severe performance problems. But this is nothing you can
offer to regular users. I created a bunch of tickets related to th
+1
On Fri, Jan 13, 2017 at 11:21 AM, Aleksey Yeschenko
wrote:
> Hi all!
>
> It seems like we have a general consensus on ending tick-tock at 3.11, and
> moving
> on to stabilisation-only for 3.11.x series.
>
> In light of this, I suggest immediate feature freeze in the 3.X branch.
>
> Meaning th
In my opinion, stabilising MVs would count towards bug fixing, to totally
acceptable
for the 3.11.X line. No conflict here.
--
AY
On 13 January 2017 at 17:56:06, Jonathan Haddad (j...@jonhaddad.com) wrote:
+1 (non binding) to feature freeze.
I also like the idea of stabilizing MVs. Ben, you
+1 (non binding) to feature freeze.
I also like the idea of stabilizing MVs. Ben, you've probably been the
most vocal about the issues, have you made any progress towards making them
work any better during bootstrap / etc? Any idea of fixing them is a major
undertaking?
Jon
On Fri, Jan 13, 201
To elaborate further, under the current consensus there would be no 3.12
release.
Meaning that there are a few features that already made it to 3.X (3.12) that
would
either:
a) have to be reverted
b) have to be discarded together with the remained of the 3.X branch
If the vote goes through, I
+1 also I appreciate any effort on MV stability. It is an official 3.x
feature but not production ready for the masses.
Am 13.01.2017 18:34 schrieb "Jonathan Ellis" :
> +1
>
> On Fri, Jan 13, 2017 at 11:21 AM, Aleksey Yeschenko
> wrote:
>
> > Hi all!
> >
> > It seems like we have a general conse
+1
On Fri, Jan 13, 2017 at 11:21 AM, Aleksey Yeschenko
wrote:
> Hi all!
>
> It seems like we have a general consensus on ending tick-tock at 3.11, and
> moving
> on to stabilisation-only for 3.11.x series.
>
> In light of this, I suggest immediate feature freeze in the 3.X branch.
>
> Meaning th
Hi all!
It seems like we have a general consensus on ending tick-tock at 3.11, and
moving
on to stabilisation-only for 3.11.x series.
In light of this, I suggest immediate feature freeze in the 3.X branch.
Meaning that only bug fixes go to the 3.11/3.X branch from now on.
All new features that
15 matches
Mail list logo
