Applications Lifecycle Policy

[Albert Astals Cid]

El dimecres, 12 de juliol de 2017, a les 7:09:12 CEST, Martin Flöser va 
escriure:
> Am 2017-07-12 00:20, schrieb Albert Astals Cid:
> > El dimecres, 5 de juliol de 2017, a les 21:37:09 CEST, Martin Flöser va
> > 
> > escriure:
> >> Am 2017-07-04 13:20, schrieb Jonathan Riddell:
> >> > The applications lifecycle policy needs an update
> >> > 
> >> > Is this a good current state of it or are there more stages?
> >> 
> >> Hi all,
> >> 
> >> I'm now going to propose a rather radical change to the process:
> >> 
> >> 
> >> 3. Remove the 2 week Review process
> > 
> > If we don't have review, at which point do i say:
> >  * Your i18n handling is broken
> >  * Your library installed headers will be a pain to maintain ABI
> >  * etc
> > 
> > Never?
> > 
> > The review process for me is a way to make you realize that things you
> > didn't
> > think were important now suddenly are since you want to be a grownup.
> 
> Please see my other replies to this thread which also discuss how I
> imagine this to work for the translation team.
> 
> > Of course you can break it again later but I would like to hope that
> > once told
> > how to do those things properly it may be easier to keep them doing
> > right
> 
> Right, like KWin where I am the fourth maintainer after review. That's
> my whole point: replace the review with automated checks always running.

That's an awesome proposition with an small flaw. At the moment we have 
volunteers that do the manual checks, do we have volunteers to write the 
automated checks?

Cheers,
  Albert

> 
> Cheers
> Martin