6:57 p.m.
Hi,
alpha2 codefroze ~1 week ago but there are still a tons of issues set with it as fix
version (many from way before
alphs2 codefreeze)
Please take a look and make sure they get triaged ASAP.
Thanks,
Max
10:21 p.m.
If you're thinking "Hey, I would, but I can't find a query that shows me
my JIRAs", then look no further:
https://issues.jboss.org/issues/?filter=12319172&jql=%28project%20%3D...
Or if you want that subset by only YOUR JIRAs, add "AND assignee =
currentUser()" to filter out everything but your own assignments:
https://issues.jboss.org/issues/?filter=12319172&jql=%28project%20%3D...
Then if you want to bulk-move stuff to Beta1, you can use the gear icon
in the top right corner of the page (not the gear icon that appears on
each line of the query results table). Assuming that you only select
JBIDE or JBDS issues, you can then bulk-change them to a new fixVersion.
On 04/17/2013 12:57 PM, Max Rydahl Andersen wrote:
Hi,
alpha2 codefroze ~1 week ago but there are still a tons of issues set with it as fix
version (many from way before
alphs2 codefreeze)
Please take a look and make sure they get triaged ASAP.
Thanks,
Max
_______________________________________________
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
5:21 p.m.
Our issue count is now down to 7 in JBIDE and 3 in JBDS. Thank you!
Still a way to go but much better than the ~100 earlier.
The two biggest problems I see is
https://issues.jboss.org/browse/JBIDE-13989 which indicates some bad packaging or bundle
load sequence error and https://issues.jboss.org/browse/JBIDE-14087 which indicate a
rather big memory leak somewhere.
The others are also annoyances/errors but seem to be mostly build/updatesite related thus
I assume that is part of the
build nick will be doing tonight or he/mistria will push them to beta1 if not relevant.
btw. the proper query to know which you should triage is not just by assignee but by
component owner (so you get all issues which are in a component you own):
https://issues.jboss.org/issues/?filter=12319172&jql=(project%20%3D%2...
by using componentsLeadByUser() you get those no matter who they are assigned to.
/max
On Wed, Apr 17, 2013 at 04:21:21PM -0400, Nick Boldt wrote:
If you're thinking "Hey, I would, but I can't find a
query that shows
me my JIRAs", then look no further:
https://issues.jboss.org/issues/?filter=12319172&jql=%28project%20%3D...
Or if you want that subset by only YOUR JIRAs, add "AND assignee =
currentUser()" to filter out everything but your own assignments:
https://issues.jboss.org/issues/?filter=12319172&jql=%28project%20%3D...
Then if you want to bulk-move stuff to Beta1, you can use the gear
icon in the top right corner of the page (not the gear icon that
appears on each line of the query results table). Assuming that you
only select JBIDE or JBDS issues, you can then bulk-change them to a
new fixVersion.
On 04/17/2013 12:57 PM, Max Rydahl Andersen wrote:
>Hi,
>
>alpha2 codefroze ~1 week ago but there are still a tons of issues set with it as fix
version (many from way before
>alphs2 codefreeze)
>
>Please take a look and make sure they get triaged ASAP.
>
>Thanks,
>Max
>_______________________________________________
>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
4033
days inactive
4035
days old
jbosstools-dev@lists.jboss.org
2 comments
2 participants
participants (2)
-
Max Rydahl Andersen -
Nick Boldt