You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@accumulo.apache.org by GitBox <gi...@apache.org> on 2018/03/08 22:30:12 UTC

[GitHub] ctubbsii commented on a change in pull request #59: proposal for github issues

ctubbsii commented on a change in pull request #59: proposal for github issues
URL: https://github.com/apache/accumulo-website/pull/59#discussion_r173313259
 
 

 ##########
 File path: contributor/making-release.md
 ##########
 @@ -22,6 +22,14 @@ There are number of things that are required before attempting to build a releas
 
 Given all of this, it's recommended that you only attempt making a release from a GNU/Linux machine.
 
+## Triage issues.
+
+Before creating a release candidate, all open issues with a fix version of the
+release candidate should be triaged.  During the transition from JIRA to GitHub
+issues, anyone doing triage will need to search for open issues in both
+locations.  Searching in both locations is only necessary for branches that
+have not released since the transition started.
 
 Review comment:
   > Are we using the milestones feature?
   
   I really wish we could make use of milestones, but there does not seem to be a good way available to have multiple milestones. The only way I could think of was to have multiple issues, with different milestones, for the same issue, but I don't think that's as convenient as labels. It would be confusing to mix and match the two, though we may discover a good way to use them in the future (milestones based on time rather than versions, for example). I think Keith's idea to use labels is better.

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services