[GitHub] joshelser commented on a change in pull request #59: proposal for github issues
joshelser commented on a change in pull request #59: proposal for github issues URL: https://github.com/apache/accumulo-website/pull/59#discussion_r174223864 ## 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: Ok, thanks! 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: us...@infra.apache.org With regards, Apache Git Services
[GitHub] joshelser commented on a change in pull request #59: proposal for github issues
joshelser commented on a change in pull request #59: proposal for github issues URL: https://github.com/apache/accumulo-website/pull/59#discussion_r174213350 ## 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: > Yes, I think it would be best to move the info in contrib.md to the website and mention that the labels only apply to the main repo. Could remove the info from contrib.md. Did this happen? 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: us...@infra.apache.org With regards, Apache Git Services
[GitHub] joshelser commented on a change in pull request #59: proposal for github issues
joshelser commented on a change in pull request #59: proposal for github issues URL: https://github.com/apache/accumulo-website/pull/59#discussion_r173278005 ## 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: Keith just pointed me at https://github.com/apache/accumulo/pull/396/files#diff-6a3371457528722a734f3c51d9238c13R35 which explains the `vX.Y.Z` convention for tracking "fixVersion" on GH issues. At risk of duplicating information across these two PRs, should there be some consolidation here? 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: us...@infra.apache.org With regards, Apache Git Services
[GitHub] joshelser commented on a change in pull request #59: proposal for github issues
joshelser commented on a change in pull request #59: proposal for github issues URL: https://github.com/apache/accumulo-website/pull/59#discussion_r173275897 ## 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: What's the mechanism for determining when a release candidate is "done" on Github issues? Open issues with some label? Are we using the milestones feature? 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: us...@infra.apache.org With regards, Apache Git Services
[GitHub] joshelser commented on a change in pull request #59: proposal for github issues
joshelser commented on a change in pull request #59: proposal for github issues URL: https://github.com/apache/accumulo-website/pull/59#discussion_r172633190 ## File path: pages/how-to-contribute.md ## @@ -19,9 +19,19 @@ This document provides basic instructions for contributing to Accumulo. If you ## Issues -Any contribution should have a corresponding issue. Accumulo uses [JIRA] for issue tracking. Before creating an issue, -you will need to create an [Apache JIRA account][jira-signup]. If you need help finding an issue to work on, check out -the [open issues labeled for newbies][newbie-issues] or [contact us][contact]. +Accumulo uses GitHub issues to track bugs and features. Each git repository Review comment: Thanks. I don't think there is any "hard" problem that will prevent us from making this work. I just want to make sure we all understand how to do it. I appreciate the effort to put this in writing. 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: us...@infra.apache.org With regards, Apache Git Services
[GitHub] joshelser commented on a change in pull request #59: proposal for github issues
joshelser commented on a change in pull request #59: proposal for github issues URL: https://github.com/apache/accumulo-website/pull/59#discussion_r172627994 ## File path: pages/how-to-contribute.md ## @@ -19,9 +19,19 @@ This document provides basic instructions for contributing to Accumulo. If you ## Issues -Any contribution should have a corresponding issue. Accumulo uses [JIRA] for issue tracking. Before creating an issue, -you will need to create an [Apache JIRA account][jira-signup]. If you need help finding an issue to work on, check out -the [open issues labeled for newbies][newbie-issues] or [contact us][contact]. +Accumulo uses GitHub issues to track bugs and features. Each git repository Review comment: I think this is OK for contributors to use, but the broader questions of how issue mgmt is handled for releases when a release contains changes tracked both in GH issues and JIRA is not. As a developer, I do not know how everyone else is planning to know when a branch contains all necessary changes for a release to happen. 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: us...@infra.apache.org With regards, Apache Git Services
[GitHub] joshelser commented on a change in pull request #59: proposal for github issues
joshelser commented on a change in pull request #59: proposal for github issues URL: https://github.com/apache/accumulo-website/pull/59#discussion_r172596758 ## File path: pages/how-to-contribute.md ## @@ -19,9 +19,19 @@ This document provides basic instructions for contributing to Accumulo. If you ## Issues -Any contribution should have a corresponding issue. Accumulo uses [JIRA] for issue tracking. Before creating an issue, -you will need to create an [Apache JIRA account][jira-signup]. If you need help finding an issue to work on, check out -the [open issues labeled for newbies][newbie-issues] or [contact us][contact]. +Accumulo uses GitHub issues to track bugs and features. Each git repository Review comment: I understand phrasing this for the eventual state when we have everything transitioned off of JIRA, but we're not there yet. Add an exception for the accumulo.git repo for now? 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: us...@infra.apache.org With regards, Apache Git Services
