From kde-i18n-doc  Fri Feb 17 22:08:48 2017
From: Milian Wolff <mail () milianw ! de>
Date: Fri, 17 Feb 2017 22:08:48 +0000
To: kde-i18n-doc
Subject: Re: Preparing heaptrack 1.0 release
Message-Id: <4679815.KY4L1gKavP () agathebauer>
X-MARC-Message: https://marc.info/?l=kde-i18n-doc&m=148736934813171
MIME-Version: 1
Content-Type: multipart/mixed; boundary="--nextPart5143020.lQSX3yTMnn"

--nextPart5143020.lQSX3yTMnn
Content-Transfer-Encoding: 7Bit
Content-Type: text/plain; charset="us-ascii"

On Dienstag, 14. Februar 2017 00:58:00 CET Luigi Toscano wrote:
> Milian Wolff ha scritto:
> > Hey all,
> > 
> > I just branched off heaptrack 1.0 in preparation of the first release.
> > 
> > Where do I select the stable i18n branch nowadays?
> 
> sysadmin/repo-metadata, it is open to everyone with a developer account now.
> 
> Anyway, I fixed it and copied the translations.
> https://commits.kde.org/sysadmin/repo-metadata/ff3c09b944509b27340b070aea05e
> 6dcf3527799

Great, thank you Luigi!

> Translators: the desktop and appdata files have been added today, so you
> will see their pot files in both stable5 and trunk5. Please don't forget to
> update both branches!

Yes, that would be appreciated.

> > Also, would it be OK with you guys if I spin the first 1.0 tarballs in 2
> > weeks time from now? Considering that this is a development tool, most
> > people will use it in english anyways, so I personally don't consider
> > i18n extremely important to have for the very first release. But of
> > course, I and many others will very much appreciate a properly localized
> > heaptrack for future releases.
>
> At least the desktop and the appdata files could be relevant. Apart from
> that I guess than 2 weeks is fine (but let's hear others too).

If noone objects heavily, I will continue with my initial plan and spin the 
release in one week during the weekend.

Thanks everyone

-- 
Milian Wolff
mail@milianw.de
http://milianw.de
--nextPart5143020.lQSX3yTMnn
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: This is a digitally signed message part.
Content-Transfer-Encoding: 7Bit

-----BEGIN PGP SIGNATURE-----

iF0EABECAB0WIQQ9hWiGkJfGXJj40nYMDrISzR0TkwUCWKd0cAAKCRAMDrISzR0T
k3eEAJ0caYVnWLUoIZ7BzlgSWSIfcbrfbgCgtOChWAkh/OVGuHHw96B7mCht/3c=
=jzu3
-----END PGP SIGNATURE-----

--nextPart5143020.lQSX3yTMnn--