Agreed, renaming to main is for the next cycle, if there is one. Let's get this out the door.
Saxon is a fair point. Re growing Xalan to handle XSLT 2 or 3: certainly not a small task... I don't have a good sizing on that since our version was tangled into a migration from iterators over DTM to a cursor abstraction independent of the underlying document representation. As I remember it, most of the XSLT2 work was implementing additional axes (and extending the grammar to support them) and functions rather than major alterations of the processor's structure. I could be wrong. I'd like to see Xalan survive, after all the hours I put into it. But given that most hackers seem to have moved from XML to JSON and its cousins, and have been insistent upon reinventing everything we did rather than learning from it (or, better, adding JSON support to our tools), and that the HTML community fought against moving to xml-based, this whole ecosystem may be end-of-life. It would be good to know why folks who are now using Xalan have chosen to stay with it. The question really is how much folks want Xalan specifically and why... which may get back into whether they care enough to make Xalan happen, care enough to rework their products to use SAXON, or if the whole question is becoming moot. -- /_ Joe Kesselman (he/him/his) -/ _) My Alexa skill for New Music/New Sounds fans: / https://www.amazon.com/dp/B09WJ3H657/ () Plaintext Ribbon Campaign /\ Stamp out HTML mail! ________________________________ From: Gary Gregory <garydgreg...@gmail.com> Sent: Friday, March 24, 2023 7:20:05 AM To: dev@xalan.apache.org <dev@xalan.apache.org> Subject: Re: [request to review, and vote] XalanJ 2.7.3 release candidate RC9 My current POV on renaming branches is to not do it now or while we are trying to release 2.7.3. It's been a long road just to get where we are and adding yet another moving part is not going to help us release 2.7.3 sooner. Plus I don't need to spin my wheels updating scripts, and various bits and pieces I have laying around at this time. For the future, my current recommendation is to replace Xalan with SaxonHE because writing transformations in XSLT 2 and 3 is IMO so much easier than using Xalan which is still stuck on 1. The future of Xalan-J from my POV is to provide bug fixes which includes security updates, or move to the attic. Anything more feels unproductive in the big picture for me. Even the talk a long time ago of supporting XPath 2 through Psychopath (the Eclipse codebase?) did not happen. Yes, it would be nice to have a full feature XSLT 3 engine at Xalan but that's a multiple person year project IMO. And from a user's POV, why? When I can use SaxonHE today. There might be some perceived value for some contributors of pitching in and getting associated with Xalan but I would encourage such folk to step back and look at the big picture. Cheers, Gary On Fri, Mar 24, 2023, 06:42 Mukul Gandhi <muk...@apache.org<mailto:muk...@apache.org>> wrote: Hi Joseph, On Fri, Mar 24, 2023 at 3:40 PM Joseph Kesselman <kesh...@alum.mit.edu<mailto:kesh...@alum.mit.edu>> wrote: > > https://www.git-tower.com/learn/git/faq/git-rename-master-to-main > > Among others. There are social sensitivities which make "main" the preferred > name these days. It isn't critical, but it would be polite to make this > change at some point. Thanks for the thoughts. Following are my personal thoughts about this topic, Majority (I'd say near all) of git repositories have a default branch named 'master'. Changing XalanJ git repos's master branch to have another name (like 'main'), might confuse XalanJ users from the point of view of git source control system perspective. But I'd leave this analysis for possible action, to Gary. I've a different query to you, Do you have little time and interest to, port the following one of XalanJ test script for linux : https://github.com/apache/xalan-test/blob/master/tests/2.7.3_release/2.7.3_release.bat? -- Regards, Mukul Gandhi --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@xalan.apache.org<mailto:dev-unsubscr...@xalan.apache.org> For additional commands, e-mail: dev-h...@xalan.apache.org<mailto:dev-h...@xalan.apache.org>
