KEXI 3.2.0 & KEXI Frameworks Released
Dear All I am happy to announce availability of final 3.2.0 version of KEXI, KDb, KProperty and KReport. Please find the files at https://community.kde.org/Kexi/Releases#3.2.0. There are over 80 bug fixes and improvements since 3.1.0, please see the change log at https://community.kde.org/Kexi/Releases/3.2.0_Changes. Universal snapshots of this and future KEXI versions are also automatically built for Linux (Flatpak) and for Windows (Craft) every night. Windows installer is included as well. Windows versions are marked as Technology Preview what means they are functional but not feature-complete. Please report bugs and wishes as documented at https://community.kde.org/Kexi/File_a_bug_or_wish. -- regards, Jaroslaw Staniek KDE: : A world-wide network of software engineers, artists, writers, translators : and facilitators committed to Free Software development - kde.org KEXI: : A visual database apps builder - kexi-project.org calligra.org/kexi twitter.com/kexi_project facebook.com/kexi.project t.me/kexi_project Qt Certified Specialist: : linkedin.com/in/jstaniek <http://www.linkedin.com/in/jstaniek>
Re: support for other Apple iWorks documents (Pages, ...)?
On Fri, 1 Feb 2019 at 21:20, René J.V. Bertin wrote: > On Friday February 01 2019 12:01:08 Jaroslaw Staniek wrote: > > Hi > > >I doubt it due to scope of the challenge. It's not matter of just plugging > >the lib into Calligra filters. > > Looking at how lean the Keynote import plugin seems to be I was hoping it > would. But I also just discovered that plugin doesn't work with my .key > files - after I managed to force-build Stage which was uneventful once I > had figured out which file to hack (is there an official way to say "ignore > there's no current maintainer, just build it"?) > > >+ NIH. Sending ODF files to users of MSO is no longer a blocker, why it > >would be different with Apple users? > > Not sure what you mean here; I'm looking for import of my .pages documents. > I don't remember if and how well my version(*) of Pages exports to ODF > format, but it's export to .doc is ... perfectable. > I mean that if ODF was a common denominator for iWorks->outside world too then the future would be brighter. That's a wishful thinking of course. Unless export of ODF was modernized, Apple is now way more closed-mindset company than MS ;) > *) From iWorks 09. Old, but one of the best releases before they started > stripping more advanced features that may or may not have been restored in > later versions which won't run on my OS version. > > I'll see if and how LO deals with those .pages files (pardon, directories > :) ) of mine. > -- regards, Jaroslaw Staniek KDE: : A world-wide network of software engineers, artists, writers, translators : and facilitators committed to Free Software development - kde.org KEXI: : A visual database apps builder - kexi-project.org calligra.org/kexi twitter.com/kexi_project facebook.com/kexi.project t.me/kexi_project Qt Certified Specialist: : linkedin.com/in/jstaniek <http://www.linkedin.com/in/jstaniek>
Re: support for other Apple iWorks documents (Pages, ...)?
I doubt it due to scope of the challenge. It's not matter of just plugging the lib into Calligra filters. I would assume all major suites support standards already (OpenDocument Format) as a common base. Even MS have admitted that MSOOXML is not such a base (even) for their tech [1], to me it was more like a smoke and mirrors + NIH. Sending ODF files to users of MSO is no longer a blocker, why it would be different with Apple users? If the matter is desktop publishing/specific features present only in iWorks then there's no way to have wide support for that, by definition such things are application-specific. [1] https://www.reddit.com/r/linux/comments/5yvntm/former_head_of_microsoft_office_development_brags/ On Fri, 1 Feb 2019 at 11:34, René J.V. Bertin wrote: > Hi, > > Has any work been done on using libetonyek to import other Apple iWorks > documents, notably text documents from Pages? Supposing it's actually > usable? > > Thanks, > R. > -- regards, Jaroslaw Staniek KDE: : A world-wide network of software engineers, artists, writers, translators : and facilitators committed to Free Software development - kde.org KEXI: : A visual database apps builder - kexi-project.org calligra.org/kexi twitter.com/kexi_project facebook.com/kexi.project t.me/kexi_project Qt Certified Specialist: : linkedin.com/in/jstaniek <http://www.linkedin.com/in/jstaniek>
3.2 Beta of KEXI & KEXI Frameworks Released
Dear All! We are happy to announce the 3.2 Beta release of KEXI, KDb, KProperty and KReport. Please find it at https://community.kde.org/Kexi/Releases#3.2.0_Beta_1. Since the 3.1.0 version KEXI and the frameworks received about 200 improvements and bug fixes. These are source code downloads. For binaries ask your Linux distributor. The source code is known to build and run with Linux (gcc, clang) and MS Windows (msvc>=2013). Some binaries such as installers for Windows 64bit are planned for the RC or stable version. Changelog: https://community.kde.org/Kexi/Releases/3.2.0_Changes Release schedule: https://community.kde.org/Kexi/Schedules#3.2.0 We would have one RC release within 30 days and then final 3.2. Your feedback and support is welcome! https://community.kde.org/Kexi/Contact -- regards, Jaroslaw Staniek KDE: : A world-wide network of software engineers, artists, writers, translators : and facilitators committed to Free Software development - kde.org KEXI: : A visual database apps builder - kexi-project.org calligra.org/kexi twitter.com/kexi_project facebook.com/kexi.project t.me/kexi_project Qt Certified Specialist: : linkedin.com/in/jstaniek <http://www.linkedin.com/in/jstaniek>
Re: Bumping qt version
On Tue, 15 Jan 2019 at 21:13, Adam Pigg wrote: > Sailfish will shortly (tm) be upgrading to 5.9 so that wont block for > much longer i hope. My understanding is they are working out the > legal issues around the license changes ... technically the port is > ready. I dont really understand the issue myself! > Yes I noticed. 5.9 is much for conservative such as OS vendors / hardware platforms. Yet, I meant the pattern - it is not uncommon that people bump more than to 5.9. Doing so just because, say, "Qt 5.11 works on my desktop" is not optimal approach. > > On Tue, 15 Jan 2019 at 12:01, René J.V. Bertin > wrote: > > > > On Tuesday January 15 2019 12:53:03 Jaroslaw Staniek wrote: > > > If there's no reason to force upgrade, I would not. Also (guess what) > LTS > > > distros seem refuse to upgrade without users doing extra steps. > > > > Amen to that! > > > > I'm very annoyed by the fact that KF5 Frameworks just moved to Qt 5.10, > for no real good reason AFAICT. > > (As a result I find myself backporting the necessary bits of 5.10 to my > Qt 5.9 build...) > > > > R. > -- regards, Jaroslaw Staniek KDE: : A world-wide network of software engineers, artists, writers, translators : and facilitators committed to Free Software development - kde.org KEXI: : A visual database apps builder - kexi-project.org calligra.org/kexi twitter.com/kexi_project facebook.com/kexi.project t.me/kexi_project Qt Certified Specialist: : linkedin.com/in/jstaniek <http://www.linkedin.com/in/jstaniek>
Re: Bumping qt version
On Tue, 15 Jan 2019 at 12:44, wrote: > Any reason not to require qt 5.9? > We are at 5.3 atm. > Not strictly related to calligra.git but similar case for KEXI/KEXI frameworks: it is caused by Sailfish depending on such older Qt. If there's no reason to force upgrade, I would not. Also (guess what) LTS distros seem refuse to upgrade without users doing extra steps. Good reason would be a Qt bug blocking fundamental features of certain apps, I can recall such cases for Krita tablet support in older times. -- regards, Jaroslaw Staniek KDE: : A world-wide network of software engineers, artists, writers, translators : and facilitators committed to Free Software development - kde.org KEXI: : A visual database apps builder - kexi-project.org calligra.org/kexi twitter.com/kexi_project facebook.com/kexi.project t.me/kexi_project Qt Certified Specialist: : linkedin.com/in/jstaniek <http://www.linkedin.com/in/jstaniek>
Re: KEXI, KDb, KProperty, KReport 3.2.0 ready to translate
Ok, thanks! https://phabricator.kde.org/D18096 On Tue, 8 Jan 2019 at 13:32, Jonathan Riddell wrote: > Yes, that's how Plasma and Applications do it. Not all projects to it > this way, but once a new stable branch is made repo-metadata's stable > branch should be updated to allow translations. > > Jonathan > > On Tue, 8 Jan 2019 at 12:28, Jaroslaw Staniek wrote: > > > > > > > > On Tue, 8 Jan 2019 at 13:22, Jonathan Riddell wrote: > >> > >> It blocks any translations to 3.2 branch as there's nowhere the > >> translations end up. > >> > >> In KDE neon we also set our dev-stable builds using the repo-metadata > >> branches so I'd need to override those to build this forthcoming > >> release as we do for other beta and pre-beta software. > > > > > > Thanks. So is it normal practice to bump repo-metadata version weeks > before the .0 release? > > > >> > >> Jonathan > >> > >> On Tue, 8 Jan 2019 at 12:03, Jaroslaw Staniek wrote: > >> > > >> > > >> > Does it block anything on your end? If so we can update. CI already > has stable set to 3.2 for example. > >> > 3.1 branch is for the current stable because nothing from 3.2 is > released. > >> > We have 3.2 earlier because we had to bump minor version due to new > APIs. > >> > > >> > On Tue, 8 Jan 2019 at 12:44, Jonathan Riddell > wrote: > >> >> > >> >> The stable branch is still set to 3.1 in repo-metadata > >> >> > >> >> Jonathan > >> >> > >> >> On Tue, 8 Jan 2019 at 09:59, Jaroslaw Staniek > wrote: > >> >> > > >> >> > > >> >> > Dear All, > >> >> > I'd like to declare string freeze for 4 projects: KEXI, KDb, > >> >> > KProperty, KReport version 3.2.0. > >> >> > > >> >> > Beta would be announced on Jan 21st. > >> >> > Stable is planned for February so there is one month for > >> >> > testing messages and translating. There are not too many new > strings. > >> >> > Translating of docs is not recommended, they need major update. > >> >> > > >> >> > All the code is in branch 3.2 of repo kexi/kdb/kproperty/kreport. > >> >> > > >> >> > Technical details: > >> >> > 3.2.0 KDb, KProperty, KReport may have new APIs but are backward > compatible with 3.1.0. > >> >> > KEXI 3.2.0 requires update of KDb, KProperty, KReport to 3.2.0. > >> >> > > >> >> > -- > >> >> > regards, Jaroslaw Staniek > >> >> > > >> >> > KDE: > >> >> > : A world-wide network of software engineers, artists, writers, > translators > >> >> > : and facilitators committed to Free Software development - > kde.org > >> >> > KEXI: > >> >> > : A visual database apps builder - kexi-project.org > calligra.org/kexi > >> >> > twitter.com/kexi_project facebook.com/kexi.project > t.me/kexi_project > >> >> > Qt Certified Specialist: > >> >> > : linkedin.com/in/jstaniek > >> > > >> > > >> > > >> > -- > >> > regards, Jaroslaw Staniek > >> > > >> > KDE: > >> > : A world-wide network of software engineers, artists, writers, > translators > >> > : and facilitators committed to Free Software development - kde.org > >> > KEXI: > >> > : A visual database apps builder - kexi-project.org calligra.org/kexi > >> > twitter.com/kexi_project facebook.com/kexi.project > t.me/kexi_project > >> > Qt Certified Specialist: > >> > : linkedin.com/in/jstaniek > > > > > > > > -- > > regards, Jaroslaw Staniek > > > > KDE: > > : A world-wide network of software engineers, artists, writers, > translators > > : and facilitators committed to Free Software development - kde.org > > KEXI: > > : A visual database apps builder - kexi-project.org calligra.org/kexi > > twitter.com/kexi_project facebook.com/kexi.project t.me/kexi_project > > Qt Certified Specialist: > > : linkedin.com/in/jstaniek > -- regards, Jaroslaw Staniek KDE: : A world-wide network of software engineers, artists, writers, translators : and facilitators committed to Free Software development - kde.org KEXI: : A visual database apps builder - kexi-project.org calligra.org/kexi twitter.com/kexi_project facebook.com/kexi.project t.me/kexi_project Qt Certified Specialist: : linkedin.com/in/jstaniek <http://www.linkedin.com/in/jstaniek>
Re: KEXI, KDb, KProperty, KReport 3.2.0 ready to translate
On Tue, 8 Jan 2019 at 13:22, Jonathan Riddell wrote: > It blocks any translations to 3.2 branch as there's nowhere the > translations end up. > > In KDE neon we also set our dev-stable builds using the repo-metadata > branches so I'd need to override those to build this forthcoming > release as we do for other beta and pre-beta software. > Thanks. So is it normal practice to bump repo-metadata version weeks before the .0 release? > Jonathan > > On Tue, 8 Jan 2019 at 12:03, Jaroslaw Staniek wrote: > > > > > > Does it block anything on your end? If so we can update. CI already has > stable set to 3.2 for example. > > 3.1 branch is for the current stable because nothing from 3.2 is > released. > > We have 3.2 earlier because we had to bump minor version due to new APIs. > > > > On Tue, 8 Jan 2019 at 12:44, Jonathan Riddell wrote: > >> > >> The stable branch is still set to 3.1 in repo-metadata > >> > >> Jonathan > >> > >> On Tue, 8 Jan 2019 at 09:59, Jaroslaw Staniek wrote: > >> > > >> > > >> > Dear All, > >> > I'd like to declare string freeze for 4 projects: KEXI, KDb, > >> > KProperty, KReport version 3.2.0. > >> > > >> > Beta would be announced on Jan 21st. > >> > Stable is planned for February so there is one month for > >> > testing messages and translating. There are not too many new strings. > >> > Translating of docs is not recommended, they need major update. > >> > > >> > All the code is in branch 3.2 of repo kexi/kdb/kproperty/kreport. > >> > > >> > Technical details: > >> > 3.2.0 KDb, KProperty, KReport may have new APIs but are backward > compatible with 3.1.0. > >> > KEXI 3.2.0 requires update of KDb, KProperty, KReport to 3.2.0. > >> > > >> > -- > >> > regards, Jaroslaw Staniek > >> > > >> > KDE: > >> > : A world-wide network of software engineers, artists, writers, > translators > >> > : and facilitators committed to Free Software development - kde.org > >> > KEXI: > >> > : A visual database apps builder - kexi-project.org calligra.org/kexi > >> > twitter.com/kexi_project facebook.com/kexi.project > t.me/kexi_project > >> > Qt Certified Specialist: > >> > : linkedin.com/in/jstaniek > > > > > > > > -- > > regards, Jaroslaw Staniek > > > > KDE: > > : A world-wide network of software engineers, artists, writers, > translators > > : and facilitators committed to Free Software development - kde.org > > KEXI: > > : A visual database apps builder - kexi-project.org calligra.org/kexi > > twitter.com/kexi_project facebook.com/kexi.project t.me/kexi_project > > Qt Certified Specialist: > > : linkedin.com/in/jstaniek > -- regards, Jaroslaw Staniek KDE: : A world-wide network of software engineers, artists, writers, translators : and facilitators committed to Free Software development - kde.org KEXI: : A visual database apps builder - kexi-project.org calligra.org/kexi twitter.com/kexi_project facebook.com/kexi.project t.me/kexi_project Qt Certified Specialist: : linkedin.com/in/jstaniek <http://www.linkedin.com/in/jstaniek>
Re: KEXI, KDb, KProperty, KReport 3.2.0 ready to translate
Does it block anything on your end? If so we can update. CI already has stable set to 3.2 for example. 3.1 branch is for the current stable because nothing from 3.2 is released. We have 3.2 earlier because we had to bump minor version due to new APIs. On Tue, 8 Jan 2019 at 12:44, Jonathan Riddell wrote: > The stable branch is still set to 3.1 in repo-metadata > > Jonathan > > On Tue, 8 Jan 2019 at 09:59, Jaroslaw Staniek wrote: > > > > > > Dear All, > > I'd like to declare string freeze for 4 projects: KEXI, KDb, > > KProperty, KReport version 3.2.0. > > > > Beta would be announced on Jan 21st. > > Stable is planned for February so there is one month for > > testing messages and translating. There are not too many new strings. > > Translating of docs is not recommended, they need major update. > > > > All the code is in branch 3.2 of repo kexi/kdb/kproperty/kreport. > > > > Technical details: > > 3.2.0 KDb, KProperty, KReport may have new APIs but are backward > compatible with 3.1.0. > > KEXI 3.2.0 requires update of KDb, KProperty, KReport to 3.2.0. > > > > -- > > regards, Jaroslaw Staniek > > > > KDE: > > : A world-wide network of software engineers, artists, writers, > translators > > : and facilitators committed to Free Software development - kde.org > > KEXI: > > : A visual database apps builder - kexi-project.org calligra.org/kexi > > twitter.com/kexi_project facebook.com/kexi.project t.me/kexi_project > > Qt Certified Specialist: > > : linkedin.com/in/jstaniek > -- regards, Jaroslaw Staniek KDE: : A world-wide network of software engineers, artists, writers, translators : and facilitators committed to Free Software development - kde.org KEXI: : A visual database apps builder - kexi-project.org calligra.org/kexi twitter.com/kexi_project facebook.com/kexi.project t.me/kexi_project Qt Certified Specialist: : linkedin.com/in/jstaniek <http://www.linkedin.com/in/jstaniek>
KEXI, KDb, KProperty, KReport 3.2.0 ready to translate
Dear All, I'd like to declare string freeze for 4 projects: KEXI, KDb, KProperty, KReport version 3.2.0. Beta would be announced on Jan 21st. Stable is planned for February so there is one month for testing messages and translating. There are not too many new strings. Translating of docs is not recommended, they need major update. All the code is in branch 3.2 of repo kexi/kdb/kproperty/kreport. Technical details: 3.2.0 KDb, KProperty, KReport may have new APIs but are backward compatible with 3.1.0. KEXI 3.2.0 requires update of KDb, KProperty, KReport to 3.2.0. -- regards, Jaroslaw Staniek KDE: : A world-wide network of software engineers, artists, writers, translators : and facilitators committed to Free Software development - kde.org KEXI: : A visual database apps builder - kexi-project.org calligra.org/kexi twitter.com/kexi_project facebook.com/kexi.project t.me/kexi_project Qt Certified Specialist: : linkedin.com/in/jstaniek <http://www.linkedin.com/in/jstaniek>
Re: Moving plan into separate repository
On Mon, 29 Oct 2018 at 12:21, Dag wrote: > Many thanks! > That cleared things up, I fidle with it until I'm satisfied, push to a > scratch repo, and ask sysadmin for a move. > That is cool to know! Cheers Dag. -- regards, Jaroslaw Staniek KDE: : A world-wide network of software engineers, artists, writers, translators : and facilitators committed to Free Software development - http://kde.org KEXI: : A visual database apps builder - http://calligra.org/kexi http://twitter.com/kexi_project https://facebook.com/kexi.project Qt Certified Specialist: : http://www.linkedin.com/in/jstaniek
Re: Moving plan into separate repository
On Mon, 29 Oct 2018 at 09:01, Dag wrote: > > I'm looking into this to simplify releases, same as you have done with > kexi. > I hoped you had some hints for me, I haven't got much help from > sysadmins, > so I'm wondering what do they need to do and what do I need to do? Hello Dag 1. Click sysadmin request on Phabricator to request the repo as the maintainer https://phabricator.kde.org/maniphest/task/edit/form/2/ 2. Most of the work was for me related to extracting git history. Work *locally* until you are happy with the history. Have someone to review it. Your project does not need to build prior to first push but better have correct history / git blame. You have some work (can take even 24h of computation locally on your machine). Please see GIT SURGERY at https://community.kde.org/Kexi/Porting_to_Qt%26KF_5 3. Also please see this entire thread and 3rd post especially: https://mail.kde.org/pipermail/kexi-devel/2015-February/000247.html 4. Example for KProperty extraction: I succeeded with this - created two parts of history because in the days of koffice lib/ was renamed to libs/: git filter-branch -f --subdirectory-filter libs/koproperty/ -- kproperty git filter-branch -f --subdirectory-filter lib/koproperty/ -- kproperty-lib then: git rebase --root --preserve-merges --onto kproperty-lib This shows type of renames you may want. Your root dir is going to have src/ subdir etc., so everything is moving. Same goes to test dirs. All depends on how clean history you want, KEXI's is tracked sown to pre-git times, April 1998 :) 5. Moving/simplifying/copying of some Calligra's cmake magic script and automatism. They are going to be simplified so developers are not confused that they build entire calligra. Remove as many unused files as possible. 6. Please note that KEXI had no dependencies on calligra/libs/ (apart from one optional plugin) due to the fact that is it is a very different type of app. Since you have them you need to design how the dependencies will be built: so far Calligra neither export them nor maintain BC for them especially. Once you are on the outside with Plan you have to depend on releases of Calligra anyway or make them in another repo (!) and have someone maintain them (which would be awesome). I say that is needed unless you copy these dependencies (if they are large this can be against the principles) or remove them (may be impossible or not practical depending on how large the dependencies are, Krita looks like a similar case to me and it has managed to separate from them). 7. Optional: Plan can obsolete entire Calligra package in the distros since there are going to be the same files installed by current calligra.git and the plan.git. You can make sure your new files are unique on a distro and bump version or even rename all installed files so there's zero conflict with the "old" Plan from Calligra. I went further and implemented side-by-side install-ability for KEXI - across all minor versions. Regards, Jarek. -- regards, Jaroslaw Staniek KDE: : A world-wide network of software engineers, artists, writers, translators : and facilitators committed to Free Software development - http://kde.org KEXI: : A visual database apps builder - http://calligra.org/kexi http://twitter.com/kexi_project https://facebook.com/kexi.project Qt Certified Specialist: : http://www.linkedin.com/in/jstaniek
Krita donation proposal
Dear Calligra contributors, Congratulations again on the donation [1] and big thanks to the Handshake Foundation for recognizing Calligra! tl;dr: I'd like to propose that 10% of the sum goes to support Krita. Introduction As person helping with completing the donation process I'd like to repeat the fact that Calligra was recognized by the Handshake Foundation as an organization having specific achievements in the FOSS world. The Foundation decided to offer the donation unconditionally and independently of the KDE's one. Unlike other "Office" projects Calligra has no dedicated foundation so the solution was to join KDE e.V. on the task around the bookkeeping and related matters and to ensure transparency. It also felt most natural since we're KDE. So there was no decision of the KDE board or KDE community to split the one fund to Calligra and the rest of KDE, there are two funds. Details Now that we're around next, harder step, I'd like to share my position that addresses possible question of the contributors and fans: what with supporting Krita? Based on what I learned from the donor the funding is based on recognition for the *entire* history of KOffice/Calligra so Krita being important member of our family, not only can but *should* be included i nthe support. Krita has been on the same level of organization as other Calligra applications until 2.9 version [2]. There were 10 visible Calligra apps, not counting variations of apps like mobile or Active and the Office Engine. So I'd like to propose that 10% of the sum goes to support Krita, formally the Krita Foundation. Assertions This is my idea, without any requests from the Krita side. And for my understanding the idea does not limit possibility of Krita or current Calligra to benefit from the "KDE" donation, especially indirectly, e.g. through the shared infrastructure and common development programs. Common sense suggest me reasonable requirement for supporting Calligra sub-projects: they needs to be active (have relatively recent releases) with potential to growth, and activity should be sufficiently independent of existence of the attractive funding that was received. I think Krita meets these requirements. [1] https://dot.kde.org/2018/10/15/kde-ev-receives-sizeable-donation-handshake-foundation [2] https://www.calligra.org/krita -- regards, Jaroslaw Staniek KDE: : A world-wide network of software engineers, artists, writers, translators : and facilitators committed to Free Software development - http://kde.org KEXI: : A visual database apps builder - http://calligra.org/kexi http://twitter.com/kexi_project https://facebook.com/kexi.project Qt Certified Specialist: : http://www.linkedin.com/in/jstaniek
Re: handshake and calligra?
On 6 August 2018 at 11:44, Boudewijn Rempt wrote: > Hi, > > I just noticed that on https://handshake.org/ they mention "caligra" as a > recipient of their community grants. Despite the misspelling, the link > goes to > https://calligra.org. Does anyone know anything about that? If it's true, > we > probably should do a post about it, and what's going to be done with the > grant, but if not, we'd need to have that taken down... Hi Boud If there's something it's donation to KDE e.V. for Calligra apps, as Calligra is not backed by separate organization. I can ask to fix the name though, thanks for pointing out. -- regards, Jaroslaw Staniek KDE: : A world-wide network of software engineers, artists, writers, translators : and facilitators committed to Free Software development - http://kde.org KEXI: : A visual database apps builder - http://calligra.org/kexi http://twitter.com/kexi_project https://facebook.com/kexi.project Qt Certified Specialist: : http://www.linkedin.com/in/jstaniek
Re: Awesome build.kde.org for KEXI / Calligra
On 2 August 2018 at 17:51, wrote: > Great stuff! > > How easy, or difficult would it be to add > appimage, and macos? > Neither is automatic - I do not know if anyone contributes KEXI or dependencies to these to targets. -- regards, Jaroslaw Staniek KDE: : A world-wide network of software engineers, artists, writers, translators : and facilitators committed to Free Software development - http://kde.org KEXI: : A visual database apps builder - http://calligra.org/kexi http://twitter.com/kexi_project https://facebook.com/kexi.project Qt Certified Specialist: : http://www.linkedin.com/in/jstaniek
Awesome build.kde.org for KEXI / Calligra
Dear All, Thanks to our KDE sysadmin Ben Cooksley and the admins team in general we can use a matrix of builds for KEXI, its frameworks and Calligra! - Linux (SUSE) - Windiows (MSVC) - FreeBSD + All the above for stable (x.y branches) and unstable (master branches). Click the "Calligra" tab on the dashboard and you're on https://build.kde.org/view/Calligra/ for nice reports. I updated a static HTML page http://kexi-project.org/build_status.html with all the new builds. L/W/F means Linux/Windows/FreeBSD. Status visualization like before is based on shields.io. You can copy this single file file locally and it will still work. The build setup is so awesome Ben, thanks so much :) PS: For now we need a contributor for the Windows Calligra build, it's failing due to boost https://build.kde.org/view/Calligra/job/Calligra%20calligra%20stable-kf5-qt5%20WindowsMSVCQt5.10/lastBuild/console -- regards, Jaroslaw Staniek KDE: : A world-wide network of software engineers, artists, writers, translators : and facilitators committed to Free Software development - http://kde.org KEXI: : A visual database apps builder - http://calligra.org/kexi http://twitter.com/kexi_project https://facebook.com/kexi.project Qt Certified Specialist: : http://www.linkedin.com/in/jstaniek
Re: Fwd: KDE CI: Dependency Build Calligra kf5-qt5 WindowsMSVCQt5.10 - Build # 1 - Failure!
On 27 July 2018 at 11:29, Ben Cooksley wrote: > On Fri, Jul 27, 2018 at 6:34 AM, Dag wrote: > > From cmake: > > * KF5AkonadiContact , Library for Accessing Contacts stored in Akonadi , > > <https://www.kde.org/> > >Optionally used by Plan > > * KF5Akonadi , Library for general Access to Akonadi , > > <https://www.kde.org/> > >Optionally used by semantic items Event and Contact > > > > Plan's use og KF5AkonadiContact is atm not working but needs a > > reimplementation anyways to be useful, > > so I have no problem with removing it for Windows. > > > > The semantic items stuff is also not working atm, it has not yet been > ported > > properly I think. > > So at least for the near future, there should be no problem with making > it > > optional for Windows. > > Thanks Dag, > > I've now made the CI system ignore Akonadi Contacts for Calligra on > Windows. > I'll start a fresh Dependency Build run for Calligra shortly. > Many thanks Ben! > > > > > > > --- > > Cheers, > > > > Dag > > Cheers, > Ben > > > > > > > > > Jaroslaw Staniek skrev den 2018-07-25 11:03: > >> > >> Hi Calligra Devs, > >> Thanks to Ben, we're getting a Jenkins view for Calligra builds: > >> https://build.kde.org/view/Calligra/. > >> I am forwarding info on one defect so you have opportunity to fix this > >> dependency to make Calligra auto-build on Windows! > >> One way I would imagine is to make Prison optional dependency. Another > >> to make it temporarily off on Windows or optional on Windows. > >> > >> @Ben > >> I understand this issue is not affecting kexi* builds for Windows? > >> > >> -- Forwarded message -- > >> From: BEN COOKSLEY > >> Date: 25 July 2018 at 10:53 > >> Subject: Fwd: KDE CI: Dependency Build Calligra kf5-qt5 > >> WindowsMSVCQt5.10 - Build # 1 - Failure! > >> To: Jaroslaw Staniek > >> > >> Hey Jaroslaw, > >> > >> I'm afraid you'll need to resolve this before we can continue with > >> Calligra on Windows CI builds. > >> > >> If akonadi-contacts is an optional dependency of Calligra we can > >> exclude it, otherwise you'll have to arrange for > >> > >> Prison's dependencies to be buildable on Windows using Craft.. > >> > >> Cheers, > >> Ben > >> > >> -- Forwarded message -- > >> From: CI SYSTEM > >> Date: Wed, Jul 25, 2018 at 12:20 AM > >> Subject: KDE CI: Dependency Build Calligra kf5-qt5 WindowsMSVCQt5.10 - > >> Build # 1 - Failure! > >> To: bcooks...@kde.org > >> > >> BUILD FAILURE > >> > >> Build URL > >> > >> https://build.kde.org/job/Dependency%20Build%20Calligra% > 20kf5-qt5%20WindowsMSVCQt5.10/1/ > >> [1] > >> > >> Project: > >> Dependency Build Calligra kf5-qt5 WindowsMSVCQt5.10 > >> > >> Date of build: > >> Tue, 24 Jul 2018 09:12:57 + > >> > >> Build duration: > >> 3 hr 7 min and counting > >> > >> CONSOLE OUTPUT > >> > >> [...truncated 38.40 MB...] > >> > >> PROCESSOR_LEVEL = '6' > >> > >> PROCESSOR_REVISION = '3d02' > >> > >> PROGRAMDATA = 'C:\ProgramData' > >> > >> PROGRAMFILES = 'C:\Program Files' > >> > >> PROGRAMFILES(X86) = 'C:\Program Files (x86)' > >> > >> PROGRAMW6432 = 'C:\Program Files' > >> > >> PROMPT = '$P$G' > >> > >> PSMODULEPATH = > >> 'C:\WINDOWS\system32\WindowsPowerShell\v1.0\Modules\' > >> > >> PUBLIC = 'C:\Users\Public' > >> > >> RUN_CHANGES_DISPLAY_URL = > >> > >> 'https://build.kde.org/job/Dependency%20Build%20Calligra% > 20kf5-qt5%20WindowsMSVCQt5.10/1/display/redirect?page=changes > >> [2]' > >> > >> RUN_DISPLAY_URL = > >> > >> 'https://build.kde.org/job/Dependency%20Build%20Calligra% > 20kf5-qt5%20WindowsMSVCQt5.10/1/display/redirect > >> [3]' > >> > >> > >> STAGE_NA
Re: KDE CI: Dependency Build Calligra kf5-qt5 WindowsMSVCQt5.10 - Build # 1 - Failure!
On 25 July 2018 at 12:47, René J.V. Bertin wrote: > On Wednesday July 25 2018 22:33:33 Ben Cooksley wrote: > >On Wed, Jul 25, 2018 at 9:03 PM, Jaroslaw Staniek > wrote: > > >> One way I would imagine is to make Prison optional dependency. Another > to > >> make it temporarily off on Windows or optional on Windows. > ... > >Note that it isn't Calligra depending on Prison, it's Calligra depending > on > >Akonadi's contacts component, which in turn hard depends on Prison, that > is > >the problem. > > Does KDEPIM work on MSWin? If it doesn't (and I can easily imagine it > won't), then there's probably little use in depending on akonadi-contacts, > no? > > Good question. -- regards, Jaroslaw Staniek KDE: : A world-wide network of software engineers, artists, writers, translators : and facilitators committed to Free Software development - http://kde.org KEXI: : A visual database apps builder - http://calligra.org/kexi http://twitter.com/kexi_project https://facebook.com/kexi.project Qt Certified Specialist: : http://www.linkedin.com/in/jstaniek
Fwd: KDE CI: Dependency Build Calligra kf5-qt5 WindowsMSVCQt5.10 - Build # 1 - Failure!
Hi Calligra Devs, Thanks to Ben, we're getting a Jenkins view for Calligra builds: https://build.kde.org/view/Calligra/. I am forwarding info on one defect so you have opportunity to fix this dependency to make Calligra auto-build on Windows! One way I would imagine is to make Prison optional dependency. Another to make it temporarily off on Windows or optional on Windows. @Ben I understand this issue is not affecting kexi* builds for Windows? -- Forwarded message -- From: Ben Cooksley Date: 25 July 2018 at 10:53 Subject: Fwd: KDE CI: Dependency Build Calligra kf5-qt5 WindowsMSVCQt5.10 - Build # 1 - Failure! To: Jaroslaw Staniek Hey Jaroslaw, I'm afraid you'll need to resolve this before we can continue with Calligra on Windows CI builds. If akonadi-contacts is an optional dependency of Calligra we can exclude it, otherwise you'll have to arrange for Prison's dependencies to be buildable on Windows using Craft.. Cheers, Ben -- Forwarded message -- From: CI System Date: Wed, Jul 25, 2018 at 12:20 AM Subject: KDE CI: Dependency Build Calligra kf5-qt5 WindowsMSVCQt5.10 - Build # 1 - Failure! To: bcooks...@kde.org *BUILD FAILURE* Build URL https://build.kde.org/job/Dependency%20Build%20Calligra%20kf 5-qt5%20WindowsMSVCQt5.10/1/ Project: Dependency Build Calligra kf5-qt5 WindowsMSVCQt5.10 Date of build: Tue, 24 Jul 2018 09:12:57 + Build duration: 3 hr 7 min and counting * CONSOLE OUTPUT * [...truncated 38.40 MB...] PROCESSOR_LEVEL = '6' PROCESSOR_REVISION = '3d02' PROGRAMDATA = 'C:\ProgramData' PROGRAMFILES = 'C:\Program Files' PROGRAMFILES(X86) = 'C:\Program Files (x86)' PROGRAMW6432 = 'C:\Program Files' PROMPT = '$P$G' PSMODULEPATH = 'C:\WINDOWS\system32\WindowsPowerShell\v1.0\Modules\' PUBLIC = 'C:\Users\Public' RUN_CHANGES_DISPLAY_URL = 'https://build.kde.org/job/Dep endency%20Build%20Calligra%20kf5-qt5%20WindowsMSVCQt5.10/1/ display/redirect?page=changes' RUN_DISPLAY_URL = 'https://build.kde.org/job/Dep endency%20Build%20Calligra%20kf5-qt5%20WindowsMSVCQt5.10/1/display/redirect' STAGE_NAME = 'Build Product Dependencies' SYSTEMDRIVE = 'C:' SYSTEMROOT = 'C:\WINDOWS' TEMP = 'C:\Users\Jenkins\AppData\Local\Temp' TMP = 'C:\Users\Jenkins\AppData\Local\Temp' UCRTVERSION = '10.0.17134.0' UNIVERSALCRTSDKDIR = 'C:\Program Files (x86)\Windows Kits\10\' USERDOMAIN = 'DESKTOP-66R8QOQ' USERNAME = 'Jenkins' USERPROFILE = 'C:\Users\Jenkins' VCIDEINSTALLDIR = 'C:\Program Files (x86)\Microsoft Visual Studio\2017\Professional\Common7\IDE\VC\' VCINSTALLDIR = 'C:\Program Files (x86)\Microsoft Visual Studio\2017\Professional\VC\' VCTOOLSINSTALLDIR = 'C:\Program Files (x86)\Microsoft Visual Studio\2017\Professional\VC\Tools\MSVC\14.14.26428\' VCTOOLSREDISTDIR = 'C:\Program Files (x86)\Microsoft Visual Studio\2017\Professional\VC\Redist\MSVC\14.14.26405\' VCTOOLSVERSION = '14.14.26428' VISUALSTUDIOVERSION = '15.0' VS140COMNTOOLS = 'C:\Program Files (x86)\Microsoft Visual Studio 14.0\Common7\Tools\' VS150COMNTOOLS = 'C:\Program Files (x86)\Microsoft Visual Studio\2017\Professional\Common7\Tools\' VSCMD_ARG_APP_PLAT = 'Desktop' VSCMD_ARG_HOST_ARCH = 'x64' VSCMD_ARG_TGT_ARCH = 'x64' VSCMD_VER = '15.7.3' VSINSTALLDIR = 'C:\Program Files (x86)\Microsoft Visual Studio\2017\Professional\' WINDIR = 'C:\WINDOWS' WINDOWSLIBPATH = 'C:\Program Files (x86)\Windows Kits\10\UnionMetadata\10.0.17134.0;C:\Program Files (x86)\Windows Kits\10\References\10.0.17134.0' WINDOWSSDKBINPATH = 'C:\Program Files (x86)\Windows Kits\10\bin\' WINDOWSSDKDIR = 'C:\Program Files (x86)\Windows Kits\10\' WINDOWSSDKLIBVERSION = '10.0.17134.0\' WINDOWSSDKVERBINPATH = 'C:\Program Files (x86)\Windows Kits\10\bin\10.0.17134.0\' WINDOWSSDKVERSION = '10.0.17134.0\' WORKSPACE = 'C:\CI\workspace\Dependency Build Calligra kf5-qt5 WindowsMSVCQt5.10' __DOTNET_ADD_64BIT = '1' __DOTNET_PREFERRED_BITNESS = '64' __VSCMD_PREINIT_PATH = 'C:\Program Files (x86)\Common Files\Oracle\Java\javapath;C:\Program Files\Python36-32\Scripts\;C:\Program Files\Python36-32\;C:\ProgramData\Oracle\Java\javapath;C:\ WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\WINDOWS\System32\ WindowsPowerShell\v1.0\;C:\Program Files\Git\cmd;C:\WINDOWS\Syste m32\OpenSSH\;C:\Users\Jenkins\AppData\Local\Microsoft\WindowsApps' CMAKE_PREFIX_PATH = 'C:\CI\workspace\Dependency Build Calligra kf5-qt5 WindowsMSVCQt5.10\install-prefix;C:\Craft\CI\windows-msvc201 7_64-cl-debug;C:\Craft\CI\windows-msvc2017_64-cl-debug\dev-utils' QT_PLUGIN_PATH = 'C:\CI\workspace\Dependency Build Calligra kf5-qt5 WindowsMSVCQt5.10\install-prefix\lib\plugins;C:\Craft\CI\ windows-msvc2017_64-cl-debug\lib\qca-qt5' QML2_IMPORT_PATH = 'C:\CI\workspace\Dependency Build Calligra kf5-qt5 WindowsMSVCQt5.10\install-prefix\lib\qml' XDG_DATA_DIRS = 'C:\CI\workspace\Dependency Build Calligra kf5-qt5 WindowsMSVCQt5.10\install-prefix\share;C:\Craft\CI\windows- msvc2017_64-cl-debug\share;C:\Craft\CI\windows-msvc2017_64- cl-debug\dev-utils\share' XDG_CONFIG_DIRS = 'C:\CI\workspace\Dependency
Re: Urgent: Is the domain koffice.net still needed?
On 21 March 2018 at 17:01, Aleix Pol <aleix...@kde.org> wrote: > On Wed, Mar 21, 2018 at 12:53 PM, Jaroslaw Staniek <stan...@kde.org> wrote: >> On 21 March 2018 at 09:51, Boudewijn Rempt <b...@valdyas.org> wrote: >>> On woensdag 21 maart 2018 06:56:06 CET Ben Cooksley wrote: >>> >>>> Unfortunately just about all those links will be long dead and broken as >>>> the content of koffice.org was lost at some point. >>> >>> I do have a full backup of the old php site, even including history: >>> >>> https://github.com/boudewijnrempt/koffice-web >>> >>> I uploaded it after I discovered that even the subversion module for >>> koffice- >>> web had been deleted. The cms-based website is gone forever, of course. >>> >> >> That's great, so we have secured lots of content. Thus keeping the >> domain would make sense. > > Hi Jaroslaw, > I don't see how it relates. At the moment we are redirecting > koffice.net and .org to calligra.org. It relates this way: if we allow to hijack koffice.org like we did with kdedevelopers.org redirecting traffic coming will not be possible. No matter how well this redirection is set up (it can improve over time). -- regards, Jaroslaw Staniek KDE: : A world-wide network of software engineers, artists, writers, translators : and facilitators committed to Free Software development - http://kde.org KEXI: : A visual database apps builder - http://calligra.org/kexi http://twitter.com/kexi_project https://facebook.com/kexi.project Qt Certified Specialist: : http://www.linkedin.com/in/jstaniek
Re: Urgent: Is the domain koffice.net still needed?
On 21 March 2018 at 09:51, Boudewijn Rempt <b...@valdyas.org> wrote: > On woensdag 21 maart 2018 06:56:06 CET Ben Cooksley wrote: > >> Unfortunately just about all those links will be long dead and broken as >> the content of koffice.org was lost at some point. > > I do have a full backup of the old php site, even including history: > > https://github.com/boudewijnrempt/koffice-web > > I uploaded it after I discovered that even the subversion module for koffice- > web had been deleted. The cms-based website is gone forever, of course. > That's great, so we have secured lots of content. Thus keeping the domain would make sense. -- regards, Jaroslaw Staniek KDE: : A world-wide network of software engineers, artists, writers, translators : and facilitators committed to Free Software development - http://kde.org KEXI: : A visual database apps builder - http://calligra.org/kexi http://twitter.com/kexi_project https://facebook.com/kexi.project Qt Certified Specialist: : http://www.linkedin.com/in/jstaniek
Re: Urgent: Is the domain koffice.net still needed?
On 20 March 2018 at 13:46, Dag <dand...@get2net.dk> wrote: > Afaik we do not need koffice.net and koffice.org. > koffice.org just points to calligra.org, and koffice.net does not have any > content. We have a number of links to articles of koffice.org what for my understanding represents is huge part of what KDE was and thus, what it is. Another example is the Kontact suite. We had some discussion this month about preserving these links. Regardless technicalities and of availability volunteers to do that, this will not be possible if we loose the domain to hijackers so I would propose to keep it. And hope this will be not a disaster for the budget. :) Regarding koffice.net, it's not important at all. > > --- > Cheers, > > Dag > > > > Ben Cooksley skrev den 2018-03-20 07:25: >> >> On Tue, Mar 20, 2018 at 8:37 AM, Thomas Pfeiffer >> <thomas.pfeif...@kde.org> wrote: >>> >>> Dear Calligra team, >> >> >> Hi all, >> >>> we just got notified that the domain koffice.net is about to expire and >>> has to be renewed, and sysadmin asked the board whether the domain is still >>> used. >>> Since KOffice has not been around for years now, we wonder if you still >>> need the old domain as a redirect to calligra.org, or if we can drop it. >>> The domain is set to expire by Friday (March 23rd). >> >> >> Please note that koffice.org is also coming up for renewal one day >> after koffice.net, so comments on that would also be appreciated. >> >>> >>> If we do not get a reply from someone by *Thursday, March 22nd, 23:59:59 >>> CET* saying that the domain is still needed, we are going to drop the domain >>> koffice.net. >>> >>> Thank you, >>> Thomas >>> >>> >> >> Regards, >> Ben -- regards, Jaroslaw Staniek KDE: : A world-wide network of software engineers, artists, writers, translators : and facilitators committed to Free Software development - http://kde.org KEXI: : A visual database apps builder - http://calligra.org/kexi http://twitter.com/kexi_project https://facebook.com/kexi.project Qt Certified Specialist: : http://www.linkedin.com/in/jstaniek
KEXI 3.1.0 & KEXI Frameworks Released
Hello! I am very pleased to announce final release of KEXI 3.1 and its Frameworks. A special highlight after years-long pause is official Windows version. It costs a lot of effort to produce and maintain it so feel free to report your thoughts regarding this Preview version. Please find KEXI source code downloads, Windows installer, list of changes and issues at https://community.kde.org/Kexi/Releases#3.1.0. Further release schedule: https://community.kde.org/Kexi/Schedules -- regards, Jaroslaw Staniek KDE: : A world-wide network of software engineers, artists, writers, translators : and facilitators committed to Free Software development - http://kde.org KEXI: : A visual database apps builder - http://calligra.org/kexi http://twitter.com/kexi_project https://facebook.com/kexi.project Qt Certified Specialist: : http://www.linkedin.com/in/jstaniek
3.1.0 RC of KEXI & KEXI Frameworks Released
Dear All I am happy to announce availability of 3.1.0 Release Candidate version of KEXI, KDb, KProperty and KReport for testing. Upcoming Windows releases will be marked as a Technology Previews so any issues on Windows system, such as failing file compacting, are not blockers of the 3.1.0 release. Please find the 3.1.0 RC at https://community.kde.org/Kexi/Releases#3.1.0_RC_1 If there are no critical issues, final 3.1.0 will be released on March 9. There are quite a few bug fixes and improvements since the 3.1.0 Beta, please see the change log (search for "3.1.0 RC 1"): https://community.kde.org/Kexi/Releases/3.1.0_Changes Release schedule: https://community.kde.org/Kexi/Schedules#3.1.0 -- regards, Jaroslaw Staniek KDE: : A world-wide network of software engineers, artists, writers, translators : and facilitators committed to Free Software development - http://kde.org KEXI: : A visual database apps builder - http://calligra.org/kexi http://twitter.com/kexi_project https://facebook.com/kexi.project Qt Certified Specialist: : http://www.linkedin.com/in/jstaniek
Re: KEXI, KDb, KProperty, KReport 3.1 ready to translate
On 19 January 2018 at 13:29, Jaroslaw Staniek <stan...@kde.org> wrote: > Dear All, > I'd like to declare string freeze for 4 projects: KEXI, KDb, > KProperty, KReport version 3.1. > > Beta would be announced on Jan 29th. > Upload of stable is planned for Feb 22, 2018 so there is one month for > testing messages and translating. > Translating of docs is not recommended, it needs major update. > Hi, We've seen a number of fixes so it makes sense to release RC1 before stable. It's uploading already. Updated schedule: https://community.kde.org/Kexi/Schedules#3.1.0 Regards! > Details with dates and change logs: > https://community.kde.org/Kexi/Schedules#3.1.0 > https://community.kde.org/Kexi/Releases#3.1.0_.28PENDING.29 > > -- > regards, Jaroslaw Staniek > > KDE: > : A world-wide network of software engineers, artists, writers, translators > : and facilitators committed to Free Software development - http://kde.org > KEXI: > : A visual database apps builder - http://calligra.org/kexi > http://twitter.com/kexi_project https://facebook.com/kexi.project > Qt Certified Specialist: > : http://www.linkedin.com/in/jstaniek > -- regards, Jaroslaw Staniek KDE: : A world-wide network of software engineers, artists, writers, translators : and facilitators committed to Free Software development - http://kde.org KEXI: : A visual database apps builder - http://calligra.org/kexi http://twitter.com/kexi_project https://facebook.com/kexi.project Qt Certified Specialist: : http://www.linkedin.com/in/jstaniek
Re: Calligra 3.1 status
On 6 February 2018 at 14:21, Jonathan Riddell <j...@jriddell.org> wrote: > It's not clear what the status of Calligra 3.1 is. There's an announce up > but > https://community.kde.org/Calligra > still says 3.0.1 is stable, repo-metadata says calligra/3.0 is the > stable branch. > Thanks for reminding Jonathan. Release manager(s) shall consult the howto document https://community.kde.org/Calligra/Release_Howto In particular versions on the wiki are buried in templates linked at https://community.kde.org/Talk:Calligra > > There's a separate calligraplan tar which isn't announed why that > seems to be separate. > > Jonathan > -- regards, Jaroslaw Staniek KDE: : A world-wide network of software engineers, artists, writers, translators : and facilitators committed to Free Software development - http://kde.org KEXI: : A visual database apps builder - http://calligra.org/kexi http://twitter.com/kexi_project https://facebook.com/kexi.project Qt Certified Specialist: : http://www.linkedin.com/in/jstaniek
Re: Release announced on kde-announce-app
Thanks Dag - I'll add link to calligra announcement once it's publishes, on the KEXI release page. On 31 January 2018 at 13:53, Dan Leinir Turthra Jensen <ad...@leinir.dk> wrote: > On Wednesday, 31 January 2018 11:41:03 GMT Dag wrote: > > See att file. > > It would be swell if somebody with access could do likewise on > > calligra.org, maybe add more about gemini. > > Sorry about not sending it on Monday as promised, a range of things > ended up > distracting me quite severely. But, i've updated the file with some Gemini > notes and attached it here. I don't know who has access to calligra.org, > but > i'm thinking that spreading that access just slightly wider would perhaps > be > good... > > -- > .dan / leinir.. > http://leinir.dk/ -- regards, Jaroslaw Staniek KDE: : A world-wide network of software engineers, artists, writers, translators : and facilitators committed to Free Software development - http://kde.org KEXI: : A visual database apps builder - http://calligra.org/kexi http://twitter.com/kexi_project https://facebook.com/kexi.project Qt Certified Specialist: : http://www.linkedin.com/in/jstaniek
3.1.0 Beta of KEXI & KEXI Frameworks Released
Dear All! I am glad to announce that 3.1.0 Beta release of KEXI, KDb, KProperty and KReport is available for testing. Please find it at https://community.kde.org/Kexi/Releases#3.1.0_Beta_1. If there are no complex issues reported we would have final release on February 26. Since the 3.0.2 release KEXI and the frameworks received over 220 improvements and bug fixes. Changelog: https://community.kde.org/Kexi/Releases/3.1.0_Changes Release schedule: https://community.kde.org/Kexi/Schedules#3.1.0 -- regards, Jaroslaw Staniek KDE: : A world-wide network of software engineers, artists, writers, translators : and facilitators committed to Free Software development - http://kde.org KEXI: : A visual database apps builder - http://calligra.org/kexi http://twitter.com/kexi_project https://facebook.com/kexi.project Qt Certified Specialist: : http://www.linkedin.com/in/jstaniek
Re: 3.1.0 is out
On 29 January 2018 at 08:12, Dag <dand...@get2net.dk> wrote: > Ok, release is out so master is open for features and strings again. > > Need an announcement, I'll collect from commit log, but please, those who > has something post it here. > > @leinir could you say something about gemini? > > Big thanks. When do you plan to announce 3.1? ( https://community.kde.org/Calligra/Schedules/3.1/Release_Plan is incomplete) Just mentioning KEXI/KEXI libs 3.1.0 beta release (it's today) would be nice. I am going to mention Calligra release too in KEXI article. -- regards, Jaroslaw Staniek KDE: : A world-wide network of software engineers, artists, writers, translators : and facilitators committed to Free Software development - http://kde.org KEXI: : A visual database apps builder - http://calligra.org/kexi http://twitter.com/kexi_project https://facebook.com/kexi.project Qt Certified Specialist: : http://www.linkedin.com/in/jstaniek
Re: KEXI, KDb, KProperty, KReport 3.1 ready to translate
On Saturday, 20 January 2018, Luigi Toscano <luigi.tosc...@tiscali.it> wrote: > Jaroslaw Staniek ha scritto: >> On 19 January 2018 at 19:13, Jaroslaw Staniek <stan...@kde.org> wrote: >>> On 19 January 2018 at 19:03, Luigi Toscano <luigi.tosc...@tiscali.it> wrote: >> >>>> Are you going to release from master, or are you going to create a 3.0 branch >>>> and we should copy the translations? >>> >>> 3.1 branch will be ready for stable 3.1.x releases today. >> >> Update. All 4 repos now have 3.1 branches and 3.0.94 tags. >> This time releaseme tools worked well, translations magically found in >> extragear-libs :) >> Kudos for that. > > Were they taken from the right branch? If they were taken from the existing > stable branch, 3.0, they are probably not complete as they should be. >From stable. > > -- > 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 KEXI: : A visual database apps builder - http://calligra.org/kexi http://twitter.com/kexi_project https://facebook.com/kexi.project Qt Certified Specialist: : http://www.linkedin.com/in/jstaniek
Fwd: KEXI, KDb, KProperty, KReport 3.1 ready to translate
Hi, Week before release just wanted to say the code of the 3 framework repos (kdb, kreport, kproperty, plus KEXI) is branched in 3.1 and tagged as beta and we finally can call the frameworks ready for KDE review. Feel free to report any issues in this area. Thanks. -- Forwarded message -- From: Jaroslaw Staniek <stan...@kde.org> Date: 19 January 2018 at 23:46 Subject: Re: KEXI, KDb, KProperty, KReport 3.1 ready to translate To: Luigi Toscano <luigi.tosc...@tiscali.it> Cc: KDE i18n-doc <kde-i18n-...@kde.org>, Calligra Suite developers and users mailing list <calligra-devel@kde.org>, kexi-de...@kde.org On 19 January 2018 at 19:13, Jaroslaw Staniek <stan...@kde.org> wrote: > On 19 January 2018 at 19:03, Luigi Toscano <luigi.tosc...@tiscali.it> wrote: >> Are you going to release from master, or are you going to create a 3.0 branch >> and we should copy the translations? > > 3.1 branch will be ready for stable 3.1.x releases today. Update. All 4 repos now have 3.1 branches and 3.0.94 tags. This time releaseme tools worked well, translations magically found in extragear-libs :) Kudos for that. Tarballs uploaded, waiting for publishing and syncing. No hurry, one week left to announcement. Please report any issues. -- regards, Jaroslaw Staniek KDE: : A world-wide network of software engineers, artists, writers, translators : and facilitators committed to Free Software development - http://kde.org KEXI: : A visual database apps builder - http://calligra.org/kexi http://twitter.com/kexi_project https://facebook.com/kexi.project Qt Certified Specialist: : http://www.linkedin.com/in/jstaniek -- regards, Jaroslaw Staniek KDE: : A world-wide network of software engineers, artists, writers, translators : and facilitators committed to Free Software development - http://kde.org KEXI: : A visual database apps builder - http://calligra.org/kexi http://twitter.com/kexi_project https://facebook.com/kexi.project Qt Certified Specialist: : http://www.linkedin.com/in/jstaniek
Re: KEXI, KDb, KProperty, KReport 3.1 ready to translate
On 19 January 2018 at 19:13, Jaroslaw Staniek <stan...@kde.org> wrote: > On 19 January 2018 at 19:03, Luigi Toscano <luigi.tosc...@tiscali.it> wrote: >> Are you going to release from master, or are you going to create a 3.0 branch >> and we should copy the translations? > > 3.1 branch will be ready for stable 3.1.x releases today. Update. All 4 repos now have 3.1 branches and 3.0.94 tags. This time releaseme tools worked well, translations magically found in extragear-libs :) Kudos for that. Tarballs uploaded, waiting for publishing and syncing. No hurry, one week left to announcement. Please report any issues. -- regards, Jaroslaw Staniek KDE: : A world-wide network of software engineers, artists, writers, translators : and facilitators committed to Free Software development - http://kde.org KEXI: : A visual database apps builder - http://calligra.org/kexi http://twitter.com/kexi_project https://facebook.com/kexi.project Qt Certified Specialist: : http://www.linkedin.com/in/jstaniek
Re: KEXI, KDb, KProperty, KReport 3.1 ready to translate
On 19 January 2018 at 19:03, Luigi Toscano <luigi.tosc...@tiscali.it> wrote: > Jaroslaw Staniek ha scritto: >> Dear All, >> I'd like to declare string freeze for 4 projects: KEXI, KDb, >> KProperty, KReport version 3.1. >> >> Beta would be announced on Jan 29th. >> Upload of stable is planned for Feb 22, 2018 so there is one month for >> testing messages and translating. >> Translating of docs is not recommended, it needs major update. > > Are you going to release from master, or are you going to create a 3.0 branch > and we should copy the translations? 3.1 branch will be ready for stable 3.1.x releases today. -- regards, Jaroslaw Staniek KDE: : A world-wide network of software engineers, artists, writers, translators : and facilitators committed to Free Software development - http://kde.org KEXI: : A visual database apps builder - http://calligra.org/kexi http://twitter.com/kexi_project https://facebook.com/kexi.project Qt Certified Specialist: : http://www.linkedin.com/in/jstaniek
KEXI, KDb, KProperty, KReport 3.1 ready to translate
Dear All, I'd like to declare string freeze for 4 projects: KEXI, KDb, KProperty, KReport version 3.1. Beta would be announced on Jan 29th. Upload of stable is planned for Feb 22, 2018 so there is one month for testing messages and translating. Translating of docs is not recommended, it needs major update. Details with dates and change logs: https://community.kde.org/Kexi/Schedules#3.1.0 https://community.kde.org/Kexi/Releases#3.1.0_.28PENDING.29 -- regards, Jaroslaw Staniek KDE: : A world-wide network of software engineers, artists, writers, translators : and facilitators committed to Free Software development - http://kde.org KEXI: : A visual database apps builder - http://calligra.org/kexi http://twitter.com/kexi_project https://facebook.com/kexi.project Qt Certified Specialist: : http://www.linkedin.com/in/jstaniek
Re: Release
Sure, understood. On 6 December 2017 at 13:31, Dag <dand...@get2net.dk> wrote: > Jaroslaw Staniek skrev den 2017-12-05 11:42: > >> Nice to hear this, Dag. >> For the record, next 30 days is also estimated time for Kexi & >> Frameworks 3.1 release. >> There are Plan -> Frameworks dependencies, right? >> > Yes and no :) > If it is ready, I'll include it, if not it can wait for a later release. > > > >> On 5 December 2017 at 10:34, Dag <dand...@get2net.dk> wrote: >> >> Hi, I would like to get Plan out soonish, and it would be nice to >>> also include gemini along with words, sheets and karbon if it is >>> ready for consumption. >>> >>> I suggest January 25 for final release and a beta December 15. >>> >>> -- >>> Cheers, >>> >>> Dag >>> >> >> -- >> 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 >> > -- 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
Re: Release
Nice to hear this, Dag. For the record, next 30 days is also estimated time for Kexi & Frameworks 3.1 release. There are Plan -> Frameworks dependencies, right? On 5 December 2017 at 10:34, Dag <dand...@get2net.dk> wrote: > Hi, I would like to get Plan out soonish, and it would be nice to also > include gemini along with words, sheets and karbon if it is ready for > consumption. > > I suggest January 25 for final release and a beta December 15. > > > -- > Cheers, > > Dag > > > -- 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
Re: kproperty translations
On 17 November 2017 at 15:50, Jonathan Riddell <j...@jriddell.org> wrote: > That's the stable branch, which is on branch 3.0 which has the old Messages.sh > > https://websvn.kde.org/trunk/l10n-kf5/templates/messages/extragear-libs/ > has kpropertywidgets_qt.pot and kpropertycore_qt.pot > > Can I update Messages.sh to list the .pot file explicitly? > http://embra.edinburghlinux.co.uk/~jr/tmp/DIFF Sure, if it helps. I see this is 100% equivalent. Thanks. > > Jonathan > > > On 17 November 2017 at 14:39, Jaroslaw Staniek <stan...@kde.org> wrote: >> Hmm I see kproperty_qt.pot, which is old. No kpropertycore_qt.pot or >> kpropertywidgets_qt.pot... >> >> On 17 November 2017 at 14:59, Jonathan Riddell <j...@jriddell.org> wrote: >>> On 31 October 2017 at 16:51, Jaroslaw Staniek <stan...@kde.org> wrote: >>>> On 31 October 2017 at 17:27, Jonathan Riddell <j...@jriddell.org> wrote: >>>>> There's some fancy stuff in the translations extraction script for >>>>> kproperty >>>>> >>>>> https://cgit.kde.org/kproperty.git/tree/src/Messages.sh >>>>> >>>>> This breaks the Neon builds which try to parse those Messages.sh files >>>>> to download translations >>>>> https://build.neon.kde.org/job/xenial_unstable_calligra_kproperty_src/89/console >>>>> >>>> >>>> Hi Jonathan, >>>> I've found it less intrusive than removing git history by moving cpp >>>> files around. The review is here: https://phabricator.kde.org/D8230. >>>> >>>> I wonder how the shell scripts are parsed, what are the assumptions. >>>> In the neon link releaseme only shows me internal backtrace. >>>> Maybe we can add metadata that you can support instead of parsing scripts. >>> >>> releaseme needs the name of the .pot files spelled out, can I change >>> it to make it explicitly call them? >>> >>> http://embra.edinburghlinux.co.uk/~jr/tmp/DIFF >>> >>> >>>>> And I'm not sure scripty is happy with it either, there's no >>>>> kpropertycore_qt.pot or kpropertywidgets_qt.pot >>>>> >>>>> https://websvn.kde.org/branches/stable/l10n-kf5/templates/messages/extragear-libs/ >>>> >>>> IIRC there are no translations because the lib has not been approved >>>> via kdereview yet. >>> >>> I'm talking nonsense the files are there. >>> >>> Jonathan >> >> >> >> -- >> 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 -- 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
Re: kproperty translations
Hmm I see kproperty_qt.pot, which is old. No kpropertycore_qt.pot or kpropertywidgets_qt.pot... On 17 November 2017 at 14:59, Jonathan Riddell <j...@jriddell.org> wrote: > On 31 October 2017 at 16:51, Jaroslaw Staniek <stan...@kde.org> wrote: >> On 31 October 2017 at 17:27, Jonathan Riddell <j...@jriddell.org> wrote: >>> There's some fancy stuff in the translations extraction script for kproperty >>> >>> https://cgit.kde.org/kproperty.git/tree/src/Messages.sh >>> >>> This breaks the Neon builds which try to parse those Messages.sh files >>> to download translations >>> https://build.neon.kde.org/job/xenial_unstable_calligra_kproperty_src/89/console >>> >> >> Hi Jonathan, >> I've found it less intrusive than removing git history by moving cpp >> files around. The review is here: https://phabricator.kde.org/D8230. >> >> I wonder how the shell scripts are parsed, what are the assumptions. >> In the neon link releaseme only shows me internal backtrace. >> Maybe we can add metadata that you can support instead of parsing scripts. > > releaseme needs the name of the .pot files spelled out, can I change > it to make it explicitly call them? > > http://embra.edinburghlinux.co.uk/~jr/tmp/DIFF > > >>> And I'm not sure scripty is happy with it either, there's no >>> kpropertycore_qt.pot or kpropertywidgets_qt.pot >>> >>> https://websvn.kde.org/branches/stable/l10n-kf5/templates/messages/extragear-libs/ >> >> IIRC there are no translations because the lib has not been approved >> via kdereview yet. > > I'm talking nonsense the files are there. > > Jonathan -- 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
Re: kproperty translations
On 31 October 2017 at 17:27, Jonathan Riddell <j...@jriddell.org> wrote: > There's some fancy stuff in the translations extraction script for kproperty > > https://cgit.kde.org/kproperty.git/tree/src/Messages.sh > > This breaks the Neon builds which try to parse those Messages.sh files > to download translations > https://build.neon.kde.org/job/xenial_unstable_calligra_kproperty_src/89/console > Hi Jonathan, I've found it less intrusive than removing git history by moving cpp files around. The review is here: https://phabricator.kde.org/D8230. I wonder how the shell scripts are parsed, what are the assumptions. In the neon link releaseme only shows me internal backtrace. Maybe we can add metadata that you can support instead of parsing scripts. > And I'm not sure scripty is happy with it either, there's no > kpropertycore_qt.pot or kpropertywidgets_qt.pot > > https://websvn.kde.org/branches/stable/l10n-kf5/templates/messages/extragear-libs/ IIRC there are no translations because the lib has not been approved via kdereview yet. -- 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
Re: kexi stable translations
On 31 August 2017 at 14:58, Jonathan Riddell <j...@jriddell.org> wrote: > kexi has no stable translations. I think it should be set to use the > 3.0 branch? Is that right? Jonathan, Today yes, it could. Or: if we could we'd have this done already. But dependencies we develop (kdb, kproperty, kreport) are not marked (in KDE terms) as stable they are in the kdereview process (1% left or so). So KDE policy blocked us if I remember correctly from having translation infra working for us. Other than that, the 3.0.x line is done, 3.0.2 was the last release. Next stable is the 3.1 planned for Sep/Oct. So I don't know if it's worth the effort to enable translations for 3.0 without releasing them. Feel free to provide your advice and thanks for this contact. -- 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
Kexi 3.0.2 and frameworks released
Dear All, We're pleased to announce the release of Kexi 3.0.2 (a visual database apps builder) and associated frameworks. This time users can find over 50 improvements. Downloads and change logs: https://community.kde.org/Kexi/Releases#3.0.2 Reporting bug or wishes: https://community.kde.org/Kexi/File_a_bug_or_wish About Kexi frameworks: For the benefit and convenience of fellow software engineers, the same release includes frameworks that we develop within the Kexi Project (that is KDb, KProperty, KReport). Please note that binary compatibility (long support) for the frameworks will be offered since 3.1.0. Frameworks wikis: https://community.kde.org/KDb https://community.kde.org/KProperty https://community.kde.org/KReport -- 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
Fwd: [sysadmin/repo-metadata] projects: Move "Kexi libs" to extragear-libs, track stable i18n
;, "stable_kf5": "none",
"trunk_kf5": "master"}
\ No newline at end of file
diff --git a/projects/kdereview/kproperty/i18n.json
b/projects/kdereview/kproperty/i18n.json
deleted file mode 100644
index 16d965e..000
--- a/projects/kdereview/kproperty/i18n.json
+++ /dev/null
@@ -1 +0,0 @@
-{"trunk": "none", "stable": "none", "stable_kf5": "none",
"trunk_kf5": "master"}
\ No newline at end of file
diff --git a/projects/kdereview/kreport/i18n.json
b/projects/kdereview/kreport/i18n.json
deleted file mode 100644
index 16d965e..000
--- a/projects/kdereview/kreport/i18n.json
+++ /dev/null
@@ -1 +0,0 @@
-{"trunk": "none", "stable": "none", "stable_kf5": "none",
"trunk_kf5": "master"}
\ No newline at end of file
--
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
Re: Kexi build failure
On 11 July 2017 at 14:41, Rik Mills <rikmi...@kubuntu.org> wrote: > Latest commit from last night did the trick :) > > http://kci.pangea.pub/job/artful_unstable_kexi/60/ > > Thank you. Sorry for the delay, but our CI got tied up in rebuilds for > frameworks 5.36. > Great, thanks. BTW is there any URL and installation recipe that we can publish at https://community.kde.org/Kexi/Releasesto point to Kexi on Kubuntu? People are asking about that just like for Calligra (rarely updated https://userbase.kde.org/Calligra/Download page). > Regards > > Rik > > On 10/07/17 23:04, Jaroslaw Staniek wrote: > > > > > > On 10 July 2017 at 23:39, Rik Mills <rikmi...@kubuntu.org > > <mailto:rikmi...@kubuntu.org>> wrote: > > > > I see on IRC > > > > [22:12] GIT_SILENT Fix possible build error on some Qt > > versions > > [22:12] CCMAIL:rikmi...@kubuntu.org > > <mailto:rikmi...@kubuntu.org> > > [22:12] > > https://commits.kde.org/kexi/b2c0cdb8708b4dc98b7e05b36e8218 > 575dd5f01a <https://commits.kde.org/kexi/b2c0cdb8708b4dc98b7e05b36e8218 > 575dd5f01a> > > > > but no such commit in git > > > > "Bad commit reference: b2c0cdb8708b4dc98b7e05b36e8218575dd5f01a" > > > > > > Please try again: > > https://commits.kde.org/kexi/d4dbcccf2221802faf9640c8a1b7ce7dc253ff8f > > > > > > > > > > from the link. > > > > On 10/07/17 22:12, Jaroslaw Staniek wrote: > > > > > > > > > On 10 July 2017 at 23:00, Rik Mills < > > > > > > rikmi...@kubuntu.org <mailto:rikmi...@kubuntu.org> > > <mailto:rikmi...@kubuntu.org <mailto:rikmi...@kubuntu.org>>> wrote: > > > > > > Hi. > > > > > > After commit: > > > https://cgit.kde.org/kexi.git/commit/?id= > 12d1adf10466a34304bdd229eb892696480b2558 > > <https://cgit.kde.org/kexi.git/commit/?id= > 12d1adf10466a34304bdd229eb892696480b2558> > > > <https://cgit.kde.org/kexi.git/commit/?id= > 12d1adf10466a34304bdd229eb892696480b2558 > > <https://cgit.kde.org/kexi.git/commit/?id= > 12d1adf10466a34304bdd229eb892696480b2558>> > > > > > > The kexi master branch fails to build on Kubuntu CI with the > errors in > > > the following log > > > > > > https://launchpadlibrarian.net/328135944/buildlog_ubuntu- > artful-amd64.kexi_1%3A3.0.1+p17.10+git20170710.1658-0_BUILDING.txt.gz > > <https://launchpadlibrarian.net/328135944/buildlog_ubuntu- > artful-amd64.kexi_1%3A3.0.1+p17.10+git20170710.1658-0_BUILDING.txt.gz> > > > <https://launchpadlibrarian.net/328135944/buildlog_ubuntu- > artful-amd64.kexi_1%3A3.0.1+p17.10+git20170710.1658-0_BUILDING.txt.gz > > <https://launchpadlibrarian.net/328135944/buildlog_ubuntu- > artful-amd64.kexi_1%3A3.0.1+p17.10+git20170710.1658-0_BUILDING.txt.gz>> > > > > > > Seems to be an issue which occurs with the Qt 5.7.1 that we > still have > > > in ubuntu artful for a short while, but not with Qt 5.9.1 when > I did a > > > test build with that instead. Also explains why I did not see > this > > > failure on Neon CI or build.kde.org <http://build.kde.org> > > <http://build.kde.org> > > > > > > > > > Possible fix pushed, please test, thanks Rik. > > > > > > > > > -- > > > 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 > > <http://www.linkedin.com/in/jstaniek> > > > > > > > > > > -- > > 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 > > -- 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
Re: Kexi build failure
On 10 July 2017 at 23:39, Rik Mills <rikmi...@kubuntu.org> wrote: > I see on IRC > > [22:12] GIT_SILENT Fix possible build error on some Qt > versions > [22:12] CCMAIL:rikmi...@kubuntu.org > [22:12] > https://commits.kde.org/kexi/b2c0cdb8708b4dc98b7e05b36e8218575dd5f01a > > but no such commit in git > > "Bad commit reference: b2c0cdb8708b4dc98b7e05b36e8218575dd5f01a" > Please try again: https://commits.kde.org/kexi/d4dbcccf2221802faf9640c8a1b7ce7dc253ff8f > > from the link. > > On 10/07/17 22:12, Jaroslaw Staniek wrote: > > > > > > On 10 July 2017 at 23:00, Rik Mills < > > > > rikmi...@kubuntu.org <mailto:rikmi...@kubuntu.org>> wrote: > > > > Hi. > > > > After commit: > > https://cgit.kde.org/kexi.git/commit/?id= > 12d1adf10466a34304bdd229eb892696480b2558 > > <https://cgit.kde.org/kexi.git/commit/?id= > 12d1adf10466a34304bdd229eb892696480b2558> > > > > The kexi master branch fails to build on Kubuntu CI with the errors > in > > the following log > > > > https://launchpadlibrarian.net/328135944/buildlog_ubuntu- > artful-amd64.kexi_1%3A3.0.1+p17.10+git20170710.1658-0_BUILDING.txt.gz > > <https://launchpadlibrarian.net/328135944/buildlog_ubuntu- > artful-amd64.kexi_1%3A3.0.1+p17.10+git20170710.1658-0_BUILDING.txt.gz> > > > > Seems to be an issue which occurs with the Qt 5.7.1 that we still > have > > in ubuntu artful for a short while, but not with Qt 5.9.1 when I did > a > > test build with that instead. Also explains why I did not see this > > failure on Neon CI or build.kde.org <http://build.kde.org> > > > > > > Possible fix pushed, please test, thanks Rik. > > > > > > -- > > 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 > > -- 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
Re: Kexi build failure
On 10 July 2017 at 23:00, Rik Mills < rikmi...@kubuntu.org> wrote: > Hi. > > After commit: > https://cgit.kde.org/kexi.git/commit/?id=12d1adf10466a34304bdd229eb8926 > 96480b2558 > > The kexi master branch fails to build on Kubuntu CI with the errors in > the following log > > https://launchpadlibrarian.net/328135944/buildlog_ubuntu- > artful-amd64.kexi_1%3A3.0.1+p17.10+git20170710.1658-0_BUILDING.txt.gz > > Seems to be an issue which occurs with the Qt 5.7.1 that we still have > in ubuntu artful for a short while, but not with Qt 5.9.1 when I did a > test build with that instead. Also explains why I did not see this > failure on Neon CI or build.kde.org > > Possible fix pushed, please test, thanks Rik. -- 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
Volunteers needed for making flatpak scripts
Hello, Volunteers are needed for making flatpak scripts. This is alternative for AppImages snapshots on Linux. Getting a flatpak-builder json manifest into the flatpak-kde-applications repository will get us nightly builds. https://cgit.kde.org/flatpak-kde-applications.git/tree/ PS: the same call for help regarding Calligra flatpak. -- 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
Re: broken download link
Hi Igor, The 2.x series are not in development anymore by the Calligra project. The download link even if it's 2 years old shall still exist, no idea why it disappeared (and all mirrors just follow) so it's good idea to ask by filling a bug at http://bugs.kde.org or asking KDE at forum.kde.org. Maybe that was a cleanup due to limited resources. On 19 May 2017 at 08:40, Игорь Фоменко <fomenk...@gmail.com> wrote: > Hi > I can`t download your suit because link > https://download.kde.org/stable/calligra-2.9.6/calligragemini_x64_2.9.6.0.msi.mirrorlist > is not working > > -- > Best regards > Igor Fomenko -- 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
Re: no stable translations
On 24 April 2017 at 16:57, Jonathan Riddell <j...@jriddell.org> wrote: > how about moving them out of kdereview into calligra? They've been in > kdereview for over 6 months > I am not sure what's easier - to change downstream or change upstream and undo for next release. They're in kdereview is for the code; translations are minor topic compared to code. Time needed for the process is adequate to the projects' workforce. We're at 90% or so, stay tuned... > > Jonathan > > > On 24 April 2017 at 14:47, Jaroslaw Staniek <stan...@kde.org> wrote: > > > > > > On 24 April 2017 at 15:26, Jonathan Riddell <j...@jriddell.org> wrote: > >> > >> There's no stable translations for kexi or calligra in the stable > branches > >> > >> > >> https://websvn.kde.org/branches/stable/l10n-kf5/ > templates/messages/calligra/ > >> > >> > >> Is this deliberate or an oversight? It messes up building packages in > >> neon > > > > > > For Kexi, its dependencies > > > > (kdb, kreport, kproperty) have no stable translations (within the KDE > > infra). The libs were still kept in playground during the 3.0 series; > > kdereview is in progress. Once it's done stable release 3.1 would make > the > > fix. > > > > -- > > 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 > -- 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
Re: no stable translations
On 24 April 2017 at 15:26, Jonathan Riddell <j...@jriddell.org> wrote: > There's no stable translations for kexi or calligra in the stable branches > > https://websvn.kde.org/branches/stable/l10n-kf5/ > templates/messages/calligra/ > > > Is this deliberate or an oversight? It messes up building packages in neon > For Kexi, its dependencies (kdb, kreport, kproperty) have no stable translations (within the KDE infra). The libs were still kept in playground during the 3.0 series; kdereview is in progress. Once it's done stable release 3.1 would make the fix. -- 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
Re: 3.0.1 RC1 of Kexi/KDb/KProperty/KReport released
On 16 March 2017 at 23:01, Jonathan Riddell <j...@jriddell.org> wrote: > kproperty no longer has translations > 3.0.0 had kproperty-3.0.0/po/pt/kproperty_qt.po files, these are not > in the 3.0.1 tar > > Yes that's because the releaseme tool failed to give them to me, neither hacks that I usually use. As you can see I managed to do some tricks for other libs. and no idea what was the difference. Regular translations would come after the kdereview process is finished for the libs (that is: 3.1). If nobody tracks down the issues for the 3.0.x, 3.0.2 won't have translations or we can just ship older translations. Everything is (poorly) reported to sysadmins and the authors of releaseme. Jonathan > > > On 13 March 2017 at 12:25, Jaroslaw Staniek <stan...@kde.org> wrote: > > Hi, > > 3.0.1 uploaded: > > https://community.kde.org/Kexi/Releases#3.0.1_Downloads > > > > They contain minor changes compared to RC1. kexi and kdb packages have po > > folders with that we have so far, this is why their file versions are > > 3.0.1.1, not 3.0.1 (this is to address bug > > https://bugs.kde.org/show_bug.cgi?id=377488). Translations are not yet > fully > > set up in the KDE infra because the libraries are under a kdereview > process. > > > > The packages will be announced today unless there's a critical blocker. > > > > > > On 6 March 2017 at 00:36, Jaroslaw Staniek <stan...@kde.org> wrote: > >> > >> Dear All, > >> RC1 of 3.0.1 Kexi/KDb/KProperty/KReport is available at > >> https://share.kde.org/index.php/s/Qqw6vGAS8TVox8n > >> Please test, if there are no issues reported we would release in a week. > >> > >> Order of building as always: KDb, KProperty, KReport, Kexi. > >> > >> Note: Kexi 3.0.1 depends on the libraries in version 3.0.x. Libraries in > >> version 3.1 are incompatible. > >> > >> Changelog: https://community.kde.org/Kexi/Releases#3.0.1_Changes > >> > >> Release schedule: https://community.kde.org/Kexi/Schedules#3.0.1 > >> > >> -- > >> 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 > > > > > > > > > > -- > > 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 > -- 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
Re: Kexi 3.0.1 and frameworks released
On 14 March 2017 at 11:09, Jaroslaw Staniek <stan...@kde.org> wrote: > > Thanks Treeve, sysadmins have been notified. > Copied, thanks: https://download.kde.org/stable/kreport/src/kreport-3.0.1.tar.xz.sig.mirrorlist > > > On 14 March 2017 at 08:53, Treeve Jelbert <tre...@scarlet.be> wrote: > >> On Mon, 13 Mar 2017 23:01:59 +0100, Jaroslaw Staniek wrote: >> >>> Dear All, >>> >>> We're pleased to announce the release of Kexi 3.0.1 (a visual database >>> apps >>> builder) and associated frameworks. >>> >>> Downloads & change logs: >>> https://community.kde.org/Kexi/Releases#3.0.1 >>> >> >> kreport missing .sig file at >> https://download.kde.org/stable/kreport/src >> >> >> >> >>> Reporting bug or wishes: >>> https://community.kde.org/Kexi/File_a_bug_or_wish >>> >>> About Kexi frameworks: For the benefit and convenience of fellow software >>> engineers, the same release includes frameworks that we develop within >>> the >>> Kexi Project (that is KDb, KProperty, KReport). Please note that binary >>> compatibility (long support) for the frameworks will be offered since >>> 3.1.0. >>> >>> Frameworks wiki: >>> https://community.kde.org/KDb >>> https://community.kde.org/KProperty >>> https://community.kde.org/KReport >>> >>> >> > > > -- > 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 > -- 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
Re: Kexi 3.0.1 and frameworks released
Thanks Treeve, sysadmins have been notified. On 14 March 2017 at 08:53, Treeve Jelbert <tre...@scarlet.be> wrote: > On Mon, 13 Mar 2017 23:01:59 +0100, Jaroslaw Staniek wrote: > >> Dear All, >> >> We're pleased to announce the release of Kexi 3.0.1 (a visual database >> apps >> builder) and associated frameworks. >> >> Downloads & change logs: >> https://community.kde.org/Kexi/Releases#3.0.1 >> > > kreport missing .sig file at > https://download.kde.org/stable/kreport/src > > > > >> Reporting bug or wishes: >> https://community.kde.org/Kexi/File_a_bug_or_wish >> >> About Kexi frameworks: For the benefit and convenience of fellow software >> engineers, the same release includes frameworks that we develop within the >> Kexi Project (that is KDb, KProperty, KReport). Please note that binary >> compatibility (long support) for the frameworks will be offered since >> 3.1.0. >> >> Frameworks wiki: >> https://community.kde.org/KDb >> https://community.kde.org/KProperty >> https://community.kde.org/KReport >> >> > -- 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
Kexi 3.0.1 and frameworks released
Dear All, We're pleased to announce the release of Kexi 3.0.1 (a visual database apps builder) and associated frameworks. Downloads & change logs: https://community.kde.org/Kexi/Releases#3.0.1 Reporting bug or wishes: https://community.kde.org/Kexi/File_a_bug_or_wish About Kexi frameworks: For the benefit and convenience of fellow software engineers, the same release includes frameworks that we develop within the Kexi Project (that is KDb, KProperty, KReport). Please note that binary compatibility (long support) for the frameworks will be offered since 3.1.0. Frameworks wiki: https://community.kde.org/KDb https://community.kde.org/KProperty https://community.kde.org/KReport -- 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
Re: 3.0.1 RC1 of Kexi/KDb/KProperty/KReport released
Hi, 3.0.1 uploaded: https://community.kde.org/Kexi/Releases#3.0.1_Downloads They contain minor changes compared to RC1. kexi and kdb packages have po folders with that we have so far, this is why their file versions are 3.0.1.1, not 3.0.1 (this is to address bug https://bugs.kde.org/show_bug.cgi?id=377488). Translations are not yet fully set up in the KDE infra because the libraries are under a kdereview process. The packages will be announced today unless there's a critical blocker. On 6 March 2017 at 00:36, Jaroslaw Staniek <stan...@kde.org> wrote: > Dear All, > RC1 of 3.0.1 Kexi/KDb/KProperty/KReport is available at > https://share.kde.org/index.php/s/Qqw6vGAS8TVox8n > Please test, if there are no issues reported we would release in a week. > > Order of building as always: KDb, KProperty, KReport, Kexi. > > Note: Kexi 3.0.1 depends on the libraries in version 3.0.x. Libraries in > version 3.1 are incompatible. > > Changelog: https://community.kde.org/Kexi/Releases#3.0.1_Changes > > Release schedule: https://community.kde.org/Kexi/Schedules#3.0.1 > > -- > 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 > -- 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
3.0.1 RC1 of Kexi/KDb/KProperty/KReport released
Dear All, RC1 of 3.0.1 Kexi/KDb/KProperty/KReport is available at https://share.kde.org/index.php/s/Qqw6vGAS8TVox8n Please test, if there are no issues reported we would release in a week. Order of building as always: KDb, KProperty, KReport, Kexi. Note: Kexi 3.0.1 depends on the libraries in version 3.0.x. Libraries in version 3.1 are incompatible. Changelog: https://community.kde.org/Kexi/Releases#3.0.1_Changes Release schedule: https://community.kde.org/Kexi/Schedules#3.0.1 -- 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
Re: isn't it time for...
Thanks! Added a small note about Kexi to make it clear and fixed the Support button. Congratulations everyone involved! According to https://community.kde.org/Calligra/Schedules/3.0/Porting_Notes the port took about 2 years... On 15 January 2017 at 15:08, Camilla Boemann <c...@boemann.dk> wrote: > Done > > -Original Message- > From: calligra-devel [mailto:calligra-devel-boun...@kde.org] On Behalf Of > Boudewijn Rempt > Sent: 14. januar 2017 20:29 > To: calligra-devel@kde.org > Subject: isn't it time for... > > A release announcement? > > -- > Boudewijn Rempt | http://www.krita.org, http://www.valdyas.org > > -- 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
Re: Version stuff in CMakeLists.txt
On 4 January 2017 at 11:36, Boudewijn Rempt <b...@valdyas.org> wrote: > On Wed, 4 Jan 2017, Jaroslaw Staniek wrote: > > > But I can't spot the calligra/3.0 branch which shall be set to 3.0.0 > > version... > > It was decided not to use release branches, but release from master. > I see master is set at 3.0.1 now. I wonder where's a place for BIC changes in calligra.git and new features, e.g. for 3.1? > -- > Boudewijn Rempt | http://www.krita.org, http://www.valdyas.org > -- 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
Re: 3.0.0.1 tarball + signature
On 5 January 2017 at 12:25, Camilla Boemann <c...@boemann.dk> wrote: > Sure but I did say in my draft that we are porting and that it sets a > bright new future – but really for the average user it doesn’t matter much > what kind of tools we use – it’s what it means for the user that is > important > Yes, I think the above is sufficient. Our audience are contributors so it's not nonimportant IMHO but deserves separate section just like we always do :) Thanks. > > *From:* calligra-devel [mailto:calligra-devel-boun...@kde.org] *On Behalf > Of *Jaroslaw Staniek > *Sent:* 5. januar 2017 11:45 > *To:* Calligra Suite developers and users mailing list < > calligra-devel@kde.org> > *Subject:* Re: 3.0.0.1 tarball + signature > > > > > > > > On 5 January 2017 at 11:32, Boudewijn Rempt <b...@valdyas.org> wrote: > > On Thu, 5 Jan 2017, Jaroslaw Staniek wrote: > > > On 5 January 2017 at 11:05, Boudewijn Rempt <b...@valdyas.org> wrote: > > > > > On Thu, 5 Jan 2017, Jaroslaw Staniek wrote: > > > > > > > IMHO If it's not marked as a big thing, the media and users will > > > > definitely mark this as not important and move over. Inkscape just > made a > > > > release that highlights a port to GTK+3 as an important news. > > > > > > Um... The version inkscape just released isn't the gtk3 port, it's > still > > > gtk2 based. > > > > > > I referred to > > https://inkscape.org/en/news/2017/01/04/inkscape-version-092-released/ > > and it > > > > marks C++ upgrade and Gtk3 port as important. > > > > > > No: it says "(Future infrastructure changes include switching from bzr to > git, shifting from Gtk2 to Gtk3, and moving to the C++11 standard.)" I.e., > that's what they're going to do. > > > > Sorry, just noticed this, hard grammar to me; regardless, they found it > important to notify users what they do apart of adding features and more > importantly why :) > > > > > > > -- > > 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 > -- 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
Re: 3.0.0.1 tarball + signature
On 5 January 2017 at 11:32, Boudewijn Rempt <b...@valdyas.org> wrote: > On Thu, 5 Jan 2017, Jaroslaw Staniek wrote: > > > On 5 January 2017 at 11:05, Boudewijn Rempt <b...@valdyas.org> wrote: > > > > > On Thu, 5 Jan 2017, Jaroslaw Staniek wrote: > > > > > > > IMHO If it's not marked as a big thing, the media and users will > > > > definitely mark this as not important and move over. Inkscape just > made a > > > > release that highlights a port to GTK+3 as an important news. > > > > > > Um... The version inkscape just released isn't the gtk3 port, it's > still > > > gtk2 based. > > > > > > I referred to > > https://inkscape.org/en/news/2017/01/04/inkscape-version-092-released/ > > and it > > > > marks C++ upgrade and Gtk3 port as important. > > > > > > No: it says "(Future infrastructure changes include switching from bzr to > git, shifting from Gtk2 to Gtk3, and moving to the C++11 standard.)" I.e., > that's what they're going to do. > Sorry, just noticed this, hard grammar to me; regardless, they found it important to notify users what they do apart of adding features and more importantly why :) -- 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
Re: Version stuff in CMakeLists.txt
On 5 January 2017 at 11:12, Dag <dand...@get2net.dk> wrote: > Jaroslaw Staniek skrev den 2017-01-05 10:50: > >> On 5 January 2017 at 08:59, Dag <dand...@get2net.dk> wrote: >> >> Had a closer look at this, and there is some cmake logic when >>> generating calligraversion.h: >>> Any 3.0.x unstable (alpha/beta/rc) will get version 2.99.x. (3.1.x >>> will be 3.0.x, etc) >>> Afaics this scheme only works when a minor version is increased, e.g >>> 3.0.x -> 3.1.0. >>> Is this a disaster? Probably not. If you add a conditional compile >>> e.g in 3.0.1 you cannot test in an unstable release, but that would >>> not be often, I think. >>> >>> Alternatives: >>> 1) Add a unstable release number as proposed by Rene. >>> >>> 2) Drop the special unstable numbers (89, 90..) and use the release >>> number as a sequential number. >>> E.g: We released stable 3.0.0, so now the unstable will get 3.0.1 >>> (string could be 3.0.1 Alpha) and when we make a new release it >>> would be 3.0.2. >>> This will give unique and increasing version numbers, with the >>> drawback that you can not see from version alone if it is unstable >>> or stable, but we can use version string for that. >>> >>> Opinions? >>> >> >> IIRC we release no alphas. Even when we had that, we release no alphas >> the patch version - for x.y.z (z>0). >> x.(y-1).89 is thus compatible with the sequence, it comes after all >> x.(y-1).* stable and before the next stable x.y.z. >> > Hmmm, do you mean we only release unstable when minor version is updated, > in which case this will (almost) work? > After 2.9.11 our 3.0.0 beta was 2.9.8x or so (regardless of the fact if it was physically released). All version are in sequence as in semantic versioning. As you see minor version was not updated, it was still 9. It turned 0 since 3.0.0. https://community.kde.org/Calligra/Schedules/2.9/Release_Plan > I think we still have the problem that the version in git will get a lower > version than the last version released, but as said above we could live > with that. > > >> Between 3.0.0 and 3.0.1 there's no extra number needed. >> >> What we had with the x.y.z.v was special I think. (?) >> > Yes, forget that. > >> >> >> >> Dag skrev den 2017-01-04 10:45: >>> >>> I can't figure out how this is meant to be used. >>>> >>>> We have now released 3.0.0.1. Next should probably be 3.0.1. >>>> So I gather current should be an alpha: >>>> Major: 3 >>>> Minor: 0 >>>> Release: 89 >>>> >>>> But then we would go backwards to Release: 1 when releasing, >>>> and after that we go to Release: 89 again and we can't see >>>> what 3.0.89 actually means as it will crop up for every new 3.0 >>>> release. >>>> >>>> Is it just me being confused, or... >>>> Anybody? >>>> >>> >> -- >> 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 [1] >> >> Links: >> -- >> [1] http://www.linkedin.com/in/jstaniek >> > -- 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
Re: 3.0.0.1 tarball + signature
On 5 January 2017 at 10:03, Dag <dand...@get2net.dk> wrote: > Camilla Boemann skrev den 2017-01-03 12:59: > >> I have prepared a release announcement, but it doesn't say much so maybe >> someone has suggestions as to what we should highlight? >> > Since it is mainly a port it isn't that much to highlight, but what *is* > in and what is *not in* is the main thing imo. > > IMHO If it's not marked as a big thing, the media and users will definitely mark this as not important and move over. Inkscape just made a release that highlights a port to GTK+3 as an important news. For me this release is more of a "OpenOffice->LibreOffice fork" scale. If our patch is smaller it's "only" because we have no chaos with German comments as the original code base :) It was a huge development and org work to perform the port of Calligra. (In case of Kexi which is not part of these releases, more than a port is in the box, there's a lot of polishing and "new" db engine) I would risk by keeping people in false perception that ports happen by just running a magical script. If we look at the Plan alone, it depends on Kexi frameworks that were in development consuming 8 years or so. (We're still making them KF5-like for the KDE review in 3.1 version). The readers may be also interested in what a "being a Qt5 app" means (new tech, more opening to further mobile ports, and after all, a must to be alive since Qt4 isn't developed anymore). When the announcement is made I'd add a part for Kexi explaining it has an independent release schedule. > If you want to include some bug fixes also, I have these: > > Plan: > Fix crash on startup > Bug: 371930 > > Avoid crash in special cases (eg. when New is pressed) > BUG: 346976 > > Fix crash on close > BUG: 373527 > > > Fix printing treeviews > BUG:302916 > > Add export report definition, fix bug in report import > BUG: 325263 > > Usability: Never block save, add Milestone option to task dialog > BUG:322661 > BUG:352226 > > Implement sort by wbs to sort by wbs structure and not by the wbs code > string > BUG:308857 > > Re-instate handling richtext (description) in reports > CCBUG:329430 > > Fix potential crash in resource request debug statement > BUG:358674 > > > > -- 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
Re: Version stuff in CMakeLists.txt
On 5 January 2017 at 08:59, Dag <dand...@get2net.dk> wrote: > Had a closer look at this, and there is some cmake logic when generating > calligraversion.h: > Any 3.0.x unstable (alpha/beta/rc) will get version 2.99.x. (3.1.x will be > 3.0.x, etc) > Afaics this scheme only works when a minor version is increased, e.g 3.0.x > -> 3.1.0. > Is this a disaster? Probably not. If you add a conditional compile e.g in > 3.0.1 you cannot test in an unstable release, but that would not be often, > I think. > > Alternatives: > 1) Add a unstable release number as proposed by Rene. > > 2) Drop the special unstable numbers (89, 90..) and use the release number > as a sequential number. > E.g: We released stable 3.0.0, so now the unstable will get 3.0.1 (string > could be 3.0.1 Alpha) and when we make a new release it would be 3.0.2. > This will give unique and increasing version numbers, with the drawback > that you can not see from version alone if it is unstable or stable, but we > can use version string for that. > > Opinions? > > IIRC we release no alphas. Even when we had that, we release no alphas the patch version - for x.y.z (z>0). x.(y-1).89 is thus compatible with the sequence, it comes after all x.(y-1).* stable and before the next stable x.y.z. Between 3.0.0 and 3.0.1 there's no extra number needed. What we had with the x.y.z.v was special I think. (?) > > Dag skrev den 2017-01-04 10:45: > >> I can't figure out how this is meant to be used. >> >> We have now released 3.0.0.1. Next should probably be 3.0.1. >> So I gather current should be an alpha: >> Major: 3 >> Minor: 0 >> Release: 89 >> >> But then we would go backwards to Release: 1 when releasing, >> and after that we go to Release: 89 again and we can't see >> what 3.0.89 actually means as it will crop up for every new 3.0 release. >> >> Is it just me being confused, or... >> Anybody? >> > -- 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
Re: Version stuff in CMakeLists.txt
On 4 January 2017 at 11:09, René J.V. Bertin <rjvber...@gmail.com> wrote: > On Wednesday January 4 2017 10:45:39 Dag wrote: > > >We have now released 3.0.0.1. Next should probably be 3.0.1. > >So I gather current should be an alpha: > >Major: 3 > >Minor: 0 > >Release: 89 > Hi All, Maybe the logic (where I contributed) in CMakeLists.txt that counts the versions/soversions/etc. assumes a x.y.z scheme only and not x.y.z.v. I don't think it's a bad thing. 3.0.0.1 is only a CALLIGRA_VERSION_STRING. Numerically our version is 3.0.0. So next stable would be 3.0.1 and "alpha 3.1.0 unstable" is 3.0.89 - it's probably the time to update CMakeLists.txt in master to it. But I can't spot the calligra/3.0 branch which shall be set to 3.0.0 version... > > > >But then we would go backwards to Release: 1 when releasing, > >and after that we go to Release: 89 again and we can't see > >what 3.0.89 actually means as it will crop up for every new 3.0 release. > >Is it just me being confused, or... > > No, that's something that's been confusing me in other projects too. > > FWIW, KDevelop 5.1 will be released soon, up from 5.0.3 . Their current > version (in CMakeLists.txt and the git tag) is 5.0.80. Who knows, maybe > that'll become 5.0.99 for the gold release candidate whatever version. > > So what would be wrong with 3.0.0.89? Conveys clearly enough the message > that it's not just a patch release, and that it's closer to 3.0.1 than to > 3.0.0 . > > R. > -- 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
Re: calligra tarball contains kexi translations also contained in the kexi tarball (idem for krita)
On 26 December 2016 at 20:04, René J.V. Bertin <rjvber...@gmail.com> wrote: > Hi, > > The venom is all in the title: the calligra and kexi tarballs both contain > translations for kexi. > The same applies to krita. > > This is very annoying for packaging, unless I missed a CMake switch in > Calligra's cmake file to filter out unwanted translations per product? > > OK, heard about that already from somewhere but how is this possible since if there's no trace of Kexi code in calligra.git since 3.0.0? Is this just about file name clashes? PS: I recommend adding kexi-de...@kde.org to these threads. -- 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
Re: Kexi/Mac
On 26 December 2016 at 21:34, René J.V. Bertin <rjvber...@gmail.com> wrote: > On Monday December 26 2016 20:18:39 Jaroslaw Staniek wrote: > >These are great news, René! > >Maybe I am repeating myself but the enforcement of the widget style and > >icon theme is dictated by a specific approach: maintainer of a style is > >free to add the style/theme and even change the default or add an > >alternative. > > I didn't deactivate anything to force a particular applications style, so > I'm not sure which enforcement of widget style you're hinting at. For > Breeze I just deactivate the check in the toplevel CMake file because the > packaging system ensures that the icon theme is present. > > Do note that all this probably won't work with an unpatched Qt where > QStandardPaths returns very different locations and icon themes can only be > installed as an embedded resource. For application styles it's even more > difficult: if you want the full theming including fonts and colour palettes > you need to provide your own platform theme plugin (basically, the KDE > platform theme plugin from plasma-integration, or rather the Mac-specific > version from my osx-integration "scratch" repo). > > >Unless these contributions are here I am a bit afraid we're risking > >inconsistencies between platforms and inferior experience on Mac (no docs, > >incomplete icon theme or styles). > > You must have misunderstood something: the experience *is* inferior on Mac > ATM, with a stock Qt and without jumping through a certain number of hoops. > It would be much easier and in line with consensus among KDE devs to ensure > that Kexi works with the Macintosh native theme. Using Breeze icons with > that isn't an issue of course; there are even instructions on creating the > required embeddable resource (by Kate's author, Christoph Cullmann). > > Those instructions might even be useful to figure out how to create the > icons.rcc resource during Kexi's build (and then to be installed as a > Kexi-specific resource), I think that would be a more elegant and cleaner > approach than depending on the resource's presence. > I am sure current Kexi master may be inferior on Mac to what you see on Linux or Windows because it was not tested there at all. Nice to hear new from Wojtek too... One thing, the 3.0 branch for 3.0.x series is explicitly unsupported for Mac - we're not changing it anymore for anything but more critical bugfixes. The KDE's breeze-icons.rcc is built by default now from breeze-icons.git (my patch was accepted). Kexi's kexi_breeze.rcc is built in Kexi already the way you describe since 3.0.0. The same thing is used since 3.0.0 for KReport/KProperty. I recommend using master branches for all the repos though. All means are used to make Kexi work OK with stock Qt. > >I'm sorry if this conservative talk sounds like raising a bar. > > I don't mind. I really don't like Breeze (theme nor style), but as long as > I don't have any use for Kexi personally (currently a simple fact) I'm much > less concerned by choices that affect the interface appearance than I would > be with, say, KDevelop or digiKam. > > I may have a bit of time this week to look at the file dialog question. > > About that: Kexi just finished building on my Linux rig, and I get a very > similar issue when I use the import wizard to import a database and then > open the dialog configure drop-down menu. With the QtCurve menu the mouse > and keyboard are grabbed, meaning I have to use a remote connection (or a > timed kill command) to get out of the ensuing deadlock. This doesn't happen > in any other application, so something fishy is going on here. (Evidently > there's no mouse or keyboard grab on Mac, not in the X11 sense in any case). > Good, thanks for reporting any issues in detail. bugs.kde.org is preferred, and screenshots/videos help a lot. One good thing almost ready for Windows that can be good for Mac too: KFileWidget would be optional so native Open/Save dialogs (+KUrlRequester and a simple QFileSystemModel-based list view) would be available for non-Plasma platforms. -- 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
Re: Kexi/Mac
On 26 December 2016 at 19:13, René J.V. Bertin <rjvber...@gmail.com> wrote: > Hi, > > A little FYI/thumbs-up ... despite plans to get Karbon working on Mac > first it's Kexi that won in the end. > > Not the standalone, all-inclusive app bundle some might be hoping for, but > a MacPorts package (port): > > https://github.com/RJVB/macstrop/tree/master/kf5/kf5-kexi > > I've committed a few minor patches (building and installing the app icon, > building the handbook) but there's need for more work: the interface is > completely messed up when using the native Macintosh widget style. > > This *may* be the kind of glitch that made KCalc unusable with the native > style. > > https://bugs.kde.org/show_bug.cgi?id=374177 > > > Additionally there's an issue with the file dialog; the menu for choosing > the sorting and display mode opens but doesn't work, and drop-down > completion lists appear in the background. These features work in other KF5 > applications. > > Maybe Kexi shouldn't try to impose the Breeze iconset on Mac? > These are great news, René! Maybe I am repeating myself but the enforcement of the widget style and icon theme is dictated by a specific approach: maintainer of a style is free to add the style/theme and even change the default or add an alternative. So there's open path to change of the default e.g. on Mac to a specific different default. It's possible as soon as the new default is not 'worse' than the Breeze one. Contributions are needed in kexi.git, kreport.git, kproperty.git it seems. Also once we have documentation updated, we need these contributions to be extended to the docs: Mac docs will need updates. Unless these contributions are here I am a bit afraid we're risking inconsistencies between platforms and inferior experience on Mac (no docs, incomplete icon theme or styles). I'm sorry if this conservative talk sounds like raising a bar. A first step, a lower bar, could be an alternative icons set for Kexi. Icon sets are somehow supersets of icon themes from Linux, dedicated, and can be deployed separately, just like you know it from Firefox, etc. Support for this is not yet ready because, you guess it, lack of contributors willing to work on them. > R. > -- 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
Kexi tasks
Dear Kexi contributors and users, 1. Tasks moved KDE's service todo.kde.org will be retired soon. The replacement is a more modern and multipurpose http://phabricator.kde.org tool. We've been using Kexi board for task management: https://todo.kde.org/?controller=board=show_id=8 I reviewed, updated and then moved all these tasks from todo.kde.org to Kexi Workboard: https://phabricator.kde.org/project/view/17/ Shortcuts for your convenience: http://bit.ly/kexitasks Some tasks wider than Kexi has been moved to Workboards of so-called Kexi frameworks: - KProperty: https://phabricator.kde.org/project/view/19/ shortcut http://bit.ly/kpropertytasks - KDb: https://phabricator.kde.org/project/view/20/ shortcut http://bit.ly/kdbtasks - KReport: https://phabricator.kde.org/project/view/21/ shortcut http://bit.ly/kreporttasks 3. Bugs and wishes In the following days a number of wishes or bugs will be also created based on the removed tasks at http://bugs.kde.org or in addition to existing tasks. We have the usual distinction because wishes and bugs are items that are not particularly being handled at the moment, while tasks are some concrete activity that needs to be accomplished. By the way, shortcuts: http://bit.ly/kexibugs http://bit.ly/kexiwishes 2. Plans Remaining information to be moved to Phabricator and bugs.kde.org is located on the wiki: - https://community.kde.org/Kexi/Tasks - https://community.kde.org/Kexi/TODOs I hope collecting the information in one place will improve your experience. We have lots of the data now and many ideas, but much more is needed. Feel free to report wishes, bugs, discuss on Kexi mailing list or Kexi forums. This message has been posted to the forums too: https://forum.kde.org/viewtopic.php?f=220=137025=367767#p367767 -- 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
Re: Release, again
On 25 November 2016 at 12:14, Dag <dand...@get2net.dk> wrote: > Hi, everybody > We are closing in on release I don't think I know of more than getting the > migration stuff in. > Has anybody anything else they think has to be done before release? > Good! If this helps in any way, Kexi uses kde:releaseme and this is the newest check list we have: https://phabricator.kde.org/T3592 -- 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
Re: "non standalone app bundle" builds on Mac
On 8 November 2016 at 14:50, René J.V. Bertin <rjvber...@gmail.com> wrote:
> On Tuesday November 08 2016 13:20:37 Jaroslaw Staniek wrote:
>
> > > KDE software mostly uses the form
> > >
> > > #include
> > >
> > > whereas on Mac you'd include the main header of a Foo.framework with
> > > (presuming it's not ObjC)
> > >
> > > #include
> > >
> >
> > Maybe that can be seen as misfeature of Xcode and related tools because a
> > point is that the header is _silently_ found even if you're not
>
> No, I don't think you can say that. Support for this (and frameworks
> bundles) has even made it into gcc (on Linux too); I doubt that would have
> happened if there were anything wrong with the principle.
>
> I'm fairly certain that Qt also use the notation in their code
> and examples (#include ).
>
> I see your point about protection, but it's simple enough to avoid that.
> How can you pick up the wrong Foo/Foo headers but pick the right
> corresponding libFoo or Foo.framework, or vice versa? If that happens
> there's something wrong with your install.
>
> The KF5 framework headers all live under ${prefix}/include/KF5, meaning
> that even with a notation you still have to point the compiler to
> the appropriate parent directory.
>
> As a bonus you do not end up with endless compiler command lines on which
> you can no longer find relevant information (or which might even lead to
> issues when they become too long).
>
> > you, you get much nicer preprocessor error if you missed certain entry in
> > target_link_libraries().
>
> I don't think the preprocessor cares what cmake did or didn't do :)
>
>
Fine with me, what are the KF5 rules say?
It's a SoK period so it's pretty possible that some students can help with
such changes :)
R.
>
--
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
Re: "non standalone app bundle" builds on Mac
On 8 November 2016 at 13:09, René J.V. Bertin <rjvber...@gmail.com> wrote:
> On Tuesday November 08 2016 12:17:23 Jaroslaw Staniek wrote:
>
> >
> > I hope special cases in a cmake buildsystem would not be a problem. I've
> > worked with cmake-based build systems that support Makefiles generator
> > (JOM/NMake) and VS generators in the same cmake scripts. The later is a
> > multi-generator so it adds so much extra work since it's different than
> the
> > Makefiles gen. For now I have not checked if the current xCode generator
> is
> > as complex in use as the VS in this regard. Thoughts?
>
> I have no idea how it compares to the VS generator. It's been improved
> recently and I've checked a few projects, but haven't gone much beyond
> that. I think manual tuning of the project would be required, esp. if you
> want to do things that you cannot really achieve directly with CMake.
>
> > or large apps were packaged using scripts. I'd appreciate some info on
> how
> > do you see the current situation (of xCode cmake generator?) if we don't
> > want to require manual mouse clicks in xCode to prepare builds.
>
> See above, Xcode projects are like MSVC projects in that you maintain them
> manually ("what you see is all you get" ...). I actually have little
> experience with the current Xcode versions as I've drifted away from
> development requiring its use since I'm no longer using OS X 10.6 .
> However, as with MSVC there is usually little more you have to do than
> simply adding new files to targets.
> Once you have a project though you can build it from the commandline,
> there's an xcodebuild utility that knows quite a few tricks for that.
>
> >
>
> > >
> >
> > Nope, really, clang shall build them just fine and they should work;
> only
> > plugin paths are most probably something to test if we want to use
> non-Unix
> > approach to paths.
>
> Yes, QStandardPaths is a problem. Qt folks may disagree, but I have the
> impression it wasn't designed with much regard for the potential special
> needs of complex software like KDE's on platforms that don't use
> XDG-compliant locations (that's what we're really talking about here).
> It's also a pity that there is nothing (in the ECM for instance) that
> determines the install locations from the QStandardPath locations, that
> should remove the need for a lot of hacking and additional testing.
>
> > As programming frameworks, so programmers can pick up them as they pick
> up
> > parts of KF5 or some other extra Qt modules for they project. In a
>
> I repeat, "framework" is a term that's already taken in the Mac universe :)
>
I know that so let's use 'Mac Frameworks' term for that :)
> One habit that I see which stands in the way of building KF5 libraries
> (including those with framework status) as a Mac framework is the way
> headers are included.
> KDE software mostly uses the form
>
> #include
>
> whereas on Mac you'd include the main header of a Foo.framework with
> (presuming it's not ObjC)
>
> #include
>
Maybe that can be seen as misfeature of Xcode and related tools because a
point is that the header is _silently_ found even if you're not
linking against respective library that the headers belong too. Then
linking errors (or worse, runtime errors) happen. With you're just
sure that if you used the cmake tools that find libraries (packages) for
you, you get much nicer preprocessor error if you missed certain entry in
target_link_libraries().
> this tells the compiler to search for
> {/System,}/Library/Frameworks/Foo.frameworks/Headers/Foo
> in addition to /usr{/local,}/include/Foo/Foo plus any in other paths you
> may have specified. You'd have to add the individual .framework/Headers
> directories to include them if you don't use the "rich" specification. Not
> the easiest thing to do in Xcode (the interface is a bit clunky).
>
> A bit of a missed chance: most all of KF5's framework headerfiles install
> in a way that would make them accessible using the Foo/Foo notation...
>
> R
>
I'd like to see the headers portable across platforms...
--
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
Re: "non standalone app bundle" builds on Mac
On 6 November 2016 at 13:55, René J.V. Bertin <rjvber...@gmail.com> wrote: > On Sunday November 06 2016 13:47:13 Friedrich W. H. Kossebau wrote: > > > For properly reaching Krita devs please use the ml kimageshop (sic, > named like > > that for historic reasons): > > https://mail.kde.org/mailman/listinfo/kimageshop > > Thanks. Great, yet another mailing list subscription ... :) > > Hi René Thanks for the interest! In addition Kexi-specific things can be discussed at a kexi-devel list :) There were enthusiastic people interested in contributing Mac builds of Kexi but they disappeared so this task is open for maintainer. Bundling or discovering server installation(s) (pgsql, mysql), bundling dependencies -- these are all task for adoption. In my opinion Kexi fits to a standalone path, just like on Windows, to become as native as possible, well, but not more native than that. For example KFileWidget being very Plasma-oriented is close to be removed on Windows and could be also removed on Mac, in favour of a Url field + [..] button (KUrlRequester). I've also not seen Mac builds of Kexi-derived projects: KDb, KReport, KProperty. These are general-purpose frameworks and Kexi dependencies. If they are missing for Mac it would be nice to see them available too as frameworks for general use. If you ever try the code for Kexi and the the three frameworks on Mac, IO'd suggest to use master branches, i.e. development for 3.1, currently under the KDE Review process. There are quite a few changes since 3.0 and 3.0 frameworks are not marked at binary compatible release. 3.1 hopefully will be. > The question I raised isn't relevant to them only, of course, but also for > the rest of Calligra. > > And FWIW: if it's not obvious I can spend a few words explaining why the > MacPorts KF5 ports us "linuxy" builds. > > > R. > -- 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
Re: state of release and release plan
On 27 October 2016 at 13:11, Friedrich W. H. Kossebau <kosse...@kde.org> wrote: > Hi Dag & all, > > Am Mittwoch, 26. Oktober 2016, 14:03:12 CEST schrieb Dag: > > Hi > > Another month came and went, and not much happened... > > I'm actually a little afraid of releasing because we might attract some > > users. > > Well, to be more precise, that there will be nobody to support those > > users. > > If I speak openly that is also my subjective line of thinking. > > Making a release of software means giving it to others and thus making a > promise to them, so subscribing to moral responsibilities. > > Even while having spent so much time and energy into the porting over the > last > two years, I am not sure I am motivated to spent my bit of needed time into > maintenance where needed by non-contributors currently. At least when it > comes > to the main Calligra editor apps. > > My personal interest is in the middleware and technology, and I joined the > Calligra project because it was closest to what I would like to have, > though > with big plans for redesigning basic parts (and quite some draft branches > are > on my local disk). Which is also why I never officially signed up as > maintainer of any of the maintainer-less apps, only for the plugins for > Okular > and some import filters. > > Still, to get some momentum in this discussion, I have just taken the > liberty > to push a commit which removes Braindump, Karbon app & Stage app from > release > builds, as there is no-one even coming close to be a maintainer. At least > with > Stage I hope that commit will trigger someone to react, but then hope dies > last, they say ;) > And by that commit I also express my hope that you the Plan, Sheets & Words > maintainers will still do a release for your software, so that my porting > contributions are coming to someone else's gain still. > > Besides that though I have to state now (also to myself) that I have no > personal motivation to drive or invest into any release work right now, as > there is no itch to scratch for myself here, especially when looking at the > consequences. > > I will happily assist where possible though anyone with a Calligra 3.0 > release > for small related tasks. > > > Also, not to be forgotten, KChart and KGantt needs to be released. > > Yes, thanks for the push :) Though I have had already started to play > around > with the packaging scripts the other WE. As written in private email, > planning > for release on latest Nov. 7th. > > > Thanks for concrete actions, Friedrich. Adding KDE community to the channel... I have no doubts that middleware tech of the project has the most chances to be actively developed. tl;dr for others: Large parts of Calligra will be frozen, buried in KDE git and not released if there are no maintainers. Very soon, so feel free to share the request with the outside world. -- 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
Re: state of release and release plan
On 26 October 2016 at 14:03, Dag <dand...@get2net.dk> wrote: > Hi > Another month came and went, and not much happened... > I'm actually a little afraid of releasing because we might attract some > users. > Well, to be more precise, that there will be nobody to support those users. > An example; a user posed a question about words on the forum close to 2 > months ago, still no answer. > I don't know enough to determine if the problem he ahs is just a matter of > doing it the right way or if it is a bug or a limitation in odt or > something else. It would take me a lot of time to find out so it would be > much better if someone in the know (eg Camilla) could have answered. > > I would support plan of course, but what about words and sheets? > Camila and Tomas; what are you able to commit to, are there others? > I'm willing to set aside other stuff I'm working on to help, but I would > need guidance to get anything done in a reasonable time and reviews of > course, so I don't mess up too much. > > Also, not to be forgotten, KChart and KGantt needs to be released. > > Right, Dag. Like you, I am wondering too about this great code base. In order to be closer to reality, let's admit, software releases take time too. I've not seen many commits recently to calligra.git to say at least, yet activities moving us closer to release. The commits I see are mostly for Plan or are build fixes. Even if the first release (beta) is out, it wouldn't be the last; continued commitment is needed. So I think it's time to propose alternatives that help to reduce the overhead. What I would imagine? - stop releasing tarballs and instead only publish git tags - publish automated change logs based on git logs for tag-x.y.z-1..tag-x.y.z This reduces overhead to 10 minutes per release or so if I understand it correctly. Any saved energy could got to updating the build recipes and forum support. I am aware of incompatibility[1] with KDE's approach and what OS distributors expect but OTOH it's better than silence and it's not incompatible with today's GitHub-oriented mindset of software developers. Thousands of low-profile projects do that. If someone is interested in the source code and building/distributing binaries, this form of distribution is acceptable. My 0.02PLN. I'd be interested in other proposals. [1] Who contributes, decides. Anyone is free to get it back to the traditional workflow. Cheers, Dag. > > > Friedrich W. H. Kossebau skrev den 2016-09-20 01:33: > >> Hi, >> >> Am Samstag, 2. Juli 2016, 08:17:40 CEST schrieb Camilla Boemann: >> >> I think it's time we get a release out. We are stuck with not much work >>> going on so inspired by Dag's return let's do a push to get ready. >>> >>> I think we should cut down on the number of applications so we have >>> something manageble left. It's tough but the alternative is that Calligra >>> dies completely. And nothing prevents us from bringing apps back later. >>> >>> So my question is: What is missing for us to have a release. I am not >>> talking about all the nice to have features and bug fixes. I am asking >>> what >>> would create huge problems for our users if we release. >>> >>> Let's get things listed. I'll start: >>> >> >> Karbon: let's exclude from first release >>> >> >> From my testing it mainly works, so no real difference to Stage or Words >> IMHO >> So I would vote for include. Perhaps mark as experimental. >> >> Flow: let's exclude from first release >>> >> >> Agreed. There would be also nothing to release :) Flow has not been ported >> even, as the plan of its maintainer was to make Flow another UI to the >> Karbon >> libs, optimized for Flow-specific use-cases. Just, has not happened yet. >> >> Braindump: let's drop it completely >>> >> >> It has been ported, build and works. Pity for the work done there. But >> agreed. >> No maintainer, no users known. Time tp git rm. >> >> Gemini: >> incomplete port to QtQuick2 -> not part of release, already marked as >> STAGING >> >> Format Filters: >> guess anything that builds is on similar state as with 2.9. At least all >> my >> test files still work. >> >> Okular plugins: >> depend on unreleased Okular/KF5, work with current devel branch. >> so fine keep included in release builds. >> Okular/KF5 might be finally in KA 16.12 >> >> Other extras: >> thumbnail etc. also work, so no reason to exclude >> >> Cheers >> Friedrich >> > -- 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
Kexi and Kexi Frameworks release schedule updated
Hi, There's some update for the Kexi and Kexi Frameworks release schedules. This is a proposal awaiting for your input. https://community.kde.org/Kexi/Schedules A major change is that frameworks 3.1.0 (not Kexi) would be binary-incompatible because 3.0.0 were not sufficiently reviewed using the KDE community process and binary-incompatible changes are required to prepare for compatible releases. This is an exception. 3.2.0 is planned to be binary-compatible with 3.1.0, and so on. -- 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
Re: 'master' is 3.1 Alpha now
Update: continuous integration is now enabled for Kexi and Kexi frameworks, both for master (3.1 alpha) and stable (3.0). Links below, I can imagine they will be organized within https://build.kde.org/view/Calligra/ for easier access. https://build.kde.org/job/kexi%20master%20kf5-qt5/ https://build.kde.org/job/kexi%203.0%20stable-kf5-qt5/ https://build.kde.org/job/kdb%20master%20kf5-qt5/ https://build.kde.org/job/kdb%203.0%20stable-kf5-qt5/ https://build.kde.org/job/kproperty%20master%20kf5-qt5/ https://build.kde.org/job/kproperty%203.0%20stable-kf5-qt5/ https://build.kde.org/job/kreport%20master%20kf5-qt5/ https://build.kde.org/job/kreport%203.0%20stable-kf5-qt5/ On 6 October 2016 at 12:11, Jaroslaw Staniek <stan...@kde.org> wrote: > > > On 6 October 2016 at 11:56, Adam Pigg <a...@piggz.co.uk> wrote: > >> Thanks jaroslaw, I'm glad you've got the time for handling the releases >> and keeping all the repositories properly in sync!! >> >> Hopefully we will get a new influx of users (and bugs) from this! >> > > I think so. > > I would say many folks have been waiting for a stable number before > they start looking at things. So as usual proper testing in wider FOSS > audience happens at x.0.0 stage. > > > >> On Thu, 6 Oct 2016, 10:35 Jaroslaw Staniek, <stan...@kde.org> wrote: >> >>> Hi, >>> Congratulations to all contributors of Kexi/KDb/Property/KReport for the >>> 3.0.0 release! >>> The code for 3.0.x series is now placed in the 3.0 branches. >>> Per general habit, just after the major release our master branch in all >>> the git repos is devoted for 3.1 development. >>> 3.1 is currently at Alpha stage and has numeric version 3.0.90. >>> >>> -- >>> 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 >>> >> > > > -- > 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 > -- 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
Re: Calligra stable releases not in Debian stable Jessi
On 8 October 2016 at 15:13, Maximiliano Curia <m...@debian.org> wrote: > ¡Hola Jaroslaw! > > El 2016-09-30 a las 11:31 +0200, Jaroslaw Staniek escribió: > >> I am maintainer of Kexi, one of Calligra apps. I've just noticed that in >> Debian stable Jessi the recent Calligra is 2.8.5 which is 13 releases old. >> There are no updates to 2.8.7, and zero updates to 2.9.*. >> > > 2.8.5 is a July 2014 version. Due to security and stability issues it may >> be even better *not* to have this version released at all than receiving >> reports and users thinking that's the most recent version (this is my own >> opinion). >> > > When users run, say, a Raspberry, they see that old and unsupported (by >> us) version. So here Jessi distributes this unstable software despite many >> updates being available. I don't see the same issue with MySQL for example, >> which was updated just this month. Maybe a man power issue? >> > > I have questions then: >> - what happens? >> > > Debian has a release cycle of around 2 years. It uses three separate > tracks: unstable, testing and stable. > > For the first ~20 months of this cycle the package maintainers make > regular updates to unstable and testing, adding new software to the archive > in order to prepare for the next stable release. Packages first go through > unstable and after a while they enter into testing which is what will be > eventually considered for the stable release. > > The last part of the cycle is a freeze period where no new versions are > introduced and all the efforts go to finish the integration of the system, > closing as many bugs as possible, backporting upstream fixes, etc. > > At the end of this cycle the release is tagged as stable and stops > receiving updates, except for critical bugs, and security related issues. > This updates are evaluated by the stable release team, and/or the security > team, once accepted they are available in the proposed-updates or the > security archives till the next stable point release. > > Almost no software gets new versions in the stable release, very few > exceptions are made for critical security bugs in software that's > infeasible to backport the corresponding fixes (an exception was made for > firefox some years ago, and also for mariadb not so long ago), this is > actually a sign that there is something wrong with the software. > > > Jessie is currently the stable Debian version, the current testing version > is called stretch, and is about to enter in the freeze stage. > > - what can be done to fix the situation? >> > > The version of calligra that you point out is in the stable release and > won't get updated to a new version. The package maintainers could decide to > backport some critical fix. > > Could you point out the issues that you consider critical in 2.8.5? > > Thanks for the explanation Maximilian. If I can summarize (maybe not just for you as you have in-depth understanding but more like for users and people from the outside of our projects). If I understand correctly, the 'stability' term used by Debian is a distribution-oriented one. Do you agree that releasing stability fixes for a software, not just serious security fixes is a part of maintaining software stability? Even if we're staying with Kexi as an example, because of better familiarity, let's look at its basic 24 months+ -old changelog of version (not present in Debian stable): https://www.calligra.org/news/calligra-2-8-6-released/ It was *really* surprising for me that Debian Stable has no 2.8.7 in the offer. Knowing the idea of freezing already, I have not asked for 2.9.x but we have semantic versioning and release cycles for a purpose to serve better and predictably. It's clear that Kexi, even if updated to 2.8.6 is more stable than 2.8.5, right? Obviously there are fixes of "I can't use the software anymore" category. Are these fixes critical? Yes, if actual *using* the software for a practical purpose is the goal, not ability to have any version installable. If you're asking about security threats removed, there are such beasts, please refer to my examples for the 2.8.7 release given in this thread. Regarding "I can't use the software anymore" kind of bugs. As MS discovered long ago with the beloved Office 97, users run something like 20% of the functionality but everyone uses slightly different 20%. So also Kexi and Calligra offers a huge feature set, as any integrated software package; possible applications/combinations are hard to imagine or predict. No doubt there are users for whom versions 2.8.[0-5] contain critical issues in features they depend on so the software in that version as a no-go for them. What's user's perceived definition of stability is an
Fwd: Moved to KDE Review: KDb, KReport, KProperty
FYI -- Forwarded message -- From: Ben Cooksley <bcooks...@kde.org> Date: 7 October 2016 at 20:49 Subject: Moved to KDE Review: KDb, KReport, KProperty To: kde-core-devel <kde-core-de...@kde.org> Cc: Kexi Guy <stan...@kde.org> Hi all, Just a heads up that at the request of Jaroslaw Staniek, Sysadmin has moved the following repositories to KDE Review: - KDb (kdb) - KReport (kreport) - KProperty (kproperty) >From my understanding these are used as part of Kexi. Regards, Ben -- 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
Re: 'master' is 3.1 Alpha now
On 6 October 2016 at 11:56, Adam Pigg <a...@piggz.co.uk> wrote: > Thanks jaroslaw, I'm glad you've got the time for handling the releases > and keeping all the repositories properly in sync!! > > Hopefully we will get a new influx of users (and bugs) from this! > I think so. I would say many folks have been waiting for a stable number before they start looking at things. So as usual proper testing in wider FOSS audience happens at x.0.0 stage. > On Thu, 6 Oct 2016, 10:35 Jaroslaw Staniek, <stan...@kde.org> wrote: > >> Hi, >> Congratulations to all contributors of Kexi/KDb/Property/KReport for the >> 3.0.0 release! >> The code for 3.0.x series is now placed in the 3.0 branches. >> Per general habit, just after the major release our master branch in all >> the git repos is devoted for 3.1 development. >> 3.1 is currently at Alpha stage and has numeric version 3.0.90. >> >> -- >> 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 >> > -- 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
'master' is 3.1 Alpha now
Hi, Congratulations to all contributors of Kexi/KDb/Property/KReport for the 3.0.0 release! The code for 3.0.x series is now placed in the 3.0 branches. Per general habit, just after the major release our master branch in all the git repos is devoted for 3.1 development. 3.1 is currently at Alpha stage and has numeric version 3.0.90. -- 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
Kexi 3.0.0 & frameworks released
Dear All, We're pleased to announce the release of Kexi 3.0.0. For benefit and convenience of fellow software engineers, we're sharing frameworks originally developed within the Kexi Project (that is KDb, KProperty, KReport). There are marked with the same version 3.0.0 and are prepared for general, standalone usage. So this combined release marks a major milestone for two efforts: porting to Qt 5 started in 2014, development of the three frameworks started in 2008. Downloads & change logs: https://community.kde.org/Kexi/Releases#3.0.0 Reporting bug or wishes: https://community.kde.org/Kexi/File_a_bug_or_wish -- 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
Re: Kexi 3.0 release is coming
On 3 October 2016 at 12:02, Jaroslaw Staniek <stan...@kde.org> 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. > Please direct code fixes there from now. master branches are for 3.1 > alphas. > This is a hotfix we'd like to have before tarballs are created, it's waiting for review: https://phabricator.kde.org/D2924 So we have like one day delay. > > Our release task is https://phabricator.kde.org/T3592 if you would like > to track what's happening. > Please share any issues. > > -- > 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 > -- 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
Re: Kexi 3.0 release is coming
On 3 October 2016 at 12:21, Luigi Toscano <luigi.tosc...@tiscali.it> wrote: > On Monday, 3 October 2016 12:14:21 CEST Jaroslaw Staniek wrote: > > On 3 October 2016 at 12:06, Luigi Toscano <luigi.tosc...@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. > > Thanks Luigi OK with doing that later then. Could you look at to tell me what parts of https://phabricator.kde.org/D2916 are OK and what not yet? Probably especially the stable_kf5=3.0 values. If there's anything documented feel free to share a checklist for the 'kdereview' task. > > > -- 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
Re: Kexi 3.0 release is coming
On 3 October 2016 at 12:06, Luigi Toscano <luigi.tosc...@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 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... Thanks. -- 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
Kexi 3.0 release is coming
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. Please direct code fixes there from now. master branches are for 3.1 alphas. Our release task is https://phabricator.kde.org/T3592 if you would like to track what's happening. Please share any issues. -- 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
Re: Calligra stable releases not in Debian stable Jessi
On 1 October 2016 at 00:18, Nicolás Alvarez <nicolas.alva...@gmail.com> wrote:
> 2016-09-30 6:31 GMT-03:00 Jaroslaw Staniek <stan...@kde.org>:
>>
>> Dear Debian contributors,
>> I am maintainer of Kexi, one of Calligra apps.
>> I've just noticed that in Debian stable Jessi the recent Calligra is 2.8.5
>> which is 13 releases old. There are no updates to 2.8.7, and zero updates to
>> 2.9.*.
>>
>> 2.8.5 is a July 2014 version. Due to security and stability issues it may be
>> even better *not* to have this version released at all than receiving
>> reports and users thinking that's the most recent version (this is my own
>> opinion).
>>
>> When users run, say, a Raspberry, they see that old and unsupported (by us)
>> version. So here Jessi distributes this unstable software despite many
>> updates being available. I don't see the same issue with MySQL for example,
>> which was updated just this month. Maybe a man power issue?
>>
>> I have questions then:
>> - what happens?
>> - what can be done to fix the situation?
>> - how to coordinate better?
>>
>
> Jessie is frozen, I doubt Kexi 2.9 will ever be in 'jessie'. I don't
> see how MySQL is different, the latest version from upstream is
> 5.7.15, Jessie has 5.5.52, it was upgraded from 5.5.50 because of a
> specific security fix.
>
> See this for the criteria to get an update in stable:
> https://www.debian.org/doc/manuals/developers-reference/pkgs.html#upload-stable
>
> Can you mention specific security bugs that 2.8.5 has? That could
> justify bringing 2.8.7 in (or backporting the security fixes).
>
> And maybe 2.9 could be in the 'jessie-backports' repository. But I
> wouldn't expect it in 'jessie'.
>
>
> Of course, this is in addition to the possible lack of manpower to do
> such packaging :)
Thanks for the useful info, Nicolás.
Let's see 1st commit from 2.8.7 which removes possibility of preparing
attack that can
crash your db. Please see below. It's enough to cause Kexi to ask
a specific question and it enters infinite loop and exits with exception, thus
e.g. loosing unsaved designs.
Really we did not set formal distinction between type of instabilities
knowing that *normally* distributors take all fixes and deploy them to
the users; because this is a connected/network software for multiuser
environment consequences may be more serious than, say, in a locally
running text editor.
Honestly, we know via telemetrics that more than needed users run
outdated software.
And request free support for it.
commit db59286ef26be67eccf6f0fb31e5abdcf9911d02
Author: Jaroslaw Staniek <stan...@kde.org>
Date: Tue Nov 25 23:06:03 2014 +0100
Fix infinite recursion in msghandler.cpp
The Calligra 2.7.90 build log using msvc2010 gives this warning
concerning msghandler.cpp: 'KexiDB::MessageHandler::askQuestion' :
recursive on all control paths, function will cause runtime stack overflow
Thanks, Stephen Leibowitz
CCMAIL:librestep...@gmail.com
REVIEW:121180
FIXED-IN:2.8.7
Another, specific query can be passed by one user to another and cause
a crash; in theory also executing arbitrary code on some
architectures:
commit eaefd12562da5b422ae175351423fa15fd1a2cb4
Author: Jaroslaw Staniek <stan...@kde.org>
Date: Wed Jun 4 13:12:22 2014 +0200
Fix crash when accessing a query with duplicated table names
Example query that crashed: SELECT t.foo FROM t, t.
Now error message is displayed so user can fix the statement.
BUG:315852
FIXED-IN:2.8.4
If the database serves more than one user it can also mean denial of
service attacks: it's enough to set query to be always executed
initially e.g. for a main form.
--
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
Calligra stable releases not in Debian stable Jessi
Dear Debian contributors, I am maintainer of Kexi, one of Calligra apps. I've just noticed that in Debian stable Jessi the recent Calligra is 2.8.5 which is 13 releases old. There are no updates to 2.8.7, and zero updates to 2.9.*. 2.8.5 is a July 2014 version. Due to security and stability issues it may be even better *not* to have this version released at all than receiving reports and users thinking that's the most recent version (this is my own opinion). When users run, say, a Raspberry, they see that old and unsupported (by us) version. So here Jessi distributes this unstable software despite many updates being available. I don't see the same issue with MySQL for example, which was updated just this month. Maybe a man power issue? I have questions then: - what happens? - what can be done to fix the situation? - how to coordinate better? Best 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
Kexi 3.0.0 Beta 1 and libraries released
Dear All, Kexi 3.0.0 Beta 1 and related libraries has been released for testing and packaging. Downloads & change logs: https://community.kde.org/Kexi/Releases/3#3.0.0_Beta_1 <https://community.kde.org/Kexi/Releases/3#3.0.0_Alpha_1> Report bug or wishes: https://community.kde.org/Calligra/File_a_bug_or_wish -- 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
Re: [Maniphest] [Commented On] T3755: Kexi API docs missing in the calligra section
On 20 September 2016 at 12:08, Adam Pigg <a...@piggz.co.uk> wrote: > Are the Kexi plugins libs not part of a public Kexi API? > > > Public within Kexi, yes. Public so that independent vendors distribute own extensions? Not quite, that's not maintained. To save the overhead we're distributing all plugins that depend on Kexi with Kexi releases[1]. Except for complex cases such as form maps widget or web browser widget, that are truly optional and have larger dependencies, plugins are not even in separate packages because it's hard to think of Kexi without forms, queries or tables installed. In theory it makes sense but we don't get any benefit from it. It's like having browser not supporting sound. It's possible but not practical. > Also, the Kexi specific parts of the report plugin scripting side should be documented as user api Yes, hopefully as much as possible was moved to KReport (or maybe more can be moved?). The above does not mean we're not encouraging development of plugins. Plugins would be even possible to write in the future scripting language that we plan to support (Javascript). I am just wondering why docs for Kexi plugin developers's docs shall not be just a step or two away from the Kexi developer's (contributors) docs, not more. Obviously in a separate Doxygen group, but not within in separate web site (api.kde.org vs kexi-project.org). [1] A note for others, Since version 3, database plugins moved to the KDb project, KProperty plugins are compiled in but sit in the KProperty project, and report element plugins moved to the report KReport; all these plugins are not dependent on Kexi anymore and are distributed separately, even if we happen to have combined releases like the current Beta. > On Tue, 20 Sep 2016, 09:37 staniek (Jarosław Staniek), < > nore...@phabricator.kde.org> wrote: > >> staniek added a comment. >> >> The domain name is secured and it's KDE's already. >> >> *TASK DETAIL* >> https://phabricator.kde.org/T3755 >> >> *EMAIL PREFERENCES* >> https://phabricator.kde.org/settings/panel/emailpreferences/ >> >> *To: *staniek >> >> *Cc: *kossebau, Calligra-Devel-list, bcooksley, ochurlaud, sysadmin, >> staniek, blazquez >> > -- 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
Refreshing API docs for calligra apps
Hi, tl;dr: Using the kapidox tool is an idea to have slightly better quality of generated docs and less work mid term. Are there any folks interested in helping out with adjusting API docs format of calligra.git to refresh API docs that are currently at https://api.kde.org/bundled-apps-api/calligra-apidocs/? Note, it does not include writing docs, it's hopefully a minimal adjustment to make kapidox work. I am planning to adjust docs from kexi.git and from repos of "kexi libs". Background: (I asked for advice on what can be done to refresh API docs for calligra apps. I did so on the sysadmin project, the task is https://phabricator.kde.org/T3755 but because it's not publicly accessible I have attached the log and moved the discussion to the Calligra list. Olivier and Ben are in CC here, please keep them added as they were involved in discussions). A new proposal from Olivier Churlaud is to move API docs for Calligra apps (and libs) to a more prominent place at https://api.kde.org, where for example you can already find Marble and Okular. I see no reason why Calligra wouldn't go there in the same way. By API docs we mean not app's documentation of classes, possible design, and such, *not* necessarily public API of these apps. Such API may not exists, yet the apps qualify for having the API docs regularly generated and published for convenience of current and future contributors that look around learn the architecture, etc. This is how it all worked so far. -- 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 T3189.pdf Description: Adobe PDF document
Kexi 3.0.0 Alpha 1 with libs released
Hello, Kexi 3.0.0 Alpha 1 with libs has been released for testing and packaging: https://community.kde.org/Kexi/Releases/3#3.0.0_Alpha_1 Report bug or wishes: https://community.kde.org/Calligra/File_a_bug_or_wish -- 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
Re: kexi, kdb, kproperty, kreport ready to translate
On 13 September 2016 at 00:53, Jaroslaw Staniek <stan...@kde.org> wrote: > > kexi, kdb, kproperty, kreport are ready to translate, string freeze is on. > Hi, A quick update for translators: There are some fixes needed in translation code of kdb and kreport so messages would change in a few places. (kexi and kproperty seem to be OK). I will let you know when scripty is OK with, hopefully within 10 hours. ( error log: ftp://l10n.kde.org/160913.trunk_l10n-kf5 ) > > PS: The releaseme tool gives no translations for Kexi (so tarballs I'll > upload soon won't include translation files). > kdb, kproperty, kreport tarballs include them. > I am wondering if this is because > repo-metadata/projects/calligra/kexi/metadata.yaml > contains this: > > projectpath: calligra/kexi > > .. while the messages are still in calligra/? > I am experiencing the same issue is with Krita but maybe that's not > noticed only because the Krita Team does not seem to use releaseme for > packaging. > > Another reason for having a kexi/ subdir would be: the .po files from > various apps and plugins are too a bit too mixed within messages/calligra/ > so maybe some hierarchy would be good? > > This is what happens with my command: > > % tarme.rb --version 2.99.90 --origin trunk kexi > > "No translations for..." does not explain what paths are expected. > Any help appreciated. > > THE OUTPUT: > > calligra > kexi > INFO -- Release: Getting source (git - g...@git.kde.org:kexi [master]) > INFO -- Release: Getting translations... > INFO -- L10n: Downloading translations for kexi-2.99.90 > INFO -- L10n: No translations for: ar, af, as, ast, be, bg, be@latin, bn, > bn_IN, br, bs, ca, ca@valencia, cs, crh, csb, da, cy, de, en_GB, el, eo, > es, et, fa, eu, fi, ga, fy, fr, gd, gu, he, ha, gl, hi, hr, hne, hsb, hy, > hu, ia, is, it, id, ja, ka, kk, km, kn, ko, ku, lt, lv, lb, mai, ml, mr, > ms, mt, mk, nds, ne, nl, nb, nn, oc, or, nso, pa, pl, pt, ps, pt_BR, ro, > ru, rw, si, sk, sl, se, sq, sr@ijekavian, sr, sr@ijekavianlatin, sv, ta, > sr@latin, te, tg, th, tr, tt, ug, uz, uk, uz@cyrillic, wa, vi, zh_CN, xh, > zh_HK, zh_TW > INFO -- Release: Getting documentation... > INFO -- DocumentationL10n: Downloading documentations for kexi-2.99.90 > INFO -- DocumentationL10n: No translations for: fa, fi, fr, fy, ga, gd, > gl, ha, gu, he, hi, hne, hsb, hr, hu, ia, hy, id, is, ka, km, ja, kk, kn, > ku, ko, lb, lt, mai, mk, lv, ml, nb, ms, mt, mr, nds, ne, oc, nn, nso, pa, > or, pl, ps, ro, ru, rw, se, si, sl, sq, sk, sr, sr@ijekavian, > sr@ijekavianlatin, sr@latin, ta, te, th, tg, tt, ug, tr, uz, uz@cyrillic, > vi, wa, xh, zh_CN, zh_TW, zh_HK > INFO -- Release: Archiving source (git - g...@git.kde.org:kexi [master]) > > -- > 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 > -- 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
kexi, kdb, kproperty, kreport ready to translate
Hi Luigi, kexi, kdb, kproperty, kreport are ready to translate, string freeze is on. PS: The releaseme tool gives no translations for Kexi (so tarballs I'll upload soon won't include translation files). kdb, kproperty, kreport tarballs include them. I am wondering if this is because repo-metadata/projects/calligra/kexi/metadata.yaml contains this: projectpath: calligra/kexi .. while the messages are still in calligra/? I am experiencing the same issue is with Krita but maybe that's not noticed only because the Krita Team does not seem to use releaseme for packaging. Another reason for having a kexi/ subdir would be: the .po files from various apps and plugins are too a bit too mixed within messages/calligra/ so maybe some hierarchy would be good? This is what happens with my command: % tarme.rb --version 2.99.90 --origin trunk kexi "No translations for..." does not explain what paths are expected. Any help appreciated. THE OUTPUT: calligra kexi INFO -- Release: Getting source (git - g...@git.kde.org:kexi [master]) INFO -- Release: Getting translations... INFO -- L10n: Downloading translations for kexi-2.99.90 INFO -- L10n: No translations for: ar, af, as, ast, be, bg, be@latin, bn, bn_IN, br, bs, ca, ca@valencia, cs, crh, csb, da, cy, de, en_GB, el, eo, es, et, fa, eu, fi, ga, fy, fr, gd, gu, he, ha, gl, hi, hr, hne, hsb, hy, hu, ia, is, it, id, ja, ka, kk, km, kn, ko, ku, lt, lv, lb, mai, ml, mr, ms, mt, mk, nds, ne, nl, nb, nn, oc, or, nso, pa, pl, pt, ps, pt_BR, ro, ru, rw, si, sk, sl, se, sq, sr@ijekavian, sr, sr@ijekavianlatin, sv, ta, sr@latin, te, tg, th, tr, tt, ug, uz, uk, uz@cyrillic, wa, vi, zh_CN, xh, zh_HK, zh_TW INFO -- Release: Getting documentation... INFO -- DocumentationL10n: Downloading documentations for kexi-2.99.90 INFO -- DocumentationL10n: No translations for: fa, fi, fr, fy, ga, gd, gl, ha, gu, he, hi, hne, hsb, hr, hu, ia, hy, id, is, ka, km, ja, kk, kn, ku, ko, lb, lt, mai, mk, lv, ml, nb, ms, mt, mr, nds, ne, oc, nn, nso, pa, or, pl, ps, ro, ru, rw, se, si, sl, sq, sk, sr, sr@ijekavian, sr@ijekavianlatin, sr@latin, ta, te, th, tg, tt, ug, tr, uz, uz@cyrillic, vi, wa, xh, zh_CN, zh_TW, zh_HK INFO -- Release: Archiving source (git - g...@git.kde.org:kexi [master]) -- 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
Re: Test tarballs available for 3.0.0-pre-beta1 of KDb/KProperty/KReport and proposed release schedule
On 9 September 2016 at 14:10, Jaroslaw Staniek <stan...@kde.org> wrote: > > On 6 September 2016 at 09:55, Jaroslaw Staniek <stan...@kde.org> wrote: >> >> Hi, >> Just uploaded libraries 2.99.1, and Kexi 2.99.89 for testing. This is >> not a release. >> >> >> https://drive.google.com/folderview?id=0B0o42yCJezrDNTVfRklJY2JxVDg=sharing >> >> Some test files (kexi and MDB): >> >> >> https://drive.google.com/folderview?id=0B0o42yCJezrDd24yMUh5X1MtN1E=sharing > > > > OK, I'd like to inform you that these dates are now official since nobody > objected: > > - string freeze: Monday Sep 12 > - beta1 release: Monday Sep 19 > > A i18n-related note is that kdb/kreport/kproperty are all using Qt's i18n > facilities while Kexi is using and KF5's one. It's assumed to be working > combination but testing for corner cases would be good. Any repors like > missing or invalid use of Q_DECLARE_TR_FUNCTIONS is welcome too. By the way. I noticed the kexi tarball (created using kde:releaseme) contains no translations (no 'po' subdir). It's not clear to me why. The other 3 tarballs contain translations. -- 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
Re: Test tarballs available for 3.0.0-pre-beta1 of KDb/KProperty/KReport and proposed release schedule
On 6 September 2016 at 09:55, Jaroslaw Staniek <stan...@kde.org> wrote: > Hi, > Just uploaded libraries 2.99.1, and Kexi 2.99.89 for testing. This is > not a release. > > https://drive.google.com/folderview?id=0B0o42yCJezrDNTVfRklJ > Y2JxVDg=sharing > > Some test files (kexi and MDB): > > https://drive.google.com/folderview?id=0B0o42yCJezrDd24yMUh5 > X1MtN1E=sharing OK, I'd like to inform you that these dates are now official since nobody objected: - string freeze: Monday Sep 12 - beta1 release: Monday Sep 19 A i18n-related note is that kdb/kreport/kproperty are all using Qt's i18n facilities while Kexi is using and KF5's one. It's assumed to be working combination but testing for corner cases would be good. Any repors like missing or invalid use of Q_DECLARE_TR_FUNCTIONS is welcome too. > > > On 5 September 2016 at 17:03, Jaroslaw Staniek <stan...@kde.org> wrote: > > Dear All, > > Background blog entry: > > https://blogs.kde.org/2016/09/04/kdb-3-kproperty-3-kreport-3 > -kexi-3-and-special-offer-during-akademy > > > > 1. If someone is interested in building, first versions of tarballs > > for KDb/KProperty/KReport 3.0.0-pre-beta1. > > > > https://drive.google.com/folderview?id=0B0o42yCJezrDNTVfRklJ > Y2JxVDg=sharing > > > > They have been created using kde:releaseme and contain translations. > > This task is formulated at https://phabricator.kde.org/T3592 - you can > > watch it if you want. > > > > Order of building: KProperty before KReport as KReport depends on > KProperty. > > Pretty standard cmake building process, it will guide you when you > > miss dependencies. > > Feel free to also enable examples, tests and run the tests. > > > > Kexi tarball would join there probably today. > > All code is currently from master git branches, tags are called like > x.y.z. > > As you can see, unlike for KF5, versions of the tarballs are't > > necessarily synced. This reflects fact that we're reserving right to > > release any of them separately as long as declared compatibilities are > > assured. > > > > 2. Proposed release schedule: all the frameworks and Kexi in one day. > > Opinion is welcome here. > > > > - string freeze: Monday Sep 12 > > - beta1 release: Monday Sep 19 > > > > -- > > 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 > > > > -- > 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 > -- 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
Re: kdiagram in calligra project component?
On 7 September 2016 at 10:26, Ben Cooksley <bcooks...@kde.org> wrote: > Hi, > > Sorry, I don't see what I need to answer here? > Ben, Sorry, actually you're CCd here but I see you already presented valuable perspective in the comments of https://phabricator.kde.org/D2659. The final choice for hierarchy belongs Friedrich, the maintainer. 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
Re: Test tarballs available for 3.0.0-pre-beta1 of KDb/KProperty/KReport and proposed release schedule
On 5 September 2016 at 17:03, Jaroslaw Staniek <stan...@kde.org> wrote: > 2. Proposed release schedule: all the frameworks and Kexi in one day. > Opinion is welcome here. > > - string freeze: Monday Sep 12 > - beta1 release: Monday Sep 19 Let's confirm today that these dates work for you so we can inform translators, etc. -- 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
Re: Test tarballs available for 3.0.0-pre-beta1 of KDb/KProperty/KReport and proposed release schedule
Hi, Just uploaded libraries 2.99.1, and Kexi 2.99.89 for testing. This is not a release. https://drive.google.com/folderview?id=0B0o42yCJezrDNTVfRklJY2JxVDg=sharing Some test files (kexi and MDB): https://drive.google.com/folderview?id=0B0o42yCJezrDd24yMUh5X1MtN1E=sharing On 5 September 2016 at 17:03, Jaroslaw Staniek <stan...@kde.org> wrote: > Dear All, > Background blog entry: > https://blogs.kde.org/2016/09/04/kdb-3-kproperty-3-kreport-3-kexi-3-and-special-offer-during-akademy > > 1. If someone is interested in building, first versions of tarballs > for KDb/KProperty/KReport 3.0.0-pre-beta1. > > https://drive.google.com/folderview?id=0B0o42yCJezrDNTVfRklJY2JxVDg=sharing > > They have been created using kde:releaseme and contain translations. > This task is formulated at https://phabricator.kde.org/T3592 - you can > watch it if you want. > > Order of building: KProperty before KReport as KReport depends on KProperty. > Pretty standard cmake building process, it will guide you when you > miss dependencies. > Feel free to also enable examples, tests and run the tests. > > Kexi tarball would join there probably today. > All code is currently from master git branches, tags are called like x.y.z. > As you can see, unlike for KF5, versions of the tarballs are't > necessarily synced. This reflects fact that we're reserving right to > release any of them separately as long as declared compatibilities are > assured. > > 2. Proposed release schedule: all the frameworks and Kexi in one day. > Opinion is welcome here. > > - string freeze: Monday Sep 12 > - beta1 release: Monday Sep 19 > > -- > 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 -- 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
Test tarballs available for 3.0.0-pre-beta1 of KDb/KProperty/KReport and proposed release schedule
Dear All, Background blog entry: https://blogs.kde.org/2016/09/04/kdb-3-kproperty-3-kreport-3-kexi-3-and-special-offer-during-akademy 1. If someone is interested in building, first versions of tarballs for KDb/KProperty/KReport 3.0.0-pre-beta1. https://drive.google.com/folderview?id=0B0o42yCJezrDNTVfRklJY2JxVDg=sharing They have been created using kde:releaseme and contain translations. This task is formulated at https://phabricator.kde.org/T3592 - you can watch it if you want. Order of building: KProperty before KReport as KReport depends on KProperty. Pretty standard cmake building process, it will guide you when you miss dependencies. Feel free to also enable examples, tests and run the tests. Kexi tarball would join there probably today. All code is currently from master git branches, tags are called like x.y.z. As you can see, unlike for KF5, versions of the tarballs are't necessarily synced. This reflects fact that we're reserving right to release any of them separately as long as declared compatibilities are assured. 2. Proposed release schedule: all the frameworks and Kexi in one day. Opinion is welcome here. - string freeze: Monday Sep 12 - beta1 release: Monday Sep 19 -- 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
Re: kdiagram in calligra project component?
On 5 September 2016 at 02:47, Friedrich W. H. Kossebau <kosse...@kde.org> wrote: > > Hi Jarosław, > > Am Montag, 5. September 2016, 01:03:32 CEST schrieb Jaroslaw Staniek: > > Hi, > > Background: The kde:sysadmin/repo-metadata git repo now replaces the > > project.kde.org stuff. > > I am moving kdb, kreport and kproperty repo metadata to projects/calligra > > from playground/libs as I see them more fit to the new location and they > > are, well, developed within our master project Calligra anyway, regardless > > of repo fragmentation. > > > > That's not my play, the kde:releaseme tool which I'd be trying to use for > > preparing releases depends on the projects metadata so it's good to have > > the metadata as correct as possible. > > > > Now, that's mostly a question to Friedrich: > > > > There is projects/extragear/graphics/kdiagram. It describes "Powerful > > libraries (KChart, KGantt) for creating business diagrams". Do you think > > that kdiagram better fits to calligra/ and not so much to graphics/? > > KChart clearly implements office-oriented objects: data charts and Gantt > > charts. > > For one, those paths in the repo hierachy are just legacy and long-term will > be dropped, for a flat list of repos. That changes some of what I wrote but not the directory hierarchy, right? > Then, that description is copied unchanged from marketing-buzzword loaded > origin :) > > I had put kdiagram into projects/extragear/graphics after discussion as > diagrams can be used for lots of things. There is a (business) world outside > offices :) > Current users known to me of either KChart or KGantt are Massif-Visualizer, > something in KDEPIM, KMyMoney, Plan, a Calligra shape plugin and a KReport > plugin. > So KDiagram is a project shared by many KDE projects, nothing Calligra-centric > there. So I do not see a reason to move this. There's a graph for project organization, there's graph related to what purposes are supported. We won't simplify that in other way than tagging. On thing sure is that the two libs from KDiagram form a framework. So is the place within frameworks/ too? See my question below. > More, as long as that legacy adressing hierarchy of repos exists, I would > rather recommend to move non-Calligra-only stuff like KDb, KReport & KProperty > somewhere into the generic extragear namespace, as those libs target > developers, unlike the "apps" which make up what currently is known as > Calligra and what is about end user products. By being in the generic > extragear namespace this might help stressing the libs general usability > outside of the existing set of Calligra apps. I'd like to be consistent with what we said about extragear. You didn't like it in the "State of Proposal to improving KDE Software Repository Organization" thread and also Ben "would like to see the Extragear moniker dropped." I agree. I have to admit that I had to run deep-search to find kdiagram dir in sysadmin/repo-metadata.git. I can imagine people may need the same for kdb, etc. Question: Based on what we say here ideally I'd like the KDb/KProperty/KReport to be seen as projects/frameworks/. Is it right place? At many levels there's no connection for these projects with KF5. Please review the current draft https://phabricator.kde.org/D2659 - from what already not very right solution. > My 2 cents on that :) Thanks. -- 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
Re: kdiagram in calligra project component?
On 5 September 2016 at 01:03, Jaroslaw Staniek <stan...@kde.org> wrote: > Hi, > Background: The kde:sysadmin/repo-metadata git repo now replaces the > project.kde.org stuff. > I am moving kdb, kreport and kproperty repo metadata to > > projects/calligra from playground/libs > Actually I invented projects/calligra/frameworks even, why not? It more nicely groups by purpose. So I propose to keep kdiagram there. > as I see them more fit to the new location and they are, well, developed > within our master project Calligra anyway, regardless of repo fragmentation. > > That's not my play, the kde:releaseme tool which I'd be trying to use for > preparing releases depends on the projects metadata so it's good to have > the metadata as correct as possible. > > Now, that's mostly a question to Friedrich: > > There is projects/extragear/graphics/kdiagram. It describes "Powerful > libraries (KChart, KGantt) for creating business diagrams". Do you think > that kdiagram better fits to calligra/ and not so much to graphics/? > KChart clearly implements office-oriented objects: data charts and Gantt > charts. > > -- > 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 > -- 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
