GitHub user mdedetrich added a comment to the discussion: Should we deliver new features in 1.2.x?
> With 1.x, I think 1.2.x should be mainly for bug fixes, important dependency > upgrades (as long as they are not big bumps) and doc fixes. I don't mind > adding some deprecations. If we are talking about new features, then we > should consider going for a 1.3.0 release. I'm flexible enough if the changes > are small but non-trivial improvements should probably mean that we do a > minor release instead of a patch release. It is no more difficult to do a > 1.3.0 release than a 1.2.0 release. According to semver, for 1.2.x series (since its already released) only patch updates are allowed which is basically bug fixes. New deprecations and important dependency updates would be for 1.3.x > We've already reached a stage where 1.0.x patch releases are very unlikely > unless users come along with very meaningful reasons as to why they need bug > fixes and patch releases to 1.0.x instead of upgrading. I think 1.1.x will > reach that stage too in a few months (if we see no major issues in 1.2.x). So > I'm not worried about pushing through 1.3.x and 1.4.x releases. We don't need > to stay on 1.2.x indefinitely. Agreed, in fact we already have new features in the pipeline right now that asks for 1.3.x GitHub link: https://github.com/apache/pekko/discussions/2180#discussioncomment-14341154 ---- This is an automatically sent email for [email protected]. To unsubscribe, please send an email to: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
