On 05/13/2016 08:16 AM, Weinan Li wrote:
--
Weinan Li / JBoss


On May 13, 2016, at 5:18 PM, Alessio Soldano <asoldano@redhat.com> wrote:

Yes, I expected this situation to be a consequence of having carried over stuff from former releases. I just want to clean up things a bit and have a clear and reasonable set of issues assigned to the next release.
I agree with Ron on the "Fix Version" having to be set only if we really believe a jira will we worked for that version. Otherwise simply clean up the field (perhaps set by the reporter).
Next sub-task is to decide how to deal with the "Wanted but unscheduled" version.

I don't use it much. Maybe we can just leave the 'Fix Version' blank for such kind of issues :-)

Not sure whether Ron uses it or not.

I didn't think I did, but I see that I created one of the current "Wanted but unscheduled" issues. I just remove that, which leaves 7. Yeah, I don't see the point of having it. And if you went looking for issues with a blank Fix Version, they would be hidden.

I vote for getting rid of it.




Do we really need that?
Cheers
Alessio


Il 13/05/2016 05:26, Weinan Li ha scritto:

When we mark a release in JIRA as "released", there will be a option that will move all the unsolved issues to next candidate release(select from dropdown list). So I guess that's the reason there are many issues set to "3.0.17.Final", which was inherited from older releases. JIRA also allows us to clear the 'Fix Version' of the unsolved issues during each release, but I'm afraid that will lose the (maybe) important info.

--
Weinan Li / JBoss


On May 13, 2016, at 5:42 AM, Alessio Soldano <asoldano@redhat.com> 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.

-- 
Alessio Soldano
Web Service Lead, JBoss

_______________________________________________
resteasy-dev mailing list
resteasy-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/resteasy-dev


-- 
Alessio Soldano
Web Service Lead, JBoss



    

    

    
-- 
My company's smarter than your company (unless you work for Red Hat)