Clarification on requirements for a release

[Christian Mollekopf]

On Mon, Jul 3, 2017, at 05:26 PM, Luigi Toscano wrote:
> On Monday, 3 July 2017 17:24:41 CEST Christian Mollekopf wrote:
> > On Mon, Jul 3, 2017, at 05:21 PM, Luigi Toscano wrote:
> > > On Monday, 3 July 2017 17:15:19 CEST Harald Sitter wrote:
> > > > 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
> > > 
> > > Because playground is not supposed to have production releases, as you
> > > wrote above, so we never tracked or enabled translations for playground.
> > > It's part of the workflow.
> > 
> > I'm not looking for a "production release", I just need to release my
> > code.
> > I thought that's what the unstable prefix is about.
> 
> And I think that it's fine, if you mark that as preproduction. But I
> can't 
> access the task, so I'm not sure which objections have been raised
> exactly.

But *how* do I mark it as preproduction? I thought that is what the
unstable prefix (e.g.
https://download.kde.org/unstable/kimap2/0.2.0/src/kimap-0.2.0.tar.xz)
is for.

I add you as a subscriber to the ticket, so you're hopefully able to see
the ticket now.

Cheers,
Christian