You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@xalan.apache.org by Elliotte Rusty Harold <el...@ibiblio.org> on 2023/01/28 14:09:33 UTC
source location?
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
elharo@ibiblio.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@xalan.apache.org
For additional commands, e-mail: dev-help@xalan.apache.org
Re: source location?
Posted by Gary Gregory <ga...@gmail.com>.
Github is a mirror of the Apache Gitbox repository so it is already as true
;-)
Gary
On Mon, Jan 30, 2023, 08:05 Elliotte Rusty Harold <el...@ibiblio.org>
wrote:
> 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 <ga...@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 <el...@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 <mu...@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
> >> > <el...@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
> >> > > elharo@ibiblio.org
> >> >
> >> >
> >> > --
> >> > Regards,
> >> > Mukul Gandhi
> >> >
> >> > ---------------------------------------------------------------------
> >> > To unsubscribe, e-mail: dev-unsubscribe@xalan.apache.org
> >> > For additional commands, e-mail: dev-help@xalan.apache.org
> >> >
> >>
> >>
> >> --
> >> Elliotte Rusty Harold
> >> elharo@ibiblio.org
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: dev-unsubscribe@xalan.apache.org
> >> For additional commands, e-mail: dev-help@xalan.apache.org
> >>
>
>
> --
> Elliotte Rusty Harold
> elharo@ibiblio.org
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@xalan.apache.org
> For additional commands, e-mail: dev-help@xalan.apache.org
>
>
Re: source location?
Posted by Mukul Gandhi <mu...@apache.org>.
Hi Joseph,
On Tue, Jan 31, 2023 at 5:12 AM Joseph Kesselman <ke...@alum.mit.edu> wrote:
>
> Second the suggestion to reset Master to be a copy of the latest production release, so future development starts from that point.
Thanks, for the thoughts. I agree.
--
Regards,
Mukul Gandhi
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@xalan.apache.org
For additional commands, e-mail: dev-help@xalan.apache.org
Re: source location?
Posted by Joseph Kesselman <ke...@alum.mit.edu>.
Second the suggestion to reset Master to be a copy of the latest production release, so future development starts from that point.
Unless there's sufficient interest in doing a reconciliation pass...
--
/_ 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: Elliotte Rusty Harold <el...@ibiblio.org>
Sent: Monday, January 30, 2023 11:10:11 AM
To: dev@xalan.apache.org <de...@xalan.apache.org>
Subject: Re: source location?
On Mon, Jan 30, 2023 at 10:46 AM Mukul Gandhi <mu...@apache.org> wrote:
> But for XalanJ, this may not be easy to do. We'd need to identify, all
> deltas correctly for xalan-java repos between branch
> xalan-j_2_7_1_maint (just post the 2.7.3 release) and the master
> branch, and have those deltas synch to the master branch. Ideally,
> after this, the xalan-java's master branch shall need to be tested
> with the test suite that XalanJ has.
It's much easier than that. I am proposing that whatever source is
released as 2.7.3 becomes the main branch. Any changes in what is
currently on master that are not in 2.7.3 are simply wiped out. In the
unlikely event anyone wants to move some of them forward, that's what
history is for. I'm proposing we accept the truth that we have a
single maintained branch that only accepts bug fixes, and optimize the
workflow for what we're already doing.
--
Elliotte Rusty Harold
elharo@ibiblio.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@xalan.apache.org
For additional commands, e-mail: dev-help@xalan.apache.org
Re: source location?
Posted by Elliotte Rusty Harold <el...@ibiblio.org>.
On Mon, Jan 30, 2023 at 10:46 AM Mukul Gandhi <mu...@apache.org> wrote:
> But for XalanJ, this may not be easy to do. We'd need to identify, all
> deltas correctly for xalan-java repos between branch
> xalan-j_2_7_1_maint (just post the 2.7.3 release) and the master
> branch, and have those deltas synch to the master branch. Ideally,
> after this, the xalan-java's master branch shall need to be tested
> with the test suite that XalanJ has.
It's much easier than that. I am proposing that whatever source is
released as 2.7.3 becomes the main branch. Any changes in what is
currently on master that are not in 2.7.3 are simply wiped out. In the
unlikely event anyone wants to move some of them forward, that's what
history is for. I'm proposing we accept the truth that we have a
single maintained branch that only accepts bug fixes, and optimize the
workflow for what we're already doing.
--
Elliotte Rusty Harold
elharo@ibiblio.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@xalan.apache.org
For additional commands, e-mail: dev-help@xalan.apache.org
Re: source location?
Posted by Mukul Gandhi <mu...@apache.org>.
Hi Elliotte,
On Mon, Jan 30, 2023 at 6:35 PM Elliotte Rusty Harold
<el...@ibiblio.org> wrote:
> I would suggest that post 2.7.3 the current code be synced into the
> main branch and any future work proceed from there.
This is good for theory, and sometimes actually useful as well.
But for XalanJ, this may not be easy to do. We'd need to identify, all
deltas correctly for xalan-java repos between branch
xalan-j_2_7_1_maint (just post the 2.7.3 release) and the master
branch, and have those deltas synch to the master branch. Ideally,
after this, the xalan-java's master branch shall need to be tested
with the test suite that XalanJ has.
I suspect that, there can be chances of error to produce contents of
final master branch after the merge, in the most correct way.
I guess, it'll be better to, have us leave the xalan-java repos's
master branch remain as it's now (i.e, we just need to freeze master
branch as its now, and do no changes on that).
I believe that, the simplest and robust development approach, post
XalanJ 2.7.3 release can be, that we can create a new branch (with the
right name, perhaps like xalan-j_2_7_3_maint) from the branch
xalan-j_2_7_1_maint, and continue development on that new branch.
--
Regards,
Mukul Gandhi
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@xalan.apache.org
For additional commands, e-mail: dev-help@xalan.apache.org
Re: source location?
Posted by Elliotte Rusty Harold <el...@ibiblio.org>.
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 <ga...@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 <el...@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 <mu...@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
>> > <el...@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
>> > > elharo@ibiblio.org
>> >
>> >
>> > --
>> > Regards,
>> > Mukul Gandhi
>> >
>> > ---------------------------------------------------------------------
>> > To unsubscribe, e-mail: dev-unsubscribe@xalan.apache.org
>> > For additional commands, e-mail: dev-help@xalan.apache.org
>> >
>>
>>
>> --
>> Elliotte Rusty Harold
>> elharo@ibiblio.org
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@xalan.apache.org
>> For additional commands, e-mail: dev-help@xalan.apache.org
>>
--
Elliotte Rusty Harold
elharo@ibiblio.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@xalan.apache.org
For additional commands, e-mail: dev-help@xalan.apache.org
Re: source location?
Posted by Gary Gregory <ga...@gmail.com>.
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 <el...@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 <mu...@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
> > <el...@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
> > > elharo@ibiblio.org
> >
> >
> > --
> > Regards,
> > Mukul Gandhi
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@xalan.apache.org
> > For additional commands, e-mail: dev-help@xalan.apache.org
> >
>
>
> --
> Elliotte Rusty Harold
> elharo@ibiblio.org
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@xalan.apache.org
> For additional commands, e-mail: dev-help@xalan.apache.org
>
>
Re: source location?
Posted by Mukul Gandhi <mu...@apache.org>.
Hi Elliotte,
I'm replying to your questions inline below, as per my best
understanding. Someone, like Gary may correct me, if he wishes to do
so.
On Sun, Jan 29, 2023 at 6:21 PM Elliotte Rusty Harold
<el...@ibiblio.org> wrote:
> 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.
The XalanJ 2.7.3 RC9, should likely won't be finally released, since
that RC had few issues as were found during technical review after
that RC was released.
We've committed to XalanJ repos (implementation and tests repos) the
improvements, earlier sometime today, to address all the issues that
were found during technical review of RC9. People (the more reviews
shall be more helpful) on this list, should review these commits that
were done today, and provide their comments on this list. On basis, of
any review comments for the current state as of now of xalan-java
(branch xalan-j_2_7_1_maint) and xalan-test (branch master) repos,
we'll arrive at a decision about when and how to create the next
XalanJ 2.7.3 RC (i.e, RC10) which should again be reviewed by people
on this list for that to qualify as basis of final XalanJ 2.7.3
release.
> What's the current development process here? e.g. where/how should
> patches be sent?
I think, it'd be best to send XalanJ patches as pull requests (PRs),
on github mirror of XalanJ repos, and someone from XalanJ team shall
review them and merge to the real XalanJ repos. Anyone, wishing to
submit XalanJ PRs, should fork the relevant XalanJ branch on github
and submit the PR(s) to be merged to the real repos.
> When will the branch get merged to master?
My feeling is that, after XalanJ 2.7.3 is released from xalan-java
repos's branch xalan-j_2_7_1_maint, we could have options like below,
1) We continue to, develop on the xalan-java repos's branch
xalan-j_2_7_1_maint (in that case, merging of branch
xalan-j_2_7_1_maint to any other branch is not needed). My personal
feeling is, this is simple and best approach, since for XSLT 1.0
implementation development, XalanJ is already quite mature and only
rare bug fixes shall be needed.
This approach is also ok, since we'll create tag(s) [anyone can
download the distributable from tag, to know what was development
state when we've made XalanJ release] of the current repos state when
making a new XalanJ release.
2) We can create a new XalanJ branch from branch xalan-j_2_7_1_maint,
and develop on that new branch. With this approach, xalan-java master
branch will remain as it's now.
3) We can merge the XalanJ branch xalan-j_2_7_1_maint to master branch
(just to synch the master branch, with latest XalanJ development
state), and can continue developing on branch xalan-j_2_7_1_maint or
create a new branch from xalan-j_2_7_1_maint for further development.
Ideally, for usual development purposes, any code should not be
committed directly to XalanJ master branch.
--
Regards,
Mukul Gandhi
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@xalan.apache.org
For additional commands, e-mail: dev-help@xalan.apache.org
Re: source location?
Posted by Elliotte Rusty Harold <el...@ibiblio.org>.
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 <mu...@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
> <el...@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
> > elharo@ibiblio.org
>
>
> --
> Regards,
> Mukul Gandhi
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@xalan.apache.org
> For additional commands, e-mail: dev-help@xalan.apache.org
>
--
Elliotte Rusty Harold
elharo@ibiblio.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@xalan.apache.org
For additional commands, e-mail: dev-help@xalan.apache.org
Re: source location?
Posted by Mukul Gandhi <mu...@apache.org>.
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
<el...@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
> elharo@ibiblio.org
--
Regards,
Mukul Gandhi
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@xalan.apache.org
For additional commands, e-mail: dev-help@xalan.apache.org