No feature-branches in the mainline repositories

[David Nolden]

2010/5/19 Andreas Pakulat <apaku at gmx.de>:
> 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.

What exactly are those problems? When we start working on a different
repository, people might track that one as well, and will run into
exactly the same problems. The price is a more and more complicated
workflow. The idea of using git was making things easier, not harder,
at least i though that. Right now I'm just seeing things become more
complicated.