Next Major Release

[Felix Divo]

Hey folks,

what do you think about releasing a version 4.0.0 somewhere in May or June (that is, quite "soon"). In June, it will be two years since the last non-hotfix release of python-can (3.3.0) which means that many users that do not install the experimental version 4.0.0-dev.0 (probably most won't) are still on rather old versions and did not benefit from quite a few improvements over the year(s), right?

There is already a 4.0.0 Release milestone. It contains many many closed and also some rather large (?) issues, like the much-discussed "Bit timing config for PCAN #625" or the "Unify exception handling #356".

The first step would probably be to agree on the features that should be included. That is something that we should still either 1) decide on collaboratively or 2) we simply "release whats there on the develop branch" on May 31st. We could also do a feature freeze for two weeks (e.g. beginning at the end of May and then releasing mid-June).

What do you think? Should we release soon and if yes, how should we agree on the features that must be included (besides what was or will be merged on develop besides it).

Best
Felix D.

[Brian Thorne]

Yes! A 4.0 release in the coming months would be great, I think you just appointed yourself release manager :-P

Seems hard to believe that the last 4.0.0 pre-release is from July last year! Do feel free to make more of those by the way. Should we discuss having a few release candidates?

I would love to have the timing config and consistent exceptions decided and merged in, but I am the first to admit I find almost no time for working on python-can nowadays, so I support the "release what is there at end of May" approach.

cheers,

Brian

[Felix Divo]

Just a quick update on this:

The issue around introducing the specific exception types seems to be the last major one that would need to get finished for the 4.0.0 release. Besides that, one should probably have a release candidate 4.0.0-rc0 and wait about two weeks (?) for issues to get reported. Maybe have a second one if a lot of issues get reported. If not, a real release is published.

Cheers
Felix

[Felix Divo]

Only the issue around introducing the specific exception types is left for now. Each interface is rather easy to change if you know the code base, and one can have a look at the other changes so far too. It would be very much appreciated if someone could help: Just have a look at the issue above and feel free to ask if something is still unclear. It is very tedious to do it all alone.

Cheers

Felix D.