No feature-branches in the mainline repositories

Andreas Pakulat apaku at gmx.de
Wed May 19 10:33:18 UTC 2010


On 19.05.10 11:56:25, Niko Sams wrote:
> On Wed, May 19, 2010 at 09:56, Andreas Pakulat <apaku at gmx.de> wrote:
> > This wasn't really mentioned before so I'll do it now. Feature branches
> > should not be published into our mainline repositories, but into your
> > personal or a team clone of the repositories. The reason is so that our
> > mainlines only contain long-living branches like the stable release
> > branches. Such a feature branch may be merged later on, but just as well
> > it could happen that its being deleted, in which case people tracking
> > the branch will run into problems.
> We should remove the branches that where imported from svn from mainline too.
> What about creating a team clone and moving them there?
> For example class-generation-extraction could be moved there.

Those are ok to move I think, they're basically dead anyway (except mabe
sublime_rework)
 
> and what about 1.0 - 3.5?

This is not. While the others are clearly just features, this is part of
the history and belongs to kdevelop. And hence should IMHO be in the same
repo.

Andreas

-- 
You enjoy the company of other people.




More information about the KDevelop-devel mailing list