kicad-developers team mailing list archive

[Nick Østergaard <oe.nick@xxxxxxxxx>]

It is because of what happened in:
[Kicad-developers] Yet another 4.0.7 release bug.
https://lists.launchpad.net/kicad-developers/msg30192.html

I suspect that the script for the OSX build did not consider that tags
could move. Which I think could happen like this:

A tag will get pulled down when you pull normally. But if it changes
upstream you need to fetch with the --tags option
to sync it.

2017-11-26 20:12 GMT+01:00 Chris Pavlina <pavlina.chris@xxxxxxxxx>:

> Okay people, wtf happened here.
>
> Helping someone on IRC figure out a PDF export bug on 4.0.7, when I
> realized this:
>
> https://misc.c4757p.com/pastes/0AOyojEiEE0V.txt
>
> ^ "Tag stable release" is commit 631f6d5, on July 14. The ACTUAL 4.0.7
> tag is on 9f35e38, four commits later on August 1.
>
> Guess which one got released?
>
> Yup, we released the wrong commit for 4.0.7. The older one, missing
> several bug fixes. How did we manage to release something that wasn't
> actually tagged as 4.0.7? Doesn't the release build process involve
> something like "git checkout 4.0.7"? Help me understand what went wrong
> here...
>
> I'm still trying to figure out how a commit titled "tag stable release
> 4.0.7" and the actual 4.0.7 tag do not point at the same place, let
> alone how the release build process does not actually directly check out
> the 4.0.7 tag.
>
> --
> Chris
>
> _______________________________________________
> Mailing list: https://launchpad.net/~kicad-developers
> Post to     : kicad-developers@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp
>