Eric Kow writes:

 > If you mean identical modulo version bump, then the advantage of the
 > staging proposal is that packagers would not have to do the double work
 > of putting together the final rc and the binary.

This is not *double* the work.  As long as only the version number
changes (to remove the "rc" qualifier), the package is invariably made
by a script.  In my scripts, even uploading of successfully-built
packages can be automated (with a run-time option) for precisely this
purpose.

The real work (and frustration) comes with building the first rc:
checking the feature list to make sure you don't want to change the
list of linked libraries, working around any distro-specific issues,
etc.

YMMV, but ask the distro maintainers before assuming that this really
saves them a useful amount of work compared to the confusion caused by
having multiple versions *officially* labeled with the same tag.

 > Otherwise, the advantage is that if everything goes well, the packagers'
 > work is 100% done and we can announce source and binaries all in one go.

No, you can't.  In your scheme, you've already announced source, and
it *will* leak into production and tester environments.  This means
that if the rc fails in some way, there will be multiple versions in
use with the same tag.  This is a PITA for developers.
_______________________________________________
darcs-users mailing list
[email protected]
http://lists.osuosl.org/mailman/listinfo/darcs-users

Reply via email to