Re: [Wikitech-l] INFO: Reading web release process update

On Wed, Jan 27, 2016 at 6:27 PM, Greg Grossmeier wrote: > > > Feature flagging or using feature branches for certain things may be a > way > > to go for certain things, we're keeping that in mind definitely, thanks > for > > the reminder Greg. > > Just be clear: feature

Re: [Wikitech-l] INFO: Reading web release process update

> Feature flagging or using feature branches for certain things may be a way > to go for certain things, we're keeping that in mind definitely, thanks for > the reminder Greg. Just be clear: feature branches aren't feature flags and take you back to a place closer to a 'dev' branch :). > I

Re: [Wikitech-l] INFO: Reading web release process update

Feature flagging or using feature branches for certain things may be a way to go for certain things, we're keeping that in mind definitely, thanks for the reminder Greg. I agree with you regarding releases Gergo. The good thing about the *release*s was mainly the curated changelog of changes for

[Wikitech-l] INFO: Reading web release process update

As you may be aware, the reading team was unhappy with its current release process and shared its rationale for a different release process. This resulted in an experiment on Gather, QuickSurveys, Cards and

Re: [Wikitech-l] INFO: Reading web release process update

Thanks for this writeup (and the wiki page), Jon. Much appreciated. I only have one question/thought: > When we work on new features, we will be more mindful of +2, marking the > initial commit of a chain of commits that requires sign off from a designer > and product owner with a -2. Wouldn't

Re: [Wikitech-l] INFO: Reading web release process update

On Tue, Jan 26, 2016 at 2:11 PM, Jon Robson wrote: > We think this will be a better approach for everyone. Our only remaining > question is when and if to do release number bumps in future. We'll be back > with an answer about that shortly... ideas welcomed. > Who is the