Skip to content

DEVELOPER.md: point issue tracking at GitHub Issues - #9277

Open
linzch3 wants to merge 1 commit into
apache:masterfrom
linzch3:docs-developer-md-github-issues
Open

linzch3 wants to merge 1 commit into
apache:masterfrom
linzch3:docs-developer-md-github-issues

Conversation

@linzch3

@linzch3 linzch3 commented Nov 14, 2026

Copy link
Copy Markdown

Hi,

Storm tracks work on GitHub Issues now (README was updated in #7936), but DEVELOPER.md still pointed people at JIRA.

I updated it to match current practice:

  • Bug and feature reports, and the issue-tracker section, now link to https://github.com/apache/storm/issues
  • Beginner issues point at the good first issue label instead of the old JIRA newbie/trivial filters
  • PR titles should be short and descriptive; if a PR is tied to an issue, mention it in the description (for example Fixes #123), rather than prefixing STORM-123:
  • After a merge, close the linked GitHub issue if GitHub did not already close it

Docs only; no code changes.

What is the purpose of the change

Keep the developer docs in line with the GitHub Issues workflow.

How was the change tested

I read through the updated sections and checked that every JIRA workflow link in DEVELOPER.md is gone. I left historical STORM-XXXX citations in other files alone.

An AI assistant helped draft this change; I reviewed it and take responsibility for it.

@GGraziadei
GGraziadei requested a review from rzo1 November 15, 2026 13:49
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants