Skip to content
This repository has been archived by the owner on Oct 27, 2021. It is now read-only.

Create a 4.0.6 tag #1032

Closed
TheNikomo opened this issue Feb 22, 2017 · 4 comments
Closed

Create a 4.0.6 tag #1032

TheNikomo opened this issue Feb 22, 2017 · 4 comments

Comments

@TheNikomo
Copy link

Right now 4.0.6-rc1 is shipping kicad-library tagged at 4.0.5, meaning it doesn't include any of the fixes that have been made to kicad-library since 4.0.5 release (my main gripe is PR #917 currently).

Would it be possible to create a 4.0.6 tag for kicad-library so the rc builds can package that in the installer?
The tag should be updated to point to the final change for 4.0.6 when it is released, but I do not know what commit the tag should point at before that. I don't know of a way to make a tag always point at HEAD.

@TheNikomo
Copy link
Author

Talking on #git@freenode, trying to track HEAD with a tag would be a completely idiotic idea, and apparently using tags how KiCad is using them, is also stupid. So, that's not doable. If a tag is created, it'll have to point at a commit, or be manually rewritten once in a while.

@nickoe
Copy link
Contributor

nickoe commented Feb 22, 2017

We don't really want release branches on the libraries, this is no gain for us, mostly because we can not really resolve conflicts as easuly as can be done with typical source code.

@TheNikomo
Copy link
Author

Ideal solution for problem is probably to make RC builds pull in master instead of messing around with tags on kicad-library side

@SchrodingersGat
Copy link
Contributor

4.0.6 has been tagged

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants