Hi Joseph, On Sun, Jan 28, 2024 at 9:11 PM Joseph Kesselman <kesh...@alum.mit.edu> wrote: > > I'm not sure our version system currently supports that kind of format; we > might want to change the product name field and make it xalan-xsl3alpha 2.7.4. > > Theoretically, all the file shuffling is recorded in the git history, so > there may (should?) be a semi-reasonable way to rebase your changes on the > Mavenized master without losing their history or having to reapply and > reconcile all your changes manually. We're going to need to converge them > eventually...
There's a small typo that I wish to correct within my previous mail. The correct text is as follows, "xalan-java repos's branch 'xalan-j_xslt3.0' has lot of first time XSLT 3.0 and XPath 3.1 *features* implementations." I guess that, it may be ok if we deliver like following, XalanJ release packages comprising the next XalanJ release, xalan-xsl1 2.7.4 (XSLT 1.0 + XPath 1.0 implementation release) xalan-xsl3alpha 2.7.4 (XSLT 3.0 + XPath 3.1 implementation release, using an implementation available on XalanJ dev repos branch 'xalan-j_xslt3.0') For producing both above mentioned XalanJ release packages, we could use an existing concept of 'tags' to freeze the XalanJ codebase before we build these XalanJ release packages. To produce the above two mentioned XalanJ release packages, we need to finalize which XalanJ's repos branch/branches should have the XalanJ codebase to perform XalanJ builds for next XalanJ release. >From my side, if you wish to take XalanJ's next release's responsibility that shall be great. If I could provide any support, for producing next XalanJ release, I'll be happy to do so. May be you, Gary and others as well, could share further their opinion about this topic. -- Regards, Mukul Gandhi --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@xalan.apache.org For additional commands, e-mail: dev-h...@xalan.apache.org
