Proposal for branching policy towards KF5

Albert Astals Cid aacid at kde.org
Sun Jul 28 15:59:23 BST 2013


El Diumenge, 28 de juliol de 2013, a les 11:33:58, Torgny Nyblom va escriure:
> On Friday 26 July 2013 23.53.07 Michael Pyne wrote:
> > On Fri, July 26, 2013 21:11:21 Torgny Nyblom wrote:
> > > On Thursday 25 July 2013 18.24.50 Michael Pyne wrote:
> > > > The 'logical module groups' might play a role in the release process
> > > > after
> > > > a release is done, but shouldn't have any further role for tagging
> > > > that
> > > > I
> > > > can see. i18n is covered above.
> > > 
> > > Wouldn't this be nice to have as the source of branch info for the
> > > releases? One place to have this information instead of duplicate it for
> > > each tool/user?
> > 
> > I think I see what you're talking about, but the release team essentially
> > just make their own branch already, make their tags, that's it. Things are
> > generally not tagged directly from master or any other development branch.
> 
> Not quite :), when we make a release the tags are put on the release branch,
> i.e. KDE/4.10 for the last stable release. The release branch/tag is a
> thing of the past that was used in the SVN days.
> 
> The only release team only thing is that we keep a list of modules/branches
> that we should tag modules from. Since this will be the same as the "stable"
> branch I see no reason why we should hide this information in the release
> tools repo.

I see your point, and kind of agree that it may be useful, but i see two 
issues:
 * Right now, only me and you (afaik) commit to the release-tools repo, so I 
don't have to care about people "vandalizing" the release info in purpose or 
by mistake
 * There's moments like "a few weeks ago" where the "l10n stable" branch 
points to KDE/4.11 and "l10n unstable" to master, but release-wise and code-
wise I am not sure we should like to give 4.11 to people asking for a "stable 
code branch" since the .0 is still unreleased

Anyway if you think it's worth it, i'm not against exploring such solution :-)

Cheers,
  Albert

> 
> /Regards
> Torgny





More information about the kde-core-devel mailing list