Re: [Kicad-developers] 5.0.2 stable release.

[Rene Pöschl]

The libs are now tagged.

On 03/12/18 13:49, Wayne Stambaugh wrote:

I saw that the translation and doc repos were tagged for 5.0.2.  Where
do we stand on the library repos?

On 11/26/2018 6:49 PM, Evan Shultz wrote:

I should have also mentioned that the outstanding items milestoned for
5.0.2 are actual fixes which we would like to include. We've been
careful not to pushing breaking changes flippantly so tagging the head
of each library should be safe and an improvement. Breaking changes
haven't been intentionally made since 5.0.0 unless it was to fix an
issue that might ruin a design (wrong pinout, footprint pins swapped, etc.).

On Mon, Nov 26, 2018 at 3:08 PM Evan Shultz mailto:evan.shu...@gmail.com>> wrote:

 Yay!

 We (librarians) have a few outstanding items in the library we want
 to close before 5.0.2, but it should only be a couple of days and
 well within the one week timeline you requested. Thanks mostly to
 Antonio, we're now using the milestone feature of GH so you can see
 what's left at https://github.com/KiCad/kicad-symbols/milestone/6
 and https://github.com/KiCad/kicad-footprints/milestone/1 (for
 symbols and footprints, at least).

 On Mon, Nov 26, 2018 at 3:05 PM Wayne Stambaugh
 mailto:stambau...@gmail.com>> wrote:

 I just tagged and pushed 5.0.2 so we need to decide what we want
 to do
 about tagging the library and translation repos.  Rene, any
 thoughts on
 the library repos.  I know there have been a lot of changes
 since 5.0.1
 but as long as the existing symbols have changed too
 significantly, I'm
 fine with tagging the current head of each library.

 On 11/26/2018 5:55 PM, Nick Østergaard wrote:
 > Are we expecting to tag 5.0.1 as 5.0.2 for the libraries or are we
 > getting a minor library update as well?
 > On Mon, 26 Nov 2018 at 20:32, Wayne Stambaugh
 mailto:stambau...@gmail.com>> wrote:
 >>
 >> I just noticed a few last minute changes were made to the 5.0
 branch.
 >> Is there anything else pending or am I good to go with
 tagging 5.0.2?
 >>
 >> Cheers,
 >>
 >> Wayne
 >>
 >> On 11/25/2018 2:01 PM, Wayne Stambaugh wrote:
 >>> I plan on tagging 5.0.2 tomorrow unless is a show stopper
 bug that I am
 >>> not aware of.  My goal is to give the library, doc, and
 translations a
 >>> week to get tagged for 5.0.2 and another week for the
 installers to get
 >>> built so I can make the release announcement on 12/9.
 Please let me
 >>> know if this doesn't fit into your schedule so we can make
 other plans.
 >>>
 >>> Once 5.0.2 is released, I would like to string freeze the
 development
 >>> branch to start getting ready of 5.1 release candidates by
 the beginning
 >>> of the year.  If you have any UI string changes that you are
 planning to
 >>> make, now would be a good time.
 >>>
 >>> Thank you again everyone for your hard work.  KiCad continues to
 >>> steadily improve due to your efforts.
 >>>
 >>> Cheers,
 >>>
 >>> Wayne
 >>>
 >>
 >> ___
 >> Mailing list: https://launchpad.net/~kicad-developers
 >> Post to     : kicad-developers@lists.launchpad.net
 
 >> Unsubscribe : https://launchpad.net/~kicad-developers
 >> More help   : https://help.launchpad.net/ListHelp

 ___
 Mailing list: https://launchpad.net/~kicad-developers
 Post to     : kicad-developers@lists.launchpad.net
 
 Unsubscribe : https://launchpad.net/~kicad-developers
 More help   : https://help.launchpad.net/ListHelp


___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp




___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] Filling Zones with the Kicad 5 python API

[Seth Hillbrand]

Hi Laen (and others interested)-

There was a recent bug report (https://bugs.launchpad.net/kicad/+bug/1806506)
that showed an issue with the proposed minimal script below.  Specifically,
this did not include net classes in the data before filling.  This can lead
to incorrect boards when generating from kicad_pcb files.

To correct the script, you will need to load the net classes prior to
filling like this:

import pcbnew
board = pcbnew.GetBoard()
board.BuildListOfNets()
board.SynchronizeNetsAndNetClasses()
filler = pcbnew.ZONE_FILLER(board)
zones = board.Zones()
filler.Fill(zones)

This will be done automatically in 5.1 but will need to be explicitly
called in 5.0.1

Best-
Seth

Am Mi., 8. Aug. 2018 um 14:15 Uhr schrieb James Neal :

> Building now!  Thanks!!
>
> On Wed, Aug 8, 2018 at 1:27 PM Seth Hillbrand  wrote:
>
>> Hi Laen-
>>
>> If you are compiling yourself, you can grab the v5 branch here:
>> git clone -b 5.0 https://git.launchpad.net/kicad
>>
>> The latest commit should have re-
>> enabled zone filling as I described.
>>
>> Best-
>> Seth
>>
>> Am Mi., 8. Aug. 2018 um 13:22 Uhr schrieb James Neal :
>>
>>> Awesome!  This is the last thing standing in the way of us supporting
>>> Native Kicad 5 uploads. :)
>>>
>>> We'll take a stab at adding it to the python SWIG.
>>>
>>> -Laen
>>>
>>> On Wed, Aug 8, 2018 at 12:25 PM Seth Hillbrand 
>>> wrote:
>>>
 Hi Laen-

 Unfortunately, zone filling was factored out into a second file in Dec
 2017 and it looks like you are the first person to note that the python
 SWIG includes did not update with it.  So, at the moment, KiCad v5 doesn't
 have a zone fill command in python.  I'll see about updating that for
 v5.0.1.

 Once we fix this, the python command will change as we now have a
 dedicated zone_filler class.  The calling structure will also change.  The
 following will be the new routine to achieve this:

 import pcbnew
 board = pcbnew.GetBoard()
 filler = pcbnew.ZONE_FILLER(board)
 zones = board.Zones()
 filler.Fill(zones)


 -Seth

 Am Mi., 8. Aug. 2018 um 11:30 Uhr schrieb James Neal >>> >:

> Hey!
>
> We use the kicad python library to CAM boards for manufacturing.   One
> of the big issues we see in customer uploads is they fail to fill zones
> before saving the file, so we use this function:
>
>   def __Fill_All_Zones(self):
> # Kicad doesn't refresh ground pours automatically during plotting
> # This can lead to unusual errors if minor adjustments were made,
> # and the designer didn't manually refresh.
> # This glorious function added thanks to Adam Wolf
> for zone_index in xrange(0, self.board.GetAreaCount()):
>   zone = self.board.GetArea(zone_index)
>   if not zone.GetIsKeepout():
> #__Fill_Zone(self.board, zone)
> zone.ClearFilledPolysList();
> zone.UnFill();
> if zone.GetIsKeepout():
> return
> zone.BuildFilledSolidAreasPolygons(self.board);
> zone.SetIsFilled(True)
>
> It looks like zone.BuildFilledSolidAreasPolygons has been removed in
> the KiCAD 5 python API.  Was it replaced with something else, or is there 
> a
> new way to do this?
>
> Thanks!
> -Laen
> OSH Park
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp
>

___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

[Kicad-developers] Jenkins build is back to normal : linux-kicad-full-gcc-head #4374

[Miguel Angel Ajo]

See 



___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

[Kicad-developers] Build failed in Jenkins: linux-kicad-full-gcc-head #4373

[Miguel Angel Ajo]

See 


Changes:

[jean-pierre charras] Pcbnew: Partial revert of commit

