Re: Release 3.0.1

2017-04-04 Thread Dag
Tarball now on download.kde.org and packagers notified. Could somebody with karma prepare an announcement for Friday (or the weekend)? Created new calligra/3.0 branch so master now open for new features. Please backport (important) bugfixes in case we need a 3.0.2 release. --- Cheers, Dag

Re: Release 3.0.1

2017-03-24 Thread Dag
Turns out I ma away the next week, so if somebody does not take it the last steps, release will be delayed... --- Cheers, Dag

Re: Release 3.0.1

2017-03-23 Thread Dag
Compiled a list fixes, please add if I missed something. General --- Fix crash in move command when using arrow keys Respect container boundaries when moving shapes by arrow keys Remove shape manipulation handles when the tool is deactivated Always display shapes in the the same order in t

Re: Release 3.0.1

2017-03-20 Thread Jonathan Riddell
The usual way to pre-release them is to upload them to the same place as normal but keep permissions non-public so they don't end up on download.kde.org but are accessible to packagers. Jonathan On 20 March 2017 at 13:30, Dag wrote: > Ok, git tagged v3.0.1 and tarball created. > > Files can be

Re: Release 3.0.1

2017-03-20 Thread Dag
Ok, git tagged v3.0.1 and tarball created. Files can be found here: https://share.kde.org/index.php/s/yanrJWiQFB3rrvc My public key is here: https://share.kde.org/index.php/s/pYwk5c7UNcXGYfP Please test. Upload etc planned for next week. Cheers, Dag

RE: Release 3.0.1

2017-03-13 Thread Dag
Ok, we are in string freeze. Tarballs planned for monday 20. if translators do not bulge.

RE: Release 3.0.1

2017-03-11 Thread Camilla Boemann
Nothing new from my end, so please go ahead -Original Message- From: calligra-devel [mailto:calligra-devel-boun...@kde.org] On Behalf Of Dag Sent: 10. marts 2017 13:03 To: calligra-devel@kde.org Subject: Release 3.0.1 Hi, should we make a bug fix release soon? A few bugs has been fixed

Release 3.0.1

2017-03-10 Thread Dag
Hi, should we make a bug fix release soon? A few bugs has been fixed, and there is 3 months since 3.0.0 ;) Anybody has something that *needs* to be fixed? Cheers, Dag