All, We have decided to stop using JIRA as our ticketing system and move to GitHub Issues.
>From now on, if you have a bug report or feature request, please submit it at: https://github.com/apache/wicket/issues We thank JIRA for its many years of service, but the time has come to move on. There are a few reasons for this: - ASF JIRA has a separate account system, requiring contributors to sign up and us to approve accounts due to spam. - JIRA and GitHub are separate systems, which makes linking issues, commits and pull requests more cumbersome. - GitHub Issues and pull requests are directly linked and are already where most development activity happens. Other Apache projects have made this move before us, and some have seen an increase in contributions from new developers and broader community participation. Later this week I'll ask Apache Infra to put the old Wicket JIRA into read-only mode, after which it can join the other migrated projects in a nice green meadow somewhere in the mountains. If there is an existing JIRA ticket that you care about, please recreate it in the GitHub issue tracker and include a link to the original JIRA ticket. That way the new issue is associated with your GitHub account, and you can keep track of it there. We will not automatically migrate the existing JIRA tickets. Apart from not being able to reliably identify the original submitters on GitHub, doing so would create a considerable amount of administrative work. The core team may still pick up relevant JIRA issues while working on bug fixes and new features, but we make no guarantees. The goal of this move is to reduce administration, not create more of it. Kind regards, -- The Wicket team <http://wicketinaction.com>
