Hi From the discussion I've got, that launchpad/bundles should point only to (stable) bundles which are already released or would be released soon in the next release.
There are two things which make me wonder: 1) Why should the launchpad/bundle be something more stable than the other stuff in the SVN? There's a (stable) release which ca be used by users if they do not wish to have the newest stuff which maybe is unstable. 2) Isn't it a more risky thing to let the tests use older stuff till short before the release where we update the pom maybe to some newer bundle. So tests run against old source. And second, maybe more important, also let the users which use the newest source from the SVN use older stuff. mostly they wouldn't recognize, that they do not use most recent bundles, because they think they checked out the most recent source and run just maven to build. I think it would be a benefit for the actual source to be more stable to be tested by users which check out newest source. My initial proposal was to make a new profile (at least) to make it easy to build a launchpad/app or launchpad/webapp which includes most recent source. WDYT? best regards mike > Lets step back for a moment and look at what we got and we need: > > 1. the bundles module refers to what gets released > 2. we should test what we release > > If we agree on this I think it is clear that the testing module should > really refer to the same set of bundles as what gets released (or > better: what's intended to be released next). Therefore the testing > module should be based on the bundles module. > > If we don't keep a single reference location for this > inclusion, we run > the high risk of inconsistency and running the release candidates > against the integration tests manually at release vote time > is IMHO not > really the best of all solutions ... > > Regards > Felix > > Bertrand Delacretaz schrieb: > > On Mon, May 18, 2009 at 10:57 AM, Carsten Ziegeler > <[email protected]> wrote: > >> Bertrand Delacretaz wrote: > >>> ...so we might want to go back and have > >>> launchpad/testing use its own set of bundles version numbers. > >>> > >>> WDYT? > > > >> Ok, we can do this - so this is kind of doing like gump is > doing its stuff. > >> But I see the potential problem that we release our launchpad stuff > >> which is never tested by the integration tests as they > test some never > >> stuff where problems might already be fixed/or different. > > > > This can be solved by (manually) running the launchpad/testing tests > > against an instance of Sling started by the app or webapp modules, > > like I did for the last release. > > > > Some tests might fail if they have been created for trunk > stuff that's > > not being released yet, but even in this case noting the differences > > will be useful. > > > > -Bertrand > > >
