Josh Boyer wrote:
Gee, I looked at Fedora's rpm CVS...wasn't a single bit of indication of
*any* activity of any sort there...makes a nice example of just how
broken and disconnected from modern SCM management our system currently
is.
That's right, we wouldn't want to see inflight development in the HEAD
of our package source control. That rapidly gets in the way of doing
mass rebuilds, scripted code compliance tests, targeted fixes strikes,
etc, etc...
Our package SCM is not a software development SCM.
Because you are not being in the least bit imaginative with branches
does not in the least justify the statement you are making.
OK, how about this:
Nobody has the time nor has anyone shown overwhelming benefits to rework
our entire infrastructure to deal with a new SCM for _packages_ so that
people can do code _development_ on them when that should all be done
_upstream_.
Distributed SCMs don't change where the development work happens, they
just eliminate much of the grunge work of picking up new changes along
with the need to store a million point-in-time snapshot copies.
--
Les Mikesell
lesmikesell@xxxxxxxxx
--
fedora-devel-list mailing list
fedora-devel-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/fedora-devel-list
