Hi all,
Given the lack of wider consensus on the list about the topic I've
raised below, lets keep the Xerces-J source repositories and process as
they're currently (i.e I give up my ideas mentioned in mail trail below).
I've also rethought about the below mentioned issues and think that, how
Xerces-J source repositories and process are structured currently is
valuable.
On Mon, Oct 28, 2019 at 4:55 PM Mukul Gandhi <muk...@apache.org> wrote:
> Currently, we have following two active source code locations for Xerces-J,
>
> 1) https://svn.apache.org/repos/asf/xerces/java/trunk/
> 2)
> https://svn.apache.org/repos/asf/xerces/java/branches/xml-schema-1.1-dev/
>
> Location 2) has all the functionality what location 1) has, and
> additionally an XSD 1.1 implementation.
>
> Can we make present contents of location 2) as the contents of trunk? And
> consider, present codebase on trunk as archived and move it to a folder
> like 'archive' on the svn.
>
> I think, this shall ease the maintenance efforts for Xerces-J going
> forward. With this, in future we would only develop for trunk (which will
> have present codebase of location '2)') and shall release only a single
> variant of Xerces-J (unlike presently, where we release one build from
> trunk and another one from location '2)').
>
> What do people on this list think about above mentioned suggestions?
>
--
Regards,
Mukul Gandhi
