[jboss-as7-dev] JBoss AS 7.0.0.Beta1 tagged...

[Thomas Diesler]

How about creating a branch after code freeze. Any change to the branch 
must have a "very good reason" and would trigger a new test cycle. This 
would include external test suites that we know about. In practise WS, 
OSGi and possibly others would have to produce a stable hudson run on 
the latest code freeze branch.

On 03/17/2011 03:56 PM, David M. Lloyd wrote:
> I don't have any really good solution to this problem...
>
> On 03/17/2011 05:23 AM, Thomas Diesler wrote:
>> David, the AS test suite needs to be comprehensive - no doubt. However,
>> we have a release cycle that is different from AS and continuously test
>> a large set of OSGi functionality against AS7 trunk one a nightly basis.
>>
>> Following your suggested approach, I would need to duplicate every OSGi
>> example and functional test in the AS7 code base. Alternatively, I'm
>> suggesting to have a known "Code Freeze" date and give every subsystem
>> that has an external test suite a chance to verify/veto the intended
>> release code base.
>>
>> 1.0.0.Beta1 was broken for OSGi webapps because of last minute changes -
>> I'm looking for ways to possibly fix Beta1 and have a reasonable process
>> that avoids this to happen in the future.
>>
>> cheers
>> -thomas
>>
>> On 03/16/2011 02:30 PM, David M. Lloyd wrote:
>>> Thomas I think ultimately we need a comprehensive in-AS test suite.
>>> This is the only way we're going to be able to catch problems on an
>>> ongoing basis. I don't think we can afford to externally validate only
>>> once per release - I can absolutely guarantee that this will cause
>>> unexpected release delays.
>>>
>>> On 03/16/2011 04:27 AM, Thomas Diesler wrote:
>>>> Hi David,
>>>>
>>>> do we have a process that allows subsystem providers to verify a
>>>> potential AS7 release before it gets tagged? I have an extensive OSGi
>>>> testsuite that runs on a nightly basis against AS7 master. I noticed
>>>> this morning that this commit
>>>>
>>>> https://github.com/jbossas/jboss-as/commit/fd5696596545d9d9c2e4eb4c499bf3f1b7be62f1#server/src/main/java/org/jboss/as/server/deployment/Phase.java
>>>>
>>>>
>>>>
>>>> broke OSGi webapp support again. The related issue, which I now
>>>> reopened, is https://issues.jboss.org/browse/JBAS-8940
>>>>
>>>> Can we perhaps resolve this issue before Beta1 becomes generally
>>>> available?
>>>> To move forward I'll improve OSGi test coverage to a level were it
>>>> covers everything that is expected to work.
>>>>
>>>> cheers
>>>> -thomas
>>>>
>>>> On 03/16/2011 02:14 AM, David M. Lloyd wrote:
>>>>> I've pushed out a 7.0.0.Beta1-prerelease tag and updated upstream for
>>>>> Beta2 development. Later this week Jason will be setting the release
>>>>> "code name" and uploading the binary artifacts to be made available for
>>>>> downloading and taking care of all that business.
>>>>>
>>>>> Big thanks to everyone who put in extra effort to get this tag done. I
>>>>> expect that the official release announcement will be happening later
>>>>> this week.
>>>>>
>>>
>

-- 
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
Thomas Diesler
JBoss OSGi Lead
JBoss, a division of Red Hat
xxxxxxxxxxxxxxxxxxxxxxxxxxxx