<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<p>On 05/13/2016 05:22 AM, Alessio Soldano wrote:<br>
</p>
<blockquote cite="mid:57359CBC.5060902@redhat.com" type="cite">
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
<div class="moz-cite-prefix">Thanks Ron.<br>
I usually expected the reporter to specify the "affects
version". If it's not there, I usually assume he's using the
latest available release. We should at a given point go and
check if old jiras with no affect version are still valid
against current master.<br>
</div>
</blockquote>
<br>
There were only a few left with no Affects Version after my recent
mass attack. A lot of the ancient issues I closed were created
before the first 3.0.x release. Some others I assigned an Affects
Version based on clues from the issue's content. A few others I
asked the reporter and got some feedback. <br>
<br>
When I just looked, there were about 28 issues with no Affects
Version. Many of them were quite new, so I assigned 3.0.16.Final.
Some of them were older Feature Requests, so I gave them
3.0.16.Final also. A couple I re-read for clues. One was out of
date. So: there are currently 0 issues with no Affects Version.<br>
<br>
-Ron<br>
<br>
<blockquote cite="mid:57359CBC.5060902@redhat.com" type="cite">
<div class="moz-cite-prefix"> <br>
Thanks<br>
Alessio<br>
<br>
<br>
Il 13/05/2016 00:33, Ron Sigal ha scritto:<br>
</div>
<blockquote
cite="mid:219739e5-b767-613f-bacb-527ddcfb8825@redhat.com"
type="cite">
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
<p>I just edited most of the issues with Fix Version 3.0.17,
removing the Fix Version and, when there was no Affects
Version >= 3.0.Final, adding Affects Version 3.0.16.Final.
This way, they don't have any special status relative to other
issues with no Fix Version.<br>
</p>
<br>
<div class="moz-cite-prefix">On 05/12/2016 06:23 PM, Ron Sigal
wrote:<br>
</div>
<blockquote
cite="mid:7e61117a-d9eb-3aa5-b643-d3321f4b49e7@redhat.com"
type="cite">
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
<p>The fact that certain issues have a Fix Version of
3.0.17.Final is somewhat random. Probably the Fix Version
was set by the reporter and doesn't mean much. I only set a
Fix Version when I start to work on an issue, or otherwise
strongly believe it will get done soon. A more important
filter, I think, is anything with an Affects Version of
3.0.1.Final - 3.0.16.Final. Anything else doesn't affect, or
isn't know to affect, Resteasy 3.<br>
</p>
<br>
<div class="moz-cite-prefix">On 05/12/2016 05:42 PM, Alessio
Soldano wrote:<br>
</div>
<blockquote cite="mid:5734F8C8.7050007@redhat.com" type="cite">
<pre wrap="">Folks,
I'd like to organize a bit the work for the future month or such on
RESTEasy.
I've created 3.1.0.Beta1 version on jira and started setting that as
target for some issues / feature requests.
Please take some time to look at jira, review what's there, self-assign
/ un-assign jiras and schedule them for 3.1.0.Beta1. We should try to
come up with a reasonable payload for ~ 1 month of development.
Also note there are currently a lot of jiras scheduled for 3.0.17.Final,
but it does not look very likely that they'll all be solved in few days
(that is when we'll release 3.0.17.Final). So please update/reschedule them.
With more people actively working on the project we should try to use
JIRA properly for tracking progress on releases.
Thanks
Alessio
P.S. the comment to use on commits so that they can be automatically
linked to jiras (I still have to ask for the integration to be enabled
though, will do that soon) is "[RESTEASY-XYZ] blah blah", including
square brackets.
</pre>
</blockquote>
<br>
<pre class="moz-signature" cols="72">--
My company's smarter than your company (unless you work for Red Hat)</pre>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
resteasy-dev mailing list
<a moz-do-not-send="true" class="moz-txt-link-abbreviated" href="mailto:resteasy-dev@lists.jboss.org">resteasy-dev@lists.jboss.org</a>
<a moz-do-not-send="true" class="moz-txt-link-freetext" href="https://lists.jboss.org/mailman/listinfo/resteasy-dev">https://lists.jboss.org/mailman/listinfo/resteasy-dev</a>
</pre>
</blockquote>
<br>
<pre class="moz-signature" cols="72">--
My company's smarter than your company (unless you work for Red Hat)</pre>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
resteasy-dev mailing list
<a moz-do-not-send="true" class="moz-txt-link-abbreviated" href="mailto:resteasy-dev@lists.jboss.org">resteasy-dev@lists.jboss.org</a>
<a moz-do-not-send="true" class="moz-txt-link-freetext" href="https://lists.jboss.org/mailman/listinfo/resteasy-dev">https://lists.jboss.org/mailman/listinfo/resteasy-dev</a>
</pre>
</blockquote>
<br>
<br>
<pre class="moz-signature" cols="72">--
Alessio Soldano
Web Service Lead, JBoss</pre>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
resteasy-dev mailing list
<a class="moz-txt-link-abbreviated" href="mailto:resteasy-dev@lists.jboss.org">resteasy-dev@lists.jboss.org</a>
<a class="moz-txt-link-freetext" href="https://lists.jboss.org/mailman/listinfo/resteasy-dev">https://lists.jboss.org/mailman/listinfo/resteasy-dev</a>
</pre>
</blockquote>
<br>
<pre class="moz-signature" cols="72">--
My company's smarter than your company (unless you work for Red Hat)</pre>
</body>
</html>