-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512
Splitting all of this into "master" and "stable" branches only means that the people pulling the "stable" branch might get stale/broken/no 9999 ebuilds. It just isn't supposed to work like that.
If you'd like a sample of how this kind of thing looks in practice, here's poppler in the official Gentoo ebuild repository, with three release ebuilds and one live ebuild:
https://gitweb.gentoo.org/repo/gentoo.git/tree/app-text/poppler
Thank you, now I understand better. This means there is no need to create a branch. It also means that tde-packaging-gentoo will not be part of the 'tde' tree on r14.0.x branch.
Is there also a convention for preliminary packages? For example, as on Debian "~preXX", or on FreeBSD "+pXX"?
Personally I think it is still better to have a master and r14.0.x branch. For all maintenance releases (like R14.0.x) the various ebuild scripts can leave within the same branch, but at least when we change into a new minor release there is a clear separation between branches. Just my 2 cents. Cheers Michele