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" <[email protected]> > An: [email protected] > 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" <[email protected]> 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 > [email protected] > https://lists.sourceforge.net/lists/listinfo/qlandkartegt-users > _______________________________________________ Qlandkartegt-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qlandkartegt-users
