Clarification on requirements for a release
sitter at kde.org
Mon Jul 3 15:15:19 UTC 2017
the phab task is marked private.
on a general note I do not think this was ever discussed or agreed
upon and makes no sense (how the heck is a playground project meant to
evolve if it can't do bloody pre releases...).
making production releases from playground is not advisable because
a) playground was not peer-reviewed through kdereview and
b) for reasons I do not know playground projects cannot have stable
translations, so you couldn't do maintenance releases afterwards
without jumping through hoops to retain
even so there's plenty of stuff releasing from playground, which I'll
argue is their business. just at a glance I am seeing like 10 projects
that have production releases but live in playground.
whoever came up with this bullshit should stop putting stones in
people's way and publish the tarballs. releasing tarballs is enough of
a chore as it is.
On Mon, Jul 3, 2017 at 3:54 PM, Christian Mollekopf
<chrigi_1 at fastmail.fm> wrote:
> I wanted to do a release of kdav2, kimap2, kasync, sink and kube and
> upload tarballs to downloads.kde.org/unstable/... for that.
> My plan was to then blog about it and send a mail to
> kde-announce-apps at kde.org to announce it.
> Now I was told that technically we are not allowed to make releases
> because still in playground, which wasn't a problem for the last release
> and doesn't make much sense to me since we're trying to get early
> While I could apply for some projects to be moved to extragear I'd
> rather wait a bit and sink and kube are too early in any case.
> See https://phabricator.kde.org/T6434 for more information.
> Could somebody quickly clarify?
More information about the release-team