Re: [Kicad-developers] 5.1.1 issue

Builds of 5.1.2 have completed on the Koji build system for Fedora Rawhide and Fedora 30. The Rawhide build will push out to the mirrors in the next few days. The F30 build will push out when F30 is released in early May. Steve On 4/22/19 5:35 PM, Wayne Stambaugh wrote: > The 5.1

Re: [Kicad-developers] 5.1.1 issue

The 5.1 branch has been tagged and pushed to lauchpad. The 5.1.2 source archive has been uploaded to as well. The 5.1.3 milestone has been created and the milestone all unfixed bugs scheduled for 5.1.2 have set to 5.1.3. I will tweak the release announcement and as soon as the most of the

Re: [Kicad-developers] 5.1.1 issue

The library is tagged with 5.1.2 (I also converted the library releases named 5.1.1 as pre release on github and added a note that that release got retracted.) On 22/04/19 14:43, Wayne Stambaugh wrote: I will tag the source repo to 5.1.2 this evening when I get home from work so please tag

Re: [Kicad-developers] 5.1.1 issue

On 4/22/2019 11:22 AM, Seth Hillbrand wrote: Am 2019-04-22 08:43, schrieb Wayne Stambaugh: I will tag the source repo to 5.1.2 this evening when I get home from work so please tag the other repos for 5.1.2 at the same commit as 5.1.1.  Hopefully we can get this version released. Can we get a

Re: [Kicad-developers] 5.1.1 issue

Am 2019-04-22 08:43, schrieb Wayne Stambaugh: I will tag the source repo to 5.1.2 this evening when I get home from work so please tag the other repos for 5.1.2 at the same commit as 5.1.1.  Hopefully we can get this version released. Can we get a 5.1.3 target on the bug tracker as well? -S

Re: [Kicad-developers] 5.1.1 issue

I will tag the source repo to 5.1.2 this evening when I get home from work so please tag the other repos for 5.1.2 at the same commit as 5.1.1.  Hopefully we can get this version released. Cheers, Wayne On 4/22/2019 1:58 AM, Rene Pöschl wrote: Is this the official decision because i can tag

Re: [Kicad-developers] 5.1.1 issue

Is this the official decision because i can tag the libraries with 5.1.2 at any time. (On the same commit as 5.1.1.) On 22/04/19 00:03, Nick Østergaard wrote: Yes, just retag the 5.1.1 tags as 5.1.2 as well. We have done that before and is probably what will have the least workload. :) On

Re: [Kicad-developers] 5.1.1 issue

Hi folks! I was able to pin Boost to the previous homebrew build and things seem to build for macOS again. I generated 5.1.1 packages, and I can even upload them, but it will be mere single-digit minutes of extra effort to spin a 5.1.2 once things are tagged again. I have a 5.0 branch nightly.

Re: [Kicad-developers] 5.1.1 issue

Hey Frank, On 4/21/19 6:33 PM, Frank Severinsen wrote: > a non-dev-lead +1 ;) LOL! > > As a small side note there is a discussion on the forum to get a V5.1 > branch "nightly" going. >

Re: [Kicad-developers] 5.1.1 issue

a non-dev-lead +1 ;) As a small side note there is a discussion on the forum to get a V5.1 branch "nightly" going. This would hopefully help avoiding bugfix enduced bugs

Re: [Kicad-developers] 5.1.1 issue

Yes, just retag the 5.1.1 tags as 5.1.2 as well. We have done that before and is probably what will have the least workload. :) On Sun, 21 Apr 2019 at 23:44, Steven A. Falco wrote: > On 4/21/19 5:18 PM, Wayne Stambaugh wrote: > > It's looks like 5.1.1 has a serious issue which was fixed and

Re: [Kicad-developers] 5.1.1 issue

On 4/21/19 5:18 PM, Wayne Stambaugh wrote: > It's looks like 5.1.1 has a serious issue which was fixed and will be > released in 5.1.2. Since folks have already started downloading 5.1.1, > I don't think changing the 5.1.1 tag is a good idea. How much trouble > would it be to spin 5.1.2 and skip

[Kicad-developers] 5.1.1 issue

It's looks like 5.1.1 has a serious issue which was fixed and will be released in 5.1.2. Since folks have already started downloading 5.1.1, I don't think changing the 5.1.1 tag is a good idea. How much trouble would it be to spin 5.1.2 and skip formally releasing 5.1.1? I'm fine if we use the