Clarification on requirements for a release

[Ben Cooksley]

On Tue, Jul 4, 2017 at 3:15 AM, Harald Sitter <sitter at kde.org> wrote:
> the phab task is marked private.

Because it's a Sysadmin task, as we receive confidential requests from
time to time.
Only the task author and it's subscribers can see it.

>
> 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.

I was the one who made that decision, and it was done because there
were quite a few projects who had been making releases from playground
for well over a year.

If we don't enforce some rules around what Playground projects can and
cannot do we may as well abolish the concept of Playground altogether.
I think we can all agree that would be bad for the quality of software
produced by the KDE Community in general given the sorts of issues
which get found on review.

Kube and the like have been around for a while now, so asking the
question of whether it should be headed to KDE Review and Extragear is
a reasonable question to ask.

>
> HS

Regards,
Ben

>
> On Mon, Jul 3, 2017 at 3:54 PM, Christian Mollekopf
> <chrigi_1 at fastmail.fm> wrote:
>> Hi,
>>
>> 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
>> feedback.
>>
>> 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?
>>
>> Thanks,
>> Christian