Packaging issues before release

[dkropachev]

1. Supported distros?
2. CICD Pipeline as part of release or separate one.
3. Backport (to prior releases) binaries for some distros ? (have workflow for that ?)
4. Maybe change packager?
5. Package naming ?
6. Packages testing
7. Distribution for windows
8. Distribution for macos

Supported distros

1. Have a policy
2. Come up with list of distros based on policy

Packager

1. Decide if we switch to another packager
2. Better to have it integrated into cmake
3. Cross compilation support for macos and windows ?

Package naming

Question:
Do we add build date and hash id to the package, like so: libscylla-cpp-rs-driver1_1.0.0-20240328.f143d09a2057_noble_amd64.deb ?

.deb

regular package - libscylla-cpp-rs-driver<major>_<version>_<os>_<arch>.deb - libscylla-cpp-rs-driver1_1.0.0_noble_amd64.deb
debug symbols pacakge - libscylla-cpp-rs-driver<major>-dbgsym_<version>_<os>_<arch>.deb - libscylla-cpp-rs-driver1-dbgsym_1.0.0_noble_amd64.deb
dev pacakge - libscylla-cpp-rs-driver-dev_<version>_<os>_<arch>.deb - libscylla-cpp-rs-driver-dev_1.0.0_noble_amd64.deb

.rpm

regular package - scylla-cpp-rs-driver-<version>.<os>.<arch>.rpm - scylla-cpp-rs-driver-1.0.0.fc42.amd64.rpm
debug symbols pacakge - scylla-cpp-rs-driver-debuginfo-<version>.<os>.<arch>.rpm - scylla-cpp-rs-driver-debuginfo-1.0.0.fc42.amd64.rpm
dev pacakge - scylla-cpp-rs-driver-devel-<version>.<os>.<arch>.rpm - scylla-cpp-rs-driver-devel-1.0.0.fc42.amd64.rpm

[dkropachev]

@Lorak-mmk, @wprzytula , please comment, suggest.

[Lorak-mmk]

Backport (to prior releases) binaries for some distros ? (have workflow for that ?)

We need to first understand if it is necessary. For example, I sometimes install packages from older Fedora versions and it generally works.