This Confluence has been LDAP enabled, if you are an ASF Committer, please use your LDAP Credentials to login. Any problems file an INFRA jira ticket please.

Child pages
  • BP-9 - Github issues for Issue Tracking

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • Community have voted and decided to start using Github issues/pull requests for issue tracking for 3 months.

  • however, It needs some Github permissions and some simple/basic rules to follow.

Proposal

...

If a change is trivial, or you have the code ready, you can open a PR directly; otherwise create an issue for discussion before starting writing code.

  • Issue Labeling

    • Release - We can use “milestone” for managing releases.

    • We can start with

...

    • minimal

...

    • labels, iterate and add more if the labels are really needed.

      • Type/Kind: {bug, feature, task}

      • Component/Area: {protocol, client, bookie, tests, documentation}

      • Priority: {blocker}. If it is a blocker, mark it a blocker. Otherwise leaves it unmarked.

  • Closing the PR

    • Ask INFRA if we have the permission to merge directly in Github.

    • If we have, enable “allow squash merging”, disable “allow merge commits” and “allow rebase merging” to make a clean commit history.

    • If we don’t have the permission, improving the merge-script to close both issue and PR

Action

  • Requests corresponding permissions from INFRA

    • Permissions for committers to create labels and milestones

    • Permission for merge and close issues/pull requests

  • Add Issue and RP template under .github

  • Change to merge script to close PR and Issue

  • Update the pull request instruction at both website and wiki page