El Dimarts, 9 de juny de 2015, a les 09:40:49, Luigi Toscano va escriure:
> Il 09 giugno 2015 08:28:00 CEST, Ralf Habacker <ralf.habac...@freenet.de> ha 
scritto:
> > Am 18.05.2015 um 13:26 schrieb Albert Astals Cid:
> > > My suggestion for you if you really want to maintain a longer term
> > 
> > kdelibs4-
> > 
> > > based version of umbrello s to keep doing commits in your "last"
> > 
> > kdelibs4-
> > 
> > > branch (i guess Applications/15.04 in this case), though since we're
> > 
> > not doing
> > 
> > > any more tarballs of those i'm not sure it will reach many people,
> > 
> > you'll have
> > 
> > > to ping distro people and tell them to look into the branch
> > 
> > regularly for
> > 
> > > bugfixes or you can try releasing your own tarballs.
> > 
> > Because of this drawback, which adds an additional maintenance burden,
> > it has been decided to merge the frameworks branch back into master in
> > a
> > way to be able to provide KDE4 LTS and KF5 builds from the same
> > source.
> > 
> > Tar balls generated from the future 15.08 branch could be build for
> > KDE4
> > using default cmake command line and for KF5 with -DBUILD_KF5=1.
> 
> As I mentioned on the translators mailing list, this breaks the translations
> workflow for documentation (index.docbook.cmake). Moreover, I think you are
> shipping a kdelibs4 version with.new features, not just an "LTS" version
> (which is usually mostly maintenance-only). The cost of keeping a separate
> kdelibs4 branch for bugfixes is not so high. I ask you to reconsider this
> decision and follow the same workflow of most applications around here.

+1 Applications that build two different versions in the same branch are bound 
to break, someone will commit something that builds in the default mode and 
not in the other.

Besides it goes against all the branch usage we use in all the KDE modules, so 
you'll hit problems with i18n, CI, etc.

Please use the same workflow everyone uses.

Cheers,
  Albert

> 
> Ciao
> 
> >> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe
> >> <<


>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<

Reply via email to