pjfanning commented on PR #459: URL: https://github.com/apache/pekko-grpc/pull/459#issuecomment-2915374170
> I wonder if it wouldn't be sufficient to do a tag, and postpone creating a branch with protection and CI until we have a reason to make another 1.1.x release. * the next step after merging this is to tag the commit after the branch point as 1.2.0-M0 so that sbt-dynver produces versions for our snapshots that have 1.2.0 in their names - to differentiate from the 1.1 prefixed snapshot names currently generated * I think it is easier to just cut the 1.1.x branch now instead of creating off of an old commit in the future * this is consistent with what has been done before in this and other pekko repos * I think we could as easily just aim to have the next release be a 1.2.0 instead of planning to do a 1.1.2 release that noone is asking for * I can reduce the frequency of the publishes of snapshots for the legacy branches since we have workflow-dispatch enabled -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: notifications-unsubscr...@pekko.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: notifications-unsubscr...@pekko.apache.org For additional commands, e-mail: notifications-h...@pekko.apache.org