--
[...truncated 152.82 KB...]
[ 86%] Building CXX object 
pagelayout_editor/CMakeFiles/pl_editor_kiface.dir/__/common/page_info.cpp.o
[ 86%] Building CXX object 
pcb_calculator/CMakeFiles/pcb_calculator_kiface.dir/params_read_write.cpp.o
[ 86%] Linking CXX shared module _pl_editor.kiface
[ 87%] Building CXX object 
pcbnew/CMakeFiles/pcbnew_kiface_objects.dir/tools/pcb_selection_conditions.cpp.o
[ 87%] Building CXX object 
pcb_calculator/CMakeFiles/pcb_calculator_kiface.dir/pcb_calculator_frame.cpp.o
[ 87%] Building CXX object eeschema/CMakeFiles/eeschema_kiface.dir/erc.cpp.o
[ 87%] Building CXX object 
pcb_calculator/CMakeFiles/pcb_calculator_kiface.dir/datafile_read_write.cpp.o
[ 87%] Building CXX object 
pcbnew/CMakeFiles/pcbnew_kiface_objects.dir/tools/pcb_tool.cpp.o
[ 87%] Building CXX object 
eeschema/CMakeFiles/eeschema_kiface.dir/events_called_functions_for_edit.cpp.o
[ 87%] Building CXX object 
pcb_calculator/CMakeFiles/pcb_calculator_kiface.dir/regulators_funct.cpp.o
[ 87%] Built target pl_editor_kiface
[ 87%] Building CXX object 
pcbnew/CMakeFiles/pcbnew_kiface_objects.dir/tools/pcbnew_control.cpp.o
[ 87%] Building CXX object 
eeschema/CMakeFiles/eeschema_kiface.dir/fields_grid_table.cpp.o
[ 87%] Building CXX object 
pcbnew/CMakeFiles/pcbnew_kiface_objects.dir/tools/picker_tool.cpp.o
[ 87%] Building CXX object 
pcb_calculator/CMakeFiles/pcb_calculator_kiface.dir/tracks_width_versus_current.cpp.o
[ 87%] Building CXX object 
pcb_calculator/CMakeFiles/pcb_calculator_kiface.dir/transline_ident.cpp.o
[ 87%] Building CXX object 
eeschema/CMakeFiles/eeschema_kiface.dir/files-io.cpp.o
[ 87%] Building CXX object 
pcb_calculator/CMakeFiles/pcb_calculator_kiface.dir/UnitSelector.cpp.o
[ 87%] Building CXX object 
pcb_calculator/CMakeFiles/pcb_calculator_kiface.dir/pcb_calculator_datafile_keywords.cpp.o
[ 87%] Building CXX object 
pcb_calculator/CMakeFiles/pcb_calculator_kiface.dir/transline/transline.cpp.o
[ 87%] Building CXX object 
pcb_calculator/CMakeFiles/pcb_calculator_kiface.dir/transline/c_microstrip.cpp.o
[ 87%] Building CXX object 
pcbnew/CMakeFiles/pcbnew_kiface_objects.dir/tools/placement_tool.cpp.o
[ 87%] Building CXX object 
pcbnew/CMakeFiles/pcbnew_kiface_objects.dir/tools/point_editor.cpp.o
[ 87%] Building CXX object 
pcb_calculator/CMakeFiles/pcb_calculator_kiface.dir/transline/microstrip.cpp.o
[ 87%] Building CXX object eeschema/CMakeFiles/eeschema_kiface.dir/find.cpp.o
[ 87%] Building CXX object 
pcb_calculator/CMakeFiles/pcb_calculator_kiface.dir/transline/coplanar.cpp.o
[ 87%] Building CXX object 
pcb_calculator/CMakeFiles/pcb_calculator_kiface.dir/transline/coax.cpp.o
[ 87%] Building CXX object 
pcb_calculator/CMakeFiles/pcb_calculator_kiface.dir/transline/rectwaveguide.cpp.o
[ 87%] Building CXX object 
pcb_calculator/CMakeFiles/pcb_calculator_kiface.dir/transline/stripline.cpp.o
[ 88%] Building CXX object 
pcb_calculator/CMakeFiles/pcb_calculator_kiface.dir/transline/twistedpair.cpp.o
[ 88%] Building CXX object 
pcb_calculator/CMakeFiles/pcb_calculator_kiface.dir/transline_dlg_funct.cpp.o
[ 88%] Building CXX object 
pcbnew/CMakeFiles/pcbnew_kiface_objects.dir/tools/position_relative_tool.cpp.o
[ 88%] Building CXX object 
pcbnew/CMakeFiles/pcbnew_kiface_objects.dir/tools/selection.cpp.o
[ 88%] Building CXX object 
pcb_calculator/CMakeFiles/pcb_calculator_kiface.dir/attenuators/attenuator_classes.cpp.o
[ 88%] Building CXX object 
eeschema/CMakeFiles/eeschema_kiface.dir/generate_alias_info.cpp.o
[ 88%] Building CXX object 
pcb_calculator/CMakeFiles/pcb_calculator_kiface.dir/dialogs/pcb_calculator_frame_base.cpp.o
[ 88%] Building CXX object 
pcb_calculator/CMakeFiles/pcb_calculator_kiface.dir/dialogs/dialog_regulator_data_base.cpp.o
[ 88%] Building CXX object eeschema/CMakeFiles/eeschema_kiface.dir/getpart.cpp.o
[ 88%] Building CXX object 
eeschema/CMakeFiles/eeschema_kiface.dir/hierarch.cpp.o
[ 88%] Building CXX object 
pcbnew/CMakeFiles/pcbnew_kiface_objects.dir/tools/selection_tool.cpp.o
[ 88%] Linking CXX shared module _pcb_calculator.kiface
[ 89%] Building CXX object 
eeschema/CMakeFiles/eeschema_kiface.dir/highlight_connection.cpp.o
[ 89%] Building CXX object eeschema/CMakeFiles/eeschema_kiface.dir/hotkeys.cpp.o
[ 89%] Built target pcb_calculator_kiface
Scanning dependencies of target s3d_plugin_idf
[ 89%] Building CXX object 
plugins/3d/idf/CMakeFiles/s3d_plugin_idf.dir/s3d_plugin_idf.cpp.o
[ 89%] Building CXX object 
pcbnew/CMakeFiles/pcbnew_kiface_objects.dir/tools/tool_event_utils.cpp.o
[ 89%] Building CXX object eeschema/CMakeFiles/eeschema_kiface.dir/lib_arc.cpp.o
[ 89%] Building CXX object 
plugins/3d/idf/CMakeFiles/s3d_plugin_idf.dir/__/__/__/utils/idftools/vrml_layer.cpp.o
[ 89%] Building CXX object 
eeschema/CMakeFiles/eeschema_kiface.dir/lib_bezier.cpp.o
[ 89%] Linking CXX 

Re: [Kicad-developers] 5.0.2 stable release.

[Rene Pöschl]

I am a bit out of the loop sadly as i had quite a busy month behind me 
(new job plus some old responsibilities)


I created an issue over at the symbol repo. [1] Both to ask the other 
librarians and for a place to report design breaking changes. (A few 
symbols have been changed since 5.0.1 it seems.)
If there are no objections then i will tag tomorrow morning before i go 
to work (~06:45 CET)
A word of warning: My internet seems to be a bit unstable. If i do not 
tag tomorrow then it might have been broken completely.


[1]: https://github.com/KiCad/kicad-symbols/issues/1213

On 03/12/18 13:49, Wayne Stambaugh wrote:

I saw that the translation and doc repos were tagged for 5.0.2.  Where
do we stand on the library repos?

On 11/26/2018 6:49 PM, Evan Shultz wrote:

I should have also mentioned that the outstanding items milestoned for
5.0.2 are actual fixes which we would like to include. We've been
careful not to pushing breaking changes flippantly so tagging the head
of each library should be safe and an improvement. Breaking changes
haven't been intentionally made since 5.0.0 unless it was to fix an
issue that might ruin a design (wrong pinout, footprint pins swapped, etc.).

