Re: kio-extras versions on Bugzilla
Placing the git commit into the executable is probably a specialty we have in KMyMoney and is not available elsewhere. It may also not be (and is not for KMyMoney) available from distro packaged versions based on tarballs. Thomas On Donnerstag, 15. Juni 2023 17:34:04 CEST Jack wrote: > I like that. > > Further question on details - I can see any bug filed against (for > example) a specific git commit is eventually fixed by a released > version. Do you consider it really filed against that version, or just > fixed in that version, which didn't actually exist at the time, and no > longer (hopefully) exhibits the bug) or against the previously released > version (where it might not exist if it was introduced by a later > commit.? There is a field for "fixed in" so I don't see any reason to > change the "filed against" version. Am I missing something? > > On 6/15/23 11:30, Nate Graham wrote: > > The inherent challenge here is that everything reported against a git > > version eventually turns into a report against a specific released > > version once that version gets released. Ideally all such bug reports > > would have the version number changed accordingly to the appropriate > > number once the release is made. But that sounds really challenging to > > do. > > > > In the absence of that, maybe just "git stable branch" and "git master > > branch"? > > > > Nate > > > > > > On 6/15/23 09:14, Jack wrote: > >> I'll also ask what to do for reporting against head of a git branch > >> other than master? For programs that have a release or stable branch > >> (often named for the release number) there is a big difference > >> between head of that branch and git master. For example, KMyMoney > >> has 5.1 branch. Unfortunately, I don't know if there is any way for > >> this naming to be consistent across applications and frameworks and > >> unless something like "git production branch." > >> > >> Thoughts? > >> > >> On 6/15/23 09:26, Nate Graham wrote: > >>> My preference would be for "git master" but I'll gladly go with any > >>> alternative consensus. What I think matters more is to get > >>> *something* standardized. > >>> > >>> Nate > >>> > >>> > >>> On 6/15/23 00:52, Heiko Becker wrote: > >>>>> On 6/14/23 20:15, Justin Zobel wrote: > >>>>>> I asked Nate but he said versions on Bugzilla are added by a script. > >>>>>> > >>>>>> Can you please add git-master as a version for kio-extras on > >>>>>> Bugzilla > >>>>>> on your next batch of updates, thank you. > >>>> > >>>> On Thursday, 15 June 2023 04:17:09 CEST, Nate Graham wrote: > >>>>> ...And while we're doing this, maybe we can coordinate on a > >>>>> consistent name for it. I see we use "master", "git master" and > >>>>> "git-master" in various different places. > >>>> > >>>> While it's true that a script is used to add Gear versions to > >>>> Bugzilla, it reads those versions from CMake's project(). So it'll > >>>> not be useful without a bit of hacking, once we decide on a > >>>> consistent name. > >>>> > >>>> Regards, > >>>> Heiko > >>>> > >>>> > >>>> > > -- Regards Thomas Baumgart - You cannot strengthen the weak by weakening the strong. - signature.asc Description: This is a digitally signed message part.
Re: No 22.12.1 tag for colord-kde
Justin, On Donnerstag, 5. Januar 2023 11:18:01 CET Justin Zobel wrote: > Apologies. I thought tags existed before the tarballs. Thanks Heiko! Not according to https://community.kde.org/ReleasingSoftware steps 6 through 8 > On 5/1/23 20:33, Heiko Becker wrote: > > On Thursday, 5 January 2023 03:36:43 CET, Justin wrote: > >> Just a friendly ping :) > >> https://invent.kde.org/graphics/colord-kde/-/tags > > > > Patience :-) The tarballs are not public yet and for that reason the > > tags aren't public as well. > > > > Regards, > > Heiko -- Regards Thomas Baumgart - UTF-8 Test: The ran after a , but the ran away. - signature.asc Description: This is a digitally signed message part.
Re: Review Request: Add git support to kdesdk: create_tarball.rb
--- This is an automatically generated e-mail. To reply, visit: http://svn.reviewboard.kde.org/r/6842/#review10493 --- Test with the following settings in the config.ini here and ran it with '-a kmymoney' as option: The current stable version [kmymoney] gitModule= yes gitTag = 4.6.1 mainmodule = branches/stable/extragear-kde4 l10nmodule = extragear-office l10npath = branches/stable submodule= office kde_release = no docs = yes docpath = kmymoney/doc translations = yes version = 4.6.1 and the development version [kmymoney] gitModule= yes mainmodule = extragear submodule= office kde_release = no docs = yes translations = yes version = 4.6.90 and it looks good so far (except that the docs won't build) trunk/KDE/kdesdk/scripts/createtarball/create_tarball.rb http://svn.reviewboard.kde.org/r/6842/#comment12416 Is there a specific reason why you don't add the doc subdirectory for stuff fetched from git? - Thomas Baumgart On Nov. 29, 2011, 4:42 p.m., Kåre Särs wrote: --- This is an automatically generated e-mail. To reply, visit: http://svn.reviewboard.kde.org/r/6842/ --- (Updated Nov. 29, 2011, 4:42 p.m.) Review request for kdelibs and Release Team. Description --- This patch adds git support to create_tarball.rb in kdesdk. The patch adds two options to the ini file. The first one (gitModule) indicates that the module is located in git and the second optional parameter (gitTag) defines which tag to use for creating the release. (there is no group for kdesdk or extragear) Diffs - trunk/KDE/kdesdk/scripts/createtarball/config.ini 1266277 trunk/KDE/kdesdk/scripts/createtarball/create_tarball.rb 1266277 Diff: http://svn.reviewboard.kde.org/r/6842/diff/diff Testing --- Thanks, Kåre Särs ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team
Re: Review Request: Add git support to kdesdk: create_tarball.rb
On Nov. 30, 2011, 6:01 p.m., Thomas Baumgart wrote: trunk/KDE/kdesdk/scripts/createtarball/create_tarball.rb, line 443 http://svn.reviewboard.kde.org/r/6842/diff/1/?file=47267#file47267line443 Is there a specific reason why you don't add the doc subdirectory for stuff fetched from git? Kåre Särs wrote: The git modules I have checked, have the non-translated documents in the git repo and the directory already added in the CMakeLists.txt. I take it that, that is the standard :) So the documentation should actually be built. Apologies, you're right. KMyMoney is the culprit. We just did not update to the newer layout since we came into git from svn. - Thomas --- This is an automatically generated e-mail. To reply, visit: http://svn.reviewboard.kde.org/r/6842/#review10493 --- On Nov. 29, 2011, 4:42 p.m., Kåre Särs wrote: --- This is an automatically generated e-mail. To reply, visit: http://svn.reviewboard.kde.org/r/6842/ --- (Updated Nov. 29, 2011, 4:42 p.m.) Review request for kdelibs and Release Team. Description --- This patch adds git support to create_tarball.rb in kdesdk. The patch adds two options to the ini file. The first one (gitModule) indicates that the module is located in git and the second optional parameter (gitTag) defines which tag to use for creating the release. (there is no group for kdesdk or extragear) Diffs - trunk/KDE/kdesdk/scripts/createtarball/config.ini 1266277 trunk/KDE/kdesdk/scripts/createtarball/create_tarball.rb 1266277 Diff: http://svn.reviewboard.kde.org/r/6842/diff/diff Testing --- Thanks, Kåre Särs ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team
