A day later then expected, but the release candidate is out, next to several bugfixes we have added some new features :

- A recommended settings dialog
- UPnP plugin has been revamped, the UPnP widget has been moved from the settings dialog to the bottom tab bar
- The bandwidth scheduler has been improved : items can now be added to multiple days in one go, they can be dragged around on the scheduler and they can be resized (using the mouse)

George, would it be possible to avoid such frequent libbtcore soname bumping? Why don't you simply bump soname once when starting development of a new major release and keep it till the end of stable release no matter how many times ABI/API is broken during development cycle? Otherwise it's very difficult to package libbtcore separately for development releases (with library package name changing every two weeks).

MoDaX wrote:George, would it be possible to avoid such frequent libbtcore soname bumping? Why don't you simply bump soname once when starting development of a new major release and keep it till the end of stable release no matter how many times ABI/API is broken during development cycle? Otherwise it's very difficult to package libbtcore separately for development releases (with library package name changing every two weeks).

I guess we could that for betas and release candidates, but obviously not for final releases.

George wrote:I guess we could that for betas and release candidates, but obviously not for final releases.

Yes, but final releases and minor bugfixes should not have different ABI/API. and since you e.g. bump the soname when you start developing 3.2, no two final releases will have the same soname. Btw, what soname of libbtcore 3.1 final is going to be?

MoDaX wrote:

George wrote:I guess we could that for betas and release candidates, but obviously not for final releases.

Yes, but final releases and minor bugfixes should not have different ABI/API. and since you e.g. bump the soname when you start developing 3.2, no two final releases will have the same soname.

In practice this is not always possible, sometimes bugfixes require breaking ABI/API compatebility.

Btw, what soname of libbtcore 3.1 final is going to be?

I'm not expecting any interface changes anymore, so it should be the same.