Just ran the tests against master (we should rename that branch, per
current conventions) on Linux.
It shows the same four fails in conf.xsltc, reporting successful.
Conclusion: No regression. Acceptable Linux release candidate.
On 3/23/2023 12:24 PM, Joseph Kesselman wrote:
The regression tests are now reporting success on Linux (and Windows,
I presume) despite the several known fails in compiled mode.
It is possible -- probable? -- that this means these are not new fails
but were present and "accepted" in the previous release. This can be
confirmed.
If so, then I would say we can release, with the issues remaining open
for next iteration. That would get us onto the new BCEL, which was our
immediate priority.
Unofficial vote: Assuming the above (which I'll check, and/or others
can), shoot this alligator. Then go back to deciding what to do about
the swamp. (Draining swamps is no longer a preferred action, but
managing them as productive habitat is certainly desirable.)
As far as the backlog goes... As a past committer/reviewer/etc., I
have been considering stepping back into a more active role. I would
need minimal to no onboarding on the code itself, though I could use a
refresher on the current formal processes. It sounds like demand
exists to justify at least some scheduled effort.
I certainly wouldn't object to being funded again to put some real
focus on it. But I can at least try to step it up a notch or three in
my spare-time priorities.
On the topic of finding: I presume Apache would have no objection to
some of us having tip jars open on Ko-fi and the like? Not exactly
salary, but it would give users a way to reward/encourage effort.
(A bounty system for releasing fixes might be another worthwhile
idea, as both incremental funding and a way for users to prioritize
their concerns, but I don't know if Apache has ever considered that
and figuring out who gets paid what could be tough, especially if a
fix goes through several stages of refinement.)
--
/_ 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 <elh...@ibiblio.org>
*Sent:* Thursday, March 23, 2023 11:36:01 AM
*To:* dev@xalan.apache.org <dev@xalan.apache.org>
*Subject:* Re: [request to review, and vote] XalanJ 2.7.3 release
candidate RC9
On Thu, Mar 23, 2023 at 10:22 AM Vladimir Sitnikov
<sitnikov.vladi...@gmail.com> wrote:
> Would you please recommend what I could do better to get xalan
released earlier?
I keep giving this answer on more than one open source project. Xalan
is just the latest. What you can do to get Xalan released faster is
**pay** committers and PMC members (I am neither on this project)
enough money to allow them to prioritize this work over everything
else going on in their lives.
Reviewing code and onboarding new developers is work that takes
limited time away from all the other tasks vying for the committers'
finite time. If it doesn't contribute in a meaningful way to
scratching the committers' own itch, don't expect it to get a lot of
attention.
--
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
