On Wed, Nov 26, 2008 at 01:50:45PM +0100, Miroslav Suchý wrote: > > That is probably OK with small packages (like nocpulse-common), but it > do not work with main packages (like java), which are usually rebuild > only once just before the final release. Therefore nobody can test it.
I assume guys working on spacewalk-java do not consider it stable enough yet, that's why they did not tag it. >> Why do you want to build packages from state when they were not tagged >> (= signed off by developer)? Just wait for the developer to make >> tag(-minor)-release. > > That is for what people create nightly builds. > You do not want it? Do not use it and wait for QA repo. > You want test even partial work. Use it. > And the code in git should work. If it do not work, why did you push it > there in first place. Because you are allowed to do so. I'm not that perfect and sometimes things do not work the first time I feel I'm finished. And I have to fix stuff. > But again the main reason is stated in my first paragraph of this email. Ask developers of packages that don't seem to be tagged (often enough) why they do not tag them. 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. -- Jan Pazdziora Satellite Engineering, Red Hat _______________________________________________ Spacewalk-devel mailing list [email protected] https://www.redhat.com/mailman/listinfo/spacewalk-devel
