I made some requests months back about whether we could do a release, offering to do the work if someone could remind me of the process. The only outstanding issue that I remember offhand was the request to include xalan-test in the distro archives, which I hope to get back to soon. If you folks can't provide release instructions, tell me and I'll try to get them from someone else...
Mukul, re another ant release: I believe you confirmed that your changes build under Maven. If so I suggest releasing your branch with a Maven build as part of the move-to-Maven release. Two different build processes would not be healthy for the project. (This is also why I suggested you consider the approach we've taken with past early prototypes of future functionality, and make your changes Xalan extensions so they could be part of the base Xalan2 builds. You declined; I still not sure I understand why, but it's your sub-project and I don't feel I can demand that, even though I think it might be in your own best interest.) Gary, you were pushing hard for Maven and saying that you had plans to add some additional sanity checks to the Maven build once it existed. As noted above it arguably isn't quite complete yet, but it's near enough that you should have been able to start that work. Has more work been done on that front? I got assistance from sine Maven experts after swearing on a stack of Apache documents that we really were going to cut over so their efforts helping us wouldn't be wasted. While I am not as happy with Maven as I had hoped I would be, the migration *was* within epsilon of complete many months ago. Should I close the remaining gap and release, or has interest been lost? I agree that we're overdue to release. But I think we need consensus about what we're releasing. . -- /_ 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 <gandhi.mu...@gmail.com> Sent: Friday, June 7, 2024 6:52:12 AM To: dev@xalan.apache.org <dev@xalan.apache.org> Subject: Xalan-J release discussion Hi all, It seems to me that, as of now, Xalan-J codebase on the dev repos branch xalan-j_xslt3.0 has lots of working XSLT 3 implementation backed by many conformance tests available on dev repos branch xalan-j_xslt3.0 itself. Is it possible, we may make a formal, Xalan-J XSLT 3 user release via well known Ant build process, from dev repos branch xalan-j_xslt3.0? For now, I've mentioned Xalan-J release version as 2.8.0 within build.xml file available on dev repos branch xalan-j_xslt3.0. I'm aware that, we've a useful Maven build work available on Xalan-J dev repos branch 'master'/'main'. That's certainly useful work for Xalan-J's wider adoption, and for ease of availability of Xalan-J jars by Xalan-J user community. IMHO, any thoughts please, Gary Gregory & Joseph Kesselman and others as well about, making this proposed Xalan-J release? If Xalan-J team members on this list agree with, I'll be happy to volunteer to make this Xalan-J release. -- Regards, Mukul Gandhi --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@xalan.apache.org For additional commands, e-mail: dev-h...@xalan.apache.org
