Question regarding dist-git aesthetics with branches

[Jesse Keating]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 07/20/2010 08:55 PM, Garrett Holmstrom wrote:
> On 7/20/2010 19:13, Hans Ulrich Niedermann wrote:
>> BTW, while typing the above, I have noted that "master" or "devel" or
>> "f13" are quite easy to type, while "F-13" with capital letter and
>> hyphen is relatively complicated. Perhaps that could be an argument when
>> choosing branch names.
> 
> Using names like f13, el5, and so forth would also keep dist-git 
> consistent with git branch naming conventions.  If we were to do 
> something like that we might as well just use the value of %{dist}.

That was going to be my next question, although that would bring back
the "c" in fc13 and fc14 since that's what the dist value is.  We could
bite the bullet and change the dist value to remove the c, and just
manually keep track of making sure that builds on older releases won't
be "newer" than builds on the newer branches.  not sure if we want to go
through that pain at this point.

> 
> If rawhide development is supposed to happen on origin/master, then how 
> do branches for rawhide work?  Does fedpkg just default to building for 
> rawhide when a branch doesn't appear in a release's "branch namespace?"

Yes. Branches of rawhide would be of the form origin/<branch> so if we
don't find one of our expected f(c)??,el?,olpc? we default to building
for rawhide.


- -- 
Jesse Keating
Fedora -- Freedom² is a feature!
identi.ca: http://identi.ca/jkeating
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.14 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org/

iEYEARECAAYFAkxGgokACgkQ4v2HLvE71NV8WwCfcVOK9lNRJwb+RQJC22Ngixk3
Oa0AoMVsIdKMM3xqw28UwibrivN5Fy9z
=hKZP
-----END PGP SIGNATURE-----