<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<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>
</body>
</html>