[jbosstools-dev] 3.3.1 / 5.0.1 - more JIRAs coming / latest respin almost done

[Jiri Peterka]

Deal. We'll finish CR1a testing until end of Friday, please respin to GA 
on Sunday if no blockers are reported until end of Friday.  No CR1b 
build will be done, I'll move rest of unresolved JIRAs to 3.3.2.
Thanks, Jirka

On 07/11/2012 06:01 PM, Nick Boldt wrote:
> Agree on all counts but this was a super-short runway (due to my PTO 
> starting July 18), and not all the issues we wanted done for Friday's 
> code freeze were done in time.
>
> So, yeah, non-ideal and we'll try to do better for the .2 maintenance 
> next time around (prolly in September, depending on when 6.0.0.M1 gets 
> scheduled.
>
> I'll hold off providing you a CR1b, and we can just respin as GA on 
> Sunday, unless you want me to wait until Monday night?
>
> On 07/11/2012 04:07 AM, Jiri Peterka wrote:
>> Hi Nick,
>>
>> if there is a new respin for these, it's not possible to perform new
>> build re-test in time (this week). For small-mid versions like 5.0.1
>> expected procedure is:
>>
>> 1. All issues in JIRA for 3.3.1 are fixed first or postponed
>> 2. Then QE Build for is delivered
>> 3. QE is testing a build (we need 1 week approximately for a build) - no
>> more new JIRA fixes during this period!
>> 4. If non-trivial tests pass, then sign-off & 1:1 respin to GA, if not
>> then new JIRAs are created and we are back at step 1
>> 5. GA is put to CSP and basic verification is done by QE
>>
>> Currently we almost break all those rules which is not good for smooth
>> testing process. I know there are be PTO & other planning reasons. Still
>> we definitely need to avoid similar situations next time. Mainly step 1
>> was not fulfilled and not all JIRAs has been fixed or postponed first
>> and some fixes are still coming under QA phase. For QE it's really
>> impossible to use a new build several times in one week and provide
>> consistent testing and test results. And another expectation that is
>> valid for small-mid updates is that dev phase on branch is done when QE
>> build is coming.
>>
>> Thanks for understanding, regards,
>>
>> Jirka
>>
>> On 07/11/2012 04:27 AM, Nick Boldt wrote:
>>> Just a heads up that a few more issues have been added to the .1 pile.
>>>
>>> == UNRESOLVED ==
>>>
>>> JBIDE-12299 : Widen dependency range to support Mylyn 3.8
>>>
>>>
>>> == RESOLVED, NEEDS VERIFICATION ==
>>>
>>> JBIDE-12273 : The Source Lookup plugin is not compatible with m2e 1.1
>>> (m2e Juno)
>>>
>>> JBIDE-12111 : dynamically set the maven-compiler-plugin for seam
>>> projects, in order to avoid constraint violation occurring when
>>> mavenizing seam 2.3 projects
>>>
>>> JBIDE-12207 : Bump default Seam version in the JBoss Maven Facet
>>> wizard page
>>>
>>> JBIDE-11310 : resetting models when user switches the openshift user
>>>
>>> JBDS-2219, JBDS-2220, JBDS-2221 : central connector tweaks for mylyn
>>>
>>>
>>> == VERIFIED CLOSED ==
>>>
>>> JBDS-2218 : add eclipse-cs to Central
>>>
>>> -- 
>>>
>>> Looks like the affected components have all built and now we're just
>>> waiting on the new updatesite/installer build for JBDS to finish.
>>>
>>
>>
>