Hi Reto, thanks for starting this. Sounds good to me ;)
Best, - Fabian 2013/6/6 Reto Bachmann-Gmür <[email protected]>: > Hi Rupert, > > Thanks for your suggestions. I'll go for the 2nd option. > > Currently I'm moving the parent but the plan is to gradually copy > everything to the branch. > > The branch should also contain a new minimum launcher providing no actual > functionality but acting as a test-bed for modules. > > Cheers, > Reto > > > > On Thu, Jun 6, 2013 at 2:50 PM, Rupert Westenthaler < > [email protected]> wrote: > >> HI >> >> IMO version numbers in a branch are not a big deal. We need only to >> decide before we merge back to the trunk. >> >> In my experience there are two things to consider - to allow efficient >> development and (integration) testing: >> >> 1. having the same version numbers in a branch makes it more easy for >> developers to test the branch version with together with trunk >> versions of other bundles (as you can just hot deploy branch versions >> of the branch to normal Stanbol Launchers) >> >> 2. having different version numbers makes it easier to work on trunk >> and branch stuff at the same time (as otherwise the local maven cache >> can easily become an issue). In this case it helps development to have >> an own launcher configuration in the branch that can be used for >> testing (I had done this for the disambiguation branch) >> >> In doubt I would rather opt for the 2nd option - increasing the >> version numbers and having an own launcher used for testing within the >> branch. >> >> BTW Do you plan to move the whole codebase to the branch, just the >> commons modules, or some other subset of modules? Currently the branch >> seams to only contain a parent/parent/pom.xml file. >> >> best >> Rupert >> >> >> On Thu, Jun 6, 2013 at 2:09 PM, Reto Bachmann-Gmür <[email protected]> >> wrote: >> > Hi, >> > >> > Following our previous discussion about the large code base and Ruperts >> > suggestion I've created a new commons-ng branch with the umbrella issue >> > STANBOL-1094. >> > >> > For versions I suggest to incrementent the versions of the components in >> > the branch to the next full version. I.e. most components would become >> > 1.0.0 and the parent becomes version 14. This means that if a parent is >> > relased before the branch one the version in trunk should become >> > 13.1-SNAPSHOT. WDYT? >> > >> > Cheers, >> > Reto >> >> >> >> -- >> | Rupert Westenthaler [email protected] >> | Bodenlehenstraße 11 ++43-699-11108907 >> | A-5500 Bischofshofen >> -- Fabian http://twitter.com/fctwitt
