moving to Koji

Luke Macken lmacken at redhat.com
Mon Mar 23 18:12:48 UTC 2009


On Wed, Feb 25, 2009 at 08:11:23PM +0100, Thorsten Leemhuis wrote:
> On 25.02.2009 18:21, Toshio Kuratomi wrote:
>> Thorsten Leemhuis wrote:
>>> On 25.02.2009 16:12, Dennis Gilmore wrote:
> > [...]
>>>> To move building to koji we need to get bodhi setup and redo the
>>>> release engineering process to closely match that of Fedora. What this
>>>> means is that you will need to file a ticket with releng to have a
>>>> package added to the buildroot  if you need to build against it.   it
>>>> also means that things can hit stable sooner.  
>>> Ehh, do we really want that apart from security updates or important
>>> bugfixes (which we can and do push within minutes these days already if
>>> needed)?
>>> I ask because the "monthly" move from testing to the porper repos has a
>>> important side-effect: I slows everything down when compared to the
>>> quickly moving Fedora, which for EL repos IMHO is something good.
> >
>> I think this would still be possible with bodhi by having the
>> epel_signers push to testing frequently but push to stable on a monthly
>> basis.  Have to ask releng/lmacken to be sure, though.
>
> Luke, can you clarify? And if above works: can one push selected  
> packages (security updates and those that fix other serious bugs) at any  
> time while leaving the other, regular updates for the next monthly move?

Yes, the signer/pusher has full control over what updates they are
pushing.

The following ticket contains details on what needs to happen to get
bodhi to push updates for EPEL:

    https://fedorahosted.org/fedora-infrastructure/ticket/1230

luke




More information about the epel-devel mailing list