The current 2.next branch should be master, assuming we are ready to commit to Maven. The only issue I know of preventing that release is inclusion of test in the distro archives, which I would like to see us phase out but I will concede maybe not in this release. Announce intent and "deprecate" perhaps.
I'm sure there is nothing "special" about Xalan release... but it has been decades since I did _any_ Apache release and I need a remainder of what buttons must be pushed, what checks are required, et cetera. Feel free to point me at the obvious doc I haven't yet found. Would I already have all the required permissions, or us that another hoop to be jumped through? I would still like to fold the 3.0 prototypes into the mainline branch at some point, while keeping their prototype nature clear. While I still think making them an extension package is the cleanest solution architecturally, we *could* consider adding them as built in but in a separate namespace; that wouldn't be as clean a code separation but would at least require that users be aware that they are using something 2.0 doesn't support. I'd prefer an extension-like Xalan-specific namespace since we aren't providing the rest of 3.0, but if my arm is twisted hard enough I might be willing to see them in the W3C's XSLT 3.0 namespace. -- /_ 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: Gary Gregory <garydgreg...@gmail.com> Sent: Sunday, June 9, 2024 9:25:21 AM To: dev@xalan.apache.org <dev@xalan.apache.org> Subject: Re: Xalan-J release discussion We can decide what we want that state to be ;-) I have questions before I experiment with running builds (below) and just poking around. There is no secret knowledge or hidden instructions to run builds and releases. It's whatever we have on the site and repo. Many moons (years) ago, I had asked questions on the mailing list about what branch contains what and builds. I never got answers so I did the best I could with what I could find. Our last release was 2.7.3 which Mukul performed (thank you!). What branch is the current 2.7.4 (or 2.8.0) work? Where is the XSLT 3 branch (I see two). Are they in sync with each other? GitHub shows the default branch as "trunk" in https://github.com/apache/xalan-j which surely can't be right. Or is it? I might not even be looking at the right repo! Hm, I see TWO repositories: - https://github.com/apache/xalan-j - https://github.com/apache/xalan-java Let's start with that dual repo mess, and delete the one we do not need. Hopefully, there isn't a mix of work in both repositories ;p Gary On Sun, Jun 9, 2024, 1:27 AM Joseph Kesselman <kesh...@alum.mit.edu<mailto:kesh...@alum.mit.edu>> wrote: Actually... There was discussion of putting out one more Ant build before cutting over. Problem is that either this would need to be from before I merged the Maven restructuring, or we would need to make sure any actual code changes got cherry-picked back into a new branch off that base (and possibly then rebase the Maven build upon that, if possible). The right answer may depend partly in who is willing to do how much of the work to make it happen. Which brings me back to wanting a clear statement of our current release process... -- /_ 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: Joseph Kesselman <kesh...@alum.mit.edu<mailto:kesh...@alum.mit.edu>> Sent: Saturday, June 8, 2024 7:47:08 PM To: dev@xalan.apache.org<mailto:dev@xalan.apache.org> <dev@xalan.apache.org<mailto:dev@xalan.apache.org>> Subject: Re: Xalan-J release discussion 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<mailto:gandhi.mu...@gmail.com>> Sent: Friday, June 7, 2024 6:52:12 AM To: dev@xalan.apache.org<mailto:dev@xalan.apache.org> <dev@xalan.apache.org<mailto: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<mailto:dev-unsubscr...@xalan.apache.org> For additional commands, e-mail: dev-h...@xalan.apache.org<mailto:dev-h...@xalan.apache.org>
