Bug Reporting Update: Shifting to Gitlab

Dear Obarun Community,

We're rolling out an important update regarding bug reporting for package-related issues.

Going forward, we kindly ask our users to submit bug reports directly on our Gitlab instance, under the corresponding project for the package in question.

Why the Change?

In our ongoing efforts to streamline and centralize our bug tracking process, we've decided to consolidate all bug reports onto our Gitlab platform. This change allows for better organization, efficient tracking, and faster resolution of reported issues.

How to Report Bugs?

To report a bug related to a specific package, please follow these steps:

Visit our Gitlab Instance: Navigate to our Gitlab instance.

Search for the Package: Use the search bar to find the project corresponding to the package you're encountering issues with. For example, if you're experiencing problems with the cronie package, locate the cronie project.
Open an Issue: Once you've found the project, open a new issue detailing the bug you've encountered. Be sure to provide as much relevant information as possible, including steps to reproduce the issue, system details, and any error messages.

Benefits of Using Gitlab for Bug Reporting:

Centralized Platform: All bug reports are now centralized on our Gitlab instance, making it easier for our developers to track and manage issues.
Improved Collaboration: Gitlab's collaborative features allow for better communication and collaboration between users and developers, leading to quicker bug resolutions.
Transparent Process: By reporting bugs on Gitlab, users can track the progress of their reported issues and stay informed about any updates or resolutions.

We believe this transition will enhance the bug reporting experience for our community and enable us to provide more efficient support.

Thank you for your cooperation and continued support as we strive to improve the Obarun experience together.

Best regards,

Eric Vidal eric@obarun.org