Releases in 3 months

[Martin Graesslin]

On Monday 08 July 2013 20:06:51 Albert Astals Cid wrote:
> El Dilluns, 8 de juliol de 2013, a les 14:03:19, Scott Kitterman va 
escriure:
> > Albert Astals Cid <aacid at kde.org> wrote:
> > >El Dilluns, 8 de juliol de 2013, a les 11:25:42, Scott Kitterman va
> > >
> > >escriure:
> > >> On Monday, July 08, 2013 04:59:50 PM Àlex Fiestas wrote:
> > >> > On Monday 08 July 2013 10:40:21 Scott Kitterman wrote:
> > >> > > We've already experienced having some parts of the SC skip
> > >
> > >releases and
> > >
> > >> > > it
> > >> > > was a real problem from a distribution perspective.  Please,
> > >
> > >let's not
> > >
> > >> > > do
> > >> > > it again.
> > >> > 
> > >> > KDE-PIM will be released, just not with the features of those
> > >
> > >working with
> > >
> > >> > a 6 months release cycle.
> > >> > 
> > >> > For example, in the case of 4.12 it will have (I hope) my
> > >
> > >kde-accounts
> > >
> > >> > integration but it might not have some of the features developed by
> > >> > Laurent
> > >> > (this is just an hypothetical example).
> > >> 
> > >> I don't know how to reconcile that with what you said in the mail I
> > >
> > >was
> > >
> > >> replying to (that you snipped):
> > >> > Then you can target your features for January (4.13) there is no
> > >
> > >pressure.
> > >
> > >> > As
> > >> > I said before you can keep having 6 months schedule while others
> > >
> > >like
> > >
> > >> > Frank
> > >> > (or myself) can release features based on 3 month schedule.
> > >> > 
> > >> > You don't have to change the way you work because of this.
> > >> 
> > >> Either they do have to change and do releases every three months or
> > >
> > >elements
> > >
> > >> of the SC get skipped on some releases.  I don't see how you can have
> > >
> > >it
> > >
> > >> both ways.
> > > 
> > > * all the repositories get released
> > > * repositories only get features that are completed
> > >
> > >* If your feature will take more than 3 months to develop, you do it in
> > >a
> > >branch
> > >
> > >I don't see where's the problem and why elemens of the SC will need to
> > >skip
> > >some releases.
> > 
> > As long as they are developing features in branches, I agree.
> 
> That's how it should be, there is people using master daily, you're not
> supposed to drop unfinished/broken stuff into them.
To quote Alex initial mail in this thread:
"by keeping master always in a "releaseable" state,"

Features should not be developed in trunk, though I can understand why some 
developers do it to get more testing. The concept of integration branches is a 
solution to this problem: it allows interested people to track the development 
more closely.

Cheers
Martin