I'm all for it. Since our current release is 2.12.0, it seems to me the next release should be 2.12.1 or 2.13.0, not 2.15.0. Skipping versions will just confuse users IMO.
Gary On Tue, Dec 10, 2019 at 7:11 AM Mukul Gandhi <muk...@apache.org> wrote: > Hi all, > I've been thinking that, whether we should make a new release of > Xerces2-J or not in near future. > > I think that, to decide about this, we should know how many Jira issues > we've fixed since our previous release (2.12.0). I've produced following > Jira report (as of today), depicting this: > > https://issues.apache.org/jira/secure/ConfigureReport.jspa?projectOrFilterId=project-10520&periodName=quarterly&daysprevious=589&cumulative=false&versionLabels=all&selectedProjectId=10520&reportKey=com.atlassian.jira.jira-core-reports-plugin%3Acreatedvsresolved-report&atl_token=A5KQ-2QAV-T4JA-FDED_fee8ee71d4783bd1c62bd857be93bd1af71bb7f1_lout&Next=Next > > The above report, shows for each quarter since our previous release, how > we've responded to reported jira issues (created vs resolved). Please also > look at, the 'Data Table' mentioned at bottom of above referred report > (that points to individual Jira issues). > > I've a feeling that, we could make a new Xerces2-J release (my suggested > new version number is, 2.15.0. any thoughts?) with the improvements as are > reflected within above mentioned Jira report. The issues fixed are not too > many since our 2.12.0 release, but the new Xerces2-J release could still be > valuable to community. > > Any thoughts from devs, shall be helpful to Xerces project. > > > > > -- > Regards, > Mukul Gandhi >
