flxo commented on issue #424: URL: https://github.com/apache/avro-rs/issues/424#issuecomment-4369516195
> [@flxo](https://github.com/flxo) I do not understand what you prefer. A release 0.22 straight from HEAD. In my case this would enable me to actually use SOE which is broken in 0.21. > Since we anticipate that 0.22 will need more time I suggested to release 0.21.1 in the meantime with cherry-picks from https://github.com/apache/avro-rs/milestone/4?closed=1 This would not help me: I'm waiting for fix of that is included in !445 that _is_ a breaking change and can't go in a patch release. > > I'm also concerned about people using 0.21 from crates.io and feel the same pain I did. > > Are you talking about something that broke between 0.20 and 0.21 ? I'm talking about the SOE fix. I haven't checked if this is also broken in 0.20. > > Maybe we can add a gentle warning that everyone is advised to use HEAD because of known issues in 0.21? > > Add it where ? Although I do not see how this will be helpful. Every software has known problems and this is why new releases are made for. Some projects make releases after each merged PR but this does not work at ASF. Here we have to vote on each release for at least 3 days and there are not many active project members to approve it :-/ It takes around 2 weeks to make a release ... Thanks for clarification. Now I understand better why you wan't got get more stuff into the 0.22 - it's the bulky process. > > The `CHANGELOG` is quite outdated and scanning the history for changes that might affect me is cumbersome to impossible. > > We should remove this file. It was not updated since this library has been donated to ASF (and abandoned by its former developers). It just adds extra work for the current maintainers. We try to use https://www.conventionalcommits.org/en/v1.0.0/ since 0.18 (https://github.com/apache/avro-rs/releases) 👍 -- 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
