If you want the latest portal included with the latest installer, why don't you say so *before* we get to the last stages of releasing the damned thing? Like going to the jems installer JIRA and see what's included in the next installer release? http://jira.jboss.com/jira/browse/JBINSTALL Anyway, Rajesh's initial question was related to the how we now the combination works if there is no integration testing in CruiseControl. Same for JBoss Messaging. It's a valid point that needs to be fixed, however, I was thinking, those are community releases (not to say installer configs that are commonly perceived as previews) were we could take our chances and let the community test the combinations... Thomas Heute wrote: > True, please hold on for the JEMS installer. I'm about to tag JBoss > Portal 2.6.1 and we will get provide the bundle with JBoss AS4.2.1.GA. > > It would be awesome if the JEMS installer could provide the same > thing :) > > > Bolesław Dawidowicz wrote: >> I think that JBoss Portal 2.6.1 is going to ship AS 4.2.1.GA, and >> should come out like next week. >> >> Rajesh Rajasekaran wrote: >>> The JEMS installer for JBossAS 4.2.1.GA (JEMS Installer 1.2.1.CR3) >>> packages JBoss Portal 2.6.GA for the portal configuration >>> >>> and includes JBoss Messaging 1.3.0.GA. >>> >>> >>> >>> What should be the testing criteria for these components? >>> >>> >>> >>> JBoss Portal 2.6.GA ships with JBossAS 4.0.5.GA and there is no >>> continuous integration testing of portal 2.6.x with jboss-4.2.x. >>> >>> >>> >>> JBoss Messaging 1.3.0.GA was never included in JBoss AS Branch_4_2. >>> Is there some sort of integration testing that can be used >>> >>> for testing jboss messaging with JBoss AS 4.2.1.GA? >>> >>> >>> >>> The installer release process >>> (http://wiki.jboss.org/wiki/Wiki.jsp?page=JEMSInstallerReleaseGuide) >>> just verifies the functionalities of the >>> >>> Installer assuming all the components that go into it work together. >>> >>> >>> >>> I just brought this up to verify the above components work before >>> releasing the installer. >>> >>> >>> >>> >>> >>> Thanks >>> >>> Rajesh >>> >>> >>> >>> >>> ------------------------------------------------------------------------ >>> >>> >>> _______________________________________________ >>> jboss-development mailing list >>> jboss-development(a)lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/jboss-development >> >

I would prefer the installer team to hang on too, and include JBM 1.4.0, not 1.3.0 which is already superceded. Can we be involved in the process in the future, regarding timescales and release dates? Then we could advise better about the best version to include I can't see any release dates on JBINSTALL JIRA. When is the release date? Regarding integration tests, we have plenty, but as you know we have been prevented in adding them to AS because you guys don't want JBM there. Dimitris Andreadis wrote: > If you want the latest portal included with the latest installer, why > don't you say so *before* we get to the last stages of releasing the > damned thing? > > Like going to the jems installer JIRA and see what's included in the > next installer release? > http://jira.jboss.com/jira/browse/JBINSTALL > > Anyway, Rajesh's initial question was related to the how we now the > combination works if there is no integration testing in CruiseControl. > > Same for JBoss Messaging. > > It's a valid point that needs to be fixed, however, I was thinking, > those are community releases (not to say installer configs that are > commonly perceived as previews) were we could take our chances and > let the community test the combinations... > > Thomas Heute wrote: >> True, please hold on for the JEMS installer. I'm about to tag JBoss >> Portal 2.6.1 and we will get provide the bundle with JBoss AS4.2.1.GA. >> >> It would be awesome if the JEMS installer could provide the same >> thing :) >> >> >> Bolesław Dawidowicz wrote: >>> I think that JBoss Portal 2.6.1 is going to ship AS 4.2.1.GA, and >>> should come out like next week. >>> >>> Rajesh Rajasekaran wrote: >>>> The JEMS installer for JBossAS 4.2.1.GA (JEMS Installer 1.2.1.CR3) >>>> packages JBoss Portal 2.6.GA for the portal configuration >>>> >>>> and includes JBoss Messaging 1.3.0.GA. >>>> >>>> >>>> >>>> What should be the testing criteria for these components? >>>> >>>> >>>> >>>> JBoss Portal 2.6.GA ships with JBossAS 4.0.5.GA and there is no >>>> continuous integration testing of portal 2.6.x with jboss-4.2.x. >>>> >>>> >>>> >>>> JBoss Messaging 1.3.0.GA was never included in JBoss AS >>>> Branch_4_2. Is there some sort of integration testing that can be >>>> used >>>> >>>> for testing jboss messaging with JBoss AS 4.2.1.GA? >>>> >>>> >>>> >>>> The installer release process >>>> (http://wiki.jboss.org/wiki/Wiki.jsp?page=JEMSInstallerReleaseGuide) >>>> just verifies the functionalities of the >>>> >>>> Installer assuming all the components that go into it work together. >>>> >>>> >>>> >>>> I just brought this up to verify the above components work before >>>> releasing the installer. >>>> >>>> >>>> >>>> >>>> >>>> Thanks >>>> >>>> Rajesh >>>> >>>> >>>> >>>> >>>> ------------------------------------------------------------------------ >>>> >>>> >>>> _______________________________________________ >>>> jboss-development mailing list >>>> jboss-development(a)lists.jboss.org >>>> https://lists.jboss.org/mailman/listinfo/jboss-development >>> >> _______________________________________________ jboss-development mailing list jboss-development(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-development

Dimitris Andreadis wrote: > If you want the latest portal included with the latest installer, why > don't you say so *before* we get to the last stages of releasing the > damned thing? I missed the info. I also didn't know that 4.2.1.GA was about to get release until i made tests on 4.2.0.GA then received the notification yesterday. We have a hard time following you guys, what made us lose a lot of time for example was the migration from MyFaces to Sun RI on 4.2.0.GA.

Now on 4.2.1.GA you ship a version of Hibernate that is not even available on Hibernate.org (maybe not even tagged) and spits tons of warns. And so on, and so on.

If i was less busy trying to catch up with you i could spend more time looking ahead. > Like going to the jems installer JIRA and see what's included in the > next installer release? > http://jira.jboss.com/jira/browse/JBINSTALL Where are the dates ? Without dates it's useless. If you release the JEMS installer in 2 weeks, plan 2.6.1 if it's in a year it won't be that version. 2.6.1 is just a bug fix anyway.

> Anyway, Rajesh's initial question was related to the how we now the > combination works if there is no integration testing in CruiseControl. We need to have it run on 4.2.1.GA now, Prabhat is on vacation. So go ahead the the JEMS installer and Portal 2.6.0 sorry if i disturbed you. Next time, please ask us before you plan we could avoid this. Or send an email here *before* it is the last stages of releasing the damned thing. Don't push the little button on the joystick.