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
<mrgla...@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-unsubscr...@xerces.apache.org
For additional commands, e-mail: j-dev-h...@xerces.apache.org
