From 3a86905fdaca7cf96f2cd9aa6d2900ab93503826 Mon Sep 17 00:00:00 2001 From: Matej Novotny Date: Thu, 18 Jun 2026 14:03:30 +0200 Subject: [PATCH] Replace JIRA references with GitHub Issues --- content/contribute.md | 13 +++--- ...026-06-18-github-issues-migration.asciidoc | 41 +++++++++++++++++++ templates/partials/footer.html | 2 +- 3 files changed, 50 insertions(+), 6 deletions(-) create mode 100644 content/posts/2026-06-18-github-issues-migration.asciidoc diff --git a/content/contribute.md b/content/contribute.md index 7debe95..2fa4e24 100644 --- a/content/contribute.md +++ b/content/contribute.md @@ -35,11 +35,14 @@ to contribute, report issues, or connect with the team. Issue Tracker

- Found a bug or have a feature request? Weld Core, API, and Parent use JIRA. - Other projects like Weld Testing use GitHub Issues. + Found a bug or have a feature request? All Weld projects use GitHub Issues. + Use the issue tracker in the relevant repository.

- - JIRA + + Weld Core + + + Weld API Weld Testing @@ -153,7 +156,7 @@ to contribute, report issues, or connect with the team. ## Reporting Bugs -When filing a bug, whether on [JIRA](https://issues.redhat.com/projects/WELD/issues/) or GitHub Issues, please: +When filing a bug on GitHub Issues, please: 1. **Browse existing issues** before creating a new one to avoid duplicates 2. **Create one issue per bug** — keep each issue focused and trackable diff --git a/content/posts/2026-06-18-github-issues-migration.asciidoc b/content/posts/2026-06-18-github-issues-migration.asciidoc new file mode 100644 index 0000000..83ed71a --- /dev/null +++ b/content/posts/2026-06-18-github-issues-migration.asciidoc @@ -0,0 +1,41 @@ +--- +layout: post +title: Issue tracking moves to GitHub +author: Matej Novotny +description: All Weld projects now use GitHub Issues for bug reports and feature requests instead of JIRA +tags: [team] +--- + +We are happy to announce that all Weld projects have migrated their issue tracking to **GitHub Issues**. + +=== Background + +Historically, the main Weld repositories — link:https://github.com/weld/core[Weld Core, window="_blank"], link:https://github.com/weld/api[Weld API, window="_blank"], and link:https://github.com/weld/parent[Weld Parent, window="_blank"] — used the link:https://redhat.atlassian.net/projects/WELD/issues/[WELD JIRA project, window="_blank"] to track bugs and feature requests. +Other projects like link:https://github.com/weld/weld-testing[Weld Testing, window="_blank"] already used GitHub Issues. +This split meant that contributors had to know which tracker to use for which project, and filing a JIRA issue required a separate account. + +Over the past few weeks, we have been gradually enabling GitHub Issues across all remaining repositories and updating our documentation and contribution guides to reflect the change. +With that work now complete, GitHub Issues is the single place for all new bug reports, feature requests, and enhancement proposals across every Weld project. + +=== What does this mean for contributors? + +The main benefit is simplicity — if you already have a GitHub account, you can file an issue in any Weld repository without needing to create a separate JIRA account. +Issues, pull requests, and discussions now all live in one place, making it easier to cross-reference and track progress. + +Use the issue tracker in the relevant repository: + +* link:https://github.com/weld/core/issues[Weld Core, window="_blank"] +* link:https://github.com/weld/api/issues[Weld API, window="_blank"] +* link:https://github.com/weld/parent/issues[Weld Parent, window="_blank"] +* link:https://github.com/weld/weld-testing/issues[Weld Testing, window="_blank"] +* link:https://github.com/weld/weld.github.io/issues[Weld Website, window="_blank"] + +=== What happens to JIRA? + +The link:https://redhat.atlassian.net/projects/WELD/issues/[WELD JIRA project, window="_blank"] will remain available in read-only mode. +All existing issues, comments, and release notes will stay accessible so that we do not lose track of the history behind older changes and decisions. +However, no new issues should be created there — please use GitHub Issues going forward. + +=== Discussions + +For questions or broader discussions that do not fit into a specific issue, use link:https://github.com/weld/core/discussions[GitHub Discussions, window="_blank"] on the Core repository or reach out via the link:https://lists.jboss.org/archives/list/weld-dev@lists.jboss.org/[weld-dev mailing list, window="_blank"]. diff --git a/templates/partials/footer.html b/templates/partials/footer.html index 6510279..4a302fe 100644 --- a/templates/partials/footer.html +++ b/templates/partials/footer.html @@ -37,7 +37,7 @@ GitHub - + Issue Tracker