[Geoserver-devel] sharing of configuration directories across branches

Hi all,

Recently I have had this though. so i wanted to bring it up. I am
thinking there is probably a good reason for not doing this... perhaps
someone just needs to update my memory.

Currently we duplicate configuration directories whenever we create a
new branch. I am wondering it might be better to share them across
branches. The two major benefits i can see would be:

1. We would ensure backwards and forwards compatibility. It seems that
while we keep on adding stuff to the data directory we dont really test
how this will affect people upgrading from a previous data directory.

2. We would minimize duplication in svn :stuck_out_tongue:

Just something I was thinking about and thought i would fire it off to
the list. Feel free to poke holes in it :).

-Justin

--
Justin Deoliveira
The Open Planning Project
http://topp.openplans.org

Justin Deoliveira ha scritto:

Hi all,

Recently I have had this though. so i wanted to bring it up. I am
thinking there is probably a good reason for not doing this... perhaps
someone just needs to update my memory.

Currently we duplicate configuration directories whenever we create a
new branch. I am wondering it might be better to share them across
branches. The two major benefits i can see would be:

1. We would ensure backwards and forwards compatibility. It seems that
while we keep on adding stuff to the data directory we dont really test
how this will affect people upgrading from a previous data directory.

2. We would minimize duplication in svn :stuck_out_tongue:

Just something I was thinking about and thought i would fire it off to
the list. Feel free to poke holes in it :).

I agree for cite directories related to old protocols, but it would be bad for the release directory: if we add something that requires a new feature, the old branches would break with it (we are still not good enough to make software that's forward compatible).
I also would like to avoid piecemeal sharing, a data dir should
be entirely shared or not at all, to avoid making up the configuration
directory a tangle of svn links.
My 2 cents :slight_smile:

Cheers
Andrea