A Dimecres, 5 d'agost de 2009, John Tapsell va escriure:
> 2009/8/4 Aaron J. Seigo <aseigo@kde.org>:
> >> - especially with multiple branches synchronization - which leads to
> >> bugfixes sometimes not hitting latest 'soon-to-be-stable' branch (4.3
> >> now) or not hitting on time, as developers seem to be devoted to trunk
> >> (sometimes even when 4.3 in this case is not released).
> >
> > svn makes this much more difficult than it should be, and as Thiago has
> > opined about on k-c-d a few times we probably do it the wrong way around
> > by backporting instead of fixing in stable and then forward porting. but
> > again, svn makes this impractical.
>
> Agreed.  I can't get the hang of svn backporting, and so I simply never do
> it.
>
> With git, on the other hand, I backport daily.  It's so natural and
> easy to bug fix in stable and forward port, while simultanously adding
> features in the new branch.
>
> Once we have git, I'd like to see this issue revisited.  I would
> prefer that KDE got a reputation of "releases when ready". 

So we never release? No thanks.

Albert

> Just start
> skipping the release that we currently call ".0".
>
> John
> _______________________________________________
> release-team mailing list
> release-team@kde.org
> https://mail.kde.org/mailman/listinfo/release-team

_______________________________________________
release-team mailing list
release-team@kde.org
https://mail.kde.org/mailman/listinfo/release-team