Coordinating OO-Browser Package Release with Core Changes

As I get ready to release the new OO-Browser package (to Norbert for pre-release) how do I coordinate that release with changes that I may request to lib-src? Specifically, I'd like xoobr to be built in lib-src as part of core and I'd like to see this included in 21.4. I realize, however, that just because I may submit a patch to build xoobr in lib-src it does not mean that a new 21.4 patch release will be released shortly thereafter. So how are these things coordinated? Also, I am working with 21.4, not 21.5. If I submit a patch for 21.4 am I obligated to submit the same patch to 21.5? Or is there some higher power that ensures that all 21.4 patches are tweaked and applied to 21.5 as well? As an aside, the OO-Browser will function well without xoobr. It's just that some of its optional functionality will not be available until xoobr is available to it. -- Jake Colman Principia Partners LLC Phone: (201) 209-2467 Harborside Financial Center Fax: (201) 946-0320 902 Plaza Two E-mail: colman(a)ppllc.com Jersey City, NJ 07311 www.principiapartners.com Linux is not The Answer. Yes is the answer. Linux is The Question. - Neo