The latest stable version six branch of KiCad has been released[1].
Thank you to everyone who contributed there time and talent to make this
stable release of KiCad possible.
Cheers,
Wayne
[1]: https://www.kicad.org/blog/2022/06/KiCad-6.0.6-Release/
One other thing that I forgot, it would be nice if we could get some
extra eyes on the recent router changes to make sure there are no
regressions. Please download the latest testing build and help with the
testing if possible.
On 6/11/22 11:32, Wayne Stambaugh wrote:
> We now have a suffici
We now have a sufficient number of bug fixes in the 6.0 branch to start
thinking about a 6.0.6 stable release. The goal is to tag 6.0.6 Friday,
June 17th and make the release announcement on the 19th. If anyone has
any last minute commits to make to the documentation and/or libraries,
now is the
hpad.net/kicad-developers/msg43255.html
> <https://lists.launchpad.net/kicad-developers/msg43255.html>
> [2]
> https://launchpad.net/~mhier/+archive/ubuntu/libboost-latest/+packages
> <https://launchpad.net/~mhier/+archive/ubuntu/libboost-latest/+packages>
>
> On Mon,
It looks like someone back ported some random number generator fixes
from master that are not available in boost 1.56 which is the minimum
version in the 6.0 branch. We should address this since 18.04 LTS is a
supported system[1].
[1]:https://www.kicad.org/help/system-requirements/
On 5/9/22
Stable version 6.0.5 has officially been release. See the release
announcement[1] for more information. Thanks to everyone who made this
release possible.
Cheers,
Wayne
[1]:https://www.kicad.org/blog/2022/05/KiCad-6.0.5-Release/
___
Mailing list:
Yet another last minute critical issue was fixed yesterday so I'm
pushing tagging back another week. I will tag 6.0.5 on Monday, May 2nd.
Wayne
On 4/25/22 12:02 PM, Wayne Stambaugh wrote:
> Sending this again because apparently some folks on the mailing list
> didn't get it.
Sending this again because apparently some folks on the mailing list
didn't get it. Sorry for the noise.
Wayne
On 4/22/22 7:39 AM, Wayne Stambaugh wrote:
> Due to another crash bug being fixed, the new freeze date started on
> April 19th. To allow a full week of testing, I will be t
Due to another crash bug being fixed, the new freeze date started on
April 19th. To allow a full week of testing, I will be tagging 6.0.5 on
Wednesday, April 27th.
Cheers,
Wayne
On 4/15/22 6:30 PM, Wayne Stambaugh wrote:
> The 6.0 source branch repo has been frozen for the upcoming 6.
The 6.0 source branch repo has been frozen for the upcoming 6.0.5 stable
release. I plan on tagging the source branch on April 22nd and release
on the 24th. If you have any last minute library or documentation
changes that you would like to make before we have to tag those repos,
now is the
Thanks Mark!
On 3/31/22 11:37 AM, Jon Evans wrote:
Thanks for putting in the work to get this integrated, Mark! Having
automated crash dumps will be invaluable to improving KiCad stability.
On Wed, Mar 30, 2022 at 8:32 PM Mark Roszko wrote:
Hey folks,
We are planning to introduce the use
Hi Markus,
The KiCad version 7 feature freeze date is September 30th so your MR
would have to be merged by that date to make it in V7. Given that the
Pcbnew and 3D viewer SpaceMouse code was a rather large change set, you
should probably submit the MR by the end of August to allow time for
The stable version 6.0.4 of KiCad has been released. The packages for
most major platforms should be available. The reason there was no 6.0.3
release is that we found an issue with 6.0.3 before the official release
announcement was made and had to fix it. The KiCad development team
would
The source repo has been tagged so we need to get the remaining repos
tagged so we can get the package builders fired up.
Cheers,
Wayne
On 3/15/22 9:41 AM, Wayne Stambaugh wrote:
I am planning on tagging 6.0.3 this evening around 8PM EDT. Please let
me know if you need more time. All
I am planning on tagging 6.0.3 this evening around 8PM EDT. Please let
me know if you need more time. All of the other repos will need tagged
as well so we can packages built and uploaded. The goal is release on
Thursday, March 17th.
Cheers,
Wayne
On 3/8/22 7:32 AM, Wayne Stambaugh wrote
We are planning on releasing 6.0.3 on March 15th which means that we
will have to have all of the repos tagged by March 13th. Please let me
know if you have any issues with this time line. Thanks in advance for
the help.
Cheers,
Wayne
___
All of the repos have been tagged for 6.0.2 and the documentation
archive can be download from
https://kicad-downloads.s3.cern.ch/docs/kicad-doc-6.0.2.tar.gz. Let's
get those package builders fired up for the 6.0.2 release.
Cheers,
Wayne
___
Mailing
On 2/10/22 10:06 AM, Steven A. Falco wrote:
On 2/7/22 04:46 PM, Wayne Stambaugh wrote:
On 2/7/2022 4:39 PM, Steven A. Falco wrote:
On 2/7/22 03:39 PM, Wayne Stambaugh wrote:
The goal is to release 6.0.2 on Friday, February 11th. If this is an
issue for anyone please let me know. I apologize
On 2/7/2022 4:39 PM, Steven A. Falco wrote:
On 2/7/22 03:39 PM, Wayne Stambaugh wrote:
The goal is to release 6.0.2 on Friday, February 11th. If this is an
issue for anyone please let me know. I apologize that it's this late
due to the Launch mailing list issue.
To confirm, do you mean
The goal is to release 6.0.2 on Friday, February 11th. If this is an
issue for anyone please let me know. I apologize that it's this late
due to the Launch mailing list issue.
Cheers,
Wayne
___
Mailing list:
In case you didn't know, the KiCad developer's mailing list was down for
a few days so no one was getting the messages. If you sent anything
over the last few days and didn't get a response, your going to have to
resend it. I don't think anyone should be expected to go through the
mailing
Just a friendly reminder to developers to please update the copyright
date to 2022 as you make changes to the KiCad source files.
Cheers,
Wayne
___
Mailing list: https://launchpad.net/~kicad-developers
Post to :
t;CompactedFamily" [01,02]_[02..64]_[H,V]_2.54mm )
Same for footprints
Franck
Le 06/01/2022 à 23:43, Wayne Stambaugh a écrit :
Just a quick heads up to all library, package, documentation, and
translation developers, barring any unexpected critical bugs I will be
tagging stable release version
Just a quick heads up to all library, package, documentation, and
translation developers, barring any unexpected critical bugs I will be
tagging stable release version 6.0.1 late on Tuesday, January 11 (EST)
for official release on January 15th. If you have anything you want to
push before
The build error is fixed. Thanks.
On 12/26/21 11:55 AM, jeff wrote:
More bits committed...
On 26 Dec 2021, at 15:48, Wayne Stambaugh wrote:
Now I'm seeing this:
/home/foo/src/kicad-trunk/qa/pns/pns_log_viewer.cpp: In constructor
‘PNS_LOG_VIEWER_FRAME::PNS_LOG_VIEWER_FRAME(wxFrame
Now I'm seeing this:
/home/foo/src/kicad-trunk/qa/pns/pns_log_viewer.cpp: In constructor
‘PNS_LOG_VIEWER_FRAME::PNS_LOG_VIEWER_FRAME(wxFrame*)’:
/home/foo/src/kicad-trunk/qa/pns/pns_log_viewer.cpp:294:14: error:
request for member ‘m_ZoneDisplayMode’ in ‘settings’, which is of
pointer type
I'm seeing the following build failure this morning:
/home/foo/src/kicad-trunk/qa/qa_utils/mocks.cpp:622:28: error: no
declaration matches ‘const PCB_DISPLAY_OPTIONS&
PCB_TOOL_BASE::displayOptions() const’
622 | const PCB_DISPLAY_OPTIONS& PCB_TOOL_BASE::displayOptions() const
|
Due to the recent churn, the KiCad lead development team has decide to
tag a release candidate 2 for version 6. If testing goes well over the
weekend, the goal is to tag 6.0.0 on Monday.
Until version 6 is tagged, no new commits can be pushed directly to the
master branch. All commits until
Check to make sure the KICAD_BUILD_I18N and KICAD_I18N_UNIX_STRICT_PATH
build options are set properly. They default to OFF.
On 11/19/21 8:47 AM, Marco Ciampa wrote:
Hi devs!
In order to check the coherence of the translation I often compile and install
KiCad from source (from git).
Using
I am happy to announce that Mikolaj Wielgus has accepted an invitation
to become a member of the KiCad lead development team. Mikolaj has made
some significant contributions to the KiCad project and I look forward
to his contributions as lead developer. Please join me in
congratulating
Hi Lorenzo,
Welcome back.
It sounds to me like you are describing a variant system to allow for
different populations of the same board layout from a single schematic
design. This is already planned for version 7 so you wont have to use
any hacks like you are suggesting below to create a
Hi Steven,
I don't remember the 3D model or documentation licensing changing. The
source license did change from AGPLv3+ to GPLv3+.
Cheers,
Wayne
On 11/16/21 11:17 AM, Steven A. Falco wrote:
As we get close to releasing 6.x builds, I'd like to make sure our
packages specify the correct
Release candidate 1 of version 6 has been tagged and pushed. Package
builds should be available in the next few days for most systems. There
are still a few minor issues which should get fixed by stable release
6.0.0. If all goes well, the stable release should be ready by the end
of the
Unfortunately we found a locale issue with 5.1.11. Some of the packages
were ready and uploaded to website which resulted in a few users
downloading them which exposed the issue. We have fixed the issue but
given that users have already downloaded 5.1.11 packages, we will not be
officially
Hi Stefan,
There is not a formal release notes per se but you can see the list of
closed issues at https://gitlab.com/groups/kicad/-/milestones/6.
Cheers,
Wayne
On 10/30/2021 11:03 AM, Stefan Brüns wrote:
Hi,
I am currently preparing packages for openSUSE, and was wondering if the
release
The lead development team has agreed on a version 6 release schedule as
follows:
- String freeze November 1.
- Tag RC1 on November 15.
- All repos frozen on December 14.
- Tag all repos with 6.0.0 on December 15.
- 6.0.0 release announcement December 31 (maybe the day before Christmas
just
I had to re-tag the 5.1 branch due to removal of the old domain name and
a last minute bug fix. Please update any previous package builds to the
latest commit. I apologize for any inconvenience.
Cheers,
Wayne
___
Mailing list:
On 10/26/21 4:31 PM, Carsten Schoenert wrote:
Hello Wayne,
Am 26.10.21 um 20:38 schrieb Wayne Stambaugh:
Hi Carsten,
Do we still we still build and deploy the old 5.1 developer docs
anywhere? I guess I should remove them just in case someone else does.
I should be able to get
I purged the old domain from the 5.1 branch developer docs and pushed
everything to the 5.1 branch so we should be good to go.
- Wayne
On 10/26/21 2:40 PM, Wayne Stambaugh wrote:
Please hold off building the 5.1.11 packages until I get this fixed even
though the resulting code wont be any
Please hold off building the 5.1.11 packages until I get this fixed even
though the resulting code wont be any different, the commit hash will
be. Sorry for the headaches.
Cheers,
Wayne
On 10/26/21 2:38 PM, Wayne Stambaugh wrote:
Hi Carsten,
Do we still we still build and deploy the old
schrieb Wayne Stambaugh:
I just pushed the 5.1.11 tag to the 5.1 branch so please tag all of the
other repos so we can start the packaging process. Please let me know
if there are any issues that would delay the tagging.
I guess the loss of kicad-pcb.org isn't incorporated yet into this tag
I just pushed the 5.1.11 tag to the 5.1 branch so please tag all of the
other repos so we can start the packaging process. Please let me know
if there are any issues that would delay the tagging.
Thank you everyone for continued contributions to KiCad.
Cheers,
Wayne
On 10/21/21 9:03 AM, Dick Hollenbeck wrote:
On 10/19/21 3:29 PM, Seth Hillbrand wrote:
we attempted to secure the rights to the original domain name from Dick without
success.
This is untrue. *No* offer was ever made, neither to re-imburse nor any offer
to purchase was ever made.
"we
On 9/14/21 10:05 AM, Steven A. Falco wrote:
> Thanks, Jeff. It looks like "make clean" does the right thing - it
> removes "include/page_layout_reader_lexer.h", among others.
>
> I was used to just blowing away the build directory to clean up, but now
> I know that that is not sufficient for
Hi Johannes,
I'm curious where you got wxWidgets 3.1.6 from. The last tag I see in
the wxWidgets repo is 3.1.5 and I'm pretty sure KiCad builds fine with
wxWidgets 3.1.5. AFAIK, the version of wxWidgets packaged for Ubuntu
20.04 is 3.0.4.
Cheers,
Wayne
On 9/8/21 12:55 AM,
I am happy to announce that Roberto Fernandez Bautista has accepted an
invitation to the KiCad lead development team. Roberto has made some
significant contributions to the KiCad project and I look forward to his
contributions as lead developer. Please join me in congratulating
Roberto in
Add -DPYTHON_INCLUDE_DIR=/mingw64/include/python3.8 to the CMake command
line. You have msys2 python installed which for some reason,
FindPythonLibs.cmake detects instead of the mingw64 path.
On 7/2/2021 11:55 PM, pradeepa.kck wrote:
I am using MINGW64.
Sent on the go with Vodafone
comment about what it
would take to do that. I've been using 3.1 on Debian testing for quite
a long time now and it seems to be stable and it also fixes a lot of issues.
Ruth
On 28/06/2021 16:53, Wayne Stambaugh wrote:
Which version of KiCad are you talking about, 5.1 or master? Where
Which version of KiCad are you talking about, 5.1 or master? Where are
you getting your Kubuntu KiCad package, Kubuntu or the KiCad PPA? The
decision to build against wxWidgets 3.1 is up to the disto package
developer if you are using the disto's package.
On 6/28/21 11:38 AM, Ruth Ivimey-Cook
Piccioni wrote:
> Ah.
>
> Perhaps it would be useful to throw up a dialog to the effect that that
> the schematic should be updated?
>
> It still says
>
> PCB and schematic successfully reannotated
>
> In the dialog.
>
>
> On 2021-06-28 11:29 a.m., Way
The reannotation dialog update schematic option because it was removed
because it could leave schematics in an undefined state under certain
conditions. See commit 54e18f6b1f4c2199f8748fff82198f86522bef83 and the
related issue for details.
Wayne
On 6/28/21 9:51 AM, Brian Piccioni wrote:
> Hello
OpenCascade is now the default when building KiCad. This includes the
5.1 branch. This was done because OCC fixes a few bugs in OCE and OCE
support will eventually be removed.
Package developers should adjust the platform build and install
dependencies to OCC as required. If a platform
On 6/14/21 4:59 PM, Kevin Cozens wrote:
On 2021-06-14 4:34 p.m., Marco Ciampa wrote:
On Mon, Jun 14, 2021 at 03:43:54PM -0400, Jon Evans wrote:
You should be able to override what is found by CMake by defining the
PYTHON_EXECUTABLE variable in your cmake command line
Gosh, shame on me, it
2021 00:32 Wayne Stambaugh <mailto:stambau...@gmail.com>> napisał(a):
The test cases look correct so I don't see any issues here.
Could you please check again with better formatting below? Hertz is a
valid SI unit, so strings: "10m" and "10mHz" are valid,
Hi Sylwester,
I don't know that we need to support SI units in spice strings but I
suppose it wouldn't hurt. That would have to wait until V7 as it is a
new feature. The test cases look correct so I don't see any issues here.
- Wayne
On 5/18/21 2:06 PM, Sylwester Kocjan wrote:
Hello!
d not work last time I tried it.
On Tue, 18 May 2021 at 14:43, Wayne Stambaugh <mailto:stambau...@gmail.com>> wrote:
I just looked and the 5.1.10 windows build is using OCE. I thought we
switched over to OCC for msys2 builds but apparently not. I have
switched to OCC on my w
I just looked and the 5.1.10 windows build is using OCE. I thought we
switched over to OCC for msys2 builds but apparently not. I have
switched to OCC on my windows msys2 builds. I think we should switch
the msys2 5.1 builds to OCC because it resolves some issues.
Wayne
On 5/17/2021 3:21
How does this change affect our package devs? I'm guessing they would
have to make some package dependencies changes if OCC is going to be the
default. I would like to hear from them before we make OCC the default.
We will also have to update the developer docs to reflect this change.
Wayne
KiCad 5.1.10 has officially been released[1]. Downloads are available
now for most operating systems[2]. Thanks to everyone who contributed
their time and talent to make this release of KiCad possible.
Cheers,
Wayne
[1]: https://www.kicad.org/blog/2021/05/KiCad-5.1.10-Release/
[2]:
I just pushed the stable release tag to GitLab. Please update any repo
tags as required so we can get the packages build. I will get the
release announcement ready over the weekend. Once we have packages
ready for download and the website updated, I will make the release
announcement.
I would like to tag the 5.1.10 release on Friday, April 23rd. That
would give us a week to get packages built, the website download pages
updated, and make release announcements on all of the usual channels.
Is there anything outstanding that would prevent us from tagging on
Friday? Please
Hi Cirilo,
I would prefer that we hold off until the master branch is open for new
features. We have far more outstanding issues than I would like to see
with less than 3 months to V6 release. Adding yet another new feature
during the freeze only increases the potential bug surface. Feel
On 4/2/2021 2:08 PM, Marco Ciampa wrote:
On Fri, Apr 02, 2021 at 01:21:11PM -0400, Wayne Stambaugh wrote:
I would like to tag 5.1.10 for release by the end of April for release in
early May. This is a heads up to the rest of the development teams to
please get everything ready to go
I would like to tag 5.1.10 for release by the end of April for release
in early May. This is a heads up to the rest of the development teams
to please get everything ready to go by then. Please let me know if you
anticipate any issues with that date so I can push back the schedule.
Thanks in
ing vcpkg.
> This is the intended mode of use for applications.
>
> On Tue, Mar 23, 2021 at 12:09 PM Wayne Stambaugh <mailto:stambau...@gmail.com>> wrote:
>
> Did I misunderstand Marks's comments about MSVC? I though he said that
> pkg-config would not be available t
ing vcpkg.
> This is the intended mode of use for applications.
>
> On Tue, Mar 23, 2021 at 12:09 PM Wayne Stambaugh <mailto:stambau...@gmail.com>> wrote:
>
> Did I misunderstand Marks's comments about MSVC? I though he said that
> pkg-config would not be available t
Did I misunderstand Marks's comments about MSVC? I though he said that
pkg-config would not be available to KiCad at runtime and that it would
be available (I'm assuming via vcpkg) at build time. I really want to
avoid a separate solution for MSVC if possible.
On 3/23/21 11:32 AM, Jon Evans
On 3/23/21 11:20 AM, Jon Evans wrote:
> It sounds like the preference is to move away from using a config.h at
> all, which means all the KiCad packaging systems would need to update to
> use pkg-config to generate a header which can then be included in
> kicad's build process. Is that correct?
m KiCad at runtime. I was
thinking running it from CMake at build time to fetch the ngspice build
version.
>
> On Mon, Mar 22, 2021 at 3:18 PM Wayne Stambaugh <mailto:stambau...@gmail.com>> wrote:
>
> Would pkg-config work on all platforms? I know it works on Linux an
Would pkg-config work on all platforms? I know it works on Linux and
msys2. I would rather not have a separate hack for every platform if we
can avoid it. Does vcpkg support pkg-config? If so, then it should be
possible to use it on msvc builds as well.
On 3/22/21 2:57 PM, Jon Evans wrote:
>
On 3/20/21 11:02 AM, RigoLigo RLC wrote:
> I have a few questions about the current KiCad development.
>
> 1. new features after feature freeze?
>
> Most significantly, the separate icon set. While everyone is looking
> forward to having this small feature, it's still kinda offending the
> term
o a
> different file (not sim/ngspice.h) with no
> dependencies on ngspice itself, the settings class
> can be built without ngspice.
>
> On Thu, Mar 18, 2021 at 6:57 PM Wayne Stambaugh
> mailto:s
R_SETTINGS to a different file (not sim/ngspice.h)
> with no dependencies on ngspice itself, the settings class can be
> built without ngspice.
>
> On Thu, Mar 18, 2021 at 6:57 PM Wayne Stambaugh
> mailto:stambau...@gmail.com>> wrote:
>
> I thought abo
pice.h) with
> no dependencies on ngspice itself, the settings class can be built
> without ngspice.
>
> On Thu, Mar 18, 2021 at 6:57 PM Wayne Stambaugh <mailto:stambau...@gmail.com>> wrote:
>
> I thought about that but in what context does a simulation make sense
>
> make the settings not depend on ngspice)
>
> That way if the same settings files are shared between a build with
> ngspice and a build without, they won't get thrown away.
>
> On Thu, Mar 18, 2021 at 6:37 PM Wayne Stambaugh <mailto:stambau...@gmail.com>> wrote:
>
&
My bad. I forgot the simulator was a build option so I will have to
#ifdef the offending settings code.
- Wayne
On 3/18/21 6:02 PM, Eeli Kaikkonen wrote:
> I have disabled ngspice in cmake settings but in a recent commit by
> Wayne #include , which in turn includes
> ngspice/sharedspice.h, was
Awesome work Jon. Thanks.
- Wayne
On 3/11/21 8:43 AM, Jon Evans wrote:
> Hi all,
>
> As of 18037e2f, a new data file is generated during build that contains
> image resources for KiCad.
>
> This file should be installed to ${KICAD_DATA}/resources/images.tar.gz
> (So, something like
:
> Is ist possible to remove the remaining information from launchpad and make
> it clear that we moved?
>
> Clemens
>
> On 04/03/2021 13.44, Wayne Stambaugh wrote:
>> All KiCad development and bug tracking has been moved to GitLab. Only
>> the mailing lis
All KiCad development and bug tracking has been moved to GitLab. Only
the mailing list hosting remains on Launchpad.
- Wayne
On 2/19/21 2:23 PM, Christopher Buckley wrote:
> Are you guys still using launchpad for bug reporting / tracking?
>
> Latest bug I've found there is for June 2020...
>
Thanks!
On 2/27/21 8:54 AM, Jon Evans wrote:
> Should be fixed now.
>
> On Sat, Feb 27, 2021 at 7:48 AM Wayne Stambaugh <mailto:stambau...@gmail.com>> wrote:
>
> Looks like a commit in the last 24 hours broke KiCad builds with Python
> enabled. Here is the
Looks like a commit in the last 24 hours broke KiCad builds with Python
enabled. Here is the build error on Linux using gcc 9.3.0.
In file included from
/usr/include/x86_64-linux-gnu/c++/9/bits/c++allocator.h:33,
from /usr/include/c++/9/bits/allocator.h:46,
from
Any code contributed to KiCad would have to be release under the GPL3+
or compatible license to be accepted. Linking to proprietary drivers is
not an issue since we already link to Windows and MacOS proprietrary
libraries in order to provide KiCad on those platforms. We just cannot
ship those
Up until the conversion to the new library file format, I'm pretty sure
the 5.1.x tags are the same between GitHub and GitLab. Apparently the
PCIe symbol library was added after the 5.1.9 tag and wont be available
until V6 unless users check out the last commit before the libraries
were converted
String and icon freeze will happen at RC1. We still have several
outstanding feature freeze exceptions that need to be merged so RC1 is
looking like the end of Q1 (March) at the earliest.
Cheers,
Wayne
On 2/6/21 8:07 AM, Константин Барановский wrote:
> Could we have an icon freeze for the 6.0
Holger,
You should use something like NGSPICE_PACKAGE_VERSION to avoid namespace
clashes with other header version definitions. PACKAGE_VERSION seems
like it could be an issue.
Cheers,
Wayne
On 2/4/21 3:38 PM, Holger Vogt wrote:
> I prefer adding
> #define PACKAGE_VERSION "34+"
> to
yne,
>
> appreciate your heads up.
>
> Will restart with current file format.
>
> Cheers
>
> Johannes
>
> On 1/02/21 1:52 am, Wayne Stambaugh wrote:
>> Hi Johannes,
>>
>> The new schematic and symbol file formats are frozen unless we find a
>
f my previous efforts.
>
> Are there any activities already underway?
>
> Cheers
>
> Johannes
>
>
> On 13/08/19 11:46 pm, Wayne Stambaugh wrote:
>> Hi Johannes,
>>
>> The the new file format work is in progress and should be done in a few
>> months. The
Holger,
Thanks for the fixes. Hopefully our packagers can get this into as many
of our nightly builds as feasible. I know there will likely be some
distro related packaging issues but we should be able to support a large
number of builds.
Cheers,
Wayne
On 1/30/21 10:10 AM, Holger Vogt wrote:
Hi Sywester,
Turtle mocks looks like a better fit than gMock/gTest since it's based
on Boost which is already a dependency. At least it looks like the
project is still maintained. I don't know how it compares feature wise
to gMock so there may some things missing but are they significant
enough
Hi Reece,
We are officially in feature freeze so this is going to have to wait
until V7. I would rather not add another exception to the freeze list
as we are deeper into the freeze than I would like to be and still have
outstanding features to commit.
Cheers,
Wayne
On 12/30/20 11:53 PM,
On 12/23/20 9:38 AM, Steven A. Falco wrote:
> On 12/23/20 9:36 AM, Wayne Stambaugh wrote:
>> On 12/23/20 5:20 AM, Carsten Schoenert wrote:
>>> Hell Nick,
>>>
>>> Am 23.12.20 um 10:07 schrieb Nick Østergaard:
>>>> Hi Carsten
>>>>
>>
On 12/23/20 5:20 AM, Carsten Schoenert wrote:
> Hell Nick,
>
> Am 23.12.20 um 10:07 schrieb Nick Østergaard:
>> Hi Carsten
>>
>> This is a balancing act. Quite some time ago we decided that we should
>> make the release _announcement_ (on the website) when we have build
>> available for some
r macos and ubuntu ppa as well.
>
>
> On Tue, 22 Dec 2020 at 21:14, Wayne Stambaugh <mailto:stambau...@gmail.com>> wrote:
> >
> > 5.1.9 has been tagged for release. Please tag the library, doc, and
> > translation repos for release. I don
5.1.9 has been tagged for release. Please tag the library, doc, and
translation repos for release. I don't think we have much in the way of
changes there so is a week to get these repos tagged and another week to
get packages built for a January 5th release work for everyone? Please
let me know
I just tagged the 5.1 branch for the 5.1.8 stable release. Please tag
any remaining repos as required so we can get the packages build and
uploaded. I would like to make the release announcement next Wednesday.
Is that enough time for everyone? Thanks again to everyone who made
this release
ain site (blog) or
> the forum as well so we can spread the word?
>
> On Wed, Oct 7, 2020 at 8:23 AM Wayne Stambaugh <mailto:stambau...@gmail.com>> wrote:
>
> I am happy to announce that Mark Roszko and Thomas Pointhuber have
> accepted invitations to the KiCa
I am happy to announce that Mark Roszko and Thomas Pointhuber have
accepted invitations to the KiCad lead development team. Mark and
Thomas have be long time contributors to the KiCad project and I look
forward to their contributions as lead developers. Please join me in
congratulating them in
rmat for V6 frozen too?
>
> I want to start working with V5.99 for real work. I know the risks, but
> the risks are higher if the file format may be changed in a near future.
> I mean, I want ot be sure that the files will be opened with any V6 update.
>
> Thanks.
> Pedro.
>
Hi Marco,
On 10/3/20 11:55 AM, Marco Ciampa wrote:
> On Fri, Oct 02, 2020 at 06:46:05PM -0400, Wayne Stambaugh wrote:
>> As of now, the development branch of KiCad is closed for new feature
>> merges except for the items on the exception list. A new feature freeze
>> e
As of now, the development branch of KiCad is closed for new feature
merges except for the items on the exception list. A new feature freeze
exception tag has been created to tag existing merge requests that fall
into the exception category. All new feature merge requests will be
pushed back
1 - 100 of 5421 matches
Mail list logo
