Hi, On 2 February 2017 at 11:45, <[email protected]> wrote: > On 17-02-02 09:46:41, Alan Pope wrote: >> I was wondering if you’d be willing to have a conversation with me to >> discuss some ideas on how we can help deliver the latest and greatest >> version of OfflineIMAP to more users? > > If we should do that, i would kindly suggest making a snap of the next > branch too, and maybe even some flatpack, as to not seem discriminatory >
I don't know much about flatpak, sorry. But I know the two are not mutually exclusive. What we usually recommend is getting the snapcraft.yaml into the master branch of the project, and configure travis-ci or some other build system to make automatic builds whenever a pull request lands. That can then automatically be pushed to the 'edge' channel in the store, and be available almost instantly to adventurous users, and testers who subscribe to that channel. Later, when an OfflineIMAP release is cut, during the normal release, you'd manually push a snap to the 'stable' channel, for the more conservative users. They'd automatically get updated the next time they check in. That way you don't end up with people on old versions. We've got a bit of documentation on how to set all that up, but it hinges on there being a working yaml first, an example of which was in my first mail. https://snapcraft.io/docs/build-snaps/ci-integration Happy to answer any other questions / comments. Cheers, -- Alan Pope Community Manager Canonical - Ubuntu Engineering and Services +44 (0) 7973 620 164 [email protected] http://ubuntu.com/ _______________________________________________ OfflineIMAP-project mailing list: [email protected] http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/offlineimap-project OfflineIMAP homepages: - https://github.com/OfflineIMAP - http://offlineimap.org
