On Mon, 06 Aug 2007, Adeodato Simó wrote: > I'll throw my 2¢ here: > > The policy you have in place is there to ensure changes get reviewed > *before* being committed, partly because what gets commited gets > immediately published and hence Raphael's "review after commit via the > PTS diff mail" is not optimal. > > Parting from that, why not make the review process collaborative itself, > in a way similar (if I undersand correctly) the Policy maintainers are > implementing?:
[details skipped] I'd be fine with that. Another solution that I proposed was to use a tag to mark the version that ought to be published. That way we can commit and review in the CVS directly, and we can update the tag only when all parties are satisfied. http://www.debian.org/doc/cvs.fr.html#updates It should be a matter of doing a "cvs update -r <tag>" in the developers-reference checkout used to build the website. The sticky tag should ensure that further "cvs update" will follow that tag. Cheers, -- Raphaël Hertzog Premier livre français sur Debian GNU/Linux : http://www.ouaza.com/livre/admin-debian/
