[04:08] <c107> Sawubona, #ubuntu-motu.
[04:08] <c107> Ubuntu unjani na?
[04:27] <abhi-> hi what is the convention for version numbering for building packages from git
[04:32] <RAOF> abhi-: Generally something like $LAST_VERSION+gitYYYYMMDD
[04:33] <RAOF> Optionally, adding .$SHA
[04:33] <RAOF> So, either 0.4.3+git20140723 or 0.4.3+git20140723.ab36c1f
[04:34] <ScottK> Adding the sha is common, but nonsense.
[04:34] <ScottK> Since versions have to be monotonically increasing, adding the sha doesn't mean you can package two snapshots from the same day.
[04:35] <abhi-> RAOF, ScottK thanks
[04:35] <abhi-> ScottK: so $LAST_VERSION+gitYYYYMMDD is prefered?
[04:35] <RAOF> ScottK: It can be helpful in answering the “does this package have this upstream commit in it” question, though.
[04:35] <ScottK> yes
[04:36] <ScottK> RAOF: Sounds like perfect information for the changelog
[04:36] <ScottK> For versioning, it's just clutter.
[04:37] <Unit193> Though I have seen $NEXT_VERSION~gitYYYYMMDD, oddly.
[04:37] <RAOF> That often depends on upstream's versioning.
[04:38] <RAOF> I'd do that if, for example upstream bumps their autotools version immediately after release.
[04:38] <ScottK> Unit193: That works to.  It can either be since last version (+) or before next version (~).
[04:38] <Unit193> Mhmm.
[07:08] <dholbach> good morning