oslc-core message
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
--
[Date Index]
| [Thread Index]
| [List Home]
Subject: Re: [oslc-core] Proposed ordering of the backlog AND 3 issues to be added to the agenda
- From: "Jim Amsden" <jamsden@us.ibm.com>
- To: OSLC Core TC <oslc-core@lists.oasis-open.org>
- Date: Thu, 15 Nov 2018 11:25:18 -0500
But let's not do
this until we get the issues migrated to GitHub. We should consider current
JIRA frozen as I have taken an export of all 188 issues for the purpose
of doing the conversion to GitHub.
This unfortunately
will change Andrew's proposal since:
1. GitHub issues
don't have priority
2. The creation
date will be the date of the migration not the original creation date,
I can't change that property
3. GitHub only
has open and closed issues (no New)
Jim Amsden, Senior
Technical Staff Member
OSLC and Linked Lifecycle
Data
919-525-6575
From:
Andrii
Berezovskyi <andriib@kth.se>
To:
OSLC
Core TC <oslc-core@lists.oasis-open.org>
Date:
11/15/2018
11:14 AM
Subject:
[oslc-core]
Proposed ordering of the backlog AND 3 issues to be added to the agenda
Sent
by: <oslc-core@lists.oasis-open.org>
As I said in the meeting, I propose to
take 5 most relevant issues and to put them onto the TC agenda every meeting
no matter what (we can agree to reduce the number of those issues if there
are many agenda items otherwise). This is the only way I see us working
through that list.
The question raised by Jim and others
is what does constitute a good ordering of relevance. Here is the filter
I use:
https://issues.oasis-open.org/issues/?jql=project%20%3D%20OSLCCORE%20AND%20issuetype%20in%20standardIssueTypes()%20AND%20status%20in%20(Open%2C%20New)%20AND%20resolution%20%3D%20Unresolved%20ORDER%20BY%20priority%20DESC%2C%20created%20ASC%2C%20updated%20DESC
It features the following:
1) Primary sort by descending priority
(deal with pressing matters first)
2) Secondary sort by the ascending creation
date (deal with the oldest issues first if the priority is equal)
3) Restrict the list only to the New
and Open issues
4) Restrict the list only to the top-level
issues (filter out the subtasks)
If we have an agreement on that, here
is the list of the issues for the next meeting (we already have 2 items
on the agenda):
1) OSLCCORE-53
2) OSLCCORE-66
3) OSLCCORE-71
Unless we can reproduce the same sorting
features on Github, I would suggest to keep using Jira until we work through
this backlog.
--
/Andrew
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
--
[Date Index]
| [Thread Index]
| [List Home]