| 1 |
On Sun, Sep 23, 2018, at 21:26 CDT, Kent Fredric <kentnl@g.o> wrote: |
| 2 |
|
| 3 |
> I personally try to use something of the form: |
| 4 |
> |
| 5 |
> "Bump version to 12.234.1567" |
| 6 |
> |
| 7 |
> Mostly, because it gives some vaguely useful context when reading a |
| 8 |
> commit summary log, that doesn't necessitate you running "git log -p" |
| 9 |
> or "git diff" to find out what actually changed. |
| 10 |
|
| 11 |
++ |
| 12 |
|
| 13 |
> [...] |
| 14 |
> All of this is "nice to have" stuff I'd try to gently nudge others into |
| 15 |
> the direction of, in effort to provide useful information to not only |
| 16 |
> our users, but to other developers, and our future selves looking back |
| 17 |
> in the history trying to ascertain the importance of a given version. |
| 18 |
|
| 19 |
++ |
| 20 |
|
| 21 |
> [...] |
| 22 |
> But you can imagine how I get *just* a little bit frustrated when this |
| 23 |
> is the sort of direction I'm trying to aspire towards, but what I'm |
| 24 |
> seeing on the list is debates about "bup" vs "bump" :) |
| 25 |
|
| 26 |
++ |
| 27 |
|
| 28 |
There is nothing more to add. |
| 29 |
|
| 30 |
Best, |
| 31 |
Matthias |
Archives