We've had similar conversations before and I think we pretty much decided that backwards compatible changes without updating the namespace were ok.
(Although, from my understanding the recommended practice is to change the namespace each time a change is made) Jarek On Thu, Mar 26, 2009 at 8:28 AM, David Jencks <david_jen...@yahoo.com> wrote: > Following a user request here at apachecon eu I finally implemented the > ability to override env-entry elements in geronimo plans (GERONIMO-3954) > (also, I'm not sure if this works for ejbs -- is openejb using our env-entry > builder?) > > This requires a backwards compatible change to the geronimo naming schema. > > In the past we've tended to update the schema namespace by increasing the > version with every change although this has resulted in a lot of nuisance > and does not appear to be a recommended practice. > > So far I haven't updated the namespace. I'm very tempted to suggest that we > change our policy a bit and not change the namespace so often. > > Thoughts? > > thanks > david jencks >