On Mon, Nov 26, 2018 at 3:08 PM Evan Shultz mailto:evan.shu...@gmail.com>> wrote:

 Yay!

 We (librarians) have a few outstanding items in the library we want
 to close before 5.0.2, but it should only be a couple of days and
 well within the one week timeline you requested. Thanks mostly to
 Antonio, we're now using the milestone feature of GH so you can see
 what's left at https://github.com/KiCad/kicad-symbols/milestone/6
 and https://github.com/KiCad/kicad-footprints/milestone/1 (for
 symbols and footprints, at least).

 On Mon, Nov 26, 2018 at 3:05 PM Wayne Stambaugh
 mailto:stambau...@gmail.com>> wrote:

 I just tagged and pushed 5.0.2 so we need to decide what we want
 to do
 about tagging the library and translation repos.  Rene, any
 thoughts on
 the library repos.  I know there have been a lot of changes
 since 5.0.1
 but as long as the existing symbols have changed too
 significantly, I'm
 fine with tagging the current head of each library.

 On 11/26/2018 5:55 PM, Nick Østergaard wrote:
 > Are we expecting to tag 5.0.1 as 5.0.2 for the libraries or are we
 > getting a minor library update as well?
 > On Mon, 26 Nov 2018 at 20:32, Wayne Stambaugh
 mailto:stambau...@gmail.com>> wrote:
 >>
 >> I just noticed a few last minute changes were made to the 5.0
 branch.
 >> Is there anything else pending or am I good to go with
 tagging 5.0.2?
 >>
 >> Cheers,
 >>
 >> Wayne
 >>
 >> On 11/25/2018 2:01 PM, Wayne Stambaugh wrote:
 >>> I plan on tagging 5.0.2 tomorrow unless is a show stopper
 bug that I am
 >>> not aware of.  My goal is to give the library, doc, and
 translations a
 >>> week to get tagged for 5.0.2 and another week for the
 installers to get
 >>> built so I can make the release announcement on 12/9.
 Please let me
 >>> know if this doesn't fit into your schedule so we can make
 other plans.
 >>>
 >>> Once 5.0.2 is released, I would like to string freeze the
 development
 >>> branch to start getting ready of 5.1 release candidates by
 the beginning
 >>> of the year.  If you have any UI string changes that you are
 planning to
 >>> make, now would be a good time.
 >>>
 >>> Thank you again everyone for your hard work.  KiCad continues to
 >>> steadily improve due to your efforts.
 >>>
 >>> Cheers,
 >>>
 >>> Wayne
 >>>
 >>
 >> ___
 >> Mailing list: https://launchpad.net/~kicad-developers
 >> Post to     : kicad-developers@lists.launchpad.net
 
 >> Unsubscribe : https://launchpad.net/~kicad-developers
 >> More help   : https://help.launchpad.net/ListHelp

 ___
 Mailing list: https://launchpad.net/~kicad-developers
 Post to     : kicad-developers@lists.launchpad.net
 
 Unsubscribe : https://launchpad.net/~kicad-developers
 More help   : https://help.launchpad.net/ListHelp


___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp




___
Mailing list: 

Re: [Kicad-developers] 5.0.2 stable release.

[Steven A. Falco]

It downloaded fine from the url I posted earlier.  Thanks!

Steve

On 12/3/18 1:15 PM, Wayne Stambaugh wrote:
> Hey Steve,
> 
> I went ahead and pushed the source archive so you should be able to
> download it now.  You will still have to wait for the library repos to
> get tagged but I'm guessing the are packaged separately on most if not
> all linux distros.
> 
> Cheers,
> 
> Wayne
> 
> On 12/3/2018 12:05 PM, Steven A. Falco wrote:
>> The link is based on what I was using for 5.0.0, 5.0.1, etc.  I'd guess that 
>> as soon as you upload the source archive, the link will start working.
>>
>> Once I see your release announcement, I'll start the process of building the 
>> official Fedora packages.
>>
>>  Steve
>>
>> On 12/3/18 11:24 AM, Wayne Stambaugh wrote:
>>> Hey Steve,
>>>
>>> I have not posted the source archive yet.  I'm not sure where the link
>>> you are using came from.  I will post the source archive at the same
>>> time I make the release announcement.  This gives the installer devs a
>>> chance to get the build servers updated and the installers uploaded to
>>> the website.  As soon as the library devs get the library repos tagged,
>>> it shouldn't take more than a week to get most of the installers built.
>>>  My goal is to make the release announcement this weekend.
>>>
>>> Cheers,
>>>
>>> Wayne
>>>
>>> On 12/3/2018 11:15 AM, Steven A. Falco wrote:
 I see that the source code was tagged with 5.0.2, but I get a 404 when I 
 try to download the tar via:

 https://launchpad.net/kicad/5.0/5.0.2/+download/kicad-5.0.2.tar.xz

 Is that the correct link?  Has the tar been posted yet?

Thanks,
Steve


 On 12/3/18 7:49 AM, Wayne Stambaugh wrote:
> I saw that the translation and doc repos were tagged for 5.0.2.  Where
> do we stand on the library repos?
>
> On 11/26/2018 6:49 PM, Evan Shultz wrote:
>> I should have also mentioned that the outstanding items milestoned for
>> 5.0.2 are actual fixes which we would like to include. We've been
>> careful not to pushing breaking changes flippantly so tagging the head
>> of each library should be safe and an improvement. Breaking changes
>> haven't been intentionally made since 5.0.0 unless it was to fix an
>> issue that might ruin a design (wrong pinout, footprint pins swapped, 
>> etc.).
>>
>> On Mon, Nov 26, 2018 at 3:08 PM Evan Shultz > > wrote:
>>
>> Yay!
>>
>> We (librarians) have a few outstanding items in the library we want
>> to close before 5.0.2, but it should only be a couple of days and
>> well within the one week timeline you requested. Thanks mostly to
>> Antonio, we're now using the milestone feature of GH so you can see
>> what's left at https://github.com/KiCad/kicad-symbols/milestone/6
>> and https://github.com/KiCad/kicad-footprints/milestone/1 (for
>> symbols and footprints, at least).
>>
>> On Mon, Nov 26, 2018 at 3:05 PM Wayne Stambaugh
>> mailto:stambau...@gmail.com>> wrote:
>>
>> I just tagged and pushed 5.0.2 so we need to decide what we want
>> to do
>> about tagging the library and translation repos.  Rene, any
>> thoughts on
>> the library repos.  I know there have been a lot of changes
>> since 5.0.1
>> but as long as the existing symbols have changed too
>> significantly, I'm
>> fine with tagging the current head of each library.
>>
>> On 11/26/2018 5:55 PM, Nick Østergaard wrote:
>> > Are we expecting to tag 5.0.1 as 5.0.2 for the libraries or 
>> are we
>> > getting a minor library update as well?
>> > On Mon, 26 Nov 2018 at 20:32, Wayne Stambaugh
>> mailto:stambau...@gmail.com>> wrote:
>> >>
>> >> I just noticed a few last minute changes were made to the 5.0
>> branch.
>> >> Is there anything else pending or am I good to go with
>> tagging 5.0.2?
>> >>
>> >> Cheers,
>> >>
>> >> Wayne
>> >>
>> >> On 11/25/2018 2:01 PM, Wayne Stambaugh wrote:
>> >>> I plan on tagging 5.0.2 tomorrow unless is a show stopper
>> bug that I am
>> >>> not aware of.  My goal is to give the library, doc, and
>> translations a
>> >>> week to get tagged for 5.0.2 and another week for the
>> installers to get
>> >>> built so I can make the release announcement on 12/9. 
>> Please let me
>> >>> know if this doesn't fit into your schedule so we can make
>> other plans.
>> >>>
>> >>> Once 5.0.2 is released, I would like to string freeze the
>> development

