On Thu, Nov 25, 2010 at 12:43 PM, Alan Coopersmith <[email protected]> wrote: > Dan Nicholson wrote: >> My rosy outlook is that maintainers keep the katamari moduleset updated >> when they make releases so it's always easy to build a full Xorg from >> the released sources. > > That would be more likely to happen if it was included in the instructions on > http://www.x.org/wiki/Development/Documentation/ReleaseHOWTO > > and much more likely to happen if release.sh could update the file for us, so > we just have to remember to go commit and push when done with a set of > releases.
Those both seem reasonable. If this gets committed I'll update the wiki and see what would need to be done for release.sh. > (Though 7.6-modules sounds like it should be a snapshot of 7.6, and you'd want > a latest-tarball-modules or stable-tarball-modules to be updated instead,) I was just thinking that once 7.6 was released that the file would get copied to xorg-7.7.modules and it would just keep getting updated until the next katamari. Although, I would understand keeping the version number out of there since it could imply a katamari that no one's actually planned for. You could call it xorg-next or something. -- Dan _______________________________________________ [email protected]: X.Org development Archives: http://lists.x.org/archives/xorg-devel Info: http://lists.x.org/mailman/listinfo/xorg-devel
