Andy> At 03:33 PM 1/6/2002 -0500, Vin Shelton wrote: Andy> I agree. release-21-4 does deliver the most recent 21.4 code, by definition. The code in candidate-21-4 is in not released, it's not part of 21.4. If to me it seems useful to do merges more frequently, I will. It's just me publishing my release workspace, and putting stuff in CVS for my own convenience, rather than doing a bunch of commits in a frenzy just before a release, which has bitten me hard several times. It also allows me to experiment with automating my commits, etc., without screwing up a release. Vin and Andy are welcome to work as they please, everyone else can ignore or use candidate-21-4 as they please. But that is my private branch, just as ben-mule-21-5 is Ben's or the gc stuff is Richard's. -- Institute of Policy and Planning Sciences http://turnbull.sk.tsukuba.ac.jp University of Tsukuba Tennodai 1-1-1 Tsukuba 305-8573 JAPAN Don't ask how you can "do" free software business; ask what your business can "do for" free software.

Jan> Is there a chance of convincing you to Jan> use the "head" in the 21.4 branch for the release candidate Jan> and mark the official releases with a tag?. Of course there is. So tell me, what's in it for XEmacs (and _me_) besides embarrassment when I commit something broken and people who just want the stable code check it out (given past policy there are undoubtedly a lot of workspaces with release-21-4 sticky tags)? And an extra merge for every rc? Of course I'll consider "consistency with how others do it" and benefits to other developers. But it will be more work for me and I don't see much gain, for me or for XEmacs. -- Institute of Policy and Planning Sciences http://turnbull.sk.tsukuba.ac.jp University of Tsukuba Tennodai 1-1-1 Tsukuba 305-8573 JAPAN Don't ask how you can "do" free software business; ask what your business can "do for" free software.