You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@accumulo.apache.org by ct...@apache.org on 2019/06/17 19:10:53 UTC
[accumulo-website] branch master updated: Update contributing guide
for using project boards
This is an automated email from the ASF dual-hosted git repository.
ctubbsii pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/accumulo-website.git
The following commit(s) were added to refs/heads/master by this push:
new 05d3bcd Update contributing guide for using project boards
05d3bcd is described below
commit 05d3bcdcb348338d34183cd9f92693a572c93afa
Author: Christopher Tubbs <ct...@apache.org>
AuthorDate: Mon Jun 17 15:06:52 2019 -0400
Update contributing guide for using project boards
Add section in pages/how-to-contribute.md to describe the use of project
boards and labels
Update links in previous release notes from version-specific labels to
version-specific projects
---
_posts/release/2018-04-23-accumulo-1.9.0.md | 2 +-
_posts/release/2018-05-14-accumulo-1.9.1.md | 2 +-
_posts/release/2018-07-19-accumulo-1.9.2.md | 2 +-
_posts/release/2019-04-10-accumulo-1.9.3.md | 2 +-
pages/how-to-contribute.md | 31 ++++++++++++++++++-----------
5 files changed, 23 insertions(+), 16 deletions(-)
diff --git a/_posts/release/2018-04-23-accumulo-1.9.0.md b/_posts/release/2018-04-23-accumulo-1.9.0.md
index c1e2a13..63bdd24 100644
--- a/_posts/release/2018-04-23-accumulo-1.9.0.md
+++ b/_posts/release/2018-04-23-accumulo-1.9.0.md
@@ -109,7 +109,7 @@ Continuous ingest, random walk, and all integration test were run against RC1.
Randomwalk was run for 2 days with 7 walkers. Continuous ingest was run with 9
nodes for 24 hours followed by a successful verification.
-[GitHub]: https://github.com/apache/accumulo/issues?q=label%3Av1.9.0
+[GitHub]: https://github.com/apache/accumulo/issues?q=project%3Aapache%2Faccumulo%2F4
[JIRA]: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12312121&version=12339245
[upgrade]: {{ site.baseurl }}/docs/2.x/administration/upgrading
[user_manual]: {{ site.baseurl }}/1.9/accumulo_user_manual.html
diff --git a/_posts/release/2018-05-14-accumulo-1.9.1.md b/_posts/release/2018-05-14-accumulo-1.9.1.md
index 970de56..24c5de0 100644
--- a/_posts/release/2018-05-14-accumulo-1.9.1.md
+++ b/_posts/release/2018-05-14-accumulo-1.9.1.md
@@ -58,7 +58,7 @@ successful verification. The integration tests were run against both Hadoop
[#449]: https://github.com/apache/accumulo/issues/449
[#458]: https://github.com/apache/accumulo/issues/458
[1.9.0_notes]: {{ site.baseurl }}/release/accumulo-1.9.0/
-[GitHub]: https://github.com/apache/accumulo/issues?q=label%3Av1.9.1
+[GitHub]: https://github.com/apache/accumulo/issues?q=project%3Aapache%2Faccumulo%2F5
[examples]: {{ site.baseurl }}/1.9/examples/
[javadoc]: {{ site.baseurl }}/1.9/apidocs/
[upgrade]: {{ site.baseurl }}/docs/2.x/administration/upgrading
diff --git a/_posts/release/2018-07-19-accumulo-1.9.2.md b/_posts/release/2018-07-19-accumulo-1.9.2.md
index 9b4d788..a804c11 100644
--- a/_posts/release/2018-07-19-accumulo-1.9.2.md
+++ b/_posts/release/2018-07-19-accumulo-1.9.2.md
@@ -90,7 +90,7 @@ View the [Upgrading Accumulo documentation][upgrade] for guidance.
[#546]: https://github.com/apache/accumulo/issues/546
[#553]: https://github.com/apache/accumulo/issues/553
[#559]: https://github.com/apache/accumulo/issues/559
-[GitHub]: https://github.com/apache/accumulo/issues?q=label%3Av1.9.2
+[GitHub]: https://github.com/apache/accumulo/issues?q=project%3Aapache%2Faccumulo%2F6
[Uno]: https://github.com/apache/fluo-uno
[examples]: {{ site.baseurl }}/1.9/examples/
[fluo]: https://fluo.apache.org
diff --git a/_posts/release/2019-04-10-accumulo-1.9.3.md b/_posts/release/2019-04-10-accumulo-1.9.3.md
index 0daacf9..7c9dc69 100644
--- a/_posts/release/2019-04-10-accumulo-1.9.3.md
+++ b/_posts/release/2019-04-10-accumulo-1.9.3.md
@@ -211,7 +211,7 @@ View the [Upgrading Accumulo documentation][upgrade] for guidance.
[#1055]: https://github.com/apache/accumulo/issues/1055
[#1057]: https://github.com/apache/accumulo/issues/1057
[all-changes]: https://github.com/apache/accumulo/compare/rel/1.9.2...apache:rel/1.9.3
-[GitHub]: https://github.com/apache/accumulo/issues?q=label%3Av1.9.3
+[GitHub]: https://github.com/apache/accumulo/issues?q=project%3Aapache%2Faccumulo%2F7
[Uno]: https://github.com/apache/fluo-uno
[examples]: {{ site.baseurl }}/1.9/examples/
[fluo]: https://fluo.apache.org
diff --git a/pages/how-to-contribute.md b/pages/how-to-contribute.md
index b14ee29..202ffa3 100644
--- a/pages/how-to-contribute.md
+++ b/pages/how-to-contribute.md
@@ -41,22 +41,29 @@ finding issues to work, there may still be
## Labels
-For pull request and issues, the following labels are used in the core
-repository. Consider an issue with labels `v1.9.3`, `v2.0.2`, and `bug`. If
-the issue is open, then its a bug that someone plans to fix in 1.9.3 and 2.0.2.
-If closed, then it was fixed in those versions.
-
- Label | Description
--------------|----------------------------------------------------------------------------
- blocker | Indicates a release blocker that must be fixed in labeled versions.
- bug |
- duplicate |
- enhancement |
- vX.Y.Z | Fix version. The prefix `v` was chosen so that these labels sort last in the drop down list.
+Labels, such as `bug`, `enhancement`, and `duplicate`, are used to
+descriptively organize issues and pull requests. Issues labeled with `blocker`
+indicate that the developers have determined that the issue must be fixed prior
+to a release (to be used in conjunction with a version-specific project board;
+see the next section for information on project boards).
Currently only Accumulo committers can set labels. If you think a label should
be set, comment on the issue and someone will help.
+## Project Boards (Projects)
+
+Project boards (also "projects") are used to track the status of issues and
+pull requests for a specific milestone. Projects with names such as `2.1.0`,
+and `1.9.2` are used for tracking issues associated with a particular release
+and release planning. These are set up as basic Kanban boards with automation,
+with `To do`, `In progress`, and `Done` statuses. These projects are marked as
+"closed" when the version indicated is released. Other projects may exist for
+miscellaneous puposes, such as tracking multiple issues related to a larger
+effort. These projects will be named appropriate to indicate their purpose.
+
+Committers manage the project boards. If you need help with a project board or
+have questions, contact the developers using the link at the top of this page.
+
## Repositories
Contributions can be made to the following repositories. While the general contribution workflow is