[Kicad-developers] Feature freeze.
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 those of you who do not have commit privileges, please do not submit any new feature request patches until the stable 5 branch. Only bug fixes and existing feature polishing is allowed. Everyone please find an open bug report and fix it if possible. The sooner we get the stable 5 release out, the sooner we can start working on the stable 6 features. Many thanks to everyone who made this possible. I appreciate your continued efforts to make KiCad the best it can be. 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
Re: [Kicad-developers] Feature freeze.
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? Thanks. -- Jean-Pierre CHARRAS ___ 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] Feature freeze.
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 drawing showing the new report panel integrated
with the netlist dialog). Do you agree to merge it?
Cheers, Tom
I enclose Tom's patch rebased on the current revision. I can merge
it, if there are no further objections.
Regards, Orson
I tested the patch (after a fix), and it looks very good.
However, on Windows, there is a conflict with something, in reporter.h.
the code:
public:
/// Severity of the reported messages. Prov
enum SEVERITY {
UNDEFINED = 0x0,
INFO = 0x1,
WARNING = 0x2,
ERROR = 0x4,
ACTION = 0x8
};
conflicts, in line ERROR = 0x4,
I just modified it to:
public:
/// Severity of the reported messages. Prov
enum SEVERITY {
UNDEFINED = 0x0,
INFO = 0x1,
WARNING = 0x2,
RPT_ERROR = 0x4,
ACTION = 0x8
};
to fix it.
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.
Thanks.
If we are going to use the RPT_ prefix to resolve the conflict on
windows, I prefer that it be used for all of the enums for readability.
Either this or a namespace. I really don't have a preference.
Thanks,
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
Re: [Kicad-developers] Feature freeze.
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 integrated
with the netlist dialog). Do you agree to merge it?
Cheers, Tom
I enclose Tom's patch rebased on the current revision. I can merge
it, if there are no further objections.
Regards, Orson
I tested the patch (after a fix), and it looks very good.
However, on Windows, there is a conflict with something, in reporter.h.
the code:
public:
/// Severity of the reported messages. Prov
enum SEVERITY {
UNDEFINED = 0x0,
INFO = 0x1,
WARNING = 0x2,
ERROR = 0x4,
ACTION = 0x8
};
conflicts, in line ERROR = 0x4,
I just modified it to:
public:
/// Severity of the reported messages. Prov
enum SEVERITY {
UNDEFINED = 0x0,
INFO = 0x1,
WARNING = 0x2,
RPT_ERROR = 0x4,
ACTION = 0x8
};
to fix it.
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.
Thanks.
--
Jean-Pierre CHARRAS
___
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] Feature freeze.
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 severity parameter in Report() method, Hi Wayne, Sorry for digging this one out so late. I haven't been recently too much into into Kicad development :/ Understood. I was on a week long business trip two weeks ago and I'm still trying to get caught up. Is the default severity none or normal so that existing code still has the same look as before your changes? The default severity is undefined - which means the message will always appear in the HTML control, without any label (just like in the old reporter). - made the filtering internal to REPORTER object or its derivatives (means less code on the client side, because one needs no longer check if a message type is enabled before generating it) - added a WX_HTML_REPORT_PANEL class (the widget itself, with filtering options save report to file button) - updated plotter, export netlist windows to use the new reporter - cleaned up and standardized the messages a little bit (e.g. removed ' ERROR: something' -like messages) - added a short error message field in the IO_ERROR class (IMHO telling the user that a file was not found by showing source code file names and line/function numbers is a bit scary...). Please do not remove this for debug builds. As a developer, it is extremely valuable when determining where an error occurred in the file parser. For release builds I'm fine with removing the source code file name, function, line number, etc. I intended the short error messages only for 'dumb user' message boxes. The original, long message with the full location info (line, etc) is still there and I find it indeed very useful for debugging! Cheers, Tom PS. Now I perhaps will have to rebase the report widget on the fresh master, so give me a day or two to do that ;) No problem. I'll try to look at it as soon as you send it to me. Thanks, 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
Re: [Kicad-developers] Feature freeze.
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, Sorry for digging this one out so late. I haven't been recently too much into into Kicad development :/ Is the default severity none or normal so that existing code still has the same look as before your changes? The default severity is undefined - which means the message will always appear in the HTML control, without any label (just like in the old reporter). - made the filtering internal to REPORTER object or its derivatives (means less code on the client side, because one needs no longer check if a message type is enabled before generating it) - added a WX_HTML_REPORT_PANEL class (the widget itself, with filtering options save report to file button) - updated plotter, export netlist windows to use the new reporter - cleaned up and standardized the messages a little bit (e.g. removed ' ERROR: something' -like messages) - added a short error message field in the IO_ERROR class (IMHO telling the user that a file was not found by showing source code file names and line/function numbers is a bit scary...). Please do not remove this for debug builds. As a developer, it is extremely valuable when determining where an error occurred in the file parser. For release builds I'm fine with removing the source code file name, function, line number, etc. I intended the short error messages only for 'dumb user' message boxes. The original, long message with the full location info (line, etc) is still there and I find it indeed very useful for debugging! Cheers, Tom PS. Now I perhaps will have to rebase the report widget on the fresh master, so give me a day or two to do that ;) ___ 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] Feature freeze.
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 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 functional behavior you must run it by the developers list first. This includes me as well. The only thing I'm aware that's already in the pipe line at the moment is the footprint wizard that Orson is working on so that can be committed without approval. 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 integrated with the netlist dialog). Do you agree to merge it? Cheers, Tom Hey Tom, 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, Is the default severity none or normal so that existing code still has the same look as before your changes? - made the filtering internal to REPORTER object or its derivatives (means less code on the client side, because one needs no longer check if a message type is enabled before generating it) - added a WX_HTML_REPORT_PANEL class (the widget itself, with filtering options save report to file button) - updated plotter, export netlist windows to use the new reporter - cleaned up and standardized the messages a little bit (e.g. removed ' ERROR: something' -like messages) - added a short error message field in the IO_ERROR class (IMHO telling the user that a file was not found by showing source code file names and line/function numbers is a bit scary...). Please do not remove this for debug builds. As a developer, it is extremely valuable when determining where an error occurred in the file parser. For release builds I'm fine with removing the source code file name, function, line number, etc. The code is on my Github [1]. It also includes some refactoring of the BOARD object that encapsulates legacy ratsnest and pads list in a separate classes to make the code more manageable). The reporter stuff can be of course applied separately. I know Orson had some patches for it too, so give me a day or two to apply them and make a final version. If you changed the existing one, does it effect the default HTML control behavior? Nope, it does not touch it. I think this would be something that would be useful and fairly low risk to include before the next stable release. I'm not sure I would use it to replace wxRichMessageDialog. I didn't change this either. Cheers, Tom [1] https://github.com/twlostow/kicad-dev/tree/tom-refactor-ratsnest-and-new-reporter ___ 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] Feature freeze.
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 to do CI over KiCad, and have a separate package for python the python API SDK, or have the building tools installing the python modules along. (If we also distribute via pip it could be something as simple as calling “pip install kicad-python”) Thoughts? For stable version tracking, do we have already a name, version numbering, or something equivalent for the soon-to-be stable release, and the next one? Best, Miguel Ángel Ajo On Monday, 30 de March de 2015 at 1:46, Wayne Stambaugh wrote: 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 3/29/2015 5:50 PM, Nick Østergaard wrote: 2015-03-29 23:44 GMT+02:00 Wayne Stambaugh stambau...@gmail.com (mailto: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 meantime. Thumbs up. I'll have some more info on that over the next few days so we can start focusing on the stable release. 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 the environment require an update? Are you building this against wx 2.8? Your build is failing for undefined wxRichMessageDialog which is only available since wx 2.9.5. No, this is against 3.0.1 according to wx-config --version. I wonder if there is a custom build option when building wxWidgets under linux to enable this. I hope not. Otherwise, everyone's linux builds will be broken. I may be implementing our own custom rich message box sooner than I thought. I will try to build it on linux as soon as I can to see if I have the some problem. It builds fine on the fedora20 machine, with wx 3.0.2. This is using Ajo's wx stuff IIRC. I just finished building this on my Debian testing system and it build fine so it appears that it may be something wrong with you wx 3.0.1 build. 2015-03-29 23:23 GMT+02:00 Wayne Stambaugh stambau...@gmail.com (mailto:stambau...@gmail.com): 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 functional behavior you must run it by the developers list first. This includes me as well. The only thing I'm aware that's already in the pipe line at the moment is the footprint wizard that Orson is working on so that can be committed without approval. Please test the path configuration editor to make sure it is robust for the stable release. I did not do anything too fancy in the wxGrid control used in the editor so the grid editing will be very basic. Also, I kept the default wxGrid tab key behavior which means you will have to use Ctrl+Tab to perform the default action which is the OK button. I also created a warning dialog using wxRichMessageDialog when an externally defined environment variable is modified. I'm not really thrilled with the appearance of this dialog so I will most like roll my own version that will look a bit like our exit dialog but feed back would be appreciated. This also means that KiCad will no longer build against wxWidgets 2.8 for anyone out there still clinging to that version. Now that we are in feature freeze it's time to take stock on what is going on in other areas such as documentation and nightly builds so I will be sending out additional topic specific messages over the next few days. Thanks, Wayne ___ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net (mailto:kicad-developers@lists.launchpad.net) Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp
Re: [Kicad-developers] Feature freeze.
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 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 stable release. 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 the environment require an update? Are you building this against wx 2.8? Your build is failing for undefined wxRichMessageDialog which is only available since wx 2.9.5. No, this is against 3.0.1 according to wx-config --version. I wonder if there is a custom build option when building wxWidgets under linux to enable this. I hope not. Otherwise, everyone's linux builds will be broken. I may be implementing our own custom rich message box sooner than I thought. I will try to build it on linux as soon as I can to see if I have the some problem. It builds fine on the fedora20 machine, with wx 3.0.2. This is using Ajo's wx stuff IIRC. I just finished building this on my Debian testing system and it build fine so it appears that it may be something wrong with you wx 3.0.1 build. What is the wx version on your debian system? 2015-03-29 23:23 GMT+02:00 Wayne Stambaugh stambau...@gmail.com: 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 functional behavior you must run it by the developers list first. This includes me as well. The only thing I'm aware that's already in the pipe line at the moment is the footprint wizard that Orson is working on so that can be committed without approval. Please test the path configuration editor to make sure it is robust for the stable release. I did not do anything too fancy in the wxGrid control used in the editor so the grid editing will be very basic. Also, I kept the default wxGrid tab key behavior which means you will have to use Ctrl+Tab to perform the default action which is the OK button. I also created a warning dialog using wxRichMessageDialog when an externally defined environment variable is modified. I'm not really thrilled with the appearance of this dialog so I will most like roll my own version that will look a bit like our exit dialog but feed back would be appreciated. This also means that KiCad will no longer build against wxWidgets 2.8 for anyone out there still clinging to that version. Now that we are in feature freeze it's time to take stock on what is going on in other areas such as documentation and nightly builds so I will be sending out additional topic specific messages over the next few days. Thanks, 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
Re: [Kicad-developers] Feature freeze.
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 3/29/2015 5:50 PM, Nick Østergaard wrote: 2015-03-29 23:44 GMT+02:00 Wayne Stambaugh stambau...@gmail.com mailto: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 meantime. Thumbs up. I'll have some more info on that over the next few days so we can start focusing on the stable release. 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 the environment require an update? Are you building this against wx 2.8? Your build is failing for undefined wxRichMessageDialog which is only available since wx 2.9.5. No, this is against 3.0.1 according to wx-config --version. I wonder if there is a custom build option when building wxWidgets under linux to enable this. I hope not. Otherwise, everyone's linux builds will be broken. I may be implementing our own custom rich message box sooner than I thought. I will try to build it on linux as soon as I can to see if I have the some problem. It builds fine on the fedora20 machine, with wx 3.0.2. This is using Ajo's wx stuff IIRC. I just finished building this on my Debian testing system and it build fine so it appears that it may be something wrong with you wx 3.0.1 build. What is the wx version on your debian system? 3.0.2. I'm using the standard version in the testing branch of Debian (Jessie). 2015-03-29 23:23 GMT+02:00 Wayne Stambaugh stambau...@gmail.com mailto:stambau...@gmail.com: 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 functional behavior you must run it by the developers list first. This includes me as well. The only thing I'm aware that's already in the pipe line at the moment is the footprint wizard that Orson is working on so that can be committed without approval. Please test the path configuration editor to make sure it is robust for the stable release. I did not do anything too fancy in the wxGrid control used in the editor so the grid editing will be very basic. Also, I kept the default wxGrid tab key behavior which means you will have to use Ctrl+Tab to perform the default action which is the OK button. I also created a warning dialog using wxRichMessageDialog when an externally defined environment variable is modified. I'm not really thrilled with the appearance of this dialog so I will most like roll my own version that will look a bit like our exit dialog but feed back would be appreciated. This also means that KiCad will no longer build against wxWidgets 2.8 for anyone out there still clinging to that version. Now that we are in feature freeze it's time to take stock on what is going on in other areas such as documentation and nightly builds so I will be sending out additional topic specific messages over the next few days. Thanks, Wayne ___ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net mailto: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] Feature freeze.
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 stambau...@gmail.com mailto: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 mailto: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 meantime. Thumbs up. I'll have some more info on that over the next few days so we can start focusing on the stable release. 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 the environment require an update? Are you building this against wx 2.8? Your build is failing for undefined wxRichMessageDialog which is only available since wx 2.9.5. No, this is against 3.0.1 according to wx-config --version. I wonder if there is a custom build option when building wxWidgets under linux to enable this. I hope not. Otherwise, everyone's linux builds will be broken. I may be implementing our own custom rich message box sooner than I thought. I will try to build it on linux as soon as I can to see if I have the some problem. It builds fine on the fedora20 machine, with wx 3.0.2. This is using Ajo's wx stuff IIRC. I just finished building this on my Debian testing system and it build fine so it appears that it may be something wrong with you wx 3.0.1 build. What is the wx version on your debian system? 3.0.2. I'm using the standard version in the testing branch of Debian (Jessie). Nick, I found the problem. Apparently the wxWidgets folks changed the definition of the constructor between versions 3.0.1 and 3.0.2. I just ran into the issue on my work computer. I'll have a fix committed shortly assuming it still builds correctly against 3.0.2 Wayne 2015-03-29 23:23 GMT+02:00 Wayne Stambaugh stambau...@gmail.com mailto:stambau...@gmail.com: 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 functional behavior you must run it by the developers list first. This includes me as well. The only thing I'm aware that's already in the pipe line at the moment is the footprint wizard that Orson is working on so that can be committed without approval. Please test the path configuration editor to make sure it is robust for the stable release. I did not do anything too fancy in the wxGrid control used in the editor so the grid editing will be very basic. Also, I kept the default wxGrid tab key behavior which means you will have to use Ctrl+Tab to perform the default action which is the OK button. I also created a warning dialog using wxRichMessageDialog when an externally defined environment variable is modified. I'm not really thrilled with the appearance of this dialog so I will most like roll my own version that will look a bit like our exit dialog but feed back would be appreciated. This also means that KiCad will no longer build against wxWidgets 2.8 for anyone out there still clinging to that version. Now that we are in feature freeze it's time to take stock on what is going on in other areas such as documentation and nightly builds so I will be sending out additional topic specific messages over the next few days. Thanks, Wayne ___ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net mailto: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] Feature freeze.
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 Østergaard wrote: 2015-03-29 23:53 GMT+02:00 Wayne Stambaugh stambau...@gmail.com mailto: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 mailto: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 meantime. Thumbs up. I'll have some more info on that over the next few days so we can start focusing on the stable release. 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 the environment require an update? Are you building this against wx 2.8? Your build is failing for undefined wxRichMessageDialog which is only available since wx 2.9.5. No, this is against 3.0.1 according to wx-config --version. I wonder if there is a custom build option when building wxWidgets under linux to enable this. I hope not. Otherwise, everyone's linux builds will be broken. I may be implementing our own custom rich message box sooner than I thought. I will try to build it on linux as soon as I can to see if I have the some problem. It builds fine on the fedora20 machine, with wx 3.0.2. This is using Ajo's wx stuff IIRC. I just finished building this on my Debian testing system and it build fine so it appears that it may be something wrong with you wx 3.0.1 build. What is the wx version on your debian system? 3.0.2. I'm using the standard version in the testing branch of Debian (Jessie). Nick, I found the problem. Apparently the wxWidgets folks changed the definition of the constructor between versions 3.0.1 and 3.0.2. I just ran into the issue on my work computer. I'll have a fix committed shortly assuming it still builds correctly against 3.0.2 Great, it seems to work both on 1 and 2 on Jenkins now. Thank you for fixing. Wayne 2015-03-29 23:23 GMT+02:00 Wayne Stambaugh stambau...@gmail.com mailto:stambau...@gmail.com: 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 functional behavior you must run it by the developers list first. This includes me as well. The only thing I'm aware that's already in the pipe line at the moment is the footprint wizard that Orson is working on so that can be committed without approval. Please test the path configuration editor to make sure it is robust for the stable release. I did not do anything too fancy in the wxGrid control used in the editor so the grid editing will be very basic. Also, I kept the default wxGrid tab key behavior which means you will have to use Ctrl+Tab to perform the default action which is the OK button. I also created a warning dialog using wxRichMessageDialog when an externally defined environment variable is modified. I'm not really thrilled with the appearance of this dialog so I will most like roll my own version that will look a bit like our exit dialog but feed back would be appreciated. This also means that KiCad will no longer build against wxWidgets 2.8 for anyone out there still clinging to that version. Now that we are in feature freeze it's time to take stock on what is going on in other areas such as documentation and nightly builds so I will be sending out additional topic specific messages over the next few days. Thanks, Wayne ___ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net mailto: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] Feature freeze.
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 scary) so we are now in feature freeze. This means if you want to add a new feature or change any functional behavior you must run it by the developers list first. This includes me as well. The only thing I'm aware that's already in the pipe line at the moment is the footprint wizard that Orson is working on so that can be committed without approval. 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 integrated with the netlist dialog). Do you agree to merge it? Cheers, Tom Hey Tom, Did you create a new REPORTER object with the HTML message severity levels or did you change the existing one? If you changed the existing one, does it effect the default HTML control behavior? I think this would be something that would be useful and fairly low risk to include before the next stable release. I'm not sure I would use it to replace wxRichMessageDialog. Anyone else have any issues with this. Thanks, 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
Re: [Kicad-developers] Feature freeze.
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 is apparently too scary) so we are now in feature freeze. This means if you want to add a new feature or change any functional behavior you must run it by the developers list first. This includes me as well. The only thing I'm aware that's already in the pipe line at the moment is the footprint wizard that Orson is working on so that can be committed without approval. 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 integrated with the netlist dialog). Do you agree to merge it? Cheers, Tom I think the new view looks nice. If you judge this is not a high risk patch, I would definitely vote to get it in. ___ 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] Feature freeze.
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 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 functional behavior you must run it by the developers list first. This includes me as well. The only thing I'm aware that's already in the pipe line at the moment is the footprint wizard that Orson is working on so that can be committed without approval. 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 integrated with the netlist dialog). Do you agree to merge it? Cheers, Tom Hey Tom, 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, - made the filtering internal to REPORTER object or its derivatives (means less code on the client side, because one needs no longer check if a message type is enabled before generating it) - added a WX_HTML_REPORT_PANEL class (the widget itself, with filtering options save report to file button) - updated plotter, export netlist windows to use the new reporter - cleaned up and standardized the messages a little bit (e.g. removed ' ERROR: something' -like messages) - added a short error message field in the IO_ERROR class (IMHO telling the user that a file was not found by showing source code file names and line/function numbers is a bit scary...). The code is on my Github [1]. It also includes some refactoring of the BOARD object that encapsulates legacy ratsnest and pads list in a separate classes to make the code more manageable). The reporter stuff can be of course applied separately. I know Orson had some patches for it too, so give me a day or two to apply them and make a final version. If you changed the existing one, does it effect the default HTML control behavior? Nope, it does not touch it. I think this would be something that would be useful and fairly low risk to include before the next stable release. I'm not sure I would use it to replace wxRichMessageDialog. I didn't change this either. Cheers, Tom [1] https://github.com/twlostow/kicad-dev/tree/tom-refactor-ratsnest-and-new-reporter ___ 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] Feature freeze.
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 the environment require an update? 2015-03-29 23:23 GMT+02:00 Wayne Stambaugh stambau...@gmail.com: 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 functional behavior you must run it by the developers list first. This includes me as well. The only thing I'm aware that's already in the pipe line at the moment is the footprint wizard that Orson is working on so that can be committed without approval. Please test the path configuration editor to make sure it is robust for the stable release. I did not do anything too fancy in the wxGrid control used in the editor so the grid editing will be very basic. Also, I kept the default wxGrid tab key behavior which means you will have to use Ctrl+Tab to perform the default action which is the OK button. I also created a warning dialog using wxRichMessageDialog when an externally defined environment variable is modified. I'm not really thrilled with the appearance of this dialog so I will most like roll my own version that will look a bit like our exit dialog but feed back would be appreciated. This also means that KiCad will no longer build against wxWidgets 2.8 for anyone out there still clinging to that version. Now that we are in feature freeze it's time to take stock on what is going on in other areas such as documentation and nightly builds so I will be sending out additional topic specific messages over the next few days. Thanks, 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
Re: [Kicad-developers] Feature freeze.
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 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 stable release. 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 the environment require an update? Are you building this against wx 2.8? Your build is failing for undefined wxRichMessageDialog which is only available since wx 2.9.5. No, this is against 3.0.1 according to wx-config --version. I wonder if there is a custom build option when building wxWidgets under linux to enable this. I hope not. Otherwise, everyone's linux builds will be broken. I may be implementing our own custom rich message box sooner than I thought. I will try to build it on linux as soon as I can to see if I have the some problem. It builds fine on the fedora20 machine, with wx 3.0.2. This is using Ajo's wx stuff IIRC. 2015-03-29 23:23 GMT+02:00 Wayne Stambaugh stambau...@gmail.com: 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 functional behavior you must run it by the developers list first. This includes me as well. The only thing I'm aware that's already in the pipe line at the moment is the footprint wizard that Orson is working on so that can be committed without approval. Please test the path configuration editor to make sure it is robust for the stable release. I did not do anything too fancy in the wxGrid control used in the editor so the grid editing will be very basic. Also, I kept the default wxGrid tab key behavior which means you will have to use Ctrl+Tab to perform the default action which is the OK button. I also created a warning dialog using wxRichMessageDialog when an externally defined environment variable is modified. I'm not really thrilled with the appearance of this dialog so I will most like roll my own version that will look a bit like our exit dialog but feed back would be appreciated. This also means that KiCad will no longer build against wxWidgets 2.8 for anyone out there still clinging to that version. Now that we are in feature freeze it's time to take stock on what is going on in other areas such as documentation and nightly builds so I will be sending out additional topic specific messages over the next few days. Thanks, 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
[Kicad-developers] Feature freeze.
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 functional behavior you must run it by the developers list first. This includes me as well. The only thing I'm aware that's already in the pipe line at the moment is the footprint wizard that Orson is working on so that can be committed without approval. Please test the path configuration editor to make sure it is robust for the stable release. I did not do anything too fancy in the wxGrid control used in the editor so the grid editing will be very basic. Also, I kept the default wxGrid tab key behavior which means you will have to use Ctrl+Tab to perform the default action which is the OK button. I also created a warning dialog using wxRichMessageDialog when an externally defined environment variable is modified. I'm not really thrilled with the appearance of this dialog so I will most like roll my own version that will look a bit like our exit dialog but feed back would be appreciated. This also means that KiCad will no longer build against wxWidgets 2.8 for anyone out there still clinging to that version. Now that we are in feature freeze it's time to take stock on what is going on in other areas such as documentation and nightly builds so I will be sending out additional topic specific messages over the next few days. Thanks, 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
Re: [Kicad-developers] Feature freeze.
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 stable release. 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 the environment require an update? Are you building this against wx 2.8? Your build is failing for undefined wxRichMessageDialog which is only available since wx 2.9.5. 2015-03-29 23:23 GMT+02:00 Wayne Stambaugh stambau...@gmail.com: 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 functional behavior you must run it by the developers list first. This includes me as well. The only thing I'm aware that's already in the pipe line at the moment is the footprint wizard that Orson is working on so that can be committed without approval. Please test the path configuration editor to make sure it is robust for the stable release. I did not do anything too fancy in the wxGrid control used in the editor so the grid editing will be very basic. Also, I kept the default wxGrid tab key behavior which means you will have to use Ctrl+Tab to perform the default action which is the OK button. I also created a warning dialog using wxRichMessageDialog when an externally defined environment variable is modified. I'm not really thrilled with the appearance of this dialog so I will most like roll my own version that will look a bit like our exit dialog but feed back would be appreciated. This also means that KiCad will no longer build against wxWidgets 2.8 for anyone out there still clinging to that version. Now that we are in feature freeze it's time to take stock on what is going on in other areas such as documentation and nightly builds so I will be sending out additional topic specific messages over the next few days. Thanks, 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
Re: [Kicad-developers] Feature freeze.
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 able to get the new Windows nightlies up soon! Adam Wolf Cofounder and Engineer WL 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 the environment require an update? 2015-03-29 23:23 GMT+02:00 Wayne Stambaugh stambau...@gmail.com mailto:stambau...@gmail.com: 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 functional behavior you must run it by the developers list first. This includes me as well. The only thing I'm aware that's already in the pipe line at the moment is the footprint wizard that Orson is working on so that can be committed without approval. Please test the path configuration editor to make sure it is robust for the stable release. I did not do anything too fancy in the wxGrid control used in the editor so the grid editing will be very basic. Also, I kept the default wxGrid tab key behavior which means you will have to use Ctrl+Tab to perform the default action which is the OK button. I also created a warning dialog using wxRichMessageDialog when an externally defined environment variable is modified. I'm not really thrilled with the appearance of this dialog so I will most like roll my own version that will look a bit like our exit dialog but feed back would be appreciated. This also means that KiCad will no longer build against wxWidgets 2.8 for anyone out there still clinging to that version. Now that we are in feature freeze it's time to take stock on what is going on in other areas such as documentation and nightly builds so I will be sending out additional topic specific messages over the next few days. Thanks, Wayne ___ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net mailto: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 mailto: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] Feature freeze.
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 meantime. Thumbs up. I'll have some more info on that over the next few days so we can start focusing on the stable release. 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 the environment require an update? Are you building this against wx 2.8? Your build is failing for undefined wxRichMessageDialog which is only available since wx 2.9.5. No, this is against 3.0.1 according to wx-config --version. I wonder if there is a custom build option when building wxWidgets under linux to enable this. I hope not. Otherwise, everyone's linux builds will be broken. I may be implementing our own custom rich message box sooner than I thought. I will try to build it on linux as soon as I can to see if I have the some problem. 2015-03-29 23:23 GMT+02:00 Wayne Stambaugh stambau...@gmail.com: 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 functional behavior you must run it by the developers list first. This includes me as well. The only thing I'm aware that's already in the pipe line at the moment is the footprint wizard that Orson is working on so that can be committed without approval. Please test the path configuration editor to make sure it is robust for the stable release. I did not do anything too fancy in the wxGrid control used in the editor so the grid editing will be very basic. Also, I kept the default wxGrid tab key behavior which means you will have to use Ctrl+Tab to perform the default action which is the OK button. I also created a warning dialog using wxRichMessageDialog when an externally defined environment variable is modified. I'm not really thrilled with the appearance of this dialog so I will most like roll my own version that will look a bit like our exit dialog but feed back would be appreciated. This also means that KiCad will no longer build against wxWidgets 2.8 for anyone out there still clinging to that version. Now that we are in feature freeze it's time to take stock on what is going on in other areas such as documentation and nightly builds so I will be sending out additional topic specific messages over the next few days. Thanks, 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
Re: [Kicad-developers] Feature freeze and next release terminology
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 took Linux to 4.0 this week :)) Adam Wolf On Tue, Feb 24, 2015 at 10:22 AM, Wayne Stambaugh stambau...@gmail.com (mailto:stambau...@gmail.com) mailto:stambau...@gmail.com wrote: 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 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 around the word stable. As far as I know, every single source commit we make, we intend to be stable and usable, and we don't really commit half-features very often (if ever), and I have been seeing users get very confused about that based on the word stable for the upcoming release. This will always be a goal for the product branch as long as I am project leader. Keeping the development branch usable is important. As far as I know, there are going to be two things that make the upcoming release special: 1) a feature freeze beforehand so we can run manual tests, make sure our features work well, and hopefully fix any packaging issues on the main targets without any churn of new features 2) file format incompatibilities 3) A bunch of new features (gal, pns router, 64 layers, etc.) since the last stable release. What about instead of calling it stable, we called it by a version number? Kicad 2.0? I think more users would understand what we're doing. We discussed using a triplett. Most likely the upcoming release will be 3.0.0 or 4.0.0. Either is fine by me. There will never be a 3.1.X or 3.2.X because features will *not* be back ported under the current policy. Only critical errors (read crash, data loss, memory leaks, etc) will be fixed in the stable release branch so there will only be 3.0.1, 3.0.2, etc, versions. There will be no attempt to maintain compatibility with the development branch file formats. Either you bleed on the edge and help with testing or you live with the features in the current stable release. I am not reopening this subject for discussion for obvious reasons. We've beat this horse to death and given our resource limitations, this is the best compromise. This email is primarily directed at Wayne, but I like to keep things in the open if possible. Adam Wolf Cofounder and Engineer Wayne and Layne ___ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net (mailto:kicad-developers@lists.launchpad.net) mailto: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 (mailto:kicad-developers@lists.launchpad.net) mailto: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 (mailto: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] Feature freeze and next release terminology
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 stambau...@gmail.com mailto:stambau...@gmail.com wrote: 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 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 around the word stable. As far as I know, every single source commit we make, we intend to be stable and usable, and we don't really commit half-features very often (if ever), and I have been seeing users get very confused about that based on the word stable for the upcoming release. This will always be a goal for the product branch as long as I am project leader. Keeping the development branch usable is important. As far as I know, there are going to be two things that make the upcoming release special: 1) a feature freeze beforehand so we can run manual tests, make sure our features work well, and hopefully fix any packaging issues on the main targets without any churn of new features 2) file format incompatibilities 3) A bunch of new features (gal, pns router, 64 layers, etc.) since the last stable release. What about instead of calling it stable, we called it by a version number? Kicad 2.0? I think more users would understand what we're doing. We discussed using a triplett. Most likely the upcoming release will be 3.0.0 or 4.0.0. Either is fine by me. There will never be a 3.1.X or 3.2.X because features will *not* be back ported under the current policy. Only critical errors (read crash, data loss, memory leaks, etc) will be fixed in the stable release branch so there will only be 3.0.1, 3.0.2, etc, versions. There will be no attempt to maintain compatibility with the development branch file formats. Either you bleed on the edge and help with testing or you live with the features in the current stable release. I am not reopening this subject for discussion for obvious reasons. We've beat this horse to death and given our resource limitations, this is the best compromise. This email is primarily directed at Wayne, but I like to keep things in the open if possible. Adam Wolf Cofounder and Engineer Wayne and Layne ___ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net mailto: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 mailto: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] Feature freeze and next release terminology
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 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 around the word stable. As far as I know, every single source commit we make, we intend to be stable and usable, and we don't really commit half-features very often (if ever), and I have been seeing users get very confused about that based on the word stable for the upcoming release. This will always be a goal for the product branch as long as I am project leader. Keeping the development branch usable is important. As far as I know, there are going to be two things that make the upcoming release special: 1) a feature freeze beforehand so we can run manual tests, make sure our features work well, and hopefully fix any packaging issues on the main targets without any churn of new features 2) file format incompatibilities 3) A bunch of new features (gal, pns router, 64 layers, etc.) since the last stable release. What about instead of calling it stable, we called it by a version number? Kicad 2.0? I think more users would understand what we're doing. We discussed using a triplett. Most likely the upcoming release will be 3.0.0 or 4.0.0. Either is fine by me. There will never be a 3.1.X or 3.2.X because features will *not* be back ported under the current policy. Only critical errors (read crash, data loss, memory leaks, etc) will be fixed in the stable release branch so there will only be 3.0.1, 3.0.2, etc, versions. There will be no attempt to maintain compatibility with the development branch file formats. Either you bleed on the edge and help with testing or you live with the features in the current stable release. I am not reopening this subject for discussion for obvious reasons. We've beat this horse to death and given our resource limitations, this is the best compromise. This email is primarily directed at Wayne, but I like to keep things in the open if possible. Adam Wolf Cofounder and Engineer Wayne and Layne ___ 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] Feature freeze and next release terminology
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 upcoming release is going to be. The issues I am seeing seem to hinge around the word stable. As far as I know, every single source commit we make, we intend to be stable and usable, and we don't really commit half-features very often (if ever), and I have been seeing users get very confused about that based on the word stable for the upcoming release. As far as I know, there are going to be two things that make the upcoming release special: 1) a feature freeze beforehand so we can run manual tests, make sure our features work well, and hopefully fix any packaging issues on the main targets without any churn of new features 2) file format incompatibilities What about instead of calling it stable, we called it by a version number? Kicad 2.0? I think more users would understand what we're doing. That is a release IMHO. That is also the descriptive wore I would use instead of the word stable. This email is primarily directed at Wayne, but I like to keep things in the open if possible. Adam Wolf Cofounder and Engineer Wayne and Layne ___ 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] Feature freeze and next release terminology
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: 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 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 around the word stable. As far as I know, every single source commit we make, we intend to be stable and usable, and we don't really commit half-features very often (if ever), and I have been seeing users get very confused about that based on the word stable for the upcoming release. This will always be a goal for the product branch as long as I am project leader. Keeping the development branch usable is important. As far as I know, there are going to be two things that make the upcoming release special: 1) a feature freeze beforehand so we can run manual tests, make sure our features work well, and hopefully fix any packaging issues on the main targets without any churn of new features 2) file format incompatibilities 3) A bunch of new features (gal, pns router, 64 layers, etc.) since the last stable release. What about instead of calling it stable, we called it by a version number? Kicad 2.0? I think more users would understand what we're doing. We discussed using a triplett. Most likely the upcoming release will be 3.0.0 or 4.0.0. Either is fine by me. There will never be a 3.1.X or 3.2.X because features will *not* be back ported under the current policy. Only critical errors (read crash, data loss, memory leaks, etc) will be fixed in the stable release branch so there will only be 3.0.1, 3.0.2, etc, versions. There will be no attempt to maintain compatibility with the development branch file formats. Either you bleed on the edge and help with testing or you live with the features in the current stable release. I am not reopening this subject for discussion for obvious reasons. We've beat this horse to death and given our resource limitations, this is the best compromise. This email is primarily directed at Wayne, but I like to keep things in the open if possible. Adam Wolf Cofounder and Engineer Wayne and Layne ___ 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
[Kicad-developers] Feature freeze and next release terminology
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 around the word stable. As far as I know, every single source commit we make, we intend to be stable and usable, and we don't really commit half-features very often (if ever), and I have been seeing users get very confused about that based on the word stable for the upcoming release. As far as I know, there are going to be two things that make the upcoming release special: 1) a feature freeze beforehand so we can run manual tests, make sure our features work well, and hopefully fix any packaging issues on the main targets without any churn of new features 2) file format incompatibilities What about instead of calling it stable, we called it by a version number? Kicad 2.0? I think more users would understand what we're doing. This email is primarily directed at Wayne, but I like to keep things in the open if possible. Adam Wolf Cofounder and Engineer Wayne and Layne ___ 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
