You are viewing a plain text version of this content. The canonical link for it is here.
Posted to j-dev@xerces.apache.org by Carsten Pfeiffer <ca...@gebit.de.INVALID> on 2023/11/13 07:01:52 UTC
AW: XercesJ 2.12.3 release
Hi everyone,
there was a vote to release Xerces 2.12.3 in May 2022, which was cancelled due to lack of interest
(see https://www.mail-archive.com/j-dev@xerces.apache.org/msg06245.html).
And there was another request to create a release in April 2023 (see https://lists.apache.org/api/plain?thread=6lzq3fc2h3dn8gpw7ks885h765db546p), apparently without much feedback.
https://issues.apache.org/jira/browse/XERCESJ-1689 has a very important fix for running Xerces with any recent Java version (Java 9+, first released in 2017).
If there's anything I can do to move forward with this or help create the release, please let me know.
Thanks,
Carsten
________________________________
Von: Michael Glavassevich <mr...@ca.ibm.com>
Gesendet: Mittwoch, 19. April 2023 19:56
An: j-dev@xerces.apache.org <j-...@xerces.apache.org>
Betreff: RE: XercesJ 2.12.3 release
Hi Mukul,
Everyone on the PMC has an equal voice. There was a really good message sent out by Rich Bowen a few weeks back on this subject that would be good for everyone to read if they haven't already. Anyone who would volunteer to make a new release would be welcome to do that. I certainly support you and anyone else who wants to do that, but that never requires approval from me.
While on the subject of the PMC (and committers) it would be good to see some new additions. I know getting the existing PMC's attention for release votes these days can be challenging. I haven't had the bandwidth to approach anyone directly about their interests, but I think some of the more active participants around here might be good candidates, including those who benefit from Xerces indirectly through downstream projects like Xalan.
For anyone else reading this response, that is an open invitation to you if you're interested.
Thanks.
-----Original Message-----
From: Mukul Gandhi <mu...@apache.org>
Sent: April 10, 2023 10:16 AM
To: j-dev@xerces.apache.org
Subject: [EXTERNAL] Re: XercesJ 2.12.3 release
Hi all,
Wrt my previous mail below, following is XercesJ jira report, illustrating created vs resolved issues as of now, since the previous XercesJ release (2.12.2) was made,
https://issues.apache.org/jira/secure/ConfigureReport.jspa?projectOrFilterId=project-10520&periodName=quarterly&daysprevious=430&cumulative=false&versionLabels=all&selectedProjectId=10520&reportKey=com.atlassian.jira.jira-core-reports-plugin%3Acreatedvsresolved-report
It seems to me that, substantial XercesJ issues have been resolved during this mentioned time period.
Requesting XercesJ team (esp, Michael Glavassevich, our pmc chair), to advice whether we should make a new XercesJ release.
I'll be happy, to volunteer for this activity.
On Fri, Apr 7, 2023 at 6:08 PM Mukul Gandhi <mu...@apache.org> wrote:
> I think, as of now, there are various codebase fixes and
> improvements available within XercesJ svn repos, that're yet not
> released. These XercesJ implementation enhancements, are documented
> within the XercesJ svn repos, as part of release notes meta-data
> within XercesJ docs.
>
> The XercesJ latest build may be made, from codebase at
> INVALID URI REMOVED
> pos_asf_xerces_java_trunk_&d=DwIFaQ&c=jf_iaSHvJObTbx-siA1ZOg&r=KSsQtaT
> rbQnz98UqasbfUccVGXxb9hHxwso62zJ-DKI&m=DGbinHYpsrRmxgqxaUo4yQHzl3e63H1
> VVTP244F1_OVy8Shg5XfmuUlMFb7QHTx7&s=QWDPL8JjqfMaDqMKl-w0EVuIaeFuqrQDmXAawjzK4r4&e= and https://svn.apache.org/repos/asf/xerces/java/branches/xml-schema-1.1-dev/ , to view the latest XercesJ 2.12.3 release notes within the documentation.
>
> I'm thinking to, prepare a XercesJ 2.12.3 RC1, for review by XercesJ
> team for a possible release.
--
Regards,
Mukul Gandhi
---------------------------------------------------------------------
To unsubscribe, e-mail: j-dev-unsubscribe@xerces.apache.org
For additional commands, e-mail: j-dev-help@xerces.apache.org
B�KKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKCB�� [��X��ܚX�KK[XZ[��Y]�][��X��ܚX�P \��\˘\X�K�ܙ�B��܈Y][ۘ[��[X[� �K[XZ[��Y]�Z[ \��\˘\X�K�ܙ�B�
Re: XercesJ 2.12.3 release
Posted by Mukul Gandhi <mu...@apache.org>.
Hi all,
If anyone on this list thinks that, there may be any new issue
which is a blocker for the possibly upcoming XercesJ 2.12.3 release,
we could discuss that/those issue(s) on this list and create a XercesJ
jira issue for that, to track and resolve.
On Wed, Nov 15, 2023 at 6:10 AM Mukul Gandhi <mu...@apache.org> wrote:
>
> Hi Michael & all,
> For the XercesJ 2.12.3 release that we should try to make, if we
> may identify from existing XercesJ jira issues that're still
> unresolved (I'm suggesting to analyze any XercesJ blocker issues) that
> we need to resolve ideally via new code fixes or any other XercesJ
> configuration changes that we need to make, that'll be nice.
>
> Otherwise, we may make the XercesJ 2.12.3 new RC, by what is currently
> available on XercesJ svn repos (on 'trunk', and the branch
> 'xml-schema-1.1-dev').
--
Regards,
Mukul Gandhi
---------------------------------------------------------------------
To unsubscribe, e-mail: j-dev-unsubscribe@xerces.apache.org
For additional commands, e-mail: j-dev-help@xerces.apache.org
Re: XercesJ 2.12.3 release
Posted by Mukul Gandhi <mu...@apache.org>.
Hi Michael & all,
For the XercesJ 2.12.3 release that we should try to make, if we
may identify from existing XercesJ jira issues that're still
unresolved (I'm suggesting to analyze any XercesJ blocker issues) that
we need to resolve ideally via new code fixes or any other XercesJ
configuration changes that we need to make, that'll be nice.
Otherwise, we may make the XercesJ 2.12.3 new RC, by what is currently
available on XercesJ svn repos (on 'trunk', and the branch
'xml-schema-1.1-dev').
On Tue, Nov 14, 2023 at 12:41 PM Carsten Pfeiffer
<ca...@gebit.de.invalid> wrote:
>
> Thank you so much!
> I understand it's hard to find new maintainers, especially since XML and Xerces are well-established and known to just work.
>
> If it looks to be impossible to create new releases due to a shortage of PMC members, there is hopefully a process at Apache to deal with this situation.
>
> Again, if I can do anything to assist, technically or by asking ASF for help, let me know.
>
> Best wishes,
> Carsten
--
Regards,
Mukul Gandhi
---------------------------------------------------------------------
To unsubscribe, e-mail: j-dev-unsubscribe@xerces.apache.org
For additional commands, e-mail: j-dev-help@xerces.apache.org
AW: XercesJ 2.12.3 release
Posted by Carsten Pfeiffer <ca...@gebit.de.INVALID>.
Thank you so much!
I understand it's hard to find new maintainers, especially since XML and Xerces are well-established and known to just work.
If it looks to be impossible to create new releases due to a shortage of PMC members, there is hopefully a process at Apache to deal with this situation.
Again, if I can do anything to assist, technically or by asking ASF for help, let me know.
Best wishes,
Carsten
________________________________
Von: Mukul Gandhi <mu...@apache.org>
Gesendet: Dienstag, 14. November 2023 02:19
An: j-dev@xerces.apache.org <j-...@xerces.apache.org>
Betreff: Re: XercesJ 2.12.3 release
Hi Michael,
Thanks for the thoughts.
As you've suggested within your mail below about the XercesJ 2.12.3
release, I'll be happy to make a fresh RC around these days for
XercesJ 2.12.3 release and we can start the vote for that.
But I think, that'll require me about few weeks time (to prepare a RC
and to start the vote, for XercesJ 2.12.3 release). I need to check
the sanity of XercesJ source code again for the 2.12.3 release and few
other related tasks.
I guess you're the only other person these days other than me who
could make a XercesJ 2.12.3 release. It shall make all on XercesJ
forum very happy, if you could make the XercesJ 2.12.3 release :)
Otherwise, I could prepare RC for XercesJ 2.12.3 release and start a
vote for that.
On Tue, Nov 14, 2023 at 12:43 AM Michael Glavassevich
<mr...@ca.ibm.com> wrote:
>
> In order to have a successful vote on a release [1] it requires at least 3 +1 binding votes from members of the PMC. That has been a challenge as PMC members have become inactive / less active and other PMC members who haven’t been contributing to Xerces-J don’t tend to weigh in on the release votes.
>
> We’ve been trying to expand the PMC. Might have more success if a new vote were started now. I think Mukul otherwise had everything ready to go.
>
> Xerces desperately needs more volunteers. Personally, I help out when I can but I have very little time these days as I work on other projects and have less use of XML in my day-to-day activities. Xerces needs new committers and new PMC members in order for the project’s health to improve.
>
> Thanks.
> [1] https://www.apache.org/legal/release-policy.html#release-approval
--
Regards,
Mukul Gandhi
---------------------------------------------------------------------
To unsubscribe, e-mail: j-dev-unsubscribe@xerces.apache.org
For additional commands, e-mail: j-dev-help@xerces.apache.org
Thank
Re: XercesJ 2.12.3 release
Posted by Mukul Gandhi <mu...@apache.org>.
Hi Michael,
Thanks for the thoughts.
As you've suggested within your mail below about the XercesJ 2.12.3
release, I'll be happy to make a fresh RC around these days for
XercesJ 2.12.3 release and we can start the vote for that.
But I think, that'll require me about few weeks time (to prepare a RC
and to start the vote, for XercesJ 2.12.3 release). I need to check
the sanity of XercesJ source code again for the 2.12.3 release and few
other related tasks.
I guess you're the only other person these days other than me who
could make a XercesJ 2.12.3 release. It shall make all on XercesJ
forum very happy, if you could make the XercesJ 2.12.3 release :)
Otherwise, I could prepare RC for XercesJ 2.12.3 release and start a
vote for that.
On Tue, Nov 14, 2023 at 12:43 AM Michael Glavassevich
<mr...@ca.ibm.com> wrote:
>
> In order to have a successful vote on a release [1] it requires at least 3 +1 binding votes from members of the PMC. That has been a challenge as PMC members have become inactive / less active and other PMC members who haven’t been contributing to Xerces-J don’t tend to weigh in on the release votes.
>
> We’ve been trying to expand the PMC. Might have more success if a new vote were started now. I think Mukul otherwise had everything ready to go.
>
> Xerces desperately needs more volunteers. Personally, I help out when I can but I have very little time these days as I work on other projects and have less use of XML in my day-to-day activities. Xerces needs new committers and new PMC members in order for the project’s health to improve.
>
> Thanks.
> [1] https://www.apache.org/legal/release-policy.html#release-approval
--
Regards,
Mukul Gandhi
---------------------------------------------------------------------
To unsubscribe, e-mail: j-dev-unsubscribe@xerces.apache.org
For additional commands, e-mail: j-dev-help@xerces.apache.org
RE: XercesJ 2.12.3 release
Posted by Michael Glavassevich <mr...@ca.ibm.com>.
In order to have a successful vote on a release [1] it requires at least 3 +1 binding votes from members of the PMC. That has been a challenge as PMC members have become inactive / less active and other PMC members who haven’t been contributing to Xerces-J don’t tend to weigh in on the release votes.
We’ve been trying to expand the PMC. Might have more success if a new vote were started now. I think Mukul otherwise had everything ready to go.
Xerces desperately needs more volunteers. Personally, I help out when I can but I have very little time these days as I work on other projects and have less use of XML in my day-to-day activities. Xerces needs new committers and new PMC members in order for the project’s health to improve.
Thanks.
[1] https://www.apache.org/legal/release-policy.html#release-approval
From: Carsten Pfeiffer <ca...@gebit.de.INVALID>
Sent: Monday, November 13, 2023 2:02 AM
To: j-dev@xerces.apache.org
Subject: [EXTERNAL] AW: XercesJ 2.12.3 release
Hi everyone,
there was a vote to release Xerces 2.12.3 in May 2022, which was cancelled due to lack of interest
(see https://www.mail-archive.com/j-dev@xerces.apache.org/msg06245.html).
And there was another request to create a release in April 2023 (see https://lists.apache.org/api/plain?thread=6lzq3fc2h3dn8gpw7ks885h765db546p), apparently without much feedback.
https://issues.apache.org/jira/browse/XERCESJ-1689 has a very important fix for running Xerces with any recent Java version (Java 9+, first released in 2017).
If there's anything I can do to move forward with this or help create the release, please let me know.
Thanks,
Carsten
________________________________
Von: Michael Glavassevich <mr...@ca.ibm.com>>
Gesendet: Mittwoch, 19. April 2023 19:56
An: j-dev@xerces.apache.org<ma...@xerces.apache.org> <j-...@xerces.apache.org>>
Betreff: RE: XercesJ 2.12.3 release
Hi Mukul,
Everyone on the PMC has an equal voice. There was a really good message sent out by Rich Bowen a few weeks back on this subject that would be good for everyone to read if they haven't already. Anyone who would volunteer to make a new release would be welcome to do that. I certainly support you and anyone else who wants to do that, but that never requires approval from me.
While on the subject of the PMC (and committers) it would be good to see some new additions. I know getting the existing PMC's attention for release votes these days can be challenging. I haven't had the bandwidth to approach anyone directly about their interests, but I think some of the more active participants around here might be good candidates, including those who benefit from Xerces indirectly through downstream projects like Xalan.
For anyone else reading this response, that is an open invitation to you if you're interested.
Thanks.
-----Original Message-----
From: Mukul Gandhi <mu...@apache.org>>
Sent: April 10, 2023 10:16 AM
To: j-dev@xerces.apache.org<ma...@xerces.apache.org>
Subject: [EXTERNAL] Re: XercesJ 2.12.3 release
Hi all,
Wrt my previous mail below, following is XercesJ jira report, illustrating created vs resolved issues as of now, since the previous XercesJ release (2.12.2) was made,
https://issues.apache.org/jira/secure/ConfigureReport.jspa?projectOrFilterId=project-10520&periodName=quarterly&daysprevious=430&cumulative=false&versionLabels=all&selectedProjectId=10520&reportKey=com.atlassian.jira.jira-core-reports-plugin%3Acreatedvsresolved-report
It seems to me that, substantial XercesJ issues have been resolved during this mentioned time period.
Requesting XercesJ team (esp, Michael Glavassevich, our pmc chair), to advice whether we should make a new XercesJ release.
I'll be happy, to volunteer for this activity.
On Fri, Apr 7, 2023 at 6:08 PM Mukul Gandhi <mu...@apache.org>> wrote:
> I think, as of now, there are various codebase fixes and
> improvements available within XercesJ svn repos, that're yet not
> released. These XercesJ implementation enhancements, are documented
> within the XercesJ svn repos, as part of release notes meta-data
> within XercesJ docs.
>
> The XercesJ latest build may be made, from codebase at
> INVALID URI REMOVED
> pos_asf_xerces_java_trunk_&d=DwIFaQ&c=jf_iaSHvJObTbx-siA1ZOg&r=KSsQtaT
> rbQnz98UqasbfUccVGXxb9hHxwso62zJ-DKI&m=DGbinHYpsrRmxgqxaUo4yQHzl3e63H1
> VVTP244F1_OVy8Shg5XfmuUlMFb7QHTx7&s=QWDPL8JjqfMaDqMKl-w0EVuIaeFuqrQDmXAawjzK4r4&e= and https://svn.apache.org/repos/asf/xerces/java/branches/xml-schema-1.1-dev/ , to view the latest XercesJ 2.12.3 release notes within the documentation.
>
> I'm thinking to, prepare a XercesJ 2.12.3 RC1, for review by XercesJ
> team for a possible release.
--
Regards,
Mukul Gandhi
---------------------------------------------------------------------
To unsubscribe, e-mail: j-dev-unsubscribe@xerces.apache.org<ma...@xerces.apache.org>
For additional commands, e-mail: j-dev-help@xerces.apache.org<ma...@xerces.apache.org>
B�KKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKCB��[��X��ܚX�KK[XZ[
��Y]�][��X��ܚX�P‑\��\˘\X�K�ܙ�B��܈Y][ۘ[��[X[� �K[XZ[
��Y]�Z[ ‑\��\˘\X�K�ܙ�B