Thanks for the info. For the immediate 2.7.3 release whatever works is fine.
Going forward, it sounds like there's no active effort to support XSLT 2+, which is also fine. This does imply there's only one active branch, which is convenient. I'm a big fan of stable projects that do one thing and do it well. I would suggest that post 2.7.3 the current code be synced into the main branch and any future work proceed from there. Multi-branch development adds a large amount of extra complexity, effort, and documentation for any project that isn't releasing patches to older versions. It would also be convenient for developers if Github became the source of truth, as it is for many other Apache projects these days. However, I understand that might not be feasible if it would require changes to the release process and scripts we don't have time or funding for. On Sun, Jan 29, 2023 at 8:43 AM Gary Gregory <garydgreg...@gmail.com> wrote: > > Hi Eliotte, > > Xalan is not in good shape IMO mostly because the original authors have not > been around to maintain it. > > I've asked several times over many years on this list (back when we were > still using svn) what branch means what, how to best build this and that, and > other questions, and I never heard anything back. So we've had to fumble > along to the point where we even propose to retire Xalan-Java (Xalan-C is a > different story). I did the last 2.7.2 release many moons ago, and that was a > huge pain with much guess work. Mukul has done a fantastic job of picking up > the release management work for 2.7.3. > > Yes, there has been recent activity to release 2.7.3 mostly to pickup and > shade Apache Commons BCEL 6.7.0. There are other changes in there but the > driver is BCEL. > > Overall, I only see the point of using Xalan for maintenance when the cost of > switching to another implementation is not possible for users. > > Xalan does not support XSLT 2 or 3 and it would be a large effort to do so. > Writing XSLT 1 code is a pain, and when I need to write a non-trivial > stylesheet, I just use Saxon-HE. > > So... > > "where/how should patches be sent?" > > PRs on GitHub. > > "When will the branch get merged to master?" > > Probably never since no one knows with 100% certainty what is in each branch. > We have been going with xalan-j_2_7_1_maint which if is poorly named if that > is indeed the brach I use back when I did 2.7.2. > > HTH, > Gary > > On Sun, Jan 29, 2023, 07:51 Elliotte Rusty Harold <elh...@ibiblio.org> wrote: >> >> Thanks. Looks like master is still quite old but there's a >> xalan-j_2_7_3-rc9 that I think is what's being actively worked on. >> What's the current development process here? e.g. where/how should >> patches be sent? When will the branch get merged to master? >> >> On Sat, Jan 28, 2023 at 9:49 AM Mukul Gandhi <muk...@apache.org> wrote: >> > >> > Hi Elliotte, >> > The current XalanJ sources are on the git repos at following >> > location : https://gitbox.apache.org/repos/asf?p=xalan-java.git >> > (branch xalan-j_2_7_1_maint). >> > >> > We also, use the corresponding XalanJ tests repos at following >> > location : https://gitbox.apache.org/repos/asf?p=xalan-test.git >> > (branch master). >> > >> > On Sat, Jan 28, 2023 at 7:40 PM Elliotte Rusty Harold >> > <elh...@ibiblio.org> wrote: >> > > >> > > Where's the current source live these days? Most links on the website >> > > are broken, and the svn repo doesn't appear to have been touched since >> > > 2019. I see some release candidates are making the rounds but can't >> > > find any source code repo for them, at apache or github. >> > > >> > > -- >> > > Elliotte Rusty Harold >> > > elh...@ibiblio.org >> > >> > >> > -- >> > Regards, >> > Mukul Gandhi >> > >> > --------------------------------------------------------------------- >> > To unsubscribe, e-mail: dev-unsubscr...@xalan.apache.org >> > For additional commands, e-mail: dev-h...@xalan.apache.org >> > >> >> >> -- >> Elliotte Rusty Harold >> elh...@ibiblio.org >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: dev-unsubscr...@xalan.apache.org >> For additional commands, e-mail: dev-h...@xalan.apache.org >> -- Elliotte Rusty Harold elh...@ibiblio.org --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@xalan.apache.org For additional commands, e-mail: dev-h...@xalan.apache.org
