Enable GitHub Issues - #102
Conversation
Bukama
left a comment
There was a problem hiding this comment.
Compared with our PRs like this. Only difference is that in some (for exmaple resources) a small PR_automation.yml was also added to label things. But I think it's not a must-have.
|
we already have many Jira to GH Issues migration started https://cwiki.apache.org/confluence/display/MAVEN/JIRA+to+GitHub+Issues+switching |
More of switched project is our internal, not widely used by external users. on mentioned wiki - we have a progress, steps, used tools ... I'm going to release projects with GitHub issues to see what we need updated in release procedure |
Following this checklist to help us incorporate your
contribution quickly and easily:
for the change (usually before you start working on it). Trivial changes like typos do not
require a JIRA issue. Your pull request should address just this issue, without
pulling in other changes.
[MINSTALL-XXX] - Fixes bug in ApproximateQuantiles,where you replace
MINSTALL-XXXwith the appropriate JIRA issue. Best practiceis to use the JIRA issue title in the pull request title and in the first line of the
commit message.
mvn clean verifyto make sure basic checks pass. A more thorough check willbe performed on your pull request automatically.
mvn -Prun-its clean verify).If your pull request is about ~20 lines of code you don't need to sign an
Individual Contributor License Agreement if you are unsure
please ask on the developers list.
To make clear that you license your contribution under
the Apache License Version 2.0, January 2004
you have to acknowledge this by using the following check-box.
I hereby declare this contribution to be licenced under the Apache License Version 2.0, January 2004
In any other case, please file an Apache Individual Contributor License Agreement.