Release planning for 1.6

[Alexander Larsson]

After the summer I've been back doing some feature work on flatpak
master, and today I finally got 1.5 out, where the big new feature is
the support for application self-updates and version masking
(pinning).

The plan is for the 1.5.x series to end in 1.6 some time before the
end of the year, which will be about 7 months after the 1.4.0 release,
which is far longer than the previous expected cycle of about 4 months
between each release. This is partially due to summer vacations, but
also because feature work are slowing down as flatpak is getting more
"complete". Considering this, maybe we should change our expected
release cadence to twice a year instead? Opinions?

In terms of features for 1.6 the current plans I have are:

1. Parental controls (PR #2797)
2. Disk space checks (PR #3013)
3. Support for purchases/donation

The first one is essentially done and just need a review, the second
needs some work but shouldn't be that hard.

However, the last one is still very much in the research/design phase.
We have a document with some initial highlevel proposals, as well as
experimens in various areas. Working on this will be my priority the
coming weeks.

Does anyone have any other features they really need in 1.6? I'd like
to not add any more large features for it, but there is still a lot of
time for smaller changes to get in.

-- 
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
 Alexander Larsson                                Red Hat, Inc
       alexl at redhat.com         alexander.larsson at gmail.com