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
Assuming the default branch is always releasable, i.e., has no regressions, would it make sense to establish a regular release schedule? Are the most time-consuming aspects of the release process automated so that this request is not burdensome? If so, then I would recommend releasing every 2-3 weeks.
The text was updated successfully, but these errors were encountered:
I'm actually quite happy with the current flexible release strategy. At the current pace we get enough features / fixes together to roll out a release every month, which is nice since we are also making much progress with fpm. Still, I won't feel obliged to release for two months or longer if everybody here is busy elsewhere, it is still a volunteer project after all.
The easiest solution we can implement is a continuous release which always provides binaries from the latest head.
Assuming the default branch is always releasable, i.e., has no regressions, would it make sense to establish a regular release schedule? Are the most time-consuming aspects of the release process automated so that this request is not burdensome? If so, then I would recommend releasing every 2-3 weeks.
The text was updated successfully, but these errors were encountered: