Andre Klapper wrote:
...
> > The issue I've identified is large changes landing just before the
> > freeze. Typically these large changes require subsequent smaller
> > changes to make them release-ready, which often requires close design
> > involvement.
>
> I don't know the best solution either
Comments below.
On Wed, 2017-09-20 at 16:40 +0100, Allan Day wrote:
> ...
> > > Extend the UI freeze (or create a freeze period for major UI
> > > changes) and require that breaks get design approval.
> > >
> >
> > What would extending the freeze accomplish? We already have a long
> > UI freeze
On Wed, Sep 20, 2017 at 8:58 AM wrote:
> On Wed, Sep 20, 2017 at 4:50 AM, Allan Day wrote:
> > Extend the UI freeze (or create a freeze period for major UI changes)
> > and require that breaks get design approval.
>
> What would extending the freeze accomplish? We already have a long UI
> freeze
Hey Michael,
Thanks for your quick reply. Do bear in mind that these are just ideas; I'm
happy to discard any that don't make sense!
wrote:
...
> Extend the UI freeze (or create a freeze period for major UI changes) and
>> require that breaks get design approval.
>>
>
> What would extending the
On Wed, Sep 20, 2017 at 4:50 AM, Allan Day wrote:
Extend the UI freeze (or create a freeze period for major UI changes)
and require that breaks get design approval.
What would extending the freeze accomplish? We already have a long UI
freeze (five weeks). Wouldn't extending the freeze just ma
Hi all,
I personally found 3.26 to be a difficult release and thought that it might
be useful to share some of my experiences, along with some thoughts on how
to improve things for next time around. The issues I encountered:
1. We had two big features that landed very close to UI freeze, both
