GENERAL NOTES #1223
Replies: 1 comment
-
|
ℹ️ After a long pause, I just wanted to let you all know that Release v1.8.1 is in the pipeline indeed. As some people already asked for it: We are waiting for the currently pinned issues to be resolved and tested for verification. Once this is the case I'll go into preparations for publishing a new release. I would also be happy to have some assistance in active maintenance of this project. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Within this project the assignment of tickets on closure, as soon as a notable solution has been found, is common practise. This is done for statistical reasons in order to be able to keep track of contributors to this project (licensing). If you have contributed to this toolset and don't want to receive any further notifications on assigned tickets in the future, you may unsubscribe from these issues by disabling related notifications anytime.
Interested users and developers are encouraged to check open tickets 📌 and help with implementing new features and addressing bug reports. We are looking forward to review old tickets to further reduce the current backlog ♻️. Any help is highly appreciated, but please also consider the necessary time when doing so to avoid "dead" and incompletely resolved issues.
In order to move on with new releases we would clearly need developers contributing regularly, likely on a weekly basis and thus are willing to spend the time necessary to address and resolve open issues and bug reports. Looking at the codebase there is still a lot of work to do - on the internal structure as well as regarding to the user experience on the frontend, appearance and usability.
Beta Was this translation helpful? Give feedback.
All reactions