On Mon, 13 Jan 2025 at 16:51, Enrico Olivelli <eolive...@gmail.com> wrote: > > Given that Pulsar 4.0 has been out for a while and it is considered > production ready it is better to keep compatibility with Pulsar 4 (set the > flag to 'true') and document this flag in the release notes or any upgrade > guide from 3 to 4. > > So: > - keep the current behavior in Pulsar 4.0.2 > - document that upgrading from 3.x to 4.x requires to set that flag in > order to support rollbacks
Thanks for sharing your thoughts, Enrico. This is a really good point. Documenting this in the upgrade guide should be addressing Baodi's and Yubiao's concerns about "breaking changes". > > I know that this is not ideal, but current users of Pulsar 4 (that maybe > started on 4) will see bad surprises when upgrading to a "point release". > You can expect big surprises when you switch to a major release (2 -> 3, 3 > -> 4) but you really don't expect any surprises when you upgrade/rolback > from x.y.z to x.y.k > > I am sorry that we did not catch this behavior change, we should add some > "rollback testing" to our CI or at least to some checklist we run while > voting a new "major release". In general there isn't sufficient community activity to make such activities possible. We need more active contributors that are able to handle such improvements in our release process. -Lari