[Kicad-developers] Jenkins build is back to normal : linux-kicad-full-gcc-head #4371

[Miguel Angel Ajo]

See 



___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] 5.0.2 stable release.

[Wayne Stambaugh]

Hey Steve,

I went ahead and pushed the source archive so you should be able to
download it now.  You will still have to wait for the library repos to
get tagged but I'm guessing the are packaged separately on most if not
all linux distros.

Cheers,

Wayne

On 12/3/2018 12:05 PM, Steven A. Falco wrote:
> The link is based on what I was using for 5.0.0, 5.0.1, etc.  I'd guess that 
> as soon as you upload the source archive, the link will start working.
> 
> Once I see your release announcement, I'll start the process of building the 
> official Fedora packages.
> 
>   Steve
> 
> On 12/3/18 11:24 AM, Wayne Stambaugh wrote:
>> Hey Steve,
>>
>> I have not posted the source archive yet.  I'm not sure where the link
>> you are using came from.  I will post the source archive at the same
>> time I make the release announcement.  This gives the installer devs a
>> chance to get the build servers updated and the installers uploaded to
>> the website.  As soon as the library devs get the library repos tagged,
>> it shouldn't take more than a week to get most of the installers built.
>>  My goal is to make the release announcement this weekend.
>>
>> Cheers,
>>
>> Wayne
>>
>> On 12/3/2018 11:15 AM, Steven A. Falco wrote:
>>> I see that the source code was tagged with 5.0.2, but I get a 404 when I 
>>> try to download the tar via:
>>>
>>> https://launchpad.net/kicad/5.0/5.0.2/+download/kicad-5.0.2.tar.xz
>>>
>>> Is that the correct link?  Has the tar been posted yet?
>>>
>>> Thanks,
>>> Steve
>>>
>>>
>>> On 12/3/18 7:49 AM, Wayne Stambaugh wrote:
 I saw that the translation and doc repos were tagged for 5.0.2.  Where
 do we stand on the library repos?

 On 11/26/2018 6:49 PM, Evan Shultz wrote:
> I should have also mentioned that the outstanding items milestoned for
> 5.0.2 are actual fixes which we would like to include. We've been
> careful not to pushing breaking changes flippantly so tagging the head
> of each library should be safe and an improvement. Breaking changes
> haven't been intentionally made since 5.0.0 unless it was to fix an
> issue that might ruin a design (wrong pinout, footprint pins swapped, 
> etc.).
>
> On Mon, Nov 26, 2018 at 3:08 PM Evan Shultz  > wrote:
>
> Yay!
>
> We (librarians) have a few outstanding items in the library we want
> to close before 5.0.2, but it should only be a couple of days and
> well within the one week timeline you requested. Thanks mostly to
> Antonio, we're now using the milestone feature of GH so you can see
> what's left at https://github.com/KiCad/kicad-symbols/milestone/6
> and https://github.com/KiCad/kicad-footprints/milestone/1 (for
> symbols and footprints, at least).
>
> On Mon, Nov 26, 2018 at 3:05 PM Wayne Stambaugh
> mailto:stambau...@gmail.com>> wrote:
>
> I just tagged and pushed 5.0.2 so we need to decide what we want
> to do
> about tagging the library and translation repos.  Rene, any
> thoughts on
> the library repos.  I know there have been a lot of changes
> since 5.0.1
> but as long as the existing symbols have changed too
> significantly, I'm
> fine with tagging the current head of each library.
>
> On 11/26/2018 5:55 PM, Nick Østergaard wrote:
> > Are we expecting to tag 5.0.1 as 5.0.2 for the libraries or are 
> we
> > getting a minor library update as well?
> > On Mon, 26 Nov 2018 at 20:32, Wayne Stambaugh
> mailto:stambau...@gmail.com>> wrote:
> >>
> >> I just noticed a few last minute changes were made to the 5.0
> branch.
> >> Is there anything else pending or am I good to go with
> tagging 5.0.2?
> >>
> >> Cheers,
> >>
> >> Wayne
> >>
> >> On 11/25/2018 2:01 PM, Wayne Stambaugh wrote:
> >>> I plan on tagging 5.0.2 tomorrow unless is a show stopper
> bug that I am
> >>> not aware of.  My goal is to give the library, doc, and
> translations a
> >>> week to get tagged for 5.0.2 and another week for the
> installers to get
> >>> built so I can make the release announcement on 12/9. 
> Please let me
> >>> know if this doesn't fit into your schedule so we can make
> other plans.
> >>>
> >>> Once 5.0.2 is released, I would like to string freeze the
> development
> >>> branch to start getting ready of 5.1 release candidates by
> the beginning
> >>> of the year.  If you have any UI string changes that you are
> planning to
> >>> make, now 

Re: [Kicad-developers] [PATCH] Documentation: UI policy update about dialogs

[Wayne Stambaugh]

Hi Nabeel,

I merged your patch into the development branch.  Thank you for your
contribution to KiCad.

Cheers,

Wayne

On 12/2/2018 2:43 AM, Nabeel Ahmad wrote:
> Hi Wayne,
> 
> A revised patch is attached. Thanks.
> 
> Regards,
> Nabeel
> 
> On 1 Dec 2018 13:57:00 -0500, Wayne Stambaugh wrote:
>> Hi Nabeel,
>>
>> The documentation should read "wxFormbuilder 3.8.0 or later" so please
>> revise your patch.  Expecting developers to use a given version in not
>> reasonable due to platform differences.  This will always be an issue so
>> I'm fine with using later versions of wxFormbuilder.  Building
>> wxFormbuilder from source has been fairly trivial so I don't think it's
>> a stretch for KiCad developers to build from source if needed.
>>
>> Cheers,
>>
>> Wayne
>>
>> On 12/1/2018 8:48 AM, Nabeel Ahmad wrote:
>> > Hello,
>> >
>> >     Le 01/12/2018 à 13:23, Nabeel Ahmad a écrit : > Hello, > > Some
>> >     wxFormBuilder projects files in the source code are incompatible >
>> >     with the > wxFormBuilder version currently recommended in the
>> >     documentation [1]. One > example of such a file is [2]. This file
>> >     has been created with wxFormBuilder > v3.8.1, as evidenced by the
>> >     version date in the .cpp file generated by > it [3].
>> >     What is the problem? Files are the same (not considering the FB
>> >     build version date).
>> >
>> > The only issue is that the project file [1] fails to open with
>> > wxFB3.5-RC1 [2]
>> > which is recommended in the documentation [3]. wxFB complains about
>> > about file
>> > version [4]. The file opens without any problem with wxFB version 3.8.
>> >
>> > [1]:
> https://git.launchpad.net/kicad/tree/pcb_calculator/dialogs/pcb_calculator_frame_base.fbp
>> > [2]: https://github.com/marekr/wxFormBuilder/tree/wxFB3.5-RC1
>> > [3]:
> http://docs.kicad-pcb.org/doxygen/md_Documentation_development_ui-policy.html#dialogs
>> > [4]: See attached image
>> >
>> > Regards,
>> > Nabeel Ahmad
> 
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp
> 

___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

[Kicad-developers] Build failed in Jenkins: linux-kicad-full-gcc-head #4370

[Miguel Angel Ajo]

See 


Changes:

[Wayne Stambaugh] Docs: add docset generation target

--
[...truncated 153.81 KB...]
[ 86%] Built target pcb_calculator_kiface
[ 86%] Building CXX object 
eeschema/CMakeFiles/eeschema_kiface.dir/autoplace_fields.cpp.o
Scanning dependencies of target qa_utils
[ 86%] Building CXX object 
qa/qa_utils/CMakeFiles/qa_utils.dir/stdstream_line_reader.cpp.o
[ 86%] Built target kicad
[ 86%] Building CXX object 
pcbnew/CMakeFiles/pcbnew_kiface_objects.dir/tools/drawing_tool.cpp.o
[ 86%] Linking CXX static library libqa_utils.a
[ 86%] Built target qa_utils
Scanning dependencies of target idf2vrml
[ 86%] Building CXX object utils/idftools/CMakeFiles/idf2vrml.dir/idf2vrml.cpp.o
[ 86%] Building CXX object 
pcbnew/CMakeFiles/pcbnew_kiface_objects.dir/tools/edit_constraints.cpp.o
[ 86%] Building CXX object 
eeschema/CMakeFiles/eeschema_kiface.dir/backanno.cpp.o
[ 86%] Linking CXX executable idf2vrml
[ 86%] Building CXX object 
pcbnew/CMakeFiles/pcbnew_kiface_objects.dir/tools/edit_points.cpp.o
[ 86%] Built target idf2vrml
Scanning dependencies of target kicad-ogltest
[ 86%] Building CXX object 
utils/kicad-ogltest/CMakeFiles/kicad-ogltest.dir/kicad-ogltest.cpp.o
[ 86%] Building CXX object 
pcbnew/CMakeFiles/pcbnew_kiface_objects.dir/tools/edit_tool.cpp.o
[ 86%] Building CXX object eeschema/CMakeFiles/eeschema_kiface.dir/block.cpp.o
[ 86%] Building CXX object 
pcbnew/CMakeFiles/pcbnew_kiface_objects.dir/tools/grid_helper.cpp.o
[ 86%] Linking CXX executable kicad-ogltest
[ 86%] Building CXX object 
eeschema/CMakeFiles/eeschema_kiface.dir/bus-wire-junction.cpp.o
[ 86%] Built target kicad-ogltest
Scanning dependencies of target qa_common
[ 86%] Building CXX object qa/common/CMakeFiles/qa_common.dir/common_mocks.cpp.o
[ 86%] Building CXX object 
pcbnew/CMakeFiles/pcbnew_kiface_objects.dir/tools/microwave_tool.cpp.o
[ 86%] Building CXX object qa/common/CMakeFiles/qa_common.dir/test_module.cpp.o
Scanning dependencies of target qa_pcb_parse_input
[ 87%] Building CXX object 
qa/pcb_parse_input/CMakeFiles/qa_pcb_parse_input.dir/__/qa_utils/mocks.cpp.o
[ 87%] Building CXX object 
qa/common/CMakeFiles/qa_common.dir/__/__/common/eda_text.cpp.o
[ 87%] Building CXX object 
eeschema/CMakeFiles/eeschema_kiface.dir/busentry.cpp.o
[ 87%] Building CXX object 
pcbnew/CMakeFiles/pcbnew_kiface_objects.dir/tools/footprint_editor_tools.cpp.o
[ 87%] Building CXX object 
qa/common/CMakeFiles/qa_common.dir/__/__/common/colors.cpp.o
[ 87%] Building CXX object 
eeschema/CMakeFiles/eeschema_kiface.dir/class_libentry.cpp.o
[ 87%] Building CXX object 
qa/common/CMakeFiles/qa_common.dir/__/__/common/observable.cpp.o
[ 87%] Building CXX object qa/common/CMakeFiles/qa_common.dir/test_color4d.cpp.o
[ 87%] Building CXX object 
qa/pcb_parse_input/CMakeFiles/qa_pcb_parse_input.dir/main.cpp.o
[ 87%] Building CXX object 
pcbnew/CMakeFiles/pcbnew_kiface_objects.dir/tools/pad_tool.cpp.o
[ 87%] Building CXX object 
qa/pcb_parse_input/CMakeFiles/qa_pcb_parse_input.dir/__/__/common/base_units.cpp.o
[ 87%] Building CXX object 
qa/common/CMakeFiles/qa_common.dir/test_hotkey_store.cpp.o
[ 87%] Building CXX object 
eeschema/CMakeFiles/eeschema_kiface.dir/class_library.cpp.o
[ 87%] Building CXX object 
qa/pcb_parse_input/CMakeFiles/qa_pcb_parse_input.dir/__/__/common/xnode.cpp.o
[ 87%] Building CXX object 
qa/common/CMakeFiles/qa_common.dir/test_title_block.cpp.o
[ 87%] Building CXX object 
qa/pcb_parse_input/CMakeFiles/qa_pcb_parse_input.dir/__/__/common/base_screen.cpp.o
[ 87%] Building CXX object 
eeschema/CMakeFiles/eeschema_kiface.dir/cmp_library_keywords.cpp.o
[ 87%] Building CXX object qa/common/CMakeFiles/qa_common.dir/test_utf8.cpp.o
[ 87%] Building CXX object 
pcbnew/CMakeFiles/pcbnew_kiface_objects.dir/tools/pcb_actions.cpp.o
[ 87%] Building CXX object 
pcbnew/CMakeFiles/pcbnew_kiface_objects.dir/tools/pcb_bright_box.cpp.o
[ 87%] Building CXX object 
qa/common/CMakeFiles/qa_common.dir/libeval/test_numeric_evaluator.cpp.o
[ 87%] Building CXX object 
eeschema/CMakeFiles/eeschema_kiface.dir/cmp_library_lexer.cpp.o
[ 87%] Linking CXX executable qa_pcb_parse_input
[ 87%] Building CXX object 
pcbnew/CMakeFiles/pcbnew_kiface_objects.dir/tools/pcb_editor_control.cpp.o
[ 88%] Building CXX object 
eeschema/CMakeFiles/eeschema_kiface.dir/component_references_lister.cpp.o
[ 88%] Building CXX object 
qa/common/CMakeFiles/qa_common.dir/geometry/test_fillet.cpp.o
[ 88%] Building CXX object 
qa/common/CMakeFiles/qa_common.dir/view/test_zoom_controller.cpp.o
[ 88%] Building CXX object 
eeschema/CMakeFiles/eeschema_kiface.dir/controle.cpp.o
[ 88%] Linking CXX executable qa_common
[ 89%] Building CXX object 
pcbnew/CMakeFiles/pcbnew_kiface_objects.dir/tools/pcb_selection_conditions.cpp.o
[ 89%] Built target qa_common
[ 89%] Built target qa_pcb_parse_input
Scanning dependencies of target gerbview
[ 89%] Building CXX object 

Re: [Kicad-developers] 5.0.2 stable release.

[Steven A. Falco]

The link is based on what I was using for 5.0.0, 5.0.1, etc.  I'd guess that as 
soon as you upload the source archive, the link will start working.

Once I see your release announcement, I'll start the process of building the 
official Fedora packages.

Steve

On 12/3/18 11:24 AM, Wayne Stambaugh wrote:
> Hey Steve,
> 
> I have not posted the source archive yet.  I'm not sure where the link
> you are using came from.  I will post the source archive at the same
> time I make the release announcement.  This gives the installer devs a
> chance to get the build servers updated and the installers uploaded to
> the website.  As soon as the library devs get the library repos tagged,
> it shouldn't take more than a week to get most of the installers built.
>  My goal is to make the release announcement this weekend.
> 
> Cheers,
> 
> Wayne
> 
> On 12/3/2018 11:15 AM, Steven A. Falco wrote:
>> I see that the source code was tagged with 5.0.2, but I get a 404 when I try 
>> to download the tar via:
>>
>> https://launchpad.net/kicad/5.0/5.0.2/+download/kicad-5.0.2.tar.xz
>>
>> Is that the correct link?  Has the tar been posted yet?
>>
>>  Thanks,
>>  Steve
>>
>>
>> On 12/3/18 7:49 AM, Wayne Stambaugh wrote:
>>> I saw that the translation and doc repos were tagged for 5.0.2.  Where
>>> do we stand on the library repos?
>>>
>>> On 11/26/2018 6:49 PM, Evan Shultz wrote:
 I should have also mentioned that the outstanding items milestoned for
 5.0.2 are actual fixes which we would like to include. We've been
 careful not to pushing breaking changes flippantly so tagging the head
 of each library should be safe and an improvement. Breaking changes
 haven't been intentionally made since 5.0.0 unless it was to fix an
 issue that might ruin a design (wrong pinout, footprint pins swapped, 
 etc.).

 On Mon, Nov 26, 2018 at 3:08 PM Evan Shultz >>> > wrote:

 Yay!

 We (librarians) have a few outstanding items in the library we want
 to close before 5.0.2, but it should only be a couple of days and
 well within the one week timeline you requested. Thanks mostly to
 Antonio, we're now using the milestone feature of GH so you can see
 what's left at https://github.com/KiCad/kicad-symbols/milestone/6
 and https://github.com/KiCad/kicad-footprints/milestone/1 (for
 symbols and footprints, at least).

 On Mon, Nov 26, 2018 at 3:05 PM Wayne Stambaugh
 mailto:stambau...@gmail.com>> wrote:

 I just tagged and pushed 5.0.2 so we need to decide what we want
 to do
 about tagging the library and translation repos.  Rene, any
 thoughts on
 the library repos.  I know there have been a lot of changes
 since 5.0.1
 but as long as the existing symbols have changed too
 significantly, I'm
 fine with tagging the current head of each library.

 On 11/26/2018 5:55 PM, Nick Østergaard wrote:
 > Are we expecting to tag 5.0.1 as 5.0.2 for the libraries or are 
 we
 > getting a minor library update as well?
 > On Mon, 26 Nov 2018 at 20:32, Wayne Stambaugh
 mailto:stambau...@gmail.com>> wrote:
 >>
 >> I just noticed a few last minute changes were made to the 5.0
 branch.
 >> Is there anything else pending or am I good to go with
 tagging 5.0.2?
 >>
 >> Cheers,
 >>
 >> Wayne
 >>
 >> On 11/25/2018 2:01 PM, Wayne Stambaugh wrote:
 >>> I plan on tagging 5.0.2 tomorrow unless is a show stopper
 bug that I am
 >>> not aware of.  My goal is to give the library, doc, and
 translations a
 >>> week to get tagged for 5.0.2 and another week for the
 installers to get
 >>> built so I can make the release announcement on 12/9. 
 Please let me
 >>> know if this doesn't fit into your schedule so we can make
 other plans.
 >>>
 >>> Once 5.0.2 is released, I would like to string freeze the
 development
 >>> branch to start getting ready of 5.1 release candidates by
 the beginning
 >>> of the year.  If you have any UI string changes that you are
 planning to
 >>> make, now would be a good time.
 >>>
 >>> Thank you again everyone for your hard work.  KiCad continues 
 to
 >>> steadily improve due to your efforts.
 >>>
 >>> Cheers,
 >>>
 >>> Wayne
 >>>
 >>
 >> ___
 >> Mailing list: 

Re: [Kicad-developers] 5.0.2 stable release.

[Pedro Martin]

Hi, Wayne,

This is the version I'm using since last week.

Regards,
Pedro.

Application: kicad
Version: 5.0.2-bee76a0~70~ubuntu14.04.1, release build
Libraries:
wxWidgets 3.0.2
libcurl/7.35.0 OpenSSL/1.0.1f zlib/1.2.8 libidn/1.28 librtmp/2.3
Platform: Linux 3.16.0-77-generic x86_64, 64 bit, Little endian, wxGTK
Build Info:
wxWidgets: 3.0.2 (wchar_t,wx containers,compatible with 2.8) GTK+ 2.24
Boost: 1.54.0
OpenCASCADE Community Edition: 6.8.0
Curl: 7.35.0
Compiler: GCC 4.8.4 with C++ ABI 1002

Build settings:
USE_WX_GRAPHICS_CONTEXT=OFF
USE_WX_OVERLAY=OFF
KICAD_SCRIPTING=ON
KICAD_SCRIPTING_MODULES=ON
KICAD_SCRIPTING_WXPYTHON=OFF
KICAD_SCRIPTING_ACTION_MENU=ON
BUILD_GITHUB_PLUGIN=ON
KICAD_USE_OCE=ON
KICAD_USE_OCC=OFF
KICAD_SPICE=ON


El 3/12/18 a las 17:24, Wayne Stambaugh escribió:

Hey Steve,

I have not posted the source archive yet.  I'm not sure where the link
you are using came from.  I will post the source archive at the same
time I make the release announcement.  This gives the installer devs a
chance to get the build servers updated and the installers uploaded to
the website.  As soon as the library devs get the library repos tagged,
it shouldn't take more than a week to get most of the installers built.
  My goal is to make the release announcement this weekend.

Cheers,

Wayne

On 12/3/2018 11:15 AM, Steven A. Falco wrote:

I see that the source code was tagged with 5.0.2, but I get a 404 when I try to 
download the tar via:

https://launchpad.net/kicad/5.0/5.0.2/+download/kicad-5.0.2.tar.xz

Is that the correct link?  Has the tar been posted yet?

Thanks,
Steve


On 12/3/18 7:49 AM, Wayne Stambaugh wrote:

I saw that the translation and doc repos were tagged for 5.0.2.  Where
do we stand on the library repos?

On 11/26/2018 6:49 PM, Evan Shultz wrote:

I should have also mentioned that the outstanding items milestoned for
5.0.2 are actual fixes which we would like to include. We've been
careful not to pushing breaking changes flippantly so tagging the head
of each library should be safe and an improvement. Breaking changes
haven't been intentionally made since 5.0.0 unless it was to fix an
issue that might ruin a design (wrong pinout, footprint pins swapped, etc.).

On Mon, Nov 26, 2018 at 3:08 PM Evan Shultz mailto:evan.shu...@gmail.com>> wrote:

 Yay!

 We (librarians) have a few outstanding items in the library we want
 to close before 5.0.2, but it should only be a couple of days and
 well within the one week timeline you requested. Thanks mostly to
 Antonio, we're now using the milestone feature of GH so you can see
 what's left at https://github.com/KiCad/kicad-symbols/milestone/6
 and https://github.com/KiCad/kicad-footprints/milestone/1 (for
 symbols and footprints, at least).

 On Mon, Nov 26, 2018 at 3:05 PM Wayne Stambaugh
 mailto:stambau...@gmail.com>> wrote:

 I just tagged and pushed 5.0.2 so we need to decide what we want
 to do
 about tagging the library and translation repos.  Rene, any
 thoughts on
 the library repos.  I know there have been a lot of changes
 since 5.0.1
 but as long as the existing symbols have changed too
 significantly, I'm
 fine with tagging the current head of each library.

 On 11/26/2018 5:55 PM, Nick Østergaard wrote:
 > Are we expecting to tag 5.0.1 as 5.0.2 for the libraries or are we
 > getting a minor library update as well?
 > On Mon, 26 Nov 2018 at 20:32, Wayne Stambaugh
 mailto:stambau...@gmail.com>> wrote:
 >>
 >> I just noticed a few last minute changes were made to the 5.0
 branch.
 >> Is there anything else pending or am I good to go with
 tagging 5.0.2?
 >>
 >> Cheers,
 >>
 >> Wayne
 >>
 >> On 11/25/2018 2:01 PM, Wayne Stambaugh wrote:
 >>> I plan on tagging 5.0.2 tomorrow unless is a show stopper
 bug that I am
 >>> not aware of.  My goal is to give the library, doc, and
 translations a
 >>> week to get tagged for 5.0.2 and another week for the
 installers to get
 >>> built so I can make the release announcement on 12/9.
 Please let me
 >>> know if this doesn't fit into your schedule so we can make
 other plans.
 >>>
 >>> Once 5.0.2 is released, I would like to string freeze the
 development
 >>> branch to start getting ready of 5.1 release candidates by
 the beginning
 >>> of the year.  If you have any UI string changes that you are
 planning to
 >>> make, now would be a good time.
 >>>
 >>> Thank you again everyone for your hard work.  KiCad continues to
 >>> steadily improve due to your efforts.
 >>>
 >>> Cheers,
 >>>
 

Re: [Kicad-developers] 5.0.2 stable release.

[Wayne Stambaugh]

Hey Steve,

I have not posted the source archive yet.  I'm not sure where the link
you are using came from.  I will post the source archive at the same
time I make the release announcement.  This gives the installer devs a
chance to get the build servers updated and the installers uploaded to
the website.  As soon as the library devs get the library repos tagged,
it shouldn't take more than a week to get most of the installers built.
 My goal is to make the release announcement this weekend.

Cheers,

Wayne

On 12/3/2018 11:15 AM, Steven A. Falco wrote:
> I see that the source code was tagged with 5.0.2, but I get a 404 when I try 
> to download the tar via:
> 
> https://launchpad.net/kicad/5.0/5.0.2/+download/kicad-5.0.2.tar.xz
> 
> Is that the correct link?  Has the tar been posted yet?
> 
>   Thanks,
>   Steve
> 
> 
> On 12/3/18 7:49 AM, Wayne Stambaugh wrote:
>> I saw that the translation and doc repos were tagged for 5.0.2.  Where
>> do we stand on the library repos?
>>
>> On 11/26/2018 6:49 PM, Evan Shultz wrote:
>>> I should have also mentioned that the outstanding items milestoned for
>>> 5.0.2 are actual fixes which we would like to include. We've been
>>> careful not to pushing breaking changes flippantly so tagging the head
>>> of each library should be safe and an improvement. Breaking changes
>>> haven't been intentionally made since 5.0.0 unless it was to fix an
>>> issue that might ruin a design (wrong pinout, footprint pins swapped, etc.).
>>>
>>> On Mon, Nov 26, 2018 at 3:08 PM Evan Shultz >> > wrote:
>>>
>>> Yay!
>>>
>>> We (librarians) have a few outstanding items in the library we want
>>> to close before 5.0.2, but it should only be a couple of days and
>>> well within the one week timeline you requested. Thanks mostly to
>>> Antonio, we're now using the milestone feature of GH so you can see
>>> what's left at https://github.com/KiCad/kicad-symbols/milestone/6
>>> and https://github.com/KiCad/kicad-footprints/milestone/1 (for
>>> symbols and footprints, at least).
>>>
>>> On Mon, Nov 26, 2018 at 3:05 PM Wayne Stambaugh
>>> mailto:stambau...@gmail.com>> wrote:
>>>
>>> I just tagged and pushed 5.0.2 so we need to decide what we want
>>> to do
>>> about tagging the library and translation repos.  Rene, any
>>> thoughts on
>>> the library repos.  I know there have been a lot of changes
>>> since 5.0.1
>>> but as long as the existing symbols have changed too
>>> significantly, I'm
>>> fine with tagging the current head of each library.
>>>
>>> On 11/26/2018 5:55 PM, Nick Østergaard wrote:
>>> > Are we expecting to tag 5.0.1 as 5.0.2 for the libraries or are we
>>> > getting a minor library update as well?
>>> > On Mon, 26 Nov 2018 at 20:32, Wayne Stambaugh
>>> mailto:stambau...@gmail.com>> wrote:
>>> >>
>>> >> I just noticed a few last minute changes were made to the 5.0
>>> branch.
>>> >> Is there anything else pending or am I good to go with
>>> tagging 5.0.2?
>>> >>
>>> >> Cheers,
>>> >>
>>> >> Wayne
>>> >>
>>> >> On 11/25/2018 2:01 PM, Wayne Stambaugh wrote:
>>> >>> I plan on tagging 5.0.2 tomorrow unless is a show stopper
>>> bug that I am
>>> >>> not aware of.  My goal is to give the library, doc, and
>>> translations a
>>> >>> week to get tagged for 5.0.2 and another week for the
>>> installers to get
>>> >>> built so I can make the release announcement on 12/9. 
>>> Please let me
>>> >>> know if this doesn't fit into your schedule so we can make
>>> other plans.
>>> >>>
>>> >>> Once 5.0.2 is released, I would like to string freeze the
>>> development
>>> >>> branch to start getting ready of 5.1 release candidates by
>>> the beginning
>>> >>> of the year.  If you have any UI string changes that you are
>>> planning to
>>> >>> make, now would be a good time.
>>> >>>
>>> >>> Thank you again everyone for your hard work.  KiCad continues to
>>> >>> steadily improve due to your efforts.
>>> >>>
>>> >>> Cheers,
>>> >>>
>>> >>> Wayne
>>> >>>
>>> >>
>>> >> ___
>>> >> Mailing list: https://launchpad.net/~kicad-developers
>>> >> Post to     : kicad-developers@lists.launchpad.net
>>> 
>>> >> Unsubscribe : https://launchpad.net/~kicad-developers
>>> >> More help   : https://help.launchpad.net/ListHelp
>>>
>>> ___
>>> Mailing list: https://launchpad.net/~kicad-developers
>>> Post to     : 

Re: [Kicad-developers] 5.0.2 stable release.

[Steven A. Falco]

I see that the source code was tagged with 5.0.2, but I get a 404 when I try to 
download the tar via:

https://launchpad.net/kicad/5.0/5.0.2/+download/kicad-5.0.2.tar.xz

Is that the correct link?  Has the tar been posted yet?

Thanks,
Steve


On 12/3/18 7:49 AM, Wayne Stambaugh wrote:
> I saw that the translation and doc repos were tagged for 5.0.2.  Where
> do we stand on the library repos?
> 
> On 11/26/2018 6:49 PM, Evan Shultz wrote:
>> I should have also mentioned that the outstanding items milestoned for
>> 5.0.2 are actual fixes which we would like to include. We've been
>> careful not to pushing breaking changes flippantly so tagging the head
>> of each library should be safe and an improvement. Breaking changes
>> haven't been intentionally made since 5.0.0 unless it was to fix an
>> issue that might ruin a design (wrong pinout, footprint pins swapped, etc.).
>>
>> On Mon, Nov 26, 2018 at 3:08 PM Evan Shultz > > wrote:
>>
>> Yay!
>>
>> We (librarians) have a few outstanding items in the library we want
>> to close before 5.0.2, but it should only be a couple of days and
>> well within the one week timeline you requested. Thanks mostly to
>> Antonio, we're now using the milestone feature of GH so you can see
>> what's left at https://github.com/KiCad/kicad-symbols/milestone/6
>> and https://github.com/KiCad/kicad-footprints/milestone/1 (for
>> symbols and footprints, at least).
>>
>> On Mon, Nov 26, 2018 at 3:05 PM Wayne Stambaugh
>> mailto:stambau...@gmail.com>> wrote:
>>
>> I just tagged and pushed 5.0.2 so we need to decide what we want
>> to do
>> about tagging the library and translation repos.  Rene, any
>> thoughts on
>> the library repos.  I know there have been a lot of changes
>> since 5.0.1
>> but as long as the existing symbols have changed too
>> significantly, I'm
>> fine with tagging the current head of each library.
>>
>> On 11/26/2018 5:55 PM, Nick Østergaard wrote:
>> > Are we expecting to tag 5.0.1 as 5.0.2 for the libraries or are we
>> > getting a minor library update as well?
>> > On Mon, 26 Nov 2018 at 20:32, Wayne Stambaugh
>> mailto:stambau...@gmail.com>> wrote:
>> >>
>> >> I just noticed a few last minute changes were made to the 5.0
>> branch.
>> >> Is there anything else pending or am I good to go with
>> tagging 5.0.2?
>> >>
>> >> Cheers,
>> >>
>> >> Wayne
>> >>
>> >> On 11/25/2018 2:01 PM, Wayne Stambaugh wrote:
>> >>> I plan on tagging 5.0.2 tomorrow unless is a show stopper
>> bug that I am
>> >>> not aware of.  My goal is to give the library, doc, and
>> translations a
>> >>> week to get tagged for 5.0.2 and another week for the
>> installers to get
>> >>> built so I can make the release announcement on 12/9. 
>> Please let me
>> >>> know if this doesn't fit into your schedule so we can make
>> other plans.
>> >>>
>> >>> Once 5.0.2 is released, I would like to string freeze the
>> development
>> >>> branch to start getting ready of 5.1 release candidates by
>> the beginning
>> >>> of the year.  If you have any UI string changes that you are
>> planning to
>> >>> make, now would be a good time.
>> >>>
>> >>> Thank you again everyone for your hard work.  KiCad continues to
>> >>> steadily improve due to your efforts.
>> >>>
>> >>> Cheers,
>> >>>
>> >>> Wayne
>> >>>
>> >>
>> >> ___
>> >> Mailing list: https://launchpad.net/~kicad-developers
>> >> Post to     : kicad-developers@lists.launchpad.net
>> 
>> >> Unsubscribe : https://launchpad.net/~kicad-developers
>> >> More help   : https://help.launchpad.net/ListHelp
>>
>> ___
>> Mailing list: https://launchpad.net/~kicad-developers
>> Post to     : kicad-developers@lists.launchpad.net
>> 
>> Unsubscribe : https://launchpad.net/~kicad-developers
>> More help   : https://help.launchpad.net/ListHelp
>>
> 
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp
> 


