#6081: please keep releases.txt up-to-date

[Fedora Release Engineering]

#6081: please keep releases.txt up-to-date
------------------------------+-----------------------
  Reporter:  mclasen          |      Owner:  rel-eng@…
      Type:  task             |     Status:  new
 Milestone:  Fedora 22 Final  |  Component:  koji
Resolution:                   |   Keywords:  next
Blocked By:                   |   Blocking:
------------------------------+-----------------------
Changes (by pfrields):

 * keywords:   => next
 * cc: pfrields (added)
 * milestone:  Fedora 21 Final => Fedora 22 Final


Comment:

 In next-gen compose tools, some dependency ordering and fedmsg tie-in may
 be possible to kicks off correct tasks at the right time.  So for
 instance, if there's an approved compose, and that gets marked in some
 way, it could trigger the creation of such a file too.  threebean and I
 had tossed around an idea of doing this with some sort of
 systemd/container based solution so it doesn't have to become a human's
 job to figure out and debug the ordering constantly.

 I propose we use a keyword like ''next'' for ideas that should be covered
 in such tools.  I'm not saying those are infinitely far off, either.  I'm
 having some preliminary discussion with dgilmore & pbrobinson on how the
 Fedora Engineering team can pitch in to help with these tools and the
 process by which they're developed and tested for rel-eng use in
 production.

 I'm going to go ahead and tag this with keyword ''next'' with the
 understanding that other people may have better (or even just more
 immediate) ideas, and my intent is not to block those ideas.  This note is
 more to provide a reference point to help gather inputs.

-- 
Ticket URL: <https://fedorahosted.org/rel-eng/ticket/6081#comment:5>
Fedora Release Engineering <http://fedorahosted.org/rel-eng>
Release Engineering for the Fedora Project