[GitHub] keith-turner commented on a change in pull request #59: proposal for github issues
keith-turner commented on a change in pull request #59: proposal for github issues URL: https://github.com/apache/accumulo-website/pull/59#discussion_r174213824 ## 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, in 5b0d6c4 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] keith-turner commented on a change in pull request #59: proposal for github issues
keith-turner commented on a change in pull request #59: proposal for github issues URL: https://github.com/apache/accumulo-website/pull/59#discussion_r173279439 ## 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: My thinking was to document how each repo uses labels in Github issues in contrib.md, to allow for different labels. We could do this in future, but for now I think the labels in the core repo should be the focus. 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] keith-turner commented on a change in pull request #59: proposal for github issues
keith-turner commented on a change in pull request #59: proposal for github issues URL: https://github.com/apache/accumulo-website/pull/59#discussion_r173278928 ## 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: > At risk of duplicating information across these two PRs, should there be some consolidation here? 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. 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] keith-turner commented on a change in pull request #59: proposal for github issues
keith-turner commented on a change in pull request #59: proposal for github issues URL: https://github.com/apache/accumulo-website/pull/59#discussion_r173276491 ## 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: An absence of open issues with the fix version label. 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] keith-turner commented on a change in pull request #59: proposal for github issues
keith-turner commented on a change in pull request #59: proposal for github
issues
URL: https://github.com/apache/accumulo-website/pull/59#discussion_r172693199
##
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 understood the mailing list discussion to mean that
accumulo-{website,examples,etc} would use GH Issues, while accumulo [core]
continues to use JIRA. Did I misread that?
Mike started discussion of that option because he felt there was lack of
consensus on moving everything to github issues. My read on the cause of the
lack of consensus was the lack of a concrete starting plan that had a firm goal
of moving off JIRA. So I am proposing concrete starting plan.
Nothing has been voted on. Personally I would like to see a vote on an
option that seems to have have consensus in discussion. I am posting this
proposal for discussion.
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] keith-turner commented on a change in pull request #59: proposal for github issues
keith-turner commented on a change in pull request #59: proposal for github issues URL: https://github.com/apache/accumulo-website/pull/59#discussion_r172631048 ## 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: Right, for the time being we will need to query github and JIRA for open issues before releasing. We will also need to query both when constructing the release notes. This will need to happen until JIRA has no issues for a release. I can document this. We could speed this along by adding the following request for new issues. If you start working on an issue that exists in JIRA, please do the following : * Open a new github issue that links to the JIRA issue. * Link the JIRA issue to the GH issue. * Close the JIRA issue. If we did this, then we should be done with JIRA after all branches have had a release after the start of using GH issues. 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] keith-turner commented on a change in pull request #59: proposal for github issues
keith-turner commented on a change in pull request #59: proposal for github issues URL: https://github.com/apache/accumulo-website/pull/59#discussion_r172631048 ## 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: Right, for the time being we will need to query github and JIRA for open issues before releasing. We will also need to query both when constructing the release notes. This will need to happen until JIRA has no issues for a release. I can document this. We could speed this along by adding the following request for new issues. If you start working on an issue that exists in JIRA, please do the following : * Open a new github issue that links to the JIRA issue. * Close the JIRA issue. If we did this, then we should be done with JIRA after all branches have had a release after the start of using GH issues. 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] keith-turner commented on a change in pull request #59: proposal for github issues
keith-turner commented on a change in pull request #59: proposal for github issues URL: https://github.com/apache/accumulo-website/pull/59#discussion_r172615392 ## 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: My reading off the mailing list discussion gives me the impression that people are ok with the goal of transitioning as long as there is a starting plan and the eventual goal of not using JIRA. Hopefully this proposal provides both, if not it needs to be improved. 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] keith-turner commented on a change in pull request #59: proposal for github issues
keith-turner commented on a change in pull request #59: proposal for github issues URL: https://github.com/apache/accumulo-website/pull/59#discussion_r172614091 ## 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 am proposing that we stop using JIRA for new issues. 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
