Details
- Reviewers
quark - Group Reviewers
Restricted Project - Commits
- rFBHGX45d4727d8a85: builddeb: remove leading "hg_" to make the Debian pkg version number valid
Diff Detail
- Repository
- rFBHGX Facebook Mercurial Extensions
- Lint
Automatic diff as part of commit; lint not applicable. - Unit
Automatic diff as part of commit; unit tests not applicable.
Event Timeline
Oh, I see what's happened: the latest tag in hg-experimental is hg_4.3.1, presumably marking when it was tested or something. Prior to that no tags had been made since 2014, so we were just getting the 0.3.1 version number.
Ideally hg-experimental would have a version number other than the hg version number. What do Facebook people think?
Internally, we don't have versioned releases - we build frequently (automation), and tend to take @ of upstream hg and our extensions when we build. There has been discussion internally (@quark should recall it) about doing a "release" whenever there's a matching Mercurial release coming out, so that people trying to use upstream Mercurial releases can use the nearest tested extensions from us.
This is to make it easier to find the matched hg-experimental version with installed hg. There were several informal requests about that.
Ideally hg-experimental would have a version number other than the hg version number. What do Facebook people think?
If we don't have to support (branch and fix) old versions, that seems okay. Is it intended to be used just in debian packaging?