Given our dates have shifted for CR1 and GA, I suspect the answer is
yes to the notion that QE would have time to test these. But before I
open a bunch of JIRAs for QE to verify new versions of Central
contents, I need to know that PM wants these updates.
QE won't plan to test things unless we first decide we WANT to do the updates.
Process is generally this:
* request to update something in Central is opened as a JBDS/JBIDE JIRA
* Nick pulls a mirror onto dl.jb.o
* JIRA is assigned to QE; QE verifies that installation works and
functionality is not lost
* QE assigns JIRA back to Nick, who submits a PR for the Central TP updates
* email sent to this list for review / feedback
* changes are merged, built, and automated install tests are run
* JIRAs are resolved
* QE verifies and closes the JIRAs
HTH,
Nick
On Fri, Feb 26, 2016 at 9:54 AM, Alexey Kazakov <alkazako(a)redhat.com> wrote:
Len? Does QE have any plans to test anything from the list?
On 02/26/2016 12:22 AM, Nick Boldt wrote:
> Do we want to update anything in Central?
>
> For example, we could update to the latest Eclipse Checkstyle plugin
> 6.14 (currently 6.5):
>
>
https://issues.jboss.org/browse/JBDS-3518
>
> Do we want a newer version of any of these?
>
> * mylyn egit 4.1.1
> * m2e-wro4j 1.1
> * atlassian 3.2.5 w/ mylyn soap 3.11
> * pmd 4.0.7
> * springIDE 3.7.0
> * subclipse 1.10.9 w/ svnkit 1.8.10
> * testng 6.9.5
> * findbugs 3.0.1
>
> Many of the above are from March - June 2015, so by the time we GA
> they'll be ~1yr old.
>
> Is it worth looking for updated versions?
>
> If so, please let me know WHICH should be updated so I can open JIRAs
> to get QE to review the new versions, and then pull mirrors to update
> the Central target platform to the newer versions.
>
>
> On Wed, Feb 24, 2016 at 11:45 AM, Mickael Istria <mistria(a)redhat.com> wrote:
>> Hi all,
>>
>> We're in the last week to include upstream changes via target-platforms for
>> JBoss Tools 4.3.1 and JBDS 9.1.
>> So if you already need something, or know you'll need something to be
>> changed before code-freeze, please open a Jira immediately (and add the link
>> to it as an answer of this mail).
>>
>> Cheers,
>> --
>> Mickael Istria
>> Eclipse developer at JBoss, by Red Hat
>> My blog - My Tweets
>>
>> _______________________________________________
>> jbosstools-dev mailing list
>> jbosstools-dev(a)lists.jboss.org
>>
https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>
>
_______________________________________________
jbosstools-dev mailing list
jbosstools-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jbosstools-dev
--
Nick Boldt :: JBoss by Red Hat
Productization Lead :: JBoss Tools & Dev Studio
http://nick.divbyzero.com