I think a 1.1.0 release would be great! I'm not sure we ever discussed what it means for an issue or PR to be added to a milestone 'X' - does it mean "it is a requirement for version X", "we would like it to be in X but don't hold up the release for it", or merely "this will not make it into version prior to X"?
I think we should ideally only have "requirement for version X" tasks if we know they cannot be added later without breaking binary compatibility, or when they're meant to solve regressions compared to the previous version. Kind regards, Arnout On Thu, Jul 25, 2024 at 11:46 AM PJ Fanning <fannin...@apache.org> wrote: > Hi everyone, > I'm wondering if we should try to focus on getting a 1.1.0 release out. > It's about a year since the 1.0.0 release. > We have 1.1.0-M1 out [1] and there is a GitHub milestone [2] tracking > some further changes. > I would favour skipping an M2 release as I don't think anything > currently merged or awaiting merge causes major concerns. > What do people think? > > Thanks, > PJ > > [1] > https://pekko.apache.org/docs/pekko/1.1/release-notes/releases-1.1.html > [2] https://github.com/apache/pekko/milestone/7 > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@pekko.apache.org > For additional commands, e-mail: dev-h...@pekko.apache.org > > -- Arnout Engelen ASF Security Response Apache Pekko PMC member, ASF Member NixOS Committer Independent Open Source consultant
