Release 0.3.0

[simonschmeisser]

this is in preparation of making an official release

[Kaffeine]

-add compatibility mode "ofono-on-ring" for SailfishOS
+Import mission-control plugin from telepathy-ring (the origin telepathy-ofono plugin works only with RIL modems)

[jbruechert]

Question: Why are we maintaining debian packaging in tree, and is anyone actually using it?

I'm maintaining separate debian packaging already and wasn't even aware this exists.
The ubuntu release names in the changelog make it unuseful for building official packages in distributions.

[Kaffeine]

Question: Why are we maintaining debian packaging in tree, and is anyone actually using it?

I think this is legacy stuff from the time when telepathy-ofono developed by Canonical for their own use.

I'm also used to support RPM file for Sailfish OS in my TelegramQt repos because there is no single (VCS, e.g. git) repo with packages. Instead, they create a repository for each foreign (not developed within SFOS) package with the rpm directory and (usually) upstream code as a submodule (e.g. telepathy-qt). Later on, there is a custom OBS instance with (usually) manually uploaded service_ files. Each service_ points to the repo with rpm and upstream submodule (e.g. telepathy-qt/_service). It is much more convenient to have RPM in the upstream repo than to create an intermediate repo with a submodule.

I don't want to say that this is right, but sometimes it is justified by the circumstances.

[jbruechert]

For debian the normal situation is to have a separate repository that contains packaging and a watch file that knows where to download the sources in a version independent way, so it doesn't need manual updating.