On Sun, Jun 24, 2012 at 3:37 AM, David Hrbáč <[email protected]> wrote: > Dne 24.6.2012 03:45, Nico Kadel-Garcia napsal(a): >> A better question, perhaps, is "how can we best help" ? > > Nico's right. We know the issue and even the solution. We need to come > up with a new build infra and workflow to build, test, sign and push. We > can create something like "two or more sign-offs are ok" to sign and > push a new package in the wild. > DH
Even without push approva for the active repository, I wonder if some continuous build/regresstion test environments hosted offsite would be useful. I find it *really useful* to be able to build components I work with using "mock" and run basic regression tests on them. I'd love to make my build and test environments resemble Dag's as closely as possible, so my submitted packagtes are more likely to work well in the official Repoforge build environments. Is the build environment well defined anywhere so I can do that? I'm afraid I don't currently have the spare hardwre and bandwidth to run a dynamic mirror of the Repoforge build tree. Not at home, and since I'm a contractor, my workplace wouldn't currently spring for it. But I've got a bunch of Perl modules I'd like to RPM wrap and publish soon, and I'd love to do that with a similar build environment. _______________________________________________ users mailing list [email protected] http://lists.repoforge.org/mailman/listinfo/users
