[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-frameworks-devel
Subject:    Re: Kirigami in Frameworks
From:       Luigi Toscano <luigi.toscano () tiscali ! it>
Date:       2017-07-02 8:48:01
Message-ID: 3BCCABFF-EA8E-4346-BD7D-E79CC991D17F () tiscali ! it
[Download RAW message or body]

Il 02 luglio 2017 09:55:48 CEST, David Faure <faure@kde.org> ha scritto:
> On samedi 1 juillet 2017 13:48:28 CEST David Faure wrote:
> > On vendredi 30 juin 2017 15:16:17 CEST Marco Martin wrote:
> > > Hi,
> > > I have moved it, should be good to go.
> > > one sidenote (hoping is not a problem) for historical reasons, the
> > > tarballs were called kirigami2-version instead of just kirigami (or
> > > distributions may have some problems in upgrading).. do release
> > > scripts need to be adapted in some way?
> > 
> > Isn't this the right time to drop that historic baggage?
> > 
> > I suppose it's not just the tarball name that ends with 2, but also
> the name
> > of what's extracted from it. Which means renaming the checkout, which
> > breaks the next run of kdesrc-build... lots of trouble.
> > 
> > If this framework was supposed to be called kirigami2, let's call it
> > kirigami2, otherwise I'd say, the tarball name is changing to
> kirigami.
> > 
> > CC'ing release-team for input.
> 
> I'd like to finalize the tagging today.
> With kirigami still having issues with translations, CI, and naming,
> I'd like 
> to skip it for now and release it next month, unless there are strong
> reasons 
> to do otherwise.

Just for the record, translations have been moved almost immediately. The other \
issues are still relevant of course.

Ciao

-- 
Luigi


[prev in list] [next in list] [prev in thread] [next in thread]