Hi Reto, I generally agree but I've to say it doesn't sound really smart to have this back and forth version work on the branch, or at least a little annoying for the release manager. Apart from that +1, Tommaso
2013/2/12 Reto Bachmann-Gmür <[email protected]> > Hallo > > We have already been discussing this once: > > http://mail-archives.apache.org/mod_mbox/incubator-clerezza-dev/201203.mbox/%3ccaewfvjkk4czkwy+w3afuokob8i+00e4_dyq_-2wst1eeqzd...@mail.gmail.com%3E > > Now also after having more experience with the stanbol approach I > would like to suggest the following: > > 1) The dependency management does not contain internal dependencies > 2) All modules in trunk depend on the latest versions of the modules > in trunk, this is achieved by regularly running the mvn dependency > plugin > 3) before modules are relased they are copied to a branch and the > trunk snapshot-version is increased > 4) In the branch the module the dependencies to modules that are not > part of the released are switched back to the latest released version > (if incompatibilities become manifest the other modules are added to > the release branch) > 5) a release is prepared on the release branch > 6) vote > > The idea is to reduce to effort of developing in trunk whithout having > to worry about dependencies while making it straight forward to > release only a part of the modules. > > > WDYT? > > Cheers, > Reto >
