Hey
Well, it definitely seems like there's not much support for the idea ;)
Thanks everyone who replied. I'll go away and think about ways we can improve
things without moving FF :)
Cheers,
--
Chris Jones
> On 18 May 2017, at 11:18, Thierry Carrez wrote:
>
> Chris
Chris Jones wrote:
> I have a fairly simple proposal to make - I'd like to suggest that
> Feature Freeze move to being much earlier in the release cycle (no
> earlier than M.1 and no later than M.2 would be my preference).
> [...]
Hey Chris,
From my (admittedly too long) experience in release
On 5/17/2017 11:20 AM, Dmitry Tantsur wrote:
On 05/17/2017 05:34 PM, Chris Jones wrote:
Hey folks
I have a fairly simple proposal to make - I'd like to suggest that
Feature Freeze move to being much earlier in the release cycle (no
earlier than M.1 and no later than M.2 would be my
On 05/17/2017 05:34 PM, Chris Jones wrote:
Hey folks
I have a fairly simple proposal to make - I'd like to suggest that Feature
Freeze move to being much earlier in the release cycle (no earlier than M.1 and
no later than M.2 would be my preference).
I welcome projects to experiment with
Hey folks
I have a fairly simple proposal to make - I'd like to suggest that Feature
Freeze move to being much earlier in the release cycle (no earlier than M.1
and no later than M.2 would be my preference).
In the current arrangement (looking specifically at Pike), FF is scheduled
to happen 5