Release version 0.3.0.alpha

I'm not sure how alpha release changelogs and tags should be.

/cc @guido.gunther

upstream:

0.3.0~alpha version number in debian/changelog (for correct version sorting). For tags I'd do a v0.3.0.alpha.

Note that this will not be picked up by the automatic builders since the tag is not in the pureos/ namespace (see below).

byzantium

Use 0.3.0~alpha+pureos1 in d/changelog. I'd use an additional '+' here over the canonical version number (according to the pureos rules) since chatty is 3.0 (native) source format still (not building on the upstream Debian packaging like e.g. calls or phosh) otherwise you'd have 0.3.0~alpha-1pureos1) and 0.3.0~alphapureos1 would look odd). Release in changelog should be byzantium.

The git tag created by e.g. gbp tag will be s.th. like pureos/90.3.0_alpha+pureos1 due to https://source.puri.sm/Librem5/chatty/-/blob/pureos/byzantium/debian/gbp.conf#L3 and it will it picked up by the builders due to the tag being in the pureos/ namespace.

amber-phone

Release in changelog should be amber-phone.

Same as byzantium but with ~amber1 appended. So tag is in pureos/ namespace and is being auto built.

I mean, if I tag with alpha suffix, will it still replace the one already installed in amber-phone/byzantium on apt upgrade. I don't want that to happen (due to #450). So only explicit upgrades should update chatty

all higher version numbers will replace lower version numbers in the PureOS archive, the suffix name doesn't change anything here. The only way i see to have an alpha version and a "stable" version is to have a

chatty-dev or chatty-alpha package that has no file conflicts with the chatty package (and also uses a ~/.config/chatty-dev or similar. geary does that upstream by using meson profiles for the application paths (the packaging is then easy to adjust)

everything else e.g. blocking the alpha version in landing or amber-phone-staging will also block updates for 0.2.x.

If you only want to tag a alpha release (but not push out any packages to the PureOS archive) only care about upstream: above and ignore the byzantium and amber-phone points.

This can be closed now that !646 (merged) is in, no?

yes

closed