10:18 a.m.
TL;DR: use a filter to avoid unwanted email.
----
We've already discussed this [1], [2].
[1]
https://issues.jboss.org/browse/JBDS-2710?focusedCommentId=12850819&p...
[2]
https://issues.jboss.org/browse/JBDS-2710?focusedCommentId=12851040&p...
If you are getting too much JIRA notification email, please consider
filtering anything with a title containing "JBDS-" or "JBIDE-" which
also contains "edited comment" or "Nick Boldt updated JB" in the email
body. That's how I minimize the churn in my inbox, since I also get
those notifications.
For 3rd party validation issues, like JBDS-2710 and all the versions
that preceded it, I:
* maintain the description of the issue so that anyone can quickly look
at the issue and see what is happening for the current release of
Central / TP updates w.r.t. 3rd party content
* add status updates as new comments to the JIRA as well, so you can see
what has changed, why, and when.
It's a bit like *committing changes to a file in github*, so you can
*diff the versions*, but also *providing helpful commit comments* for
each change.
It's a workflow that works for me and provides TWO ways to track the
overall status of all the 3rd party content that Mickael & I have to
manage for each release.
Cheers,
On 11/15/2013 09:42 AM, Max Rydahl Andersen wrote:
Am I the only one that find it extremely hard to follow when we are
updating the description instead of simply use comments or subtasks
to provided updates ?
I was looking through jira notifications and I have ~80 changes to JBDS-2710 and each
delta lists everything...
Does it show up better for you all ?
Isn't there a better way to track this ? (like a subtask pr. component and if
globally relevant add comment to the aggregator ?)
Then you the emails will just contain the actual relevant change and the progress (done
or not done) can be seen in the subtask overview ?
Note, i've seen this happen with other jiras too but JBDS-2710 is just the
"biggest" one.
/max
----- Forwarded message from "Nick Boldt (JIRA)"
<jira-events(a)lists.jboss.org> -----
> From: "Nick Boldt (JIRA)" <jira-events(a)lists.jboss.org>
> To: manderse(a)redhat.com
> Date: Thu, 14 Nov 2013 16:00:08 -0500 (EST)
> Subject: [JBoss JIRA] (JBDS-2710) 3rd party certification for JBDS 7.1.0.GA
Tags: inbox
>
>
> [
https://issues.jboss.org/browse/JBDS-2710?page=com.atlassian.jira.plugin....
]
>
> Nick Boldt updated JBDS-2710:
> -----------------------------
>
> Description:
> For JBDS 7.1.0.GA, we need to ensure this list is as current and up to date as
possible.
>
> Proposed *new* connectors for JBDS 8.0:
>
> * SpringSource's Quick Search - JBDS-2686 (affects JBDS installer/Central TP) ::
*DROPPED FOR 7.1, TBD for 8.0*
>
> *New* connectors for JBDS 7.1:
>
> * Mylyn Builds Connector: Hudson/Jenkins org.eclipse.mylyn.hudson.feature
1.1.1.v20130917-0100 - JBDS-2724, JBDS-2752 :: Approved, will be in 7.1.0.Beta1
> * m2e-wro4j 1.0.2 connector - JBDS-2577 :: Approved for 7.1.0.CR1
>
> The current list of connectors in 7.0 *which can be / have been updated* in 7.1 are:
>
> *Beta1*
> * atlassian/3.2.1.v20130402 --> 3.2.2.v20130909 - JBIDE-13682, JBDS-2774 ::
Approved, will be in 7.1.0.Beta1 (affects JBT/JBDS/Central TP)
> * pmd/4.0.0.v20130510-1000 --> 4.0.1 - JBIDE-14902, JBIDE-15353 :: Approved, will
be in 7.1.0.Beta1
> * testng/6.8.1.20130330_0839/ --> 6.8.6.20130914_0724 - JBDS-2415, JBDS-2800 ::
Approved, will be in 7.1.0.Beta1 (affects JBDS installer/Central TP)
>
> *CR1*
> * VJET 0.10.0.x --> 0.10.0.201309201624 - JBIDE-14764, JBIDE-15677
(0.10.0.201309201624 will appear in CR1)
> * eclipsecs/5.6.0.201209221626 (Removed in JBIDE-14799 due to Kepler incompatibility)
--> 5.6.1.201306282206 - JBIDE-15128, JBIDE-15129 (added for CR1)
> * springide/3.3.0.201307091516-RELEASE --> 3.4.0.201310051539-RELEASE -
JBDS-2690�, JBDS-2691�, JBDS-2802, JBDS-2808, JBDS-2719
> * gwt/3.2.3.v201304260926-rel-r42 --> 3.4.2.v201310081834-rel-*r43 ONLY* -
JBDS-2486, JBDS-2801 (affects JBT/JBDS/Central TP)
>
> *CR1 or GA, TBD*
> * subclipse/1.8.20_1.7.9.1 --> 1.10_1.8 - JBDS-2485, JBDS-2709
>
> These are currently unchanged since December when we released JBDS 6.0.0:
>
> * findbugs/2.0.2.20121210 - nothing new as of 2013.10.15
>
> Additionally (Target Platform):
>
> * swtbot 2.1.1.201305311053 / junit4 - JBIDE-13843 (included in JBT TP; needed for
running UI tests)
> ** Could move up to 2.1.1.201307101628 or 2.1.2.201310__ if we want... -
http://wiki.eclipse.org/SWTBot#Latest_snapshot_build
>
> JBoss Tools Locus (for use with Teiid in JBT-IS/JBDS-IS only):
>
> * mockito/1.9.5 - JBIDE-12971� (to be included in JBT Locus 1.0.0 [1,2,3])
> * fest-assert/1.4 & fest-util/1.1.6 - JBIDE-12972� (to be included in JBT Locus
1.0.1 [1,2,3])
>
> See comments below for latest site URLs.
>
> [1] https://github.com/jbosstools/jbosstools-locus/
> [2]
https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-locus.sit...
> [3] http://download.jboss.org/jbosstools/updates/nightly/locus/trunk/
>
> � - These issues did not block the release of JBDS 7.0.0.GA, and therefore would not
block 7.1.0, but might be fixed by upgrading to SpringIDE 3.4.
>
> was:
> For JBDS 7.1.0.GA, we need to ensure this list is as current and up to date as
possible.
>
> Proposed *new* connectors for JBDS 8.0:
>
> * SpringSource's Quick Search - JBDS-2686 (affects JBDS installer/Central TP) ::
*DROPPED FOR 7.1, TBD for 8.0*
>
> *New* connector for JBDS 7.1:
>
> * Mylyn Builds Connector: Hudson/Jenkins org.eclipse.mylyn.hudson.feature
1.1.1.v20130917-0100 - JBDS-2724, JBDS-2752 :: Approved, will be in 7.1.0.Beta1
> * m2e-wro4j 1.0.2 connector - JBDS-2577 :: Approved for 7.1.0.CR1
>
> The current list of connectors in 7.0 *which can be / have been updated* in 7.1 are:
>
> *Beta1*
> * atlassian/3.2.1.v20130402 --> 3.2.2.v20130909 - JBIDE-13682, JBDS-2774 ::
Approved, will be in 7.1.0.Beta1 (affects JBT/JBDS/Central TP)
> * pmd/4.0.0.v20130510-1000 --> 4.0.1 - JBIDE-14902, JBIDE-15353 :: Approved, will
be in 7.1.0.Beta1
> * testng/6.8.1.20130330_0839/ --> 6.8.6.20130914_0724 - JBDS-2415, JBDS-2800 ::
Approved, will be in 7.1.0.Beta1 (affects JBDS installer/Central TP)
>
> *CR1*
> * VJET 0.10.0.x --> 0.10.0.201309201624 - JBIDE-14764, JBIDE-15677
(0.10.0.201309201624 will appear in CR1)
> * eclipsecs/5.6.0.201209221626 (Removed in JBIDE-14799 due to Kepler incompatibility)
--> 5.6.1.201306282206 - JBIDE-15128, JBIDE-15129 (added for CR1)
> * springide/3.3.0.201307091516-RELEASE --> 3.4.0.201310051539-RELEASE -
JBDS-2690�, JBDS-2691�, JBDS-2802, JBDS-2808, JBDS-2719
> * gwt/3.2.3.v201304260926-rel-r42 --> 3.4.2.v201310081834-rel-*r43 ONLY* -
JBDS-2486, JBDS-2801 (affects JBT/JBDS/Central TP)
>
> *CR1 or GA, TBD*
> * subclipse/1.8.20_1.7.9.1 --> 1.10_1.8 - JBDS-2485, JBDS-2709
>
> These are currently unchanged since December when we released JBDS 6.0.0:
>
> * findbugs/2.0.2.20121210 - nothing new as of 2013.10.15
>
> Additionally (Target Platform):
>
> * swtbot 2.1.1.201305311053 / junit4 - JBIDE-13843 (included in JBT TP; needed for
running UI tests)
> ** Could move up to 2.1.1.201307101628 or 2.1.2.201310__ if we want... -
http://wiki.eclipse.org/SWTBot#Latest_snapshot_build
>
> JBoss Tools Locus (for use with Teiid in JBT-IS/JBDS-IS only):
>
> * mockito/1.9.5 - JBIDE-12971� (to be included in JBT Locus 1.0.0 [1,2,3])
> * fest-assert/1.4 & fest-util/1.1.6 - JBIDE-12972� (to be included in JBT Locus
1.0.1 [1,2,3])
>
> See comments below for latest site URLs.
>
> [1] https://github.com/jbosstools/jbosstools-locus/
> [2]
https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-locus.sit...
> [3] http://download.jboss.org/jbosstools/updates/nightly/locus/trunk/
>
> � - These issues did not block the release of JBDS 7.0.0.GA, and therefore would not
block 7.1.0, but might be fixed by upgrading to SpringIDE 3.4.
>
>
>
>> 3rd party certification for JBDS 7.1.0.GA
>> -----------------------------------------
>>
>> Key: JBDS-2710
>> URL: https://issues.jboss.org/browse/JBDS-2710
>> Project: Developer Studio (JBoss Developer Studio)
>> Issue Type: Feature Request
>> Security Level: Public(Everyone can see)
>> Components: 3rd-party-certification, 3rd-party-dependencies,
requirements
>> Affects Versions: 7.0.0.GA
>> Reporter: Max Rydahl Andersen
>> Assignee: Len DiMaggio
>> Priority: Blocker
>> Fix For: 7.1.0.GA
>>
>>
>> For JBDS 7.1.0.GA, we need to ensure this list is as current and up to date as
possible.
>> Proposed *new* connectors for JBDS 8.0:
>> * SpringSource's Quick Search - JBDS-2686 (affects JBDS installer/Central TP)
:: *DROPPED FOR 7.1, TBD for 8.0*
>> *New* connectors for JBDS 7.1:
>> * Mylyn Builds Connector: Hudson/Jenkins org.eclipse.mylyn.hudson.feature
1.1.1.v20130917-0100 - JBDS-2724, JBDS-2752 :: Approved, will be in 7.1.0.Beta1
>> * m2e-wro4j 1.0.2 connector - JBDS-2577 :: Approved for 7.1.0.CR1
>> The current list of connectors in 7.0 *which can be / have been updated* in 7.1
are:
>> *Beta1*
>> * atlassian/3.2.1.v20130402 --> 3.2.2.v20130909 - JBIDE-13682, JBDS-2774 ::
Approved, will be in 7.1.0.Beta1 (affects JBT/JBDS/Central TP)
>> * pmd/4.0.0.v20130510-1000 --> 4.0.1 - JBIDE-14902, JBIDE-15353 :: Approved,
will be in 7.1.0.Beta1
>> * testng/6.8.1.20130330_0839/ --> 6.8.6.20130914_0724 - JBDS-2415, JBDS-2800
:: Approved, will be in 7.1.0.Beta1 (affects JBDS installer/Central TP)
>> *CR1*
>> * VJET 0.10.0.x --> 0.10.0.201309201624 - JBIDE-14764, JBIDE-15677
(0.10.0.201309201624 will appear in CR1)
>> * eclipsecs/5.6.0.201209221626 (Removed in JBIDE-14799 due to Kepler
incompatibility) --> 5.6.1.201306282206 - JBIDE-15128, JBIDE-15129 (added for CR1)
>> * springide/3.3.0.201307091516-RELEASE --> 3.4.0.201310051539-RELEASE -
JBDS-2690�, JBDS-2691�, JBDS-2802, JBDS-2808, JBDS-2719
>> * gwt/3.2.3.v201304260926-rel-r42 --> 3.4.2.v201310081834-rel-*r43 ONLY* -
JBDS-2486, JBDS-2801 (affects JBT/JBDS/Central TP)
>> *CR1 or GA, TBD*
>> * subclipse/1.8.20_1.7.9.1 --> 1.10_1.8 - JBDS-2485, JBDS-2709
>> These are currently unchanged since December when we released JBDS 6.0.0:
>> * findbugs/2.0.2.20121210 - nothing new as of 2013.10.15
>> Additionally (Target Platform):
>> * swtbot 2.1.1.201305311053 / junit4 - JBIDE-13843 (included in JBT TP; needed
for running UI tests)
>> ** Could move up to 2.1.1.201307101628 or 2.1.2.201310__ if we want... -
http://wiki.eclipse.org/SWTBot#Latest_snapshot_build
>> JBoss Tools Locus (for use with Teiid in JBT-IS/JBDS-IS only):
>> * mockito/1.9.5 - JBIDE-12971� (to be included in JBT Locus 1.0.0 [1,2,3])
>> * fest-assert/1.4 & fest-util/1.1.6 - JBIDE-12972� (to be included in JBT
Locus 1.0.1 [1,2,3])
>> See comments below for latest site URLs.
>> [1] https://github.com/jbosstools/jbosstools-locus/
>> [2]
https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-locus.sit...
>> [3] http://download.jboss.org/jbosstools/updates/nightly/locus/trunk/
>> � - These issues did not block the release of JBDS 7.0.0.GA, and therefore would
not block 7.1.0, but might be fixed by upgrading to SpringIDE 3.4.
>
> --
> This message is automatically generated by JIRA.
> If you think it was sent incorrectly, please contact your JIRA administrators
> For more information on JIRA, see: http://www.atlassian.com/software/jira
----- End forwarded message -----
_______________________________________________
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