On Tue, Feb 12, 2013 at 9:32 AM, Martin Gräßlin <[email protected]> wrote: > Would a solution like introducing dedicated versions help here: maybe. It > would require each developer working with such issues to track the release > team mailing list to get the notification of a respin, the new version number > and the matching git hash. Tricky and again with lots of work. Also > problematic once the final version is created because the version information > must be exactly the same otherwise Dr.Konqui magic doesn't work.
Wouldn't much of the problem be solved if the git sha was directly appended to the version number? It wouldn't even need to be all that many digits - like 3 or 4 - since it would just need to differentiate between commits around the time of the release. Traceability would be for free. You wouldn't be able to tell which tarball of the same version but different sha was the newest, but you can't tell that currently anyways. Ian _______________________________________________ release-team mailing list [email protected] https://mail.kde.org/mailman/listinfo/release-team
