Interesting question, Mukul. 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... -- /_ Joe Kesselman (he/him/his) -/ _) My Alexa skill for New Music/New Sounds fans: / https://www.amazon.com/dp/B09WJ3H657/ Caveat: Opinionated old geezer with overcompensated writer's block. May be redundant, verbose, prolix, sesquipedalian, didactic, officious, or redundant. ________________________________ From: Mukul Gandhi <muk...@apache.org> Sent: Sunday, January 28, 2024 4:54:45 AM To: dev@xalan.apache.org <dev@xalan.apache.org> Subject: Re: Release? Hi Joseph & all, On Sat, Jan 27, 2024 at 11:36 PM Joseph Kesselman <kesh...@alum.mit.edu> wrote: > Between these, I think we're getting close to the point where we should > consider a 2.7.4 release. Any agreement, disagreement, other? +1 from me, for having XalanJ's 2.7.4 XSLT 1.0 (comprising XPath 1.0 as well) release. I believe that, this release shall be built from xalan-java repos's 'master' branch, with a Maven build process. xalan-java repos's branch 'xalan-j_xslt3.0' has lot of first time XSLT 3.0 and XPath 3.1 implementations. Should we have a XalanJ simultaneous release named like as "2.7.4_xsl3_alpha1" from xalan-java repos's branch 'xalan-j_xslt3.0', using an existing Ant build process for now? -- Regards, Mukul Gandhi --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@xalan.apache.org For additional commands, e-mail: dev-h...@xalan.apache.org
