GitHub user mdedetrich added a comment to the discussion: Should we deliver new features in 1.2.x?
So to start off with, I don't think it was ever the plan that development on the 1.x series of Pekko would cease just because we started working on 2.0.0 on `main`. 2.0.0 will take a **while** and at least myself (and I would even go as far to say as the rest of the community) was under the impression that the 1.x series would continue to develop as normal. The question here is, what process should we have regarding general features/bugs/fixes for the 1.x series. Should we baes the PR first off of 2.0.x and then backport it to 1.2.x/1.3.x etc etc or should these general PR's target 1.2.x/1.3.x as a branch and then forward port it. There are pros and cos to each, with the forward porting there is a risk that we may forget a regression (as pointed out by @raboof ) but its a lot easier to make such a PR, especially if it touches code that has been modified as a specific 2.0.0 change. Its also clearer what the intent of the PR is, if it targets a 1.x branch then its a general feature but if the PR is a 2.0.0 specific change (i.e. dropping Scala 2.12, removing deprecated methods etc etc) then it targets `main` branch. I personally don't mind either way, just that it should be clear which approach to use. GitHub link: https://github.com/apache/pekko/discussions/2180#discussioncomment-14339418 ---- This is an automatically sent email for notifications@pekko.apache.org. To unsubscribe, please send an email to: notifications-unsubscr...@pekko.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: notifications-unsubscr...@pekko.apache.org For additional commands, e-mail: notifications-h...@pekko.apache.org
