[jbossws-dev] Code Freeze + Hudson QA Setup

[Thomas Diesler]

Hi Richard,

the intension of "code freeze" is that code freezes and there are no 
more changes ;-)

To do meaningful QA work you need to have a solid starting point and 
only allow for changes related to that QA work. This is because after 
any change you MUST do all the QA work again.

Looking at the road map
http://jira.jboss.org/jira/browse/JBWS?report=com.atlassian.jira.plugin.system.project:roadmap-panel

I see a number of open issues that should be resolved before QA work can 
start. The question really is, how much longer do we need to postpone 
the code freeze for all these issues to get resolved? How will this 
impact the release date?

I can answer this only for myself: JBWS-2058, JBWS-1932 should get fixed 
today, but not later than tomorrow

cheers
-thomas

Richard Opalka wrote:
> Hi Folks,
> 
>   as you know there was a code freeze on Friday.
> In order to create Hudson QA branch setup we need
> stable jbossws trunks.
>   At the moment there are two issues that we can see:
> * reopened exception handling issue [JBWS-1941] causing hudson 
> regression in native trunk
> * reopened metro build issue [JBWS-1994] causing hudson regression in 
> metro trunk
>   Alessio is already working on JBWS-1941 as I know.
> What about JBWS-1994? Are you working on it Heiko already?
> Are you too busy with SPI at the moment or you will fix this issue first?
> Or you want me to fix it for you? If yes, I need to know how to 
> correctly fix it. I read
> 
> http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4136582
> 
> forum but I'm not 100 % sure how to fix it correctly :(
> 
>   Are there any other outstanding issues folks that you want to push
> to the jbossws trunks before creating QA branches?
> 
> Richard
> 

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