teams to self-publish solutions will eventually remove the need
for these keepalives.
[1]
https://pagure.io/fedora-pgm/schedule/issues?status=Open&tags=spins+keepalive&close_status=
[2] https://fedoraproject.org/wiki/Releases/37/Spins
[3] https://pagure.io/fedora-pgm/pgm_team/n
FESco previously approved a requirement that Spin/Labs owners send a
keepalive request in order to keep building the spin or lab. I have
opened Pagure issues[1] for all Spins and Labs listed on the wiki[2].
If you are the owner of one of those spins and labs, please reply in
the appropriate ticket
On Wed, Jan 23, 2019 at 03:29:44PM -0500, John Harris wrote:
> > Future improvements to the release process that will allow for teams to
> > self-publish solutions will eventually remove the need for these
> > keepalives.
> Is that really such a great idea? How would release engineering handle that
On Wednesday, January 23, 2019 3:06:17 PM EST Ben Cotton wrote:
> Future improvements to the release process that will allow for teams to
> self-publish solutions will eventually remove the need for these keepalives.
Is that really such a great idea? How would release engineering handle that?
--
FESco previously approved a requirement that Spin/Labs owners send a
keepalive request in order to keep building the spin or lab. I have
opened Pagure issues[1] for all Spins and Labs listed on the wiki[2].
If you are the owner of one of those spins and labs, please reply in
the appropriate ticket
