Replies: 4 comments
-
To me, that should be driven by severity of bugfixes first. Important bugfixes SHOULD be released ASAP to me. New features should arrive when mature (and probably not too much per release). |
Beta Was this translation helpful? Give feedback.
-
Agreed with @lolzim |
Beta Was this translation helpful? Give feedback.
-
Definitely, important bugfixes (however we define them—number of users affected, severity of impact, etc.) shouldn't be delayed. I was referring (perhaps unclearly) to minor ones that only affect one or two users, or don't cause much disruption, etc. That said, it's also possible that we're basing this on faulty assumptions. A couple of users complained that we release too frequently, but they may well not be representative of the majority of users. Ultimately, though, it's a project decision rather than a technical one, so one for @markcheret — as long as we have something clear and agreed-upon (I'd suggest writing up whatever is decided in the Wiki) then we should be good to go. |
Beta Was this translation helpful? Give feedback.
-
To move the topic forward:
|
Beta Was this translation helpful? Give feedback.
-
During the recent release error (see #55), at least two users made the point that the Plugin updates very frequently (see here and here).
Currently, we push a new release for every bugfix, new feature, etc. with appropriate version incrementing based on the severity of the changes. However, I think it would be worth thinking about how often we want to release going forward.
A couple approaches that I think would make sense:
Thoughts and comments welcomed.
Beta Was this translation helpful? Give feedback.
All reactions