My experience with long lived branches, which this is bound to be, is that they don't work. They end up diverging too much, too often, and repeatedly merging from master (for example) is a pain (for the branch maintainer). It would be better IMO to have a realistic plan and split up that work in manageable PRs which can be merged into whatever the master branch is.
You are welcome to create the branch of course, but we should clean up what we have now first IMO. Why don't we rename xalan-j_2_7_1_maint to something more sensible first? What are in the other branches and should we keep them? Documenting all of this on the site would be nice as well. Gary On Wed, Apr 12, 2023, 07:41 Mukul Gandhi <muk...@apache.org> wrote: > Hi Gary & all, > I'm thinking to create following git new branches, for XalanJ, > > xalan-java repos : branch xalan-j_xslt3.0 from branch xalan-j_2_7_1_maint > > xalan-test repos : branch xalan-j_xslt3.0_tests from branch master > > to do XSLT 3.0 development and developing corresponding tests based on > current XalanJ implementation and tests codebase. > > After these new XalanJ branches are created, we can going forward > maintain current XalanJ XSLT 1.0 implementation as well from current > XalanJ git branches. > > Any thoughts please? > > > -- > Regards, > Mukul Gandhi > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@xalan.apache.org > For additional commands, e-mail: dev-h...@xalan.apache.org > >
