iDempiere v13 community fix and polish week. December 15th to December 21st

[Diego Ruiz]

Next week we will host iDempiere v13 Fix & Polish Week. A focused bug‑solving sprint to address the issues found during the community testing days and get v13 ready for a smooth release.

During Fix & Polish Week, we invite all developers and contributors to jump in, pick issues from the v13 bug board, and work together to:

• Fix the most important problems uncovered in testing

• Reduce the backlog of regressions and annoyances

• Improve performance and stability in real‑world scenarios

Your participation is crucial:
Every bug fixed now means fewer surprises for implementers and end users later, and more confidence for everyone planning their v13 upgrade. Whether you can take one ticket or several, every contribution helps.

We’ll share:

• A curated list of priority issues (including blockers)

• Clear guidelines on how to claim a ticket and coordinate in Mattermost

• Recognition for contributors at the end of the week (bug‑fix heroes!)

If want to give back to the project on the development side, Fix & Polish Week is the perfect moment. Stay tuned for details and the bug list.

[Diego Ruiz]

Today we kick off iDempiere v13 Fix & Polish Week – a focused week to solve the bugs found during the community testing days and get v13 ready for a rock‑solid release.

Here’s how to participate:

1. Pick a Jira ticket
Use the bug board (sorted by priority):
[JIRA Filter](https://idempiere.atlassian.net/issues?jql=type%20%3D%20Bug%20AND%20status%20%3D%20Open%20AND%20project%20%3D%20IDEMPIERE%20ORDER%20BY%20priority%20DESC%2C%20status%20ASC Focus is on Blocker and Critical issues, but any bug you fix is welcome and will be counted.
2. Assign the Jira ticket to yourself
- Open the issue
- Set yourself as Assignee
3. Claim it on Mattermost
- In the Triage channel, post a very short message so others see what you’re working on. For example: CLAIM: IDEMPIERE-1234
4. If you need help
- Ask questions in Mattermost (thread under your claim), or
- Comment directly on the Jira ticket for technical discussion.
5. Create the pull request
- Reference the Jira ticket key in the PR description.
6. Address core team review
- If reviewers request changes, update the PR until it’s approved.
7. Commit merged → ticket closed
- Once merged, transition the Jira ticket to the appropriate “Done/Resolved” status.

8. Repeat as many times as you want
- Pick another ticket from the board and go again.

Leaderboard & recognition

We’ll maintain a leaderboard based on:
- Number of tickets solved
- Priority (Blocker/Critical/Major will score higher)
- All solved tickets count toward the totals, regardless of priority.
- At the end of the week we’ll recognize our Fix & Polish Week heroes publicly.

Jump in whenever you have time - one ticket or many, every fix helps make v13 safer and smoother for the whole community.