On Saturday 09 April 2016 19:02:02 Friedrich W. H. Kossebau wrote: > IIRC elsewhere I have seen people using a version called "git" in issue > trackers, which would be used by developers for random snaphots and have them > state the git commit id explicitely in the bug report.
Alternatively, one can use the version number of the last release, and still mention in the bug report the git sha-1 they are using. This seems sufficient to me. > But that makes it hard > to track regressions/new bugs between 2 versions. > > So what about some "5.xx.0-pre" version, set once the "5.(xx-1).0" is > branched? That would allow to collect regressions/new bugs in the development > phase separately, without mixing them into bugs for the last released version. Is there an actual need for this ? It seems to me that this is over-engineering it "just in case". -- David Faure, fa...@kde.org, http://www.davidfaure.fr Working on KDE Frameworks 5 _______________________________________________ Kde-frameworks-devel mailing list Kde-frameworks-devel@kde.org https://mail.kde.org/mailman/listinfo/kde-frameworks-devel
