On 05/13/2016 05:22 AM, Alessio Soldano wrote:
Thanks Ron.
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.
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.
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.
-Ron
Thanks
Alessio
Il 13/05/2016 00:33, Ron Sigal ha scritto:
>
> 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.
>
>
> On 05/12/2016 06:23 PM, Ron Sigal wrote:
>>
>> 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.
>>
>>
>> On 05/12/2016 05:42 PM, Alessio Soldano wrote:
>>> 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.
>>>
>>
>> --
>> My company's smarter than your company (unless you work for Red Hat)
>>
>>
>> _______________________________________________
>> resteasy-dev mailing list
>> resteasy-dev(a)lists.jboss.org
>>
https://lists.jboss.org/mailman/listinfo/resteasy-dev
>
> --
> My company's smarter than your company (unless you work for Red Hat)
>
>
> _______________________________________________
> resteasy-dev mailing list
> resteasy-dev(a)lists.jboss.org
>
https://lists.jboss.org/mailman/listinfo/resteasy-dev
--
Alessio Soldano
Web Service Lead, JBoss
_______________________________________________
resteasy-dev mailing list
resteasy-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/resteasy-dev
--
My company's smarter than your company (unless you work for Red Hat)