#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 toshio):
Past few days I've had a comaintainer on a package committing SCL work
destined for Copr into a "nightly" branch of the package. I've been
getting commit email about it. I've told him to stop but he's said he
wants it there because it's destined for copr. I think that having SCL
packages in the same repo, just in a different branch is problematic for
people mentally. They're thinking of the SCL conceptually as the same
package when it needs to be thought of as a different package. Taking
mingw packages as a the model again:
* the primary package maintainers do not see commit email for changes to
the mingw package or bug reports. That's not the case if we only use a
separate branch.
* the mingw package maintainer can opt-in or opt-out of getting commit and
bug mail about the primary package if the packages have diverged. That's
not the case here. (And should be more important here as the version of an
SCL stays behind the main package whereas the mingw package attempts to
keep up with the version in Fedora).
* mingw packages that have not been approved plainly do not belong in the
Fedora git repo as they're an unreviewed package. That's apparently not
clear with SCL as branch.
--
Ticket URL: <
https://fedorahosted.org/rel-eng/ticket/5894#comment:38>
Fedora Release Engineering <
http://fedorahosted.org/rel-eng>
Release Engineering for the Fedora Project