___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : 

Re: [Kicad-developers] [PATCH] Docset generation

[Wayne Stambaugh]

Hey John,

I merged your patch.

Thanks,

Wayne

On 11/27/2018 12:28 PM, John Beard wrote:
> Hi,
> 
> This is a patch to generate docsets using our existing doxygen set-up.
> Docset documentation makes it very easy to quickly browse the docs
> using Zeal and similar [1], which means you can get IDE integration
> and other nice things.
> 
> The patch adds a "make docset" target. To actually build the docset,
> you will need doxytag2zealdb, a Python program available with pip.
> 
> There is a strange extraneous endif() in the existing version Cmake as
> well, which I
> cannot explain why it currently works at all in its current form!
> 
> The docset can be used to construct a docset feed using the CI
> infrastructure. Basically you need to host the TGZ somewhere and then
> provide an XML which changes the version and the link as needed. Zeal
> then picks up new version availability when checked.
> 
> I have a hastily constructed feed available here [2]. This means you
> can start using a nightly-ish docset today, but updates are not done
> by a CI system. It should be as simple as adding this URL in Zeal [3].
> 
> Cheers,
> 
> John
> 
> [1]: zealdocs.org
> [2]: https://github.com/johnbeard/kicad-docset
> [3]: 
> https://raw.githubusercontent.com/johnbeard/kicad-docset/master/feeds/master/KiCad.xml
> 
> 
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp
> 

___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] 5.0.2 stable release.

[Wayne Stambaugh]

I saw that the translation and doc repos were tagged for 5.0.2.  Where
do we stand on the library repos?

On 11/26/2018 6:49 PM, Evan Shultz wrote:
> I should have also mentioned that the outstanding items milestoned for
> 5.0.2 are actual fixes which we would like to include. We've been
> careful not to pushing breaking changes flippantly so tagging the head
> of each library should be safe and an improvement. Breaking changes
> haven't been intentionally made since 5.0.0 unless it was to fix an
> issue that might ruin a design (wrong pinout, footprint pins swapped, etc.).
> 
> On Mon, Nov 26, 2018 at 3:08 PM Evan Shultz  > wrote:
> 
> Yay!
> 
> We (librarians) have a few outstanding items in the library we want
> to close before 5.0.2, but it should only be a couple of days and
> well within the one week timeline you requested. Thanks mostly to
> Antonio, we're now using the milestone feature of GH so you can see
> what's left at https://github.com/KiCad/kicad-symbols/milestone/6
> and https://github.com/KiCad/kicad-footprints/milestone/1 (for
> symbols and footprints, at least).
> 
> On Mon, Nov 26, 2018 at 3:05 PM Wayne Stambaugh
> mailto:stambau...@gmail.com>> wrote:
> 
> I just tagged and pushed 5.0.2 so we need to decide what we want
> to do
> about tagging the library and translation repos.  Rene, any
> thoughts on
> the library repos.  I know there have been a lot of changes
> since 5.0.1
> but as long as the existing symbols have changed too
> significantly, I'm
> fine with tagging the current head of each library.
> 
> On 11/26/2018 5:55 PM, Nick Østergaard wrote:
> > Are we expecting to tag 5.0.1 as 5.0.2 for the libraries or are we
> > getting a minor library update as well?
> > On Mon, 26 Nov 2018 at 20:32, Wayne Stambaugh
> mailto:stambau...@gmail.com>> wrote:
> >>
> >> I just noticed a few last minute changes were made to the 5.0
> branch.
> >> Is there anything else pending or am I good to go with
> tagging 5.0.2?
> >>
> >> Cheers,
> >>
> >> Wayne
> >>
> >> On 11/25/2018 2:01 PM, Wayne Stambaugh wrote:
> >>> I plan on tagging 5.0.2 tomorrow unless is a show stopper
> bug that I am
> >>> not aware of.  My goal is to give the library, doc, and
> translations a
> >>> week to get tagged for 5.0.2 and another week for the
> installers to get
> >>> built so I can make the release announcement on 12/9. 
> Please let me
> >>> know if this doesn't fit into your schedule so we can make
> other plans.
> >>>
> >>> Once 5.0.2 is released, I would like to string freeze the
> development
> >>> branch to start getting ready of 5.1 release candidates by
> the beginning
> >>> of the year.  If you have any UI string changes that you are
> planning to
> >>> make, now would be a good time.
> >>>
> >>> Thank you again everyone for your hard work.  KiCad continues to
> >>> steadily improve due to your efforts.
> >>>
> >>> Cheers,
> >>>
> >>> Wayne
> >>>
> >>
> >> ___
> >> Mailing list: https://launchpad.net/~kicad-developers
> >> Post to     : kicad-developers@lists.launchpad.net
> 
> >> Unsubscribe : https://launchpad.net/~kicad-developers
> >> More help   : https://help.launchpad.net/ListHelp
> 
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> Post to     : kicad-developers@lists.launchpad.net
> 
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp
> 

___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] [PATCH] Numeric evaluator tests + unary "+"

[Maciej Sumiński]

Hi John,

Thank you for the patches, I have just merged them. I particularly
appreciate the unit tests, well done!

Cheers,
Orson

On 11/28/18 5:03 PM, John Beard wrote:
> Hi,
> 
> Here are some patches for the numeric evaluator.
> 
> There are three parts:
> * Add tests and test current behaviour of the numeric evaluator.
> Remove broken and unused/unbuildable old tests.
> * Add a CMake target (libeval_grammar) to allow to rebuild the grammar
> * Modify and rebuild the grammar to allow unary + in expressions. Not
> a major change, but consistent with most other numeric evaluations,
> and symmetric with the minus notation.
> 
> The CMake target is run manually and, as currently, the generated C
> source checked in. The target will only be available when lemon is
> installed.
> 
> Having this available as a CMake target makes it much more accessible
> to other developers to maintain the grammar. Tests allow to ensure
> behaviour is not changed when not expected.
> 
> Cheers,
> 
> John
> 
> 
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp
> 




signature.asc
Description: OpenPGP digital signature
___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp