You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is a small update regarding our release schedule. Since we didn't really have one in the past let's set one now, it will work this way:
We'll target the 1st of the month as our release date. There might be some delays in case the feature I'm working on requires some more time or if there are important bugs still left to fix.
After each release the Next milestone will get populated with issues I plan to work on for the next release.
Issues will generally be moved to the Next milestone from the Future milestone, which keeps track of all the issue I plan to work on in the future.
Issues in the Future milestone are roughly ordered by priority, so the ones at the top will generally be worked on before the ones at the bottom.
That's how it will work for normal releases, but there might be a couple of exceptions:
If I'm planning on doing some major changes for the next release, like implementing the plugin architecture Plugins #128 or refactoring the repo in some major way, we might skip a release date, effectively delaying the release by 1 month, as it takes some considerable amount of time to make those changes.
If some critical bugs are found, especially regarding data loss, those will be addressed immediately and a new patch release will be issued as soon as possible.
I hope that clarifies things and makes the release cycle more predictable.
As a result of these rules the v1.5.0 release will not contain as many changes as the v1.4.0 did, since I'll have just about a couple of weeks to work on that, but hopefully we should still be getting some nice features like a dark theme #18, which is kind of 90% implemented already.
Thanks for listening!
The text was updated successfully, but these errors were encountered:
This is a small update regarding our release schedule. Since we didn't really have one in the past let's set one now, it will work this way:
We'll target the 1st of the month as our release date. There might be some delays in case the feature I'm working on requires some more time or if there are important bugs still left to fix.
After each release the Next milestone will get populated with issues I plan to work on for the next release.
Issues will generally be moved to the Next milestone from the Future milestone, which keeps track of all the issue I plan to work on in the future.
Issues in the Future milestone are roughly ordered by priority, so the ones at the top will generally be worked on before the ones at the bottom.
That's how it will work for normal releases, but there might be a couple of exceptions:
If I'm planning on doing some major changes for the next release, like implementing the plugin architecture Plugins #128 or refactoring the repo in some major way, we might skip a release date, effectively delaying the release by 1 month, as it takes some considerable amount of time to make those changes.
If some critical bugs are found, especially regarding data loss, those will be addressed immediately and a new patch release will be issued as soon as possible.
I hope that clarifies things and makes the release cycle more predictable.
As a result of these rules the v1.5.0 release will not contain as many changes as the v1.4.0 did, since I'll have just about a couple of weeks to work on that, but hopefully we should still be getting some nice features like a dark theme #18, which is kind of 90% implemented already.
Thanks for listening!
The text was updated successfully, but these errors were encountered: