Hi Elliotte, On Mon, Jan 30, 2023 at 6:35 PM Elliotte Rusty Harold <elh...@ibiblio.org> wrote:
> I would suggest that post 2.7.3 the current code be synced into the > main branch and any future work proceed from there. This is good for theory, and sometimes actually useful as well. But for XalanJ, this may not be easy to do. We'd need to identify, all deltas correctly for xalan-java repos between branch xalan-j_2_7_1_maint (just post the 2.7.3 release) and the master branch, and have those deltas synch to the master branch. Ideally, after this, the xalan-java's master branch shall need to be tested with the test suite that XalanJ has. I suspect that, there can be chances of error to produce contents of final master branch after the merge, in the most correct way. I guess, it'll be better to, have us leave the xalan-java repos's master branch remain as it's now (i.e, we just need to freeze master branch as its now, and do no changes on that). I believe that, the simplest and robust development approach, post XalanJ 2.7.3 release can be, that we can create a new branch (with the right name, perhaps like xalan-j_2_7_3_maint) from the branch xalan-j_2_7_1_maint, and continue development on that new branch. -- Regards, Mukul Gandhi --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@xalan.apache.org For additional commands, e-mail: dev-h...@xalan.apache.org
