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

Reply via email to