Re: Coordinating OO-Browser Package Release with Core Changes

Jake> As I get ready to release the new OO-Browser package (to Jake> Norbert for pre-release) how do I coordinate that release Jake> with changes that I may request to lib-src? Specifically, Jake> I'd like xoobr to be built in lib-src as part of core and Jake> I'd like to see this included in 21.4. I realize, however, Jake> that just because I may submit a patch to build xoobr in Jake> lib-src it does not mean that a new 21.4 patch release will Jake> be released shortly thereafter. If you want it in 21.4, then things are easy. Vin Shelton is Lord Sheriff, Minister of the High and Low Justice. _Nobody_ commits to 21.4 without his permission anyway. Just submit the patches to xemacs-patches. If you really don't expect to work with 21.5 in the near future, then you really don't need core commit. A new file is preferably submitted as a patch against /dev/null, or (especially if it's the whole patch) as an attachment with a statement that it's a new file. Make it very clear that it's an attachment; they can be pretty easy to miss with some MUAs. I guess you need to add a stanza or so to the Makefile.in.in, and so on. How about configure requirements? Jake> If I submit a patch for 21.4 am I obligated to submit the Jake> same patch to 21.5? You simply state in the headers that the patch is intended for both 21.4 and 21.5. Preferably you should have tested that it will apply (for a new file this isn't a problem, of course, and since you'll be maintainer, presumably 21.4 and 21.5 versions of xoobr will stay in synch for quite a while). This is stated in somewhat more detail in your welcome mail, but feel free to ask for further clarification. -- Institute of Policy and Planning Sciences http://turnbull.sk.tsukuba.ac.jp University of Tsukuba Tennodai 1-1-1 Tsukuba 305-8573 JAPAN Ask not how you can "do" free software business; ask what your business can "do for" free software.