Vladimir Sitnikov Saturday, December 30, 9:04 AM Thank you for the reminder that PMC is free to ignore the rules as they see fit. Unjustified and inappropriate snark. If this was a Rule it would say Must. It's a guideline, which Apache recognized could be deviated from, and the deviation is hardly a new one.
Yes, it should be fixed. No, it doesn't have to be fixed yesterday. Yes, the team is expected to triage issues. Yes, if you see this as critical you can offer to make it happen, understanding that doing so SHOULD not cause regressions in other areas and needs to justify itself as more important if it does. You've not being ignored. You aren't even being seriously disagreed with about the core issue, though there are additional factors to consider. I do disagree on priority, and I personally am not volunteering to tackle the majority of that request at this time. I may be more interested in throwing together the start of a go/no-go smoketest, or starting to migrate tests unique to Xalan into the Xalan project, though I'm not convinced either is the best place to spend my time right now. It can't all come first. -- /_ 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: Vladimir Sitnikov <sitnikov.vladi...@gmail.com> Sent: Saturday, December 30, 2023 9:03:57 AM To: dev@xalan.apache.org <dev@xalan.apache.org> Subject: Re: Policy question re src distribution >First, remember that SHOULD is not MUST, and that one of the distro files >(bin) is already fully compiled code and carries the binary dependencies to >run it, by design and decades-long history Thank you for the reminder that PMC is free to ignore the rules as they see fit. A decade-long bad practice is not the best excuse for adding more binaries to the mix. A year ago Gary said "migration to Maven would alleviate the binaries-in-source-packages issues", and the suggestion of adding more jars to the source release goes against the rules: https://lists.apache.org/thread/v6sxd9kb3r1m5qq0vv0t6gwg5wg99y9r Since the build system is going to switch anyway, the ones who build xalan-java from the source would have to adapt anyway. There's no point in reproducing decare-old source release packages byte-to-byte. Go ahead and remove the unnecessary stuff. >it wouldn't be impossible, just ugly. I do not see reasons to go for ugly solutions that deviate from the ASF policy. How about just skipping the ugly work and avoiding xalan-test in the xalan source package? The less you have to do the faster you can deliver the first iteration. If somebody wants to execute tests, they can download xalan-test and be done with it. Vladimir
