Re: [Qlandkartegt-users] Release V1.13.2 and how to proceed in the future
On Mon, 16 Sep 2019 10:16:44 +0200 "Oliver Eichler" wrote: > Hi Dan > > good point. Haven't thought about the versions yet. Using a unified > version is a good idea. > > Not sure about the release? Do you need such a unified release asap > or is it ok to wait until the next real release? a new release would be nice, but I can take the 3 needed commits from git as patches as well, so please do what will fit your workflow best. Dan > Cheers > > Oliver > > > Gesendet: Montag, 16. September 2019 um 09:54 Uhr > > Von: "Dan Horák" > > An: qlandkartegt-users@lists.sourceforge.net > > Betreff: Re: [Qlandkartegt-users] Release V1.13.2 and how to > > proceed in the future > > > > Hi Oliver, > > > > On Wed, 11 Sep 2019 18:06:34 +0200 > > "Oliver Eichler" wrote: > > > > > Hi > > > > > > Now to a less pleasant topic: > > > Some of might have heard that Bitbucket drops Mercurial support. > > > Well I am not particular a huge fan of Mercurial but compared to > > > GIT it's way more easy to use. Plus it comes with a nice GUI tool > > > TortoisHg. This makes it easy even for no full time software > > > developers to use it and to contribute. That's why I favor it > > > over GIT for a project like QMapShack. > > > > now that all QMS related projects (QMapTool, ...) are in a single > > git repository and (will be) part of a single release, I have a > > question about versions. Can't we move them all (at least QMapTool) > > to follow the version number of the main project? It would simplify > > packaging in distros when eg. QMapTool is a separate subpackage > > built from the single source, like in Fedora. Another option (for > > Fedora) would be to provide eg. qmaptool-1.13.2, but the tool > > itself would report 1.1.1 in its About dialog. Fiddling with > > different versions in a single source package is confusing. > > > > Also, could you make a new release that would include the formerly > > standalone subprojects? > > > > > > Thanks, > > > > Dan > > > > > > ___ > > Qlandkartegt-users mailing list > > Qlandkartegt-users@lists.sourceforge.net > > https://lists.sourceforge.net/lists/listinfo/qlandkartegt-users > > ___ Qlandkartegt-users mailing list Qlandkartegt-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/qlandkartegt-users
Re: [Qlandkartegt-users] Release V1.13.2 and how to proceed in the future
Hi Dan good point. Haven't thought about the versions yet. Using a unified version is a good idea. Not sure about the release? Do you need such a unified release asap or is it ok to wait until the next real release? Cheers Oliver > Gesendet: Montag, 16. September 2019 um 09:54 Uhr > Von: "Dan Horák" > An: qlandkartegt-users@lists.sourceforge.net > Betreff: Re: [Qlandkartegt-users] Release V1.13.2 and how to proceed in the > future > > Hi Oliver, > > On Wed, 11 Sep 2019 18:06:34 +0200 > "Oliver Eichler" wrote: > > > Hi > > > > Now to a less pleasant topic: > > Some of might have heard that Bitbucket drops Mercurial support. Well > > I am not particular a huge fan of Mercurial but compared to GIT it's > > way more easy to use. Plus it comes with a nice GUI tool TortoisHg. > > This makes it easy even for no full time software developers to use > > it and to contribute. That's why I favor it over GIT for a project > > like QMapShack. > > now that all QMS related projects (QMapTool, ...) are in a single git > repository and (will be) part of a single release, I have a question > about versions. Can't we move them all (at least QMapTool) to follow the > version number of the main project? It would simplify packaging in > distros when eg. QMapTool is a separate subpackage built from the > single source, like in Fedora. Another option (for Fedora) would be to > provide eg. qmaptool-1.13.2, but the tool itself would report 1.1.1 in > its About dialog. Fiddling with different versions in a single source > package is confusing. > > Also, could you make a new release that would include the formerly > standalone subprojects? > > > Thanks, > > Dan > > > ___ > Qlandkartegt-users mailing list > Qlandkartegt-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/qlandkartegt-users > ___ Qlandkartegt-users mailing list Qlandkartegt-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/qlandkartegt-users
Re: [Qlandkartegt-users] Release V1.13.2 and how to proceed in the future
Up-to-now I identified 2 types of broken formatting (old friends from Bitbucket!): * Emphasis: The structures "__...__" and/or "_..._" are handled more restrictively in Github Markdown and might not work the same way as in Bitbucket. Solution: Replace with "**...**" resp. "*...*" and check modified layout. An easy script should be possible to find these constructs in the Wiki pages and to make the replacements automatically. * Indentation for sublists and/or quoted parts: Bitbucket supported/allowed here and there indentations with 2 spaces. In Github this leads to some broken formatting (sublists appear as quoted text, ...). A script should be possible for finding indentations. No idea yet, if some automated replacement could be part of such a script. The existing Wiki pages have certainly undetected formatting errors. There is obviously no need, to remove the described new errorts urgently. * TOC: would be nice to have this feature in the same form as with Bitbucket. Many Github users complain that such a feature is missing in Github. * Rainers scripts for adding headers/footers and for link checks: The scripts make use of hg commands. Most likely, there are equivalent commands for git that could be used to identify files in the repo. Wolfgang Am 12.09.2019 um 09:09 schrieb Oliver Eichler: Hi Wolfgang, as you are most familiar with the Wiki can you check this test mock-up: https://github.com/kiozen/QMapShack/wiki It would be good to have a list of issues to consider. Thanks Oliver Gesendet: Donnerstag, 12. September 2019 um 08:53 Uhr Von: "Wolfgang Thämelt" An: qlandkartegt-users Betreff: Re: [Qlandkartegt-users] Release V1.13.2 and how to proceed in the future Am 11.09.2019 um 18:06 schrieb Oliver Eichler: 2. Migrating the wiki is possible. The only thing that breaks is the TOC of each page. We need to find a solution for that. TOC isn't the only thing that breaks - some formatting breaks, too. Wolfgang ___ Qlandkartegt-users mailing list Qlandkartegt-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/qlandkartegt-users ___ Qlandkartegt-users mailing list Qlandkartegt-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/qlandkartegt-users
Re: [Qlandkartegt-users] Release V1.13.2 and how to proceed in the future
Renamed the repo to free the name for the real one https://github.com/kiozen/QMapShack_testing/wiki > Gesendet: Donnerstag, 12. September 2019 um 09:09 Uhr > Von: "Oliver Eichler" > An: k-w.thaem...@web.de > Cc: qlandkartegt-users > Betreff: Re: [Qlandkartegt-users] Release V1.13.2 and how to proceed in the > future > > Hi Wolfgang, > > as you are most familiar with the Wiki can you check this test mock-up: > > https://github.com/kiozen/QMapShack/wiki > > It would be good to have a list of issues to consider. > > Thanks > > Oliver > > > Gesendet: Donnerstag, 12. September 2019 um 08:53 Uhr > > Von: "Wolfgang Thämelt" > > An: qlandkartegt-users > > Betreff: Re: [Qlandkartegt-users] Release V1.13.2 and how to proceed in the > > future > > > > Am 11.09.2019 um 18:06 schrieb Oliver Eichler: > > > > > > > > 2. Migrating the wiki is possible. The only thing that breaks is the TOC > > > of each page. We need to find a solution for that. > > > > > > > TOC isn't the only thing that breaks - some formatting breaks, too. > > > > Wolfgang > > > > > > ___ > > Qlandkartegt-users mailing list > > Qlandkartegt-users@lists.sourceforge.net > > https://lists.sourceforge.net/lists/listinfo/qlandkartegt-users > > > > > ___ > Qlandkartegt-users mailing list > Qlandkartegt-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/qlandkartegt-users > ___ Qlandkartegt-users mailing list Qlandkartegt-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/qlandkartegt-users
Re: [Qlandkartegt-users] Release V1.13.2 and how to proceed in the future
Oliver, On Wednesday, 2019-09-11 18:06:34 +0200, you wrote: > ... > Now to a less pleasant topic: > ... > The easiest way seems to be to import the Bitbucket/Mercurial repository into > GitHub as GIT repository. And import it back to Bitbucket as a new > project. but wait! Once it is on GutHub why not using GitHub? They seem > to be a bit more professional if it comes to migrating repositories. This has recently also been discussed on the Mercurial mailing list in various threads [1],[2],[3],[4],[5],[6],[7],[8]. Solutions pointed out there include Sourcehut [9],[10], Kallithea [11], Heptapod [12], and HelixTeamHub [13]. Mind that I do not know anything about these pro- jects, I just want to share this information. Perhaps Mercurial's page about Mercurial hosting [14] might also be of interest. > ... > 2. Migrating the wiki is possible. The only thing that breaks is the TOC of > each page. We need to find a solution for that. Whould you mind elaborating on this? What Markdown dialect or version are they using? Sincerely, Rainer [1] https://www.mercurial-scm.org/pipermail/mercurial/2019-August/051403.html [2] https://www.mercurial-scm.org/pipermail/mercurial/2019-August/051410.html [3] https://www.mercurial-scm.org/pipermail/mercurial/2019-August/051416.html [4] https://www.mercurial-scm.org/pipermail/mercurial/2019-August/051438.html [5] https://www.mercurial-scm.org/pipermail/mercurial/2019-August/051447.html [6] https://www.mercurial-scm.org/pipermail/mercurial/2019-August/051455.html [7] https://www.mercurial-scm.org/pipermail/mercurial/2019-August/051489.html [8] https://www.mercurial-scm.org/pipermail/mercurial/2019-September/051529.html [9] https://sourcehut.org [10] https://hg.sr.ht/%7Esircmpwn/invertbucket [11] https://kallithea-scm.org/ [12] https://heptapod.net/ [13] https://info.perforce.com/try-perforce-helix-teamhub-free [14] https://www.mercurial-scm.org/wiki/MercurialHosting ___ Qlandkartegt-users mailing list Qlandkartegt-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/qlandkartegt-users
Re: [Qlandkartegt-users] Release V1.13.2 and how to proceed in the future
Hi Wolfgang, as you are most familiar with the Wiki can you check this test mock-up: https://github.com/kiozen/QMapShack/wiki It would be good to have a list of issues to consider. Thanks Oliver > Gesendet: Donnerstag, 12. September 2019 um 08:53 Uhr > Von: "Wolfgang Thämelt" > An: qlandkartegt-users > Betreff: Re: [Qlandkartegt-users] Release V1.13.2 and how to proceed in the > future > > Am 11.09.2019 um 18:06 schrieb Oliver Eichler: > > > > > 2. Migrating the wiki is possible. The only thing that breaks is the TOC of > > each page. We need to find a solution for that. > > > > TOC isn't the only thing that breaks - some formatting breaks, too. > > Wolfgang > > > ___ > Qlandkartegt-users mailing list > Qlandkartegt-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/qlandkartegt-users > ___ Qlandkartegt-users mailing list Qlandkartegt-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/qlandkartegt-users
Re: [Qlandkartegt-users] Release V1.13.2 and how to proceed in the future
Hi Christoph, thanks for the hint. I considered something similar to have GIT and HG in parallel. But it made the impression of generating more work. This is just a guts feeling. Maybe I reconsider if writing that tutorial turns out to be too weird to be understood by a majority.:D Migrating from GitHub to Bitbucket is of course possible. However I agree with most hg repo-owners on Bitbucket that their non existing migration support shouldn't be supported. I hope GitHub is more reliable in the future. Oliver - > Gesendet: Donnerstag, 12. September 2019 um 07:48 Uhr > Von: "Christoph Moench-Tegeder" > An: qlandkartegt-users@lists.sourceforge.net > Betreff: Re: [Qlandkartegt-users] Release V1.13.2 and how to proceed in the > future > > ## Oliver Eichler (oliver.eich...@gmx.de): > > > Now to a less pleasant topic: > > Some of might have heard that Bitbucket drops Mercurial support. Well > > I am not particular a huge fan of Mercurial but compared to GIT it's > > way more easy to use. Plus it comes with a nice GUI tool TortoisHg. > > This makes it easy even for no full time software developers to use > > it and to contribute. That's why I favor it over GIT for a project > > like QMapShack. > > For what it's worth, there's https://hg-git.github.io/, which might > make the migration much easier and help conserve workflows for > those who want to stay with mercurial. (I'm not getting into another > argument over version control systems, as I've seen way too many of > them over the years). Perhaps it's even possible to use this to just > push back everything into bitbucket's git and keep everything else? > > Regards, > Christoph > > -- > Spare Space > > > ___ > Qlandkartegt-users mailing list > Qlandkartegt-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/qlandkartegt-users > ___ Qlandkartegt-users mailing list Qlandkartegt-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/qlandkartegt-users
Re: [Qlandkartegt-users] Release V1.13.2 and how to proceed in the future
Thanks! Pushed it into the repo. > Gesendet: Mittwoch, 11. September 2019 um 19:07 Uhr > Von: "Sebastiaan Couwenberg" > An: qlandkartegt-users@lists.sourceforge.net > Betreff: Re: [Qlandkartegt-users] Release V1.13.2 and how to proceed in the > future > > The lintian QA tool reported a couple of spelling errors for the Debian > package build, fixed with the attached patch. > > Kind Regards, > > Bas > > -- > GPG Key ID: 4096R/6750F10AE88D4AF1 > Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1 > ___ > Qlandkartegt-users mailing list > Qlandkartegt-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/qlandkartegt-users > ___ Qlandkartegt-users mailing list Qlandkartegt-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/qlandkartegt-users
Re: [Qlandkartegt-users] Release V1.13.2 and how to proceed in the future
## Oliver Eichler (oliver.eich...@gmx.de): > Now to a less pleasant topic: > Some of might have heard that Bitbucket drops Mercurial support. Well > I am not particular a huge fan of Mercurial but compared to GIT it's > way more easy to use. Plus it comes with a nice GUI tool TortoisHg. > This makes it easy even for no full time software developers to use > it and to contribute. That's why I favor it over GIT for a project > like QMapShack. For what it's worth, there's https://hg-git.github.io/, which might make the migration much easier and help conserve workflows for those who want to stay with mercurial. (I'm not getting into another argument over version control systems, as I've seen way too many of them over the years). Perhaps it's even possible to use this to just push back everything into bitbucket's git and keep everything else? Regards, Christoph -- Spare Space ___ Qlandkartegt-users mailing list Qlandkartegt-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/qlandkartegt-users
[Qlandkartegt-users] Release V1.13.2 and how to proceed in the future
Hi a new release. It's more less a bug fix release as the BRouter Web API changed. Additionally a few other quirks are fixed, too. But there are at least two new features. Henri did a great job enhancing the workspace search. Now, you can weed out your geocaches or tracks in the workspace by searching for properties such as length ascent or tags. See https://bitbucket.org/maproom/qmapshack/wiki/AdvDataHandling#markdown-header-searching-data-in-the-workspace for a detailed description. And Karl added a calculator for cyclist to derive their energy consumption on the base of a recorded track. Just go to the track edit dialog and you will see the little button in the left bottom right where the track summary is shown. It expands to a quite impressive dialog with all parameters to play with. Now to a less pleasant topic: Some of might have heard that Bitbucket drops Mercurial support. Well I am not particular a huge fan of Mercurial but compared to GIT it's way more easy to use. Plus it comes with a nice GUI tool TortoisHg. This makes it easy even for no full time software developers to use it and to contribute. That's why I favor it over GIT for a project like QMapShack. I can't blame Bitbucket to drop it. But I am more than pissed by the way they do it. "We drop it in 10 month. Find out how to migrate everything on your own. Do not bother us." The easiest way seems to be to import the Bitbucket/Mercurial repository into GitHub as GIT repository. And import it back to Bitbucket as a new project. but wait! Once it is on GutHub why not using GitHub? They seem to be a bit more professional if it comes to migrating repositories. I tested it and it works out...quite well. 1. Migrating the repository is done very well preserving all important information. 2. Migrating the wiki is possible. The only thing that breaks is the TOC of each page. We need to find a solution for that. 3. Migrating the issue tracker is kind of shitty. There are scripts but they have a problem to preserve the user information for obvious reasons as most of the users are not registered by the very same nick name at GitHub. So it ends up with everything attached to anonymous or my nick. Probably I will copy manually some of the issues that I really see fit to be handled in the future. The rest will be dropped. After all most of them are ignored since ages. Not depended on GitHub but GIT the workflow will change quite a bit. It will be more professional and by that a bit harder for those not used to it. So far the policy to contribute to the project was quite sloppy. Now we have to follow something called GIT Flow. I won't exercise it to the detail but it will be more or less like that. Roughly said no one, including me, commits directly to the master or development branch. We are creating feature branches from the development branche, start a merge request and that will go to development branch. Each code contribution will need a ticket in the future that is referenced by the merge request. Only exception are documentation (wiki). And translations. Translations will be a merge request, too. But no ticket is needed. This is just to prepare you about what's coming up. Once the merge is done I hope I have the time to write a tutorial you can work with. Until this is done no new code contribution is accepted. I have to keep the repositories stable. In the meanwhile enjoy the release! Oliver V 1.13.2 [Issue #446] Advanced Filtering System [Issue #491] Skip saving of geo search [Issue #493] "Clone Waypoint and Move Clone" does not Respect Chosen Units [Issue #488] Printing Preview [Issue #494] BRouter segments download error [Issue #499] Screen overflow German localisation on a Notebook with 1.600 x 900 pixel [Issue #500] Tab order in Filter Cycle dialog is confused [Issue #498 ] BRouter setup issue (Windows) Add: Computation of "Energy Use Cycling" (consumption) for cycling tours ___ Qlandkartegt-users mailing list Qlandkartegt-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/qlandkartegt-users
