You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jclouds.apache.org by Andrew Gaul <ga...@apache.org> on 2014/09/03 00:50:32 UTC
jclouds roadmap
In response to Andrew P.'s mail, I updated our roadmap[1], moving
several uncompleted tasks to 2.0.0. However, I consider several of
these tasks unrealistic based on previous experiences with jclouds wish
lists. For example, the perennial de-async tasks continue to make their
appearance without progress. I would like to move all tasks to a
indefinite version and only move a task to a definite version when we
have an owner and a corresponding JIRA issue. Thoughts?
[1] https://wiki.apache.org/jclouds/Roadmap
--
Andrew Gaul
http://gaul.org/
Re: jclouds roadmap
Posted by Andrew Phillips <ap...@qrmedia.com>.
> I’ve never understood why we set the Fix Version when an issue (a)
> hasn’t been fixed and (b) hasn’t even been assigned to someone.
Is this something we should put in the committer/developer
documentation somewhere? Personally, until an issue goes to Resolved
or Fixed, I think the Fix Version should be empty?
ap
Re: jclouds roadmap
Posted by Ignasi Barrera <ig...@gmail.com>.
I don't have any strong feeling about how we use JIRA :) I said
"often" because I usually do that just for issues I know that will be
fixed soon, or to force myself to fix them (in that case I assign them
to me).
If we communicate the road map in the wiki, there's no need to
duplicate the information. As said, I'm not very worried about how we
proceed with JIRA, so whatever option that has consensus works for me
:)
On 3 September 2014 17:28, Andrew Phillips <ap...@qrmedia.com> wrote:
>> I've often set the Fix Version before the issue was assigned or fixed,
>> because that's the way you can take a look at the road map in JIRA.
>
>
> Which version do you set, then? The next version? In that case, I agree with
> the other comments that this can give a misleading impression that issues
> will be fixed even if they're completely orphaned.
>
> We can try to make it easier to use JIRA to get a view of what is likely to
> be done by assigning a (tentative) fix version when an issue is assigned to
> a person and goes In Progress, as Gaul suggested.
>
> Would that help?
>
> ap
Re: jclouds roadmap
Posted by Andrew Phillips <ap...@qrmedia.com>.
> I've often set the Fix Version before the issue was assigned or fixed,
> because that's the way you can take a look at the road map in JIRA.
Which version do you set, then? The next version? In that case, I
agree with the other comments that this can give a misleading
impression that issues will be fixed even if they're completely
orphaned.
We can try to make it easier to use JIRA to get a view of what is
likely to be done by assigning a (tentative) fix version when an issue
is assigned to a person and goes In Progress, as Gaul suggested.
Would that help?
ap
Re: jclouds roadmap
Posted by Jeremy Daggett <je...@RACKSPACE.COM>.
Similar to Ignasi, I use the fix version when creating issues to indicate
the target release an issue *should* or *will* be fixed in. That value
typically does not have to change once the issue has been marked resolved.
I plan to start using the "Start/Stop Progress² more effectively and that
will help track overall progress. There are only 6 issues "In Progress² at
the moment, and I know the community is a lot more busy that that! ;)
/jd
On 9/3/14, 8:17 AM, "Ignasi Barrera" <na...@apache.org> wrote:
>I've often set the Fix Version before the issue was assigned or fixed,
>because that's the way you can take a look at the road map in JIRA.
>
>People using JIRA to track the "state" of the next version to have an
>idea of the progress (how many planned issues remain unresolved, etc),
>would use the roadmap view, which uses the Fix Versions.
>
>
>
>On 3 September 2014 17:12, Andrew Gaul <ga...@apache.org> wrote:
>> On Wed, Sep 03, 2014 at 01:55:20PM +0000, Everett Toews wrote:
>>> On Sep 2, 2014, at 5:50 PM, Andrew Gaul <ga...@apache.org> wrote:
>>>
>>> > I would like to move all tasks to a
>>> > indefinite version and only move a task to a definite version when we
>>> > have an owner and a corresponding JIRA issue. Thoughts?
>>>
>>> +1
>>>
>>> I¹ve never understood why we set the Fix Version when an issue (a)
>>>hasn¹t been fixed and (b) hasn¹t even been assigned to someone.
>>
>> I removed the fix version for 20 orphan issues previously listed at:
>>
>>
>>https://issues.apache.org/jira/issues/?jql=project%20%3D%20JCLOUDS%20AND%
>>20resolution%20%3D%20Unresolved%20AND%20fixVersion%20!%3D%20null%20AND%20
>>assignee%20%3D%20null
>>
>> Most of these had no activity for months.
>>
>> --
>> Andrew Gaul
>> http://gaul.org/
Re: jclouds roadmap
Posted by Ignasi Barrera <na...@apache.org>.
I've often set the Fix Version before the issue was assigned or fixed,
because that's the way you can take a look at the road map in JIRA.
People using JIRA to track the "state" of the next version to have an
idea of the progress (how many planned issues remain unresolved, etc),
would use the roadmap view, which uses the Fix Versions.
On 3 September 2014 17:12, Andrew Gaul <ga...@apache.org> wrote:
> On Wed, Sep 03, 2014 at 01:55:20PM +0000, Everett Toews wrote:
>> On Sep 2, 2014, at 5:50 PM, Andrew Gaul <ga...@apache.org> wrote:
>>
>> > I would like to move all tasks to a
>> > indefinite version and only move a task to a definite version when we
>> > have an owner and a corresponding JIRA issue. Thoughts?
>>
>> +1
>>
>> I’ve never understood why we set the Fix Version when an issue (a) hasn’t been fixed and (b) hasn’t even been assigned to someone.
>
> I removed the fix version for 20 orphan issues previously listed at:
>
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20JCLOUDS%20AND%20resolution%20%3D%20Unresolved%20AND%20fixVersion%20!%3D%20null%20AND%20assignee%20%3D%20null
>
> Most of these had no activity for months.
>
> --
> Andrew Gaul
> http://gaul.org/
Re: jclouds roadmap
Posted by Andrew Gaul <ga...@apache.org>.
On Wed, Sep 03, 2014 at 01:55:20PM +0000, Everett Toews wrote:
> On Sep 2, 2014, at 5:50 PM, Andrew Gaul <ga...@apache.org> wrote:
>
> > I would like to move all tasks to a
> > indefinite version and only move a task to a definite version when we
> > have an owner and a corresponding JIRA issue. Thoughts?
>
> +1
>
> I’ve never understood why we set the Fix Version when an issue (a) hasn’t been fixed and (b) hasn’t even been assigned to someone.
I removed the fix version for 20 orphan issues previously listed at:
https://issues.apache.org/jira/issues/?jql=project%20%3D%20JCLOUDS%20AND%20resolution%20%3D%20Unresolved%20AND%20fixVersion%20!%3D%20null%20AND%20assignee%20%3D%20null
Most of these had no activity for months.
--
Andrew Gaul
http://gaul.org/
Re: jclouds roadmap
Posted by Everett Toews <ev...@RACKSPACE.COM>.
On Sep 2, 2014, at 5:50 PM, Andrew Gaul <ga...@apache.org> wrote:
> I would like to move all tasks to a
> indefinite version and only move a task to a definite version when we
> have an owner and a corresponding JIRA issue. Thoughts?
+1
I’ve never understood why we set the Fix Version when an issue (a) hasn’t been fixed and (b) hasn’t even been assigned to someone.
Everett
Re: jclouds roadmap
Posted by Andrew Phillips <ap...@qrmedia.com>.
> appearance without progress. I would like to move all tasks to a
> indefinite version and only move a task to a definite version when we
> have an owner and a corresponding JIRA issue. Thoughts?
+1. Hopefully, that will trigger some more discussion on what we as
community actually can realistically achieve, and how to plan for that.
ap