Hi,
> Independently of this question I think we should re-discus the release > process. I consider the release process as it is now as problematic for the > following reasons: > 1. When releasing a module we can either release all dependent modules > as well or move the dependencies back to the last released version. With > the first approach we end up releasing modules that did not change, with > the latter we have to make sure that there was indeed no relevant change in > the module or in any other module reached via this dependency. > 2. When releasing multiple modules, those modules that are not part of > the release have to be removed from reactor and deleted in the release > branch, otherwise they will be part of the source-zip. As after the release > we want to merge back the changes to the version number to master, we have > to do a complicated selective merge as we don’t want to merge back the > removal of modules nor the downgrading of dependencies. > Looking from a user perspective (as using clerezza components). I'd rather like all components to have the same version number. Like this I don't have to think about which component versions work together. I expect all component with the same version to work together well. In my opinion this is option 1. I don't mind about unchanged components being rebuild with a newer version. Actually I prefer it like this since it gives me confidence for the reason I gave before (everything with the same version works well together). To me its one of the first decisions we have to make. [a] Release the whole with a single version number [b] Release individual component with their own version number. I favour option [a]. Also option [a] makes using the maven versions plugin a lot easier. Who else? Regards, Minto
