It's official. We are now in the feature freeze for the stable 5
release. For those of you who have commit privileges, please do not
commit any new features to the development branch until after the stable
5 branch is created. I may make exceptions but it would take a lot of
convincing. For
On Mon, Jun 15, 2015 at 06:29:29PM +0200, jp charras wrote:
[[snip]]
keywords like UNDEFINED, INFO, WARNING , ERROR are widely used, the
risk of collision is high.
Usually I use something like:
RPT_UNDEFINED, RPT_INFO , RPT_WARNING , RPT_ERROR
to avoid this risk.
What about namespaces?
On 6/15/2015 12:29 PM, jp charras wrote:
Le 15/06/2015 16:27, Maciej Sumiński a écrit :
On 03/30/2015 12:00 AM, Tomasz Wlostowski wrote:
Hi Wayne,
Some time ago I modified a bit the REPORTER class: added message
severity levels a wxHtmlView widget to filter/display them
(see attached
Le 15/06/2015 16:27, Maciej Sumiński a écrit :
On 03/30/2015 12:00 AM, Tomasz Wlostowski wrote:
Hi Wayne,
Some time ago I modified a bit the REPORTER class: added message
severity levels a wxHtmlView widget to filter/display them
(see attached drawing showing the new report panel
On 4/26/2015 5:58 PM, Tomasz Wlostowski wrote:
On 02.04.2015 16:37, Wayne Stambaugh wrote:
Did you create a new REPORTER object with the HTML message severity
levels or did you change the existing one?
Hey Wayne,
The changes are:
- the interface of the base REPORTER class now includes
On 02.04.2015 16:37, Wayne Stambaugh wrote:
Did you create a new REPORTER object with the HTML message severity
levels or did you change the existing one?
Hey Wayne,
The changes are:
- the interface of the base REPORTER class now includes severity
parameter in Report() method,
Hi Wayne,
On 3/30/2015 5:02 PM, Tomasz Wlostowski wrote:
On 30.03.2015 21:50, Wayne Stambaugh wrote:
On 3/29/2015 6:00 PM, Tomasz Wlostowski wrote:
On 29.03.2015 23:23, Wayne Stambaugh wrote:
Attention all developers. I have finally committed the environment
variable configuration dialog (although I
Hi! :)
I have kept thinking about the new python API, I still don’t consider it
ready,
and I believe it could make sense to have them separate from tree,
with stable releases tracking the Kicad stable releases, and a development
branch.
This way, we can use the plain C++ python API in-tree
Den 30/03/2015 01.47 skrev Wayne Stambaugh stambau...@gmail.com:
On 3/29/2015 5:55 PM, Nick Østergaard wrote:
2015-03-29 23:53 GMT+02:00 Wayne Stambaugh stambau...@gmail.com:
On 3/29/2015 5:50 PM, Nick Østergaard wrote:
2015-03-29 23:44 GMT+02:00 Wayne Stambaugh stambau...@gmail.com:
On
On 3/30/2015 4:01 AM, Nick Østergaard wrote:
Den 30/03/2015 01.47 skrev Wayne Stambaugh stambau...@gmail.com
mailto:stambau...@gmail.com:
On 3/29/2015 5:55 PM, Nick Østergaard wrote:
2015-03-29 23:53 GMT+02:00 Wayne Stambaugh stambau...@gmail.com
mailto:stambau...@gmail.com:
On
On 3/30/2015 8:40 AM, Wayne Stambaugh wrote:
On 3/30/2015 4:01 AM, Nick Østergaard wrote:
Den 30/03/2015 01.47 skrev Wayne Stambaugh stambau...@gmail.com
mailto:stambau...@gmail.com:
On 3/29/2015 5:55 PM, Nick Østergaard wrote:
2015-03-29 23:53 GMT+02:00 Wayne Stambaugh
Den 30/03/2015 15.25 skrev Wayne Stambaugh stambau...@gmail.com:
On 3/30/2015 8:40 AM, Wayne Stambaugh wrote:
On 3/30/2015 4:01 AM, Nick Østergaard wrote:
Den 30/03/2015 01.47 skrev Wayne Stambaugh stambau...@gmail.com
mailto:stambau...@gmail.com:
On 3/29/2015 5:55 PM, Nick
On 3/29/2015 6:00 PM, Tomasz Wlostowski wrote:
On 29.03.2015 23:23, Wayne Stambaugh wrote:
Attention all developers. I have finally committed the environment
variable configuration dialog (although I named it the Path
Configuration because the term environment variable is apparently too
2015-03-30 0:00 GMT+02:00 Tomasz Wlostowski tomasz.wlostow...@cern.ch:
On 29.03.2015 23:23, Wayne Stambaugh wrote:
Attention all developers. I have finally committed the environment
variable configuration dialog (although I named it the Path
Configuration because the term environment variable
On 30.03.2015 21:50, Wayne Stambaugh wrote:
On 3/29/2015 6:00 PM, Tomasz Wlostowski wrote:
On 29.03.2015 23:23, Wayne Stambaugh wrote:
Attention all developers. I have finally committed the environment
variable configuration dialog (although I named it the Path
Configuration because the
Thank you for the announcement. Hopefully we can then close a lot of
bugs then, not that this is something that has not been done in the
meantime. Thumbs up.
But it seems like the newest commit does not build on the build
server. Please see:
http://ci.kicad-pcb.org/job/kicad-full/319/console
Do
2015-03-29 23:53 GMT+02:00 Wayne Stambaugh stambau...@gmail.com:
On 3/29/2015 5:50 PM, Nick Østergaard wrote:
2015-03-29 23:44 GMT+02:00 Wayne Stambaugh stambau...@gmail.com:
On 3/29/2015 5:38 PM, Nick Østergaard wrote:
Thank you for the announcement. Hopefully we can then close a lot of
bugs
Attention all developers. I have finally committed the environment
variable configuration dialog (although I named it the Path
Configuration because the term environment variable is apparently too
scary) so we are now in feature freeze. This means if you want to add a
new feature or change any
On 3/29/2015 5:38 PM, Nick Østergaard wrote:
Thank you for the announcement. Hopefully we can then close a lot of
bugs then, not that this is something that has not been done in the
meantime. Thumbs up.
I'll have some more info on that over the next few days so we can start
focusing on the
Adam,
Thanks. This will be helpful to get all of the latest code tested.
Cheers,
Wayne
On 3/29/2015 5:46 PM, Adam Wolf wrote:
Hi Wayne,
Excellent. I am working on some OS X specific bugfixes. Also, I should
be back in the States (and to decent bandwidth) by Thursday, so I should
be
On 3/29/2015 5:50 PM, Nick Østergaard wrote:
2015-03-29 23:44 GMT+02:00 Wayne Stambaugh stambau...@gmail.com:
On 3/29/2015 5:38 PM, Nick Østergaard wrote:
Thank you for the announcement. Hopefully we can then close a lot of
bugs then, not that this is something that has not been done in the
Lol :)
Miguel Ángel Ajo
On Tuesday, 24 de February de 2015 at 17:28, Wayne Stambaugh wrote:
Damn! Too late for 4.0.0. Better one up Linus by using 5.0.0. :)
On 2/24/2015 11:30 AM, Adam Wolf wrote:
Hi Wayne,
Any chance you can make a call on 3.0.0 vs 4.0.0?
(Torvalds just
Damn! Too late for 4.0.0. Better one up Linus by using 5.0.0. :)
On 2/24/2015 11:30 AM, Adam Wolf wrote:
Hi Wayne,
Any chance you can make a call on 3.0.0 vs 4.0.0?
(Torvalds just took Linux to 4.0 this week :))
Adam Wolf
On Tue, Feb 24, 2015 at 10:22 AM, Wayne Stambaugh
Here is the stable release policy:
http://ci.kicad-pcb.org/job/kicad-doxygen/ws/Documentation/doxygen/html/md_Documentation_development_stable-release-policy.html
I still need to add the numbering system to this.
On 2/24/2015 11:00 AM, Adam Wolf wrote:
Hi folks,
I have started and deleted
Den 24/02/2015 17.00 skrev Adam Wolf adamw...@feelslikeburning.com:
Hi folks,
I have started and deleted this email multiple times. I really don't
enjoy discussions like this, but sometimes they're necessary.
I have ran into quite a few misconceptions recently from non-devs about
what the
Hi Wayne,
Any chance you can make a call on 3.0.0 vs 4.0.0?
(Torvalds just took Linux to 4.0 this week :))
Adam Wolf
On Tue, Feb 24, 2015 at 10:22 AM, Wayne Stambaugh stambau...@gmail.com
wrote:
Here is the stable release policy:
Hi folks,
I have started and deleted this email multiple times. I really don't enjoy
discussions like this, but sometimes they're necessary.
I have ran into quite a few misconceptions recently from non-devs about
what the upcoming release is going to be. The issues I am seeing seem to
hinge
27 matches
Mail list logo
