Hi I think a branch for bundlelists is actually a good idea. Because we might want to release updated bundle lists in case of maintenance release ( =.=.+ ) of modules. If we do not create a branch it would be very hard to release upgraded bundle lists and launchers that include those modules.
If you like I can have a look at the bundle lists. I plan to make some improvements/changes to them anyway (e.g. ripping of the enhancement-engines from the enhancer bundle list in favor of an own bundle list(s) for enhancement engines. best Rupert On Wed, Jan 30, 2013 at 3:16 PM, Reto Bachmann-Gmür <[email protected]> wrote: > On Wed, Jan 30, 2013 at 3:08 PM, Fabian Christ <[email protected] >> wrote: > >> 2013/1/30 Fabian Christ <[email protected]>: >> > Release of stable launcher configurations and bundle lists comes next. >> >> BTW, if there is someone who wants to work on this, help is very welcome. >> >> Since the bundle lists in the trunk are all pointing to SNAPSHOT >> versions, the work on bundlelists with fixed bundle versions should be >> done in a branch. Or how do you think should we proceed with the >> bundle lists? >> > I don't see a big problem if the bunlelists in trunk temporarily point to > the released version. Much better than pointing to the previous snapshot. > Ideally of course this would be handled by the release plugin or the > launchpab plugin wouldhave the versions specified in the pom rather than in > the separate xml. > > Cheers, > Reto > > >> >> Best, >> - Fabian >> -- >> Fabian >> http://twitter.com/fctwitt >> -- | Rupert Westenthaler [email protected] | Bodenlehenstraße 11 ++43-699-11108907 | A-5500 Bischofshofen
