Minor realease policy

[guissalustiano]

Hi, the last minor diesel release was 1 year ago.
Meanwhile, we have developed some interest features that would help diesel users.

How are the plans for a new release?

[weiznich]

I generally do not give any ETA's for any releases other than: When it's done.

That written: I personally want to cut a new minor release after I finished my work on window functions (see #4322 for the basic work, after that I still want to add a few functions to have something there). Also I would like to use the #[diagnostic::do_not_recommend] attribute to improve some error messages (especially that one mentioning that Something: Expression is not fulfilled, but that needs to track down some issues in the Insertable macro to get better spans there first). Any help there is welcome and would likely make the release happen faster.

Overall I broadly aim to cut the release somewhen this summer, but as written before I won't promise anything as that really depends on the amount of time I can spend on working on diesel. After all this is still mostly a free time project for me and therefore takes less priority than other stuff.

[guissalustiano]

Thanks for the reply! I understand why you don't want to give an ETA, I'll check if I can help with some of that. Thanks!

[lsunsi]

@weiznich Just as a complement to this question, does this answer also apply to diesel-cli or it's minor release policy would be different?

[weiznich]

I generally do not consider different crates in the project as "different" in terms of major/feature releases. They are always released together, with the exception of patch releases, which only apply to those components that have actual changes.

[lsunsi]

Got it, thank you @weiznich !