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
Some of my pull requests have already causes issues for some special configurations, which I did not use when I tested these features myself. Examples are #251 and #240 . Apologies to all people who had extra work because of this.
I think it might sense to start doing releases, so users can stay on an explicitely tagged older version without things breaking.
It also makes it easier to trace changes between the different releases.
I also understand that this is extra work, but I think it is worth it if there are enough users, which I think there are for this repository (seeing how quickly new issues due to PRs are reported).
The text was updated successfully, but these errors were encountered:
First of all there is at least one release : 2.0
People working with master are experiencing bugs due to PR side effects and this is normal process I suppose (we do not have a dev branch).
Of course we agree on the need for releases alongside with release notes. Thank you for reporting this.
I think we will do a release when we are in a more steady state. For the moment we are still cleaning up the backlog of PRs that were here before @Hish15 and I became official maintainers. This process takes us some time alongside of the new issues/questions.
Some of my pull requests have already causes issues for some special configurations, which I did not use when I tested these features myself. Examples are #251 and #240 . Apologies to all people who had extra work because of this.
I think it might sense to start doing releases, so users can stay on an explicitely tagged older version without things breaking.
It also makes it easier to trace changes between the different releases.
I also understand that this is extra work, but I think it is worth it if there are enough users, which I think there are for this repository (seeing how quickly new issues due to PRs are reported).
The text was updated successfully, but these errors were encountered: