Polishing the PRD
skottler at redhat.com
Thu Jan 9 09:20:58 UTC 2014
----- Original Message -----
> From: "Marcela Mašláňová" <mmaslano at redhat.com>
> To: env-and-stacks at lists.fedoraproject.org
> Sent: Thursday, January 9, 2014 9:48:59 AM
> Subject: Re: Polishing the PRD
> On 01/08/2014 07:33 PM, Pierre-Yves Chibon wrote:
> > On Wed, Jan 08, 2014 at 05:46:17PM +0100, Tadej Janež wrote:
> >> 4) CI
> >> * Out of scope (going to take a long time to be included in Fedora,
> >> maybe even the inclusion for this group).
> >> ** AutoQA - co-operation with Fedora QA.
> >> ** Jenkins - upstream projects for Fedora should use
> >> http://jenkins.cloud.fedoraproject.org/
> > I would greatly appreciate if that 'should use' was changed into a 'can
> > use'.
> > Jenkins as part of the infra was set up because we, the infra, wanted to
> > have
> > something to do CI (see warning ). We have offered/are offering it to
> > other projects but it's
> > on a best-effort basis and in fact we do run quite often into some problems
> > when
> > running the updates.
> > 
> > https://fedoraproject.org/wiki/Jenkins@infra#What_is_Jenkins_.40_Fedora-infra.3F
> > Thanks,
> > Pierre
> > _______________________________________________
> > env-and-stacks mailing list
> > env-and-stacks at lists.fedoraproject.org
> > https://lists.fedoraproject.org/mailman/listinfo/env-and-stacks
> I don't know much about Jenkins and I don't want to push projects to use
> Jenkins if they are already using something else. So, how to put it?
> Could you formulate it better?
I think we can rephrase this to something like "Encourage upstream projects to move toward a continuous integration model, and potentially allowing them to use the Fedora jenkins instance to move in that direction" or something along those lines.
> env-and-stacks mailing list
> env-and-stacks at lists.fedoraproject.org
More information about the env-and-stacks