-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Wed, 26 Nov 2008 14:23:15 +0100 Jan Pazdziora <[EMAIL PROTECTED]> wrote:
> > To summarize: from my point of view building test-srpm (the > .git.longsha1) packages to dist-5E-sw-0.4-candidate is > counterinuitive. It has that longsha1 in its name for a reason, to > warn everybody that it was built from some random commit, not signed > off by the developer (via make tag-release). If you start feeding > them to dist-5E-sw-0.4-candidate, before long they will make their > way to dist-5E-sw-0.4 and you will see things like > SatConfig-general-1.215.38-7.git.4c57d3b9f251dd5dc7113ecf37c30cecbb6d88c1.i386.rpm > > in our yum repo. > > Other guys might have different opinion. > Just to chime in with my preference, I think I'd prefer to have it remain largely as we do today. - - Require manual package rebuilds. (assign people to keep a loose eye on certain packages if there's a genuine problem with no re-builds taking place) - - Keep the version going up for each internal rebuild. Yes we release spacewalk-package-0.4.159 but I like that each new version signifies a new tarball inside and we don't have to do any fancy patching. Even if we decided on a way to bump versions during devel cycle but then go to 0.4.0 at release would be nice. - - I'm not really keen on test-rpms appearing anywhere. I'd rather just keep using these as a developer tool and anything appearing in repos be versioned normally. Having the devel repo contain only packages that *somebody* decided to manually tag seems good to me. Devan - -- Devan Goodwin <[EMAIL PROTECTED]> Software Engineer - Spacewalk / RHN Satellite Halifax, Canada 650.567.9039x79267 -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) iEYEARECAAYFAkktbTYACgkQAyHWaPV9my7WggCfQW/ehHlEXdwtW5YeH19jOtrC 1rEAn2WowCGyPVcoPqFq5+LYWyJz55W9 =Kl2h -----END PGP SIGNATURE----- _______________________________________________ Spacewalk-devel mailing list Spacewalk-devel@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-devel