Hi Joseph,
Thanks for the thoughts.
On Fri, Aug 25, 2023 at 7:18 AM Joseph Kessselman wrote:
> It might be worth considering, if just adding functions, making them a
> set of extension functions for now. Those could be a (nearly)
> independent release stream, and would let folks start using
We all make a few mistakes. I expect to make some more...
I'm still reloading my git knowledge, but I'm not sure deleting the .zip
is the best action from a Git point of view; I seem to remember that the
ideal thing in this case would be to roll the branch back to before the
zip was merged,
Hi Gary & all,
Apologies for the inconvenience.
On Fri, Aug 25, 2023 at 1:14 AM Gary Gregory wrote:
> No, you can't tag and just release on github. Releases must be voted on and
> then made available on the Apache dist server as sources. Any other format
> like binaries, Maven Central or
mukulga merged PR #61:
URL: https://github.com/apache/xalan-java/pull/61
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail:
mukulga opened a new pull request, #61:
URL: https://github.com/apache/xalan-java/pull/61
(no comment)
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe,
No, you can't tag and just release on github. Releases must be voted on and
then made available on the Apache dist server as sources. Any other format
like binaries, Maven Central or elsewhere are offered as conveniences.
Gary
On Thu, Aug 24, 2023, 2:52 PM Stanimir Stamenkov
wrote:
> Thu, 24
Thu, 24 Aug 2023 21:02:29 +0530, /Mukul Gandhi/:
On Thu, Aug 24, 2023 at 8:23 PM Vladimir Sitnikov wrote:
Binaries make it harder to review source provenance, and they make
git slower as it transfers more data.
... With that sense, this
committed zip archive having XalanJ related jar files,
Joseph Kessselman created XALANJ-2691:
-
Summary: Refactor: Replace direct DTM reference with XCI
Key: XALANJ-2691
URL: https://issues.apache.org/jira/browse/XALANJ-2691
Project: XalanJ2
This is against apache rules! We MUST vote on a release, not check it in
our own repository. You can label the version 3.0-alpha1 for example.
Please remove these binaries ASAP and start a release VOTE instead.
Gary
On Thu, Aug 24, 2023, 12:44 PM Joseph Kesselman
wrote:
> Mutual, I'm afraid I
Mutual, I'm afraid I think you're wrong on this one. There are appropriate ways
to share early/alpha prebuilds. Checking them into the source repository is not
a good one.
--
/_ Joe Kesselman (he/him/his)
-/ _) My Alexa skill for New Music/New Sounds fans:
/
Hi Vladimir,
Thanks for the thoughts.
On Thu, Aug 24, 2023 at 8:23 PM Vladimir Sitnikov
wrote:
> What is the point of commiting binaries to source control?
>
> Binaries make it harder to review source provenance, and they make git slower
> as it transfers more data.
>
> Please consider
Ah, this is what the gripe was about. Sorry, reading out of order...
The complaint was correct. Convenience binaries really shouldn't be committed
to the git repository.
--
/_ Joe Kesselman (he/him/his)
-/ _) My Alexa skill for New Music/New Sounds fans:
/
Could you be more specific, please?
True, we shouldn't be committing binaries of anything we can generate to our
source repository. There are a few binary dependencies which are there for
historical reasons, which we intend to clean up; there are issues open on the
backlog to address those.
Hi,
What is the point of commiting binaries to source control?
Binaries make it harder to review source provenance, and they make git
slower as it transfers more data.
Please consider other options like publishing snaphots to
repository.apache.org for preview purposes.
Vladimir
--
Vladimir
Hi all,
I've been wishing to write this mail.
We've committed sometime ago today, a zip archive at location
https://github.com/apache/xalan-java/blob/xalan-j_xslt3.0/xalan-j_xslt3.0_developer_binaries_2023-08-24.zip
[1] on XalanJ repos xalan-java's branch xalan-j_xslt3.0, built from
the latest
mukulga merged PR #60:
URL: https://github.com/apache/xalan-java/pull/60
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail:
mukulga opened a new pull request, #60:
URL: https://github.com/apache/xalan-java/pull/60
(no comment)
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe,
[
https://issues.apache.org/jira/browse/XALANJ-2690?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mukul Gandhi updated XALANJ-2690:
-
Description:
I'm creating this jira issue, to track implementation of following XPath 3.1
mukulga merged PR #59:
URL: https://github.com/apache/xalan-java/pull/59
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail:
mukulga opened a new pull request, #59:
URL: https://github.com/apache/xalan-java/pull/59
(no comment)
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe,
20 matches
Mail list logo
