Nils Philippsen wrote:
And in particular, they don't describe how that workflow ensures that
the central build system knows that all distributed operations are
synchronized and what happens if they aren't.
that's actually easy. The now central and only repository would in fact
become one of many repositories, with one notable difference -- koji
would get its files from that repository. What is now "commit to central
repository, tag, build" would become "commit to local repository, tag,
push local changes to build repository, build". The synchronizing
between repositories is done by the DVCS tool or tools. Mind that DVCS
don't rely on every repository having the same content (that would be
rather pointless).
This is a different operation than having every developer have his own
copy - or at least one in every location where development happens. The
ability to work disconnected was being touted as a feature, But what
happens if a release needed to be done at the central build system and
the work some remote developer thinks is committed has not actually made
it there because it is still disconnected?
--
Les Mikesell
lesmikesell@xxxxxxxxx
--
fedora-devel-list mailing list
fedora-devel-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/fedora-devel-list
