Re: Re: Re: KDE Applications Versioning
On Tuesday 14 July 2015 07:08:57 Andreas Cord-Landwehr wrote: If it is OK this way, I can add it later today to the wiki page. Hi, since I did not hear any oppositions, I just added the paragraph to the wiki page draft. Cheers, Andreas
Re: KDE Applications Versioning
Hi, Since this hasn't been finalized I didn't include it in my email to kde-cvs- announce about the creation of the 15.08 branches for the KDE Applications modules. Cheers, Albert El Dimarts, 14 de juliol de 2015, a les 07:08:57, Andreas Cord-Landwehr va escriure: On Monday 13 July 2015 23:14:17 Albert Astals Cid wrote: I did a few tweaks, i still feel it seems this is the official way other than an optional way of defining the version but maybe that's just me. Hi, I have the same feeling as Albert that the current text is not clear enough that both variants (increase version by hand and using the scripted approach) are fine. What about adding an introduction paragraph like the following: - snip - Every application has an application version number that regular has to be increased to distinguish different versions of the application (e.g., features, bugfixes). When an application does not have its own release schedule but is released alongside with KDE Applications, there is also the version number of the KDE Applications release. It is the maintainer's duty to take care on increasing the version number regularly and there are specifically two possible ways: 1. increase the version number by hand for each new release 2. use the same version number as KDE Applications and let the release script update the version number In the following, we explain how to use the scripted version numbers. - snap - If it is OK this way, I can add it later today to the wiki page. I somehow missed that mail ;=) I am all for adding that paragraph and then moving the wiki page to the right place. Greetings Christoph -- - Dr.-Ing. Christoph Cullmann - AbsInt Angewandte Informatik GmbH Email: cullm...@absint.com Science Park 1 Tel: +49-681-38360-22 66123 Saarbrücken Fax: +49-681-38360-20 GERMANYWWW: http://www.AbsInt.com Geschäftsführung: Dr.-Ing. Christian Ferdinand Eingetragen im Handelsregister des Amtsgerichts Saarbrücken, HRB 11234
Re: KDE Applications Versioning
El Dilluns, 20 de juliol de 2015, a les 09:42:40, Andreas Cord-Landwehr va escriure: On Tuesday 14 July 2015 07:08:57 Andreas Cord-Landwehr wrote: If it is OK this way, I can add it later today to the wiki page. Hi, since I did not hear any oppositions, I just added the paragraph to the wiki page draft. Ok, i moved it to https://community.kde.org/Applications/Versioning and removed the construction notice. Cheers, Albert Cheers, Andreas
Re: KDE Applications Versioning
Since this hasn't been finalized I didn't include it in my email to kde-cvs- announce about the creation of the 15.08 branches for the KDE Applications modules. Cheers, Albert El Dimarts, 14 de juliol de 2015, a les 07:08:57, Andreas Cord-Landwehr va escriure: On Monday 13 July 2015 23:14:17 Albert Astals Cid wrote: I did a few tweaks, i still feel it seems this is the official way other than an optional way of defining the version but maybe that's just me. Hi, I have the same feeling as Albert that the current text is not clear enough that both variants (increase version by hand and using the scripted approach) are fine. What about adding an introduction paragraph like the following: - snip - Every application has an application version number that regular has to be increased to distinguish different versions of the application (e.g., features, bugfixes). When an application does not have its own release schedule but is released alongside with KDE Applications, there is also the version number of the KDE Applications release. It is the maintainer's duty to take care on increasing the version number regularly and there are specifically two possible ways: 1. increase the version number by hand for each new release 2. use the same version number as KDE Applications and let the release script update the version number In the following, we explain how to use the scripted version numbers. - snap - If it is OK this way, I can add it later today to the wiki page. Cheers, Andreas
Re: Re: KDE Applications Versioning
On Monday 13 July 2015 23:14:17 Albert Astals Cid wrote: I did a few tweaks, i still feel it seems this is the official way other than an optional way of defining the version but maybe that's just me. Hi, I have the same feeling as Albert that the current text is not clear enough that both variants (increase version by hand and using the scripted approach) are fine. What about adding an introduction paragraph like the following: - snip - Every application has an application version number that regular has to be increased to distinguish different versions of the application (e.g., features, bugfixes). When an application does not have its own release schedule but is released alongside with KDE Applications, there is also the version number of the KDE Applications release. It is the maintainer's duty to take care on increasing the version number regularly and there are specifically two possible ways: 1. increase the version number by hand for each new release 2. use the same version number as KDE Applications and let the release script update the version number In the following, we explain how to use the scripted version numbers. - snap - If it is OK this way, I can add it later today to the wiki page. Cheers, Andreas
Re: KDE Applications Versioning
On Mon, Jul 13, 2015 at 8:51 AM, Christoph Cullmann cullm...@absint.com wrote: - Ursprüngliche Mail - El Dissabte, 11 de juliol de 2015, a les 16:59:13, Christoph Cullmann va escriure: - Ursprüngliche Mail - El Dissabte, 11 de juliol de 2015, a les 15:52:44, Christoph Cullmann va escriure: Hi, something like that? https://userbase.kde.org/KDE_Applications_Versioning I'd like to make it clearer that this is optional and maybe also an example that only uses KDE_APPLICATIONS_VERSION_MICRO Also KDE_APPLICATIONS_VERSION is not replaced at all, just MAJOR MINOR and MICRO as in the script i linked. Yeah, thats true, I just wanted to show the typical boiler plate you might want. Where to move it? userbase doesn't seem the right place for this tbh, what does it have to do with users, techbase? Lol, ok, that's true, I actually wanted to add it to techbase, but guess after the login I ended up on the wrong wiki and did not check that again :/ And is the script in place now? I linked it in the email to the release-team thread (why so much list hopping?), so yes. Because I am not on release-team :P I only read the request for some article here ;=) Next time you send emails there, you may awnt to add a P.S: saying you're not subscribed so people CC you on answers. Yeah, that was my fault, sorry ;=) I updated the page a bit: https://userbase.kde.org/KDE_Applications_Versioning If I get any feedback, until now, nobody touched the page, that this is OK, we should move it over to techbase, any idea for a good location there? I'd put it with the other release engineering materials, where-ever they are located... Greetings Christoph Regards, Ben -- - Dr.-Ing. Christoph Cullmann - AbsInt Angewandte Informatik GmbH Email: cullm...@absint.com Science Park 1 Tel: +49-681-38360-22 66123 Saarbrücken Fax: +49-681-38360-20 GERMANYWWW: http://www.AbsInt.com Geschäftsführung: Dr.-Ing. Christian Ferdinand Eingetragen im Handelsregister des Amtsgerichts Saarbrücken, HRB 11234
Re: KDE Applications Versioning
- Ursprüngliche Mail - El Dissabte, 11 de juliol de 2015, a les 16:59:13, Christoph Cullmann va escriure: - Ursprüngliche Mail - El Dissabte, 11 de juliol de 2015, a les 15:52:44, Christoph Cullmann va escriure: Hi, something like that? https://userbase.kde.org/KDE_Applications_Versioning I'd like to make it clearer that this is optional and maybe also an example that only uses KDE_APPLICATIONS_VERSION_MICRO Also KDE_APPLICATIONS_VERSION is not replaced at all, just MAJOR MINOR and MICRO as in the script i linked. Yeah, thats true, I just wanted to show the typical boiler plate you might want. Where to move it? userbase doesn't seem the right place for this tbh, what does it have to do with users, techbase? Lol, ok, that's true, I actually wanted to add it to techbase, but guess after the login I ended up on the wrong wiki and did not check that again :/ And is the script in place now? I linked it in the email to the release-team thread (why so much list hopping?), so yes. Because I am not on release-team :P I only read the request for some article here ;=) Next time you send emails there, you may awnt to add a P.S: saying you're not subscribed so people CC you on answers. Yeah, that was my fault, sorry ;=) I updated the page a bit: https://userbase.kde.org/KDE_Applications_Versioning If I get any feedback, until now, nobody touched the page, that this is OK, we should move it over to techbase, any idea for a good location there? Greetings Christoph -- - Dr.-Ing. Christoph Cullmann - AbsInt Angewandte Informatik GmbH Email: cullm...@absint.com Science Park 1 Tel: +49-681-38360-22 66123 Saarbrücken Fax: +49-681-38360-20 GERMANYWWW: http://www.AbsInt.com Geschäftsführung: Dr.-Ing. Christian Ferdinand Eingetragen im Handelsregister des Amtsgerichts Saarbrücken, HRB 11234
Re: KDE Applications Versioning
Hi, something like that? https://userbase.kde.org/KDE_Applications_Versioning Where to move it? And is the script in place now? Greetings Christoph - Ursprüngliche Mail - On Wed, Jul 8, 2015 at 1:24 PM, Aleix Pol aleix...@kde.org wrote: On Wed, Jul 8, 2015 at 11:43 AM, Martin Klapetek martin.klape...@gmail.com wrote: As the KDE Apps release is getting near, is this being considered/deployed? Should we be setting some CMake variables? Cheers -- Martin Klapetek | KDE Developer Yes, that's why Albert was asking for a blog/wiki documentation. ...on a release-team mailing list to which I guess most of us are not subscribed ;) Cheers -- Martin Klapetek | KDE Developer -- - Dr.-Ing. Christoph Cullmann - AbsInt Angewandte Informatik GmbH Email: cullm...@absint.com Science Park 1 Tel: +49-681-38360-22 66123 Saarbrücken Fax: +49-681-38360-20 GERMANYWWW: http://www.AbsInt.com Geschäftsführung: Dr.-Ing. Christian Ferdinand Eingetragen im Handelsregister des Amtsgerichts Saarbrücken, HRB 11234
Re: KDE Applications Versioning
El Dissabte, 11 de juliol de 2015, a les 15:52:44, Christoph Cullmann va escriure: Hi, something like that? https://userbase.kde.org/KDE_Applications_Versioning I'd like to make it clearer that this is optional and maybe also an example that only uses KDE_APPLICATIONS_VERSION_MICRO Also KDE_APPLICATIONS_VERSION is not replaced at all, just MAJOR MINOR and MICRO as in the script i linked. Where to move it? userbase doesn't seem the right place for this tbh, what does it have to do with users, techbase? And is the script in place now? I linked it in the email to the release-team thread (why so much list hopping?), so yes. Cheers, Albert Greetings Christoph - Ursprüngliche Mail - On Wed, Jul 8, 2015 at 1:24 PM, Aleix Pol aleix...@kde.org wrote: On Wed, Jul 8, 2015 at 11:43 AM, Martin Klapetek martin.klape...@gmail.com wrote: As the KDE Apps release is getting near, is this being considered/deployed? Should we be setting some CMake variables? Cheers -- Martin Klapetek | KDE Developer Yes, that's why Albert was asking for a blog/wiki documentation. ...on a release-team mailing list to which I guess most of us are not subscribed ;) Cheers -- Martin Klapetek | KDE Developer
Re: KDE Applications Versioning
- Ursprüngliche Mail - El Dissabte, 11 de juliol de 2015, a les 15:52:44, Christoph Cullmann va escriure: Hi, something like that? https://userbase.kde.org/KDE_Applications_Versioning I'd like to make it clearer that this is optional and maybe also an example that only uses KDE_APPLICATIONS_VERSION_MICRO Also KDE_APPLICATIONS_VERSION is not replaced at all, just MAJOR MINOR and MICRO as in the script i linked. Yeah, thats true, I just wanted to show the typical boiler plate you might want. Where to move it? userbase doesn't seem the right place for this tbh, what does it have to do with users, techbase? Lol, ok, that's true, I actually wanted to add it to techbase, but guess after the login I ended up on the wrong wiki and did not check that again :/ And is the script in place now? I linked it in the email to the release-team thread (why so much list hopping?), so yes. Because I am not on release-team :P I only read the request for some article here ;=) Greetings Christoph -- - Dr.-Ing. Christoph Cullmann - AbsInt Angewandte Informatik GmbH Email: cullm...@absint.com Science Park 1 Tel: +49-681-38360-22 66123 Saarbrücken Fax: +49-681-38360-20 GERMANYWWW: http://www.AbsInt.com Geschäftsführung: Dr.-Ing. Christian Ferdinand Eingetragen im Handelsregister des Amtsgerichts Saarbrücken, HRB 11234
Re: KDE Applications Versioning
On Wed, Jul 8, 2015 at 11:43 AM, Martin Klapetek martin.klape...@gmail.com wrote: As the KDE Apps release is getting near, is this being considered/deployed? Should we be setting some CMake variables? Cheers -- Martin Klapetek | KDE Developer Yes, that's why Albert was asking for a blog/wiki documentation. Aleix
Re: KDE Applications Versioning
On Wed, Jul 8, 2015 at 1:24 PM, Aleix Pol aleix...@kde.org wrote: On Wed, Jul 8, 2015 at 11:43 AM, Martin Klapetek martin.klape...@gmail.com wrote: As the KDE Apps release is getting near, is this being considered/deployed? Should we be setting some CMake variables? Cheers -- Martin Klapetek | KDE Developer Yes, that's why Albert was asking for a blog/wiki documentation. ...on a release-team mailing list to which I guess most of us are not subscribed ;) Cheers -- Martin Klapetek | KDE Developer
Re: KDE Applications Versioning
As the KDE Apps release is getting near, is this being considered/deployed? Should we be setting some CMake variables? Cheers -- Martin Klapetek | KDE Developer
Re: KDE Applications Versioning
El Dilluns, 8 de juny de 2015, a les 20:25:19, Christoph Cullmann va escriure: Hi, for frameworks, it is all very nice and automatic, the version in the CMakeLists.txt get auto-updated on each KF 5.x release. It seems to me, for the applications collection, something similar might make sense. E.g. I missed to ever update the Kate version since 5.0 and other applications like Dolphin and Konsole seem to have similar problems. Do you actually read/receive the emails we sent to kde-cvs-announce saying you need to update the versions? Cheers, Albert Would it make sense to have some we auto-define some version CMake var to KDE Application release number? For e.g. bug reports that would make all things easier. Or do I miss some magic already in place (e.g. the opensuse packages seems to have patched release numbers, at least for Konsole). Greetings Christoph
Re: KDE Applications Versioning
On Tue, Jun 9, 2015 at 11:35 AM, David Jarvie djar...@kde.org wrote: There has been debate about this for frameworks, and there is an argument there (not agreed by everybody) for making all frameworks have the same version, since framework libraries are dependencies for other software. The same arguments don't apply to applications, which in general are not dependencies. Other than convenience for maintainers who forget to update version numbers, I can see no good reason for forcing applications to have a uniform version number. I prefer using the version number to reflect the development status of the application (by use of major, minor and patch version numbers), as in the past. This makes it easier when dealing with bug reports, to know the state of the program at the version in question. For maintainers who want to use some other scheme, that's also fine. The important thing is to leave the choice. Personally I prefer having the application versions matching the release version (ie. 15.04.x) so that there is no additional versions mapping required (is version 3.4 part of KDE Applications 15.04 or 15.08 or..?). So I for one would also welcome such feature, but can absolutely relate to David's position too; the versioning should not be forced on Applications. So this could be easily made opt-in by using some predefined CMake variable and projects having such var would get the version raised by the scripts. +1 to that idea. Hi, I don't want to force people to use it, just to have always existing and updated KDE_APPLICATIONS_ variables around for people wanting to use them. And I think it makes sense to use them for a lot apps, given not many apps have any real version number updates it seems ;=) (it makes bug reports much nicer, if you can actually track the bug to some released version) Greetings Christoph -- - Dr.-Ing. Christoph Cullmann - AbsInt Angewandte Informatik GmbH Email: cullm...@absint.com Science Park 1 Tel: +49-681-38360-22 66123 Saarbrücken Fax: +49-681-38360-20 GERMANYWWW: http://www.AbsInt.com Geschäftsführung: Dr.-Ing. Christian Ferdinand Eingetragen im Handelsregister des Amtsgerichts Saarbrücken, HRB 11234
Re: KDE Applications Versioning
On Mon, June 8, 2015 11:32 pm, Aleix Pol wrote: On Mon, Jun 8, 2015 at 8:25 PM, Christoph Cullmann cullm...@absint.com wrote: Hi, for frameworks, it is all very nice and automatic, the version in the CMakeLists.txt get auto-updated on each KF 5.x release. It seems to me, for the applications collection, something similar might make sense. E.g. I missed to ever update the Kate version since 5.0 and other applications like Dolphin and Konsole seem to have similar problems. Would it make sense to have some we auto-define some version CMake var to KDE Application release number? For e.g. bug reports that would make all things easier. Or do I miss some magic already in place (e.g. the opensuse packages seems to have patched release numbers, at least for Konsole). Greetings Christoph I'd welcome such feature. I always forget to update my applications' version. Maybe it would be best to ask the release-t...@kde.org? There has been debate about this for frameworks, and there is an argument there (not agreed by everybody) for making all frameworks have the same version, since framework libraries are dependencies for other software. The same arguments don't apply to applications, which in general are not dependencies. Other than convenience for maintainers who forget to update version numbers, I can see no good reason for forcing applications to have a uniform version number. I prefer using the version number to reflect the development status of the application (by use of major, minor and patch version numbers), as in the past. This makes it easier when dealing with bug reports, to know the state of the program at the version in question. For maintainers who want to use some other scheme, that's also fine. The important thing is to leave the choice. -- David Jarvie. KDE developer. KAlarm author - http://www.astrojar.org.uk/kalarm
Re: KDE Applications Versioning
On Tue, Jun 9, 2015 at 11:35 AM, David Jarvie djar...@kde.org wrote: There has been debate about this for frameworks, and there is an argument there (not agreed by everybody) for making all frameworks have the same version, since framework libraries are dependencies for other software. The same arguments don't apply to applications, which in general are not dependencies. Other than convenience for maintainers who forget to update version numbers, I can see no good reason for forcing applications to have a uniform version number. I prefer using the version number to reflect the development status of the application (by use of major, minor and patch version numbers), as in the past. This makes it easier when dealing with bug reports, to know the state of the program at the version in question. For maintainers who want to use some other scheme, that's also fine. The important thing is to leave the choice. Personally I prefer having the application versions matching the release version (ie. 15.04.x) so that there is no additional versions mapping required (is version 3.4 part of KDE Applications 15.04 or 15.08 or..?). So I for one would also welcome such feature, but can absolutely relate to David's position too; the versioning should not be forced on Applications. So this could be easily made opt-in by using some predefined CMake variable and projects having such var would get the version raised by the scripts. +1 to that idea. Cheers -- Martin Klapetek | KDE Developer
Re: KDE Applications Versioning
On Tue, Jun 9, 2015 at 12:12 PM, Christoph Cullmann cullm...@absint.com wrote: Personally I prefer having the application versions matching the release version (ie. 15.04.x) so that there is no additional versions mapping required (is version 3.4 part of KDE Applications 15.04 or 15.08 or..?). So I for one would also welcome such feature, but can absolutely relate to David's position too; the versioning should not be forced on Applications. So this could be easily made opt-in by using some predefined CMake variable and projects having such var would get the version raised by the scripts. +1 to that idea. I also think using two different version numbers is potentially confusing to users. For Ark, we will use the Applications version from 15.08 onwards. Regards, Ragnar
KDE Applications Versioning
Hi, for frameworks, it is all very nice and automatic, the version in the CMakeLists.txt get auto-updated on each KF 5.x release. It seems to me, for the applications collection, something similar might make sense. E.g. I missed to ever update the Kate version since 5.0 and other applications like Dolphin and Konsole seem to have similar problems. Would it make sense to have some we auto-define some version CMake var to KDE Application release number? For e.g. bug reports that would make all things easier. Or do I miss some magic already in place (e.g. the opensuse packages seems to have patched release numbers, at least for Konsole). Greetings Christoph -- - Dr.-Ing. Christoph Cullmann - AbsInt Angewandte Informatik GmbH Email: cullm...@absint.com Science Park 1 Tel: +49-681-38360-22 66123 Saarbrücken Fax: +49-681-38360-20 GERMANYWWW: http://www.AbsInt.com Geschäftsführung: Dr.-Ing. Christian Ferdinand Eingetragen im Handelsregister des Amtsgerichts Saarbrücken, HRB 11234
Re: KDE Applications Versioning
On Mon, Jun 8, 2015 at 8:25 PM, Christoph Cullmann cullm...@absint.com wrote: Hi, for frameworks, it is all very nice and automatic, the version in the CMakeLists.txt get auto-updated on each KF 5.x release. It seems to me, for the applications collection, something similar might make sense. E.g. I missed to ever update the Kate version since 5.0 and other applications like Dolphin and Konsole seem to have similar problems. Would it make sense to have some we auto-define some version CMake var to KDE Application release number? For e.g. bug reports that would make all things easier. Or do I miss some magic already in place (e.g. the opensuse packages seems to have patched release numbers, at least for Konsole). Greetings Christoph -- - Dr.-Ing. Christoph Cullmann - AbsInt Angewandte Informatik GmbH Email: cullm...@absint.com Science Park 1 Tel: +49-681-38360-22 66123 Saarbrücken Fax: +49-681-38360-20 GERMANYWWW: http://www.AbsInt.com Geschäftsführung: Dr.-Ing. Christian Ferdinand Eingetragen im Handelsregister des Amtsgerichts Saarbrücken, HRB 11234 I'd welcome such feature. I always forget to update my applications' version. Maybe it would be best to ask the release-t...@kde.org? Aleix
