[#506] - Create a "Release" view
- Closed
- 13 Sep 2018
- Medium
- Build: master
- # 506
With the switch away from JoomlaCode, we've lost some of the automated tools that were used by the release team (OK, mostly me
- List of issues closed during the release cycle - This can integrate with GitHub's milestones but will require more hands on activity from JBS or other project teams that might use the application; only items that were fixed for a release cycle should ultimately be listed with a milestone and other issues be moved to another milestone or unassigned
- List of contributors during a release cycle - This would show a list of all users with activity between two releases, be it code committed or tracker activity. We'll need to write some sort of API for this, but at the basic level it could be two queries: a query of the issues table and joined to the activities and milestones tables, filtered on a milestone ID and unique usernames for all issues processed in a period and a query strictly on the activities table filtered on a start/end timeframe and unique usernames
- Release metadata - Devise a method of tracking the number of issues open at the start and end of each release period, number of issues submitted during the period, number of issues closed during the period (and under what status; fixed, known issue, etc.), additional numbers as we think of it
The gamification pieces have been a great motivator to community members and contributors as it's a way to recognize their efforts in the project. This also helps us compile numbers on release day to highlight the activity of a given timeframe.
| Labels |
Added:
enhancement
|
||
| Labels |
Added:
requirement
v1.x
|
||
Issues and pulls can be assigned to milestones as a way of grouping items (I did it the other day for pulls targeting 3.4, see https://github.com/joomla/joomla-cms/milestones/Joomla!%203.4.0).
There's different ways to manage issue-to-milestone relations, but for our purposes, the desired end state is that any item that's closed as fixed during a release cycle gets assigned to the milestone for that release. This helps create a replacement for http://developer.joomla.org/version-3-3-2-release-notes.html by having a consolidated listing of all items.
So on github milestones works in a very similar way to labels?
Sounds to me like the easiest workflow is for the committer to assign it to
a release, therefore creating a milestone as part of the commit process. so
we dont need an interface on jissues to manage this just a way to view it
On 25 September 2014 03:26, Michael Babker notifications@github.com wrote:
Issues and pulls can be assigned to milestones as a way of grouping items
(I did it the other day for pulls targeting 3.4, see
https://github.com/joomla/joomla-cms/milestones/Joomla!%203.4.0).There's different ways to manage issue-to-milestone relations, but for our
purposes, the desired end state is that any item that's closed as fixed
during a release cycle gets assigned to the milestone for that release.
This helps create a replacement for
http://developer.joomla.org/version-3-3-2-release-notes.html by having a
consolidated listing of all items.—
Reply to this email directly or view it on GitHub
#506 (comment).
Brian Teeman
Co-founder Joomla! and OpenSourceMatters Inc.
http://brian.teeman.net/
Which is why you titled this create a view - doh
This comment was created with the J!Tracker Application at http://issues.joomla.org/.
I don't know where I'm completely going with this yet but I've started a branch to build this out. So far it just allows us to store release data from GitHub. For now I imagine it's going to be mostly display with very little admin (but we'll need minimal admin as I have it able to associate a release to a milestone, something GitHub doesn't do) and it'll probably have a list page per project and an item page with the data we choose to display.
| Status | New | ⇒ | Closed |
| Closed_Date | 0000-00-00 00:00:00 | ⇒ | 2018-09-13 01:34:15 |
| Closed_By | ⇒ | mbabker |
##List of issues closed during the release cycle##
Can you explain more about how you see this working with Milestones
This comment was created with the J!Tracker Application at http://issues.joomla.org/.