#5636: Use a staging area for test composes and safe practices when naming them

[Fedora Release Engineering]

#5636: Use a staging area for test composes and safe practices when naming them
------------------------------+-----------------------
  Reporter:  kparal           |      Owner:  rel-eng@…
      Type:  task             |     Status:  closed
 Milestone:  Fedora 19 Final  |  Component:  other
Resolution:  fixed            |   Keywords:
Blocked By:                   |   Blocking:
------------------------------+-----------------------
Changes (by ausil):

 * resolution:   => fixed
 * status:  reopened => closed


Comment:

 i changed the compose script to noty open up permission after things have
 been synced. the reason why things would show up empty  was that id
 noticed things went bad and ctrl-c killed the running process but not the
 script and it would go onto the next step. There is a lot of work to
 improve things but really what we have now is as good as it will get.

 We have a completely private staging area, Ḯ've been trying this cycle
 tyo automate many bits. its not entirely been perfect. but it has been
 constantly improving. all the scripts used are in the releng git repo and
 always have been. prior to F20 many of the steps were 100% manual, I would
 have to wait till things were done then kick off the next step.

 I believe that all composes should be public but Beta RC1 for instance did
 remain hidden from view.

 This ticket is the wrong place to offer help, please use the mailing list
 or preferably #fedora-releng where we could have a real time discussion.

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