#5894: git branches for SCL packages

[Fedora Release Engineering]

#5894: git branches for SCL packages
------------------------------+-----------------------
  Reporter:  mmaslano         |      Owner:  rel-eng@…
      Type:  task             |     Status:  new
 Milestone:  Fedora 21 Alpha  |  Component:  git
Resolution:                   |   Keywords:
Blocked By:                   |   Blocking:
------------------------------+-----------------------

Comment (by mmaslano):

 Replying to [comment:42 toshio]:
 > Replying to [comment:41 hhorak]:
 >
 > > As for the content not suitable for Fedora -- that's actually purpose
 of the topic branches, that there is some content not suitable for Fedora
 yet. I see no problem here either.
 >
 > This would be the crux of the disagreement.  In the past, the postiion
 has been content not suitable for Fedora does not belong in the Fedora
 pkgs git repo.

 Really? I regularly used in the past special branches for development of
 RC releases, which I merged later. Nightly branches are for prototype of
 the Continuous Integration. See PRD of Env and Stacks WG, which you co-
 created
 https://fedoraproject.org/wiki/Env_and_Stacks/Product_Requirements_Document#Continuous_integration_.28CI.29

 If you believe that nightly branches for Continuous Integration are wrong
 and shouldn't exist without explicit approval, then Env WG can write
 Change for F22 about it and ask FESCo. Usage of SCL in those branches is
 minor here. They are used because in this case it's easier to install
 nightly builds. Nigthly branches are all about Continuous Integration,
 which means attracting more developers because Fedora will support it and
 easier development of those components.

 As was pointed above those nightly will be merged without SCL into the
 main branch.

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