<html><head><style type='text/css'>p { margin: 0; }</style></head><body><div style='font-family: Times New Roman; font-size: 12pt; color: #000000'><div>(Sorry for the delay - I am just back from PTO today - I was not able to reply when I was in Brno last week.)</div><div><br></div><div>It's not a disaster, as the QE team was able to verify the bug fixes - and move other bugs to 5.0.2 - but in future for patches/small updates, we should focus/limit the bug fixes to a controlled set. </div><div><br></div><div>The 5.0.1 release became a larger and more time-consuming effort that we had planned or wanted. </div><div><br></div><div><br></div>Thanks!,<div>Len</div><div><br></div><div><br></div><div>(Yeah - I would have voted for the minimalist approach. ;-)</div><div><br></div><div><br></div><div><br><br><hr id="zwchr"><blockquote style="border-left:2px solid rgb(16, 16, 255);margin-left:5px;padding-left:5px;color:#000;font-weight:normal;font-style:normal;text-decoration:none;font-family:Helvetica,Arial,sans-serif;font-size:12pt;"><b>From: </b>"Nick Boldt" <nboldt@redhat.com><br><b>To: </b>"Len DiMaggio" <ldimaggi@redhat.com><br><b>Cc: </b>"Jiri Peterka" <jpeterka@redhat.com>, "jbds-pm-list" <jbds-pm-list@redhat.com>, jbosstools-dev@lists.jboss.org, external-exadel-list@redhat.com<br><b>Sent: </b>Wednesday, July 11, 2012 7:08:40 PM<br><b>Subject: </b>Re: 3.3.1 / 5.0.1 - more JIRAs coming / latest respin almost done<br><br>AFAIK there were multiple plans in place. One minimalist one, and one <br>with a different set of urgent things to fix.<br><br>Max specifically asked that JBDS-2218, 2219, 2220, and 2221 get done <br>while he was AFK on PTO, but then later said we should only do the <br>smaller set. So, to resolve this conflicting direction, I went with the <br>superset.<br><br>---<br><br>As to uping versions of 3rd party plugins, that will have to slip to 5.0.2.<br><br>I've been waiting on feedback on these for at least a month:<br><br>https://issues.jboss.org/browse/JBIDE-11167 GWT VE & WB 2.5.x/2.6.x<br>https://issues.jboss.org/browse/JBDS-2187 GWT 2.5.x/2.6.x<br>https://issues.jboss.org/browse/JBDS-1998 subclipse 1.8<br>https://issues.jboss.org/browse/JBDS-2001 egit 1.3<br>https://issues.jboss.org/browse/JBDS-2032 testng 6.4<br>https://issues.jboss.org/browse/JBDS-2166 findbugs 2.0.1<br>https://issues.jboss.org/browse/JBDS-1627 jslint 1.5<br><br>Once they're accepted by QE I can push them into JBDS, but I need your <br>authorization to do so first. Note too that there's now a GWT 3.0.1 for <br>both Eclipse 3.7 and 4.2, which will ALSO need vetting - see <br>https://issues.jboss.org/browse/JBDS-2235 for that one - need to decide <br>if we want 3.0.1 in JBDS 5 and 6, or just 6. Since 3.0.1 is the first <br>version I found that supports Juno, I've added it to the reqs mirror and <br>TP in advance of your approvals simply because it's the only version <br>available. Should you deem it unacceptable, I'll of course remove it.<br><br>Cheers,<br><br>Nick<br><br>On 07/11/2012 05:53 PM, Len DiMaggio wrote:<br>> Greetings from Prague everyone,<br>><br>> This plan sounds good - but - I thought that the plan for 5.0.1/3.3.1<br>> was to fix these bugs, and no others?<br>> /<br>> /<br>> /> JBIDE-12249, A lot of failures to install from marketplace.eclipse.org<br>>> JBIDE-12248, JBoss Tools (Indigo) Installation from Eclipse Marketplace<br>>> fails for Eclipse Indigo 3.7.0 and 3.7.1<br>>><br>>> Are we also up-ing the versions of some 3rd party plugins?<br>>> JBDS-2212, audit version numbers of features/plugins in JBDS 5.0.0 vs.<br>>> 4.1.3/<br>><br>> The release seems to have grown quite a bit from this list.<br>><br>><br>> -- Len<br>><br>><br>><br>><br>> ------------------------------------------------------------------------<br>><br>> *From: *"Jiri Peterka" <jpeterka@redhat.com><br>> *To: *"Nick Boldt" <nboldt@redhat.com><br>> *Cc: *"jbds-pm-list" <jbds-pm-list@redhat.com>,<br>> jbosstools-dev@lists.jboss.org, external-exadel-list@redhat.com<br>> *Sent: *Wednesday, July 11, 2012 12:22:36 PM<br>> *Subject: *Re: 3.3.1 / 5.0.1 - more JIRAs coming / latest respin<br>> almost done<br>><br>> Deal. We'll finish CR1a testing until end of Friday, please respin<br>> to GA<br>> on Sunday if no blockers are reported until end of Friday. No CR1b<br>> build will be done, I'll move rest of unresolved JIRAs to 3.3.2.<br>> Thanks, Jirka<br>><br>> On 07/11/2012 06:01 PM, Nick Boldt wrote:<br>> > Agree on all counts but this was a super-short runway (due to my PTO<br>> > starting July 18), and not all the issues we wanted done for<br>> Friday's<br>> > code freeze were done in time.<br>> ><br>> > So, yeah, non-ideal and we'll try to do better for the .2<br>> maintenance<br>> > next time around (prolly in September, depending on when 6.0.0.M1<br>> gets<br>> > scheduled.<br>> ><br>> > I'll hold off providing you a CR1b, and we can just respin as GA on<br>> > Sunday, unless you want me to wait until Monday night?<br>> ><br>> > On 07/11/2012 04:07 AM, Jiri Peterka wrote:<br>> >> Hi Nick,<br>> >><br>> >> if there is a new respin for these, it's not possible to perform new<br>> >> build re-test in time (this week). For small-mid versions like 5.0.1<br>> >> expected procedure is:<br>> >><br>> >> 1. All issues in JIRA for 3.3.1 are fixed first or postponed<br>> >> 2. Then QE Build for is delivered<br>> >> 3. QE is testing a build (we need 1 week approximately for a<br>> build) - no<br>> >> more new JIRA fixes during this period!<br>> >> 4. If non-trivial tests pass, then sign-off & 1:1 respin to GA,<br>> if not<br>> >> then new JIRAs are created and we are back at step 1<br>> >> 5. GA is put to CSP and basic verification is done by QE<br>> >><br>> >> Currently we almost break all those rules which is not good for<br>> smooth<br>> >> testing process. I know there are be PTO & other planning<br>> reasons. Still<br>> >> we definitely need to avoid similar situations next time. Mainly<br>> step 1<br>> >> was not fulfilled and not all JIRAs has been fixed or postponed<br>> first<br>> >> and some fixes are still coming under QA phase. For QE it's really<br>> >> impossible to use a new build several times in one week and provide<br>> >> consistent testing and test results. And another expectation that is<br>> >> valid for small-mid updates is that dev phase on branch is done<br>> when QE<br>> >> build is coming.<br>> >><br>> >> Thanks for understanding, regards,<br>> >><br>> >> Jirka<br>> >><br>> >> On 07/11/2012 04:27 AM, Nick Boldt wrote:<br>> >>> Just a heads up that a few more issues have been added to the<br>> .1 pile.<br>> >>><br>> >>> == UNRESOLVED ==<br>> >>><br>> >>> JBIDE-12299 : Widen dependency range to support Mylyn 3.8<br>> >>><br>> >>><br>> >>> == RESOLVED, NEEDS VERIFICATION ==<br>> >>><br>> >>> JBIDE-12273 : The Source Lookup plugin is not compatible with<br>> m2e 1.1<br>> >>> (m2e Juno)<br>> >>><br>> >>> JBIDE-12111 : dynamically set the maven-compiler-plugin for seam<br>> >>> projects, in order to avoid constraint violation occurring when<br>> >>> mavenizing seam 2.3 projects<br>> >>><br>> >>> JBIDE-12207 : Bump default Seam version in the JBoss Maven Facet<br>> >>> wizard page<br>> >>><br>> >>> JBIDE-11310 : resetting models when user switches the openshift<br>> user<br>> >>><br>> >>> JBDS-2219, JBDS-2220, JBDS-2221 : central connector tweaks for<br>> mylyn<br>> >>><br>> >>><br>> >>> == VERIFIED CLOSED ==<br>> >>><br>> >>> JBDS-2218 : add eclipse-cs to Central<br>> >>><br>> >>> --<br>> >>><br>> >>> Looks like the affected components have all built and now we're<br>> just<br>> >>> waiting on the new updatesite/installer build for JBDS to finish.<br>> >>><br>> >><br>> >><br>> ><br>><br>><br>><br>><br>> --<br>><br>> Len DiMaggio (ldimaggi@redhat.com)<br>> JBoss by Red Hat<br>> 314 Littleton Road<br>> Westford, MA 01886 USA<br>> tel: 978.392.3179<br>> cell: 781.472.9912<br>> http://www.redhat.com<br>> http://community.jboss.org/people/ldimaggio<br>><br>> <http://www.redhat.com><br>><br><br>-- <br>Nick Boldt :: JBoss by Red Hat<br>Productization Lead :: JBoss Tools & Dev Studio<br>http://nick.divbyzero.com<br></blockquote><br><br><br>-- <br><div><span name="x"></span><br>Len DiMaggio (ldimaggi@redhat.com)<br>JBoss by Red Hat<br>314 Littleton Road<br>Westford, MA 01886 USA<br>tel: 978.392.3179<br>cell: 781.472.9912<br>http://www.redhat.com<br>http://community.jboss.org/people/ldimaggio<br><br><a href="http://www.redhat.com"><img style="border: 0pt none;" src="cid:c6c10e8d024a8fb399a68176671a77c1f39395dd@zimbra" doc="Briefcase/RHxJBpngthumb.png"></a><br><span name="x"></span><br></div></div></div></body></html>