You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Oct 27, 2021. It is now read-only.
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.
The text was updated successfully, but these errors were encountered:
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.
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.
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.
The text was updated successfully, but these errors were encountered: