GitHub user mdedetrich added a comment to the discussion: Split out google connectors into its own repo
> I'm not opposed to this change. One consideration is that this means these > components will have their own release/vote cycle, right? Yes that is the main point actually, I want to avoid doing a 1.2.x release for pekko connectors when in reality only 1-2 connectors have major changes > That might be challenging as it's already sometimes difficult to find people > to vote on releases. I think this would actually make things easier, right now I think people are more or less blindly voting for releases especially in the case of pekko-connectors where its not entirely obvious which connectors have zero changes and which ones have actual changes. > On the other hand, reducing the scope of the release might make it easier. This is how I see it. GitHub link: https://github.com/apache/pekko-connectors/discussions/1034#discussioncomment-12790075 ---- 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
