On Monday, 17 December 2012 at 17:45:12 UTC, David Nadlinger
wrote:
On Monday, 17 December 2012 at 17:31:45 UTC, foobar wrote:
Huh?
Both LLVM and KDE are developed on *subversion* and as such
their work-flows are not applicable. Not to mention that KDE
is vastly different in concept and goals than a programming
language.
Subversion is conceptually very different from git and its
model imposes practical restrictions that are not relevant for
git, mostly with regards to branches, merging, etc. Actions
which are first class and trivial to accomplish in git. This
is analogous to designing highways based on the speed
properties of bicycles.
Guess what, I know that. The post by SomeDude just claimed that
release branches in general are impractical and not used by
open source projects, which is wrong.
David
I was actually correct, saying that it can only work with very
few releases, and indeed, for KDE, there are at most 2 releases
per year and usually less.
For instance, the 4.10 is scheduled to span from october 2012 to
july 2013, with numerous patches and corrective releases in
between. So it's roughly the same release process as the one
branch/year I advocated.
And it's not the same at all as creating one branch every month.