On Sep 25, 2007, at 12:38 PM, Jarek Gawor wrote:
Vamsi,
In general I think we agree on how things should be handled when
schema changes. Also, the patch I looked at had schema changes made in
the existing .xsd files and I assumed that the new files would be
introduced in trunk only. But since
On 9/26/07, Kevan Miller [EMAIL PROTECTED] wrote:
On Sep 25, 2007, at 12:38 PM, Jarek Gawor wrote:
Vamsi,
In general I think we agree on how things should be handled when
schema changes. Also, the patch I looked at had schema changes made in
the existing .xsd files and I assumed that
Vamsi,
In general I think we agree on how things should be handled when
schema changes. Also, the patch I looked at had schema changes made in
the existing .xsd files and I assumed that the new files would be
introduced in trunk only. But since nobody else has an issue with that
change, that's
I meant the geronimo-jetty-2.0.1.xsd, geronimo-web-2.0.1.xsd, and
geronimo-tomcat-2.0.1.xsd.
I guess the main question is what is our versioning policy (if any)
and what should and should not go into a patch and/or minor release.
Jarek
On 9/21/07, Vamsavardhana Reddy [EMAIL PROTECTED] wrote:
From ... I can live with introducing an optional element to an existing
schema in your original e-mail, I assume that you are not totally against
the schema changes. From what I understand, when a schema is changed
(except for some corrections in comments or some annotations), it can no
longer
