In order to know what version of product X goes in what installer
release we need some kind of installer roadmap with dates.
Amit Bhayani wrote:
Since JEMS Installer is all about different components, I believe it
would be great if leads of individual component drive the future
requirements.
I tried mailing jBPM, Portal, JBoss Messaging, Seam team number of
times on what they want but didn't get much response.
JEMS Installer 1.2.1CR2 which included JBoss AS 4.2.0.GA, JBoss
Messaging 1.2.0.SP1 and Portal 2.6CR3 (Lot of issues were faced here
to integrate portal 2.6.CR3 with JBoss AS 4.2.0.GA) is still in QA and
now I don't think it makes any sense to release as all these
components are already changed.
So going forward I would request individual leads to open up JIRA
request on what they want in next release of JEMS Installer, and
installer team will take care of it.
Also integration testing is one issue where we don't have concrete
answer, but remember this is just Community Installer for early
adoption of new releases of components so I guess emphasis should be
on releasing the Installer early in cycle rather than 100% accurate.
Amit.
Tim Fox wrote:
> 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
>