Fwd: Kexi 3.0 release is coming

Jaroslaw Staniek staniek at kde.org
Tue Oct 4 15:52:04 UTC 2016


---------- Forwarded message ----------
From: Luigi Toscano <luigi.toscano at tiscali.it>
Date: 3 October 2016 at 12:21
Subject: Re: Kexi 3.0 release is coming
To: kde-i18n-doc at kde.org
Cc: Jaroslaw Staniek <staniek at kde.org>, "kexi-devel at kde.org" <
kexi-devel at kde.org>, Calligra Suite developers and users mailing list <
calligra-devel at kde.org>


On Monday, 3 October 2016 12:14:21 CEST Jaroslaw Staniek wrote:
> On 3 October 2016 at 12:06, Luigi Toscano <luigi.toscano at tiscali.it>
wrote:
> > On Monday, 3 October 2016 12:02:14 CEST Jaroslaw Staniek wrote:
> > > Hi,
> > > We're close to the 3.0 release. I plan to create tarballs today.
> > >
> > > Maintenance 3.0 branches have been created for Kexi projects
> > > (kexi/kdb/kproperty/kreport git) already.
> >
> > We should finalize the move of the libraries outside of playground
(which
> > requires anyway passing through kdereview). We don't usually track
stable
> > branches of translations for playground modules (if it has releases,
it's
> > not
> > playground).
>
> ​Good,
> ​I remember I had a review like this when we had some time to discuss:
> https://phabricator.kde.org/D2659.
> I see no points against the move, just you may remember we were not really
> sure the move is good idea at the moment or needed:
> https://phabricator.kde.org/D2659#49459

I did not wrote that the move is not needed. I was commenting about the
final
destination.
If we put aside the destination, moving is required as "playground" and
"stable branches" don't mix according our rules.

The step about "moving to kdereview" is not new and it is the usual rule
that
should (have) happen(ed) like in other similar cases, again regardless of
the
destination.

> Would you (or anyone else) be able to assist me in the move so we're ready
> for the release as planned? I did not allocate any resources for exactly
> this task today...

You can release for the current, but we can't create the translation
branches
for the stable branch until this is settled. So if you want to release, I
would say (but I'm not part of release-team, which is not in CC either),
release today but then allocate the time to move stuff around.

--
Luigi





-- 
regards, Jaroslaw Staniek

KDE:
: A world-wide network of software engineers, artists, writers, translators
: and facilitators committed to Free Software development - http://kde.org
Calligra Suite:
: A graphic art and office suite - http://calligra.org
Kexi:
: A visual database apps builder - http://calligra.org/kexi
Qt Certified Specialist:
: http://www.linkedin.com/in/jstaniek
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/release-team/attachments/20161004/ddfd144d/attachment.html>


More information about the release-team mailing list