Re: [Kicad-developers] 5.1 branch freeze

[Nick Østergaard]

Please see the  comments about #4328 onnthe issue itself. I don't think you
are testimg with the same conditions.

ons. 6. maj 2020 12.55 skrev jp charras :

> Le 06/05/2020 à 00:09, Nick Østergaard a écrit :
> > Mmm, when you mean branch freeze, I assume you really mean that we
> > have a string freeze for the branch.
> >
> > I am sorta wondering why we can't enable the CI, for example. [1]
> >
> > Also as a heads up, there a couple of critical issues for the 5.1.6
> > milestone being added after 5.1.6-rc1 [2], most importantly [3] and
> > [4].
> >
> > [1]
> https://gitlab.com/kicad/code/kicad/-/merge_requests/198#note_337036264
> > [2] https://gitlab.com/groups/kicad/code/-/milestones/1
> > [3] https://gitlab.com/kicad/code/kicad/-/issues/4328
> > [4] https://gitlab.com/kicad/code/kicad/-/issues/4284
> >
>
> I cannot reproduce the crashes, both on W7 and Kubuntu 18.04LTS.
> issue 4328 can be depending on libraries or Window manager (or can be
> fixed since 5.1.5.0 version).
> issue 4284 can be related to some multi-threading seg-fault, very hard to
> reproduce.
>
>
> --
> 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] 5.1 branch freeze

[jp charras]

Le 06/05/2020 à 00:09, Nick Østergaard a écrit :
> Mmm, when you mean branch freeze, I assume you really mean that we
> have a string freeze for the branch.
> 
> I am sorta wondering why we can't enable the CI, for example. [1]
> 
> Also as a heads up, there a couple of critical issues for the 5.1.6
> milestone being added after 5.1.6-rc1 [2], most importantly [3] and
> [4].
> 
> [1] https://gitlab.com/kicad/code/kicad/-/merge_requests/198#note_337036264
> [2] https://gitlab.com/groups/kicad/code/-/milestones/1
> [3] https://gitlab.com/kicad/code/kicad/-/issues/4328
> [4] https://gitlab.com/kicad/code/kicad/-/issues/4284
> 

I cannot reproduce the crashes, both on W7 and Kubuntu 18.04LTS.
issue 4328 can be depending on libraries or Window manager (or can be fixed 
since 5.1.5.0 version).
issue 4284 can be related to some multi-threading seg-fault, very hard to 
reproduce.


-- 
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] 5.1 branch freeze

[Nick Østergaard]

Mmm, when you mean branch freeze, I assume you really mean that we
have a string freeze for the branch.

I am sorta wondering why we can't enable the CI, for example. [1]

Also as a heads up, there a couple of critical issues for the 5.1.6
milestone being added after 5.1.6-rc1 [2], most importantly [3] and
[4].

[1] https://gitlab.com/kicad/code/kicad/-/merge_requests/198#note_337036264
[2] https://gitlab.com/groups/kicad/code/-/milestones/1
[3] https://gitlab.com/kicad/code/kicad/-/issues/4328
[4] https://gitlab.com/kicad/code/kicad/-/issues/4284

On Sun, 3 May 2020 at 14:26, Wayne Stambaugh  wrote:
>
> We are just under two weeks out of the 5.1.6 release.  If anyone needs
> any extra time.  Please let me know.
>
> Thanks,
>
> Wayne
>
> On 4/16/20 8:19 AM, Wayne Stambaugh wrote:
> > Done.
> >
> > On 4/16/20 7:58 AM, Nick Østergaard wrote:
> >> Just the tag in git
> >>
> >> tor. 16. apr. 2020 13.25 skrev Wayne Stambaugh  >> >:
> >>
> >> Nick,
> >>
> >> Do you need a source archive or just the tag?
> >>
> >> Cheers,
> >>
> >> Wayne
> >>
> >> On 4/16/20 3:58 AM, Nick Østergaard wrote:
> >> > Can we have a 5.1.6-rc1 tag then?
> >> >
> >> > tor. 16. apr. 2020 03.30 skrev Wayne Stambaugh
> >> mailto:stambau...@gmail.com>
> >> > >>:
> >> >
> >> > The 5.1 branch has been frozen in order to prepare for the
> >> 5.1.6 stable
> >> > release.  Please do not make any commits to the 5.1 branch
> >> without first
> >> > confirming with the lead dev team and no translated string
> >> changes.  I
> >> > would like to release on Friday, May 15th if possible so
> >> please let me
> >> > know if there is any reason we cannot make that date.  Thank
> >> you to all
> >> > the development teams for your continued efforts.
> >> >
> >> > Cheers,
> >> >
> >> > Wayne
> >> >
> >> > ___
> >> > Mailing list: https://launchpad.net/~kicad-developers
> >> > Post to : kicad-developers@lists.launchpad.net
> >> 
> >> >  >> >
> >> > Unsubscribe : https://launchpad.net/~kicad-developers
> >> > More help   : https://help.launchpad.net/ListHelp
> >> >
> >>

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

Re: [Kicad-developers] 5.1 branch freeze

[Wayne Stambaugh]

We are just under two weeks out of the 5.1.6 release.  If anyone needs
any extra time.  Please let me know.

Thanks,

Wayne

On 4/16/20 8:19 AM, Wayne Stambaugh wrote:
> Done.
> 
> On 4/16/20 7:58 AM, Nick Østergaard wrote:
>> Just the tag in git
>>
>> tor. 16. apr. 2020 13.25 skrev Wayne Stambaugh > >:
>>
>> Nick,
>>
>> Do you need a source archive or just the tag?
>>
>> Cheers,
>>
>> Wayne
>>
>> On 4/16/20 3:58 AM, Nick Østergaard wrote:
>> > Can we have a 5.1.6-rc1 tag then?
>> >
>> > tor. 16. apr. 2020 03.30 skrev Wayne Stambaugh
>> mailto:stambau...@gmail.com>
>> > >>:
>> >
>> >     The 5.1 branch has been frozen in order to prepare for the
>> 5.1.6 stable
>> >     release.  Please do not make any commits to the 5.1 branch
>> without first
>> >     confirming with the lead dev team and no translated string
>> changes.  I
>> >     would like to release on Friday, May 15th if possible so
>> please let me
>> >     know if there is any reason we cannot make that date.  Thank
>> you to all
>> >     the development teams for your continued efforts.
>> >
>> >     Cheers,
>> >
>> >     Wayne
>> >
>> >     ___
>> >     Mailing list: https://launchpad.net/~kicad-developers
>> >     Post to     : kicad-developers@lists.launchpad.net
>> 
>> >     > >
>> >     Unsubscribe : https://launchpad.net/~kicad-developers
>> >     More help   : https://help.launchpad.net/ListHelp
>> >
>>

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

Re: [Kicad-developers] 5.1 branch freeze

[Simon Richter]

Hi,

On 16.04.20 03:30, Wayne Stambaugh wrote:

> The 5.1 branch has been frozen in order to prepare for the 5.1.6 stable
> release.  Please do not make any commits to the 5.1 branch without first
> confirming with the lead dev team and no translated string changes.

Presumably that implies that translators should check whether anything
needs to be done.

Current translation status on the 5.1 branch seems to be

LANG;TRANSLATED;FUZZY;UNTRANSLATED
bg;1262;3052;1352
ca;2738;1914;1014
cs;5430;162;74
de;5666;;
el;2894;2241;531
en;5666;;
es;4566;948;152
fi;1240;2950;1476
fr;5666;;
hu;5607;40;19
it;5666;;
ja;5580;60;26
ko;370;2798;2498
lt;1853;3277;536
nl;877;3123;1666
pl;5622;34;10
pt;5656;6;4
ru;5666;;
sk;1210;2751;1705
sl;292;2598;2776
sv;342;1502;3822
zh_CN;5666;;
zh_TW;4541;954;171

Done: de, en, fr, it, ru, zh_CN

Need work: cs, hu, ja, pl, pt

The others have larger issues, and we might want to check whether they
are still maintained and/or we can find volunteers for them.

   Simon



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

Re: [Kicad-developers] 5.1 branch freeze

[Wayne Stambaugh]

Done.

On 4/16/20 7:58 AM, Nick Østergaard wrote:
> Just the tag in git
> 
> tor. 16. apr. 2020 13.25 skrev Wayne Stambaugh  >:
> 
> Nick,
> 
> Do you need a source archive or just the tag?
> 
> Cheers,
> 
> Wayne
> 
> On 4/16/20 3:58 AM, Nick Østergaard wrote:
> > Can we have a 5.1.6-rc1 tag then?
> >
> > tor. 16. apr. 2020 03.30 skrev Wayne Stambaugh
> mailto:stambau...@gmail.com>
> > >>:
> >
> >     The 5.1 branch has been frozen in order to prepare for the
> 5.1.6 stable
> >     release.  Please do not make any commits to the 5.1 branch
> without first
> >     confirming with the lead dev team and no translated string
> changes.  I
> >     would like to release on Friday, May 15th if possible so
> please let me
> >     know if there is any reason we cannot make that date.  Thank
> you to all
> >     the development teams for your continued efforts.
> >
> >     Cheers,
> >
> >     Wayne
> >
> >     ___
> >     Mailing list: https://launchpad.net/~kicad-developers
> >     Post to     : kicad-developers@lists.launchpad.net
> 
> >      >
> >     Unsubscribe : https://launchpad.net/~kicad-developers
> >     More help   : https://help.launchpad.net/ListHelp
> >
> 

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

Re: [Kicad-developers] 5.1 branch freeze

[Nick Østergaard]

Just the tag in git

tor. 16. apr. 2020 13.25 skrev Wayne Stambaugh :

> Nick,
>
> Do you need a source archive or just the tag?
>
> Cheers,
>
> Wayne
>
> On 4/16/20 3:58 AM, Nick Østergaard wrote:
> > Can we have a 5.1.6-rc1 tag then?
> >
> > tor. 16. apr. 2020 03.30 skrev Wayne Stambaugh  > >:
> >
> > The 5.1 branch has been frozen in order to prepare for the 5.1.6
> stable
> > release.  Please do not make any commits to the 5.1 branch without
> first
> > confirming with the lead dev team and no translated string changes.
> I
> > would like to release on Friday, May 15th if possible so please let
> me
> > know if there is any reason we cannot make that date.  Thank you to
> all
> > the development teams for your continued efforts.
> >
> > Cheers,
> >
> > Wayne
> >
> > ___
> > Mailing list: https://launchpad.net/~kicad-developers
> > Post to : kicad-developers@lists.launchpad.net
> > 
> > Unsubscribe : https://launchpad.net/~kicad-developers
> > More help   : https://help.launchpad.net/ListHelp
> >
>
___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] 5.1 branch freeze

[Wayne Stambaugh]

Nick,

Do you need a source archive or just the tag?

Cheers,

Wayne

On 4/16/20 3:58 AM, Nick Østergaard wrote:
> Can we have a 5.1.6-rc1 tag then?
> 
> tor. 16. apr. 2020 03.30 skrev Wayne Stambaugh  >:
> 
> The 5.1 branch has been frozen in order to prepare for the 5.1.6 stable
> release.  Please do not make any commits to the 5.1 branch without first
> confirming with the lead dev team and no translated string changes.  I
> would like to release on Friday, May 15th if possible so please let me
> know if there is any reason we cannot make that date.  Thank you to all
> the development teams for your continued efforts.
> 
> Cheers,
> 
> Wayne
> 
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> Post to     : kicad-developers@lists.launchpad.net
> 
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp
> 

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

Re: [Kicad-developers] 5.1 branch freeze

[Nick Østergaard]

Can we have a 5.1.6-rc1 tag then?

tor. 16. apr. 2020 03.30 skrev Wayne Stambaugh :

> The 5.1 branch has been frozen in order to prepare for the 5.1.6 stable
> release.  Please do not make any commits to the 5.1 branch without first
> confirming with the lead dev team and no translated string changes.  I
> would like to release on Friday, May 15th if possible so please let me
> know if there is any reason we cannot make that date.  Thank you to all
> the development teams for your continued efforts.
>
> Cheers,
>
> Wayne
>
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp
>
___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] 5.1 branch commits

[Jeff Young]

Oops.  At least one of those was mine.  Apologies.

Cheers,
Jeff.


> On 6 Nov 2019, at 22:08, Wayne Stambaugh  wrote:
> 
> Just a reminder, please do not push any commits to the 5.1 branch unless
> it fixes a high priority bug (crash or data loss) without letting the
> dev team know.  I want to avoid the 5.1.1 and 5.1.3 disasters.  Looking
> at the commits that flew in under the radar I didn't see anything that
> looked like a problem but I would still rather the dev team review all
> changes before making changes to the 5.1 branch.  Once 5.1.5 is released
> then when can resume the normal bug fixing.
> 
> 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] 5.1 branch

[Jeff Young]

Cool.  Thanks, Tom.

> On 19 Jul 2018, at 16:28, Tomasz Wlostowski  wrote:
> 
> On 18/07/18 13:06, Jeff Young wrote:
>> Hi Tom, et al,
>> 
>> I assume we just need to drop wxDC for the canvas, but that UI constructs 
>> (such as colour swatches, etc.) would continue to use wxDC?
> 
> To clarify: SCH/PCB preview widgets will also use GAL.
> 
> Tom
> 
>> 
>> Thanks,
>> Jeff.
>> 
>> 
>>> On 17 Jul 2018, at 15:44, Tomasz Wlostowski  
>>> wrote:
>>> 
>>> On 16/07/18 17:54, Wayne Stambaugh wrote:
 I was really hoping just to fix the wxDC issues with GTK3 rather than
 implement GAL unless Tom implemented a wxDC GAL and that is all we
 expose for 5.1.  The primary goal here is to fix the GTK3 rendering
 issues so we can enable wxPython support again.  We need to limit our
 risk exposure for 5.1.
 
>>> Hi Wayne,
>>> 
>>> The sooner we drop wxDC, the better for Kicad. I wouldn't do it because
>>> of the GTK3/Python issues (since it's a neverending Linux problem of
>>> changing APIs and libraries), but for performance reasons - on OSX for
>>> instance, eeschema is sometimes barely usable because of slow drawing.
>>> 
>>> I hope I'll be able to devote some time to cleaning up the eeschema-gal
>>> code in the coming weeks. So far, the main canvas and the library editor
>>> are implemented, with the symbol preview widgets & library browser
>>> remaining.
>>> 
>>> 
 I'm assuming the printing is a v6 goal.
>>> 
>>> Orson made quite a lot of progress with Cairo printing. IIRC it can make
>>> it to the 5.1.
>>> 
>>> Cheers,
>>> Tom
>>> 
 
 On 7/16/2018 11:15 AM, Maciej Sumiński wrote:
> Tom has already prepared a proof-of-concept eeschema with GAL rendering,
> which still uses the legacy tools. I have some promising results
> switching the printing system to Cairo GAL. Obviously we will face some
> unexpected obstacles, but I have high hopes.
> 
> Cheers,
> Orson
> 
> On 07/16/2018 03:40 PM, Wayne Stambaugh wrote:
>> Yes, assuming we can get that to work without dragging in Phoenix.
>> 
>> On 7/16/2018 9:27 AM, Jeff Young wrote:
>>> 5.1 is also for the GTK3 fixes, right?
>>> 
 On 16 Jul 2018, at 14:23, Wayne Stambaugh  wrote:
 
 On 7/16/2018 9:19 AM, Simon Richter wrote:
> Hi,
> 
> On 15.07.2018 13:39, Jeff Young wrote:
> 
>> I renamed my 6.0 branch to 5.1, since most of what it contains goes 
>> there.
> 
> What is the difference between 5.1 and 6.0? What goes into which 
> branch?
> 
> Simon
> 
 
 5.1 is only for the UI refactoring Jeff is working on along with any 
 bug
 fixes that get merged into the 5.0 branch.  Any new features such as 
 the
 new schematic file formats or GALification of eeschema are v6 only.
 
 ___
 Mailing list: https://launchpad.net/~kicad-developers
 Post to : kicad-developers@lists.launchpad.net
 Unsubscribe : https://launchpad.net/~kicad-developers
 More help   : https://help.launchpad.net/ListHelp
>>> 
>> 
>> ___
>> Mailing list: https://launchpad.net/~kicad-developers
>> Post to : kicad-developers@lists.launchpad.net
>> Unsubscribe : https://launchpad.net/~kicad-developers
>> More help   : https://help.launchpad.net/ListHelp
>> 
> 
> 
> 
> 
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp
> 
 
 ___
 Mailing list: https://launchpad.net/~kicad-developers
 Post to : kicad-developers@lists.launchpad.net
 Unsubscribe : https://launchpad.net/~kicad-developers
 More help   : https://help.launchpad.net/ListHelp
 
>>> 
>>> 
>>> ___
>>> Mailing list: https://launchpad.net/~kicad-developers
>>> Post to : kicad-developers@lists.launchpad.net
>>> Unsubscribe : https://launchpad.net/~kicad-developers
>>> More help   : https://help.launchpad.net/ListHelp
>> 
> 


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

Re: [Kicad-developers] 5.1 branch

[Tomasz Wlostowski]

On 18/07/18 13:06, Jeff Young wrote:
> Hi Tom, et al,
> 
> I assume we just need to drop wxDC for the canvas, but that UI constructs 
> (such as colour swatches, etc.) would continue to use wxDC?

To clarify: SCH/PCB preview widgets will also use GAL.

Tom

> 
> Thanks,
> Jeff.
> 
> 
>> On 17 Jul 2018, at 15:44, Tomasz Wlostowski  
>> wrote:
>>
>> On 16/07/18 17:54, Wayne Stambaugh wrote:
>>> I was really hoping just to fix the wxDC issues with GTK3 rather than
>>> implement GAL unless Tom implemented a wxDC GAL and that is all we
>>> expose for 5.1.  The primary goal here is to fix the GTK3 rendering
>>> issues so we can enable wxPython support again.  We need to limit our
>>> risk exposure for 5.1.
>>>
>> Hi Wayne,
>>
>> The sooner we drop wxDC, the better for Kicad. I wouldn't do it because
>> of the GTK3/Python issues (since it's a neverending Linux problem of
>> changing APIs and libraries), but for performance reasons - on OSX for
>> instance, eeschema is sometimes barely usable because of slow drawing.
>>
>> I hope I'll be able to devote some time to cleaning up the eeschema-gal
>> code in the coming weeks. So far, the main canvas and the library editor
>> are implemented, with the symbol preview widgets & library browser
>> remaining.
>>
>>
>>> I'm assuming the printing is a v6 goal.
>>
>> Orson made quite a lot of progress with Cairo printing. IIRC it can make
>> it to the 5.1.
>>
>> Cheers,
>> Tom
>>
>>>
>>> On 7/16/2018 11:15 AM, Maciej Sumiński wrote:
 Tom has already prepared a proof-of-concept eeschema with GAL rendering,
 which still uses the legacy tools. I have some promising results
 switching the printing system to Cairo GAL. Obviously we will face some
 unexpected obstacles, but I have high hopes.

 Cheers,
 Orson

 On 07/16/2018 03:40 PM, Wayne Stambaugh wrote:
> Yes, assuming we can get that to work without dragging in Phoenix.
>
> On 7/16/2018 9:27 AM, Jeff Young wrote:
>> 5.1 is also for the GTK3 fixes, right?
>>
>>> On 16 Jul 2018, at 14:23, Wayne Stambaugh  wrote:
>>>
>>> On 7/16/2018 9:19 AM, Simon Richter wrote:
 Hi,

 On 15.07.2018 13:39, Jeff Young wrote:

> I renamed my 6.0 branch to 5.1, since most of what it contains goes 
> there.

 What is the difference between 5.1 and 6.0? What goes into which 
 branch?

  Simon

>>>
>>> 5.1 is only for the UI refactoring Jeff is working on along with any bug
>>> fixes that get merged into the 5.0 branch.  Any new features such as the
>>> new schematic file formats or GALification of eeschema are v6 only.
>>>
>>> ___
>>> Mailing list: https://launchpad.net/~kicad-developers
>>> Post to : kicad-developers@lists.launchpad.net
>>> Unsubscribe : https://launchpad.net/~kicad-developers
>>> More help   : https://help.launchpad.net/ListHelp
>>
>
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp
>




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

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


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

Re: [Kicad-developers] 5.1 branch

[Maciej Sumiński]

Hi Jeff,

Yes, for the moment we work to replace wxDC only in places that really
need it. So far it was necessary in pcbnew to boost performance, now
eeschema suffers the same problem with GTK3.

Cheers,
Orson

On 07/18/2018 01:06 PM, Jeff Young wrote:
> Hi Tom, et al,
> 
> I assume we just need to drop wxDC for the canvas, but that UI constructs 
> (such as colour swatches, etc.) would continue to use wxDC?
> 
> Thanks,
> Jeff.
> 
> 
>> On 17 Jul 2018, at 15:44, Tomasz Wlostowski  
>> wrote:
>>
>> On 16/07/18 17:54, Wayne Stambaugh wrote:
>>> I was really hoping just to fix the wxDC issues with GTK3 rather than
>>> implement GAL unless Tom implemented a wxDC GAL and that is all we
>>> expose for 5.1.  The primary goal here is to fix the GTK3 rendering
>>> issues so we can enable wxPython support again.  We need to limit our
>>> risk exposure for 5.1.
>>>
>> Hi Wayne,
>>
>> The sooner we drop wxDC, the better for Kicad. I wouldn't do it because
>> of the GTK3/Python issues (since it's a neverending Linux problem of
>> changing APIs and libraries), but for performance reasons - on OSX for
>> instance, eeschema is sometimes barely usable because of slow drawing.
>>
>> I hope I'll be able to devote some time to cleaning up the eeschema-gal
>> code in the coming weeks. So far, the main canvas and the library editor
>> are implemented, with the symbol preview widgets & library browser
>> remaining.
>>
>>
>>> I'm assuming the printing is a v6 goal.
>>
>> Orson made quite a lot of progress with Cairo printing. IIRC it can make
>> it to the 5.1.
>>
>> Cheers,
>> Tom
>>
>>>
>>> On 7/16/2018 11:15 AM, Maciej Sumiński wrote:
 Tom has already prepared a proof-of-concept eeschema with GAL rendering,
 which still uses the legacy tools. I have some promising results
 switching the printing system to Cairo GAL. Obviously we will face some
 unexpected obstacles, but I have high hopes.

 Cheers,
 Orson

 On 07/16/2018 03:40 PM, Wayne Stambaugh wrote:
> Yes, assuming we can get that to work without dragging in Phoenix.
>
> On 7/16/2018 9:27 AM, Jeff Young wrote:
>> 5.1 is also for the GTK3 fixes, right?
>>
>>> On 16 Jul 2018, at 14:23, Wayne Stambaugh  wrote:
>>>
>>> On 7/16/2018 9:19 AM, Simon Richter wrote:
 Hi,

 On 15.07.2018 13:39, Jeff Young wrote:

> I renamed my 6.0 branch to 5.1, since most of what it contains goes 
> there.

 What is the difference between 5.1 and 6.0? What goes into which 
 branch?

  Simon

>>>
>>> 5.1 is only for the UI refactoring Jeff is working on along with any bug
>>> fixes that get merged into the 5.0 branch.  Any new features such as the
>>> new schematic file formats or GALification of eeschema are v6 only.
>>>
>>> ___
>>> Mailing list: https://launchpad.net/~kicad-developers
>>> Post to : kicad-developers@lists.launchpad.net
>>> Unsubscribe : https://launchpad.net/~kicad-developers
>>> More help   : https://help.launchpad.net/ListHelp
>>
>
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp
>




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

>>>
>>> ___
>>> Mailing list: https://launchpad.net/~kicad-developers
>>> Post to : kicad-developers@lists.launchpad.net
>>> Unsubscribe : https://launchpad.net/~kicad-developers
>>> More help   : https://help.launchpad.net/ListHelp
>>>
>>
>>
>> ___
>> 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
> 




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

Re: [Kicad-developers] 5.1 branch

[Jeff Young]

Hi Tom, et al,

I assume we just need to drop wxDC for the canvas, but that UI constructs (such 
as colour swatches, etc.) would continue to use wxDC?

Thanks,
Jeff.


> On 17 Jul 2018, at 15:44, Tomasz Wlostowski  wrote:
> 
> On 16/07/18 17:54, Wayne Stambaugh wrote:
>> I was really hoping just to fix the wxDC issues with GTK3 rather than
>> implement GAL unless Tom implemented a wxDC GAL and that is all we
>> expose for 5.1.  The primary goal here is to fix the GTK3 rendering
>> issues so we can enable wxPython support again.  We need to limit our
>> risk exposure for 5.1.
>> 
> Hi Wayne,
> 
> The sooner we drop wxDC, the better for Kicad. I wouldn't do it because
> of the GTK3/Python issues (since it's a neverending Linux problem of
> changing APIs and libraries), but for performance reasons - on OSX for
> instance, eeschema is sometimes barely usable because of slow drawing.
> 
> I hope I'll be able to devote some time to cleaning up the eeschema-gal
> code in the coming weeks. So far, the main canvas and the library editor
> are implemented, with the symbol preview widgets & library browser
> remaining.
> 
> 
>> I'm assuming the printing is a v6 goal.
> 
> Orson made quite a lot of progress with Cairo printing. IIRC it can make
> it to the 5.1.
> 
> Cheers,
> Tom
> 
>> 
>> On 7/16/2018 11:15 AM, Maciej Sumiński wrote:
>>> Tom has already prepared a proof-of-concept eeschema with GAL rendering,
>>> which still uses the legacy tools. I have some promising results
>>> switching the printing system to Cairo GAL. Obviously we will face some
>>> unexpected obstacles, but I have high hopes.
>>> 
>>> Cheers,
>>> Orson
>>> 
>>> On 07/16/2018 03:40 PM, Wayne Stambaugh wrote:
 Yes, assuming we can get that to work without dragging in Phoenix.
 
 On 7/16/2018 9:27 AM, Jeff Young wrote:
> 5.1 is also for the GTK3 fixes, right?
> 
>> On 16 Jul 2018, at 14:23, Wayne Stambaugh  wrote:
>> 
>> On 7/16/2018 9:19 AM, Simon Richter wrote:
>>> Hi,
>>> 
>>> On 15.07.2018 13:39, Jeff Young wrote:
>>> 
 I renamed my 6.0 branch to 5.1, since most of what it contains goes 
 there.
>>> 
>>> What is the difference between 5.1 and 6.0? What goes into which branch?
>>> 
>>>  Simon
>>> 
>> 
>> 5.1 is only for the UI refactoring Jeff is working on along with any bug
>> fixes that get merged into the 5.0 branch.  Any new features such as the
>> new schematic file formats or GALification of eeschema are v6 only.
>> 
>> ___
>> Mailing list: https://launchpad.net/~kicad-developers
>> Post to : kicad-developers@lists.launchpad.net
>> Unsubscribe : https://launchpad.net/~kicad-developers
>> More help   : https://help.launchpad.net/ListHelp
> 
 
 ___
 Mailing list: https://launchpad.net/~kicad-developers
 Post to : kicad-developers@lists.launchpad.net
 Unsubscribe : https://launchpad.net/~kicad-developers
 More help   : https://help.launchpad.net/ListHelp
 
>>> 
>>> 
>>> 
>>> 
>>> ___
>>> Mailing list: https://launchpad.net/~kicad-developers
>>> Post to : kicad-developers@lists.launchpad.net
>>> Unsubscribe : https://launchpad.net/~kicad-developers
>>> More help   : https://help.launchpad.net/ListHelp
>>> 
>> 
>> ___
>> Mailing list: https://launchpad.net/~kicad-developers
>> Post to : kicad-developers@lists.launchpad.net
>> Unsubscribe : https://launchpad.net/~kicad-developers
>> More help   : https://help.launchpad.net/ListHelp
>> 
> 
> 
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp


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

Re: [Kicad-developers] 5.1 branch

[Tomasz Wlostowski]

On 16/07/18 17:54, Wayne Stambaugh wrote:
> I was really hoping just to fix the wxDC issues with GTK3 rather than
> implement GAL unless Tom implemented a wxDC GAL and that is all we
> expose for 5.1.  The primary goal here is to fix the GTK3 rendering
> issues so we can enable wxPython support again.  We need to limit our
> risk exposure for 5.1.
> 
Hi Wayne,

The sooner we drop wxDC, the better for Kicad. I wouldn't do it because
of the GTK3/Python issues (since it's a neverending Linux problem of
changing APIs and libraries), but for performance reasons - on OSX for
instance, eeschema is sometimes barely usable because of slow drawing.

I hope I'll be able to devote some time to cleaning up the eeschema-gal
code in the coming weeks. So far, the main canvas and the library editor
are implemented, with the symbol preview widgets & library browser
remaining.


> I'm assuming the printing is a v6 goal.

Orson made quite a lot of progress with Cairo printing. IIRC it can make
it to the 5.1.

Cheers,
Tom

> 
> On 7/16/2018 11:15 AM, Maciej Sumiński wrote:
>> Tom has already prepared a proof-of-concept eeschema with GAL rendering,
>> which still uses the legacy tools. I have some promising results
>> switching the printing system to Cairo GAL. Obviously we will face some
>> unexpected obstacles, but I have high hopes.
>>
>> Cheers,
>> Orson
>>
>> On 07/16/2018 03:40 PM, Wayne Stambaugh wrote:
>>> Yes, assuming we can get that to work without dragging in Phoenix.
>>>
>>> On 7/16/2018 9:27 AM, Jeff Young wrote:
 5.1 is also for the GTK3 fixes, right?

> On 16 Jul 2018, at 14:23, Wayne Stambaugh  wrote:
>
> On 7/16/2018 9:19 AM, Simon Richter wrote:
>> Hi,
>>
>> On 15.07.2018 13:39, Jeff Young wrote:
>>
>>> I renamed my 6.0 branch to 5.1, since most of what it contains goes 
>>> there.
>>
>> What is the difference between 5.1 and 6.0? What goes into which branch?
>>
>>   Simon
>>
>
> 5.1 is only for the UI refactoring Jeff is working on along with any bug
> fixes that get merged into the 5.0 branch.  Any new features such as the
> new schematic file formats or GALification of eeschema are v6 only.
>
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp

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


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

Re: [Kicad-developers] 5.1 branch

[Maciej Sumiński]

On 07/16/2018 05:54 PM, Wayne Stambaugh wrote:
> I was really hoping just to fix the wxDC issues with GTK3 rather than
> implement GAL unless Tom implemented a wxDC GAL and that is all we
> expose for 5.1.  The primary goal here is to fix the GTK3 rendering
> issues so we can enable wxPython support again.  We need to limit our
> risk exposure for 5.1.

There is no new wxDC GAL backend implemented, which IMHO reduces the
risk as Cairo backend has been already tested a bit. Staying with two
rendering engines also reduces the amount of code to maintain.

I have already spent some time trying to fix GTK3 problems, both in
eeschema and in pcbnew. GTK3 fixes in eeschema resulted in a slight
performance drop, whereas for pcbnew I was unable to come up with a
solution.

> I'm assuming the printing is a v6 goal.

Broken legacy canvas in pcbnew means layout printing is also broken. A
simple workaround is to remove printing completely and request users to
use PDF plotting.

Cheers,
Orson

> On 7/16/2018 11:15 AM, Maciej Sumiński wrote:
>> Tom has already prepared a proof-of-concept eeschema with GAL rendering,
>> which still uses the legacy tools. I have some promising results
>> switching the printing system to Cairo GAL. Obviously we will face some
>> unexpected obstacles, but I have high hopes.
>>
>> Cheers,
>> Orson
>>
>> On 07/16/2018 03:40 PM, Wayne Stambaugh wrote:
>>> Yes, assuming we can get that to work without dragging in Phoenix.
>>>
>>> On 7/16/2018 9:27 AM, Jeff Young wrote:
 5.1 is also for the GTK3 fixes, right?

> On 16 Jul 2018, at 14:23, Wayne Stambaugh  wrote:
>
> On 7/16/2018 9:19 AM, Simon Richter wrote:
>> Hi,
>>
>> On 15.07.2018 13:39, Jeff Young wrote:
>>
>>> I renamed my 6.0 branch to 5.1, since most of what it contains goes 
>>> there.
>>
>> What is the difference between 5.1 and 6.0? What goes into which branch?
>>
>>   Simon
>>
>
> 5.1 is only for the UI refactoring Jeff is working on along with any bug
> fixes that get merged into the 5.0 branch.  Any new features such as the
> new schematic file formats or GALification of eeschema are v6 only.
>
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp

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




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

Re: [Kicad-developers] 5.1 branch

[Maciej Suminski]

Whew, I think that was ~1200 bugs fixed/feature requests handled. Well
done, team! Now let's sweep our mailboxes..

Cheers,
Orson

On 07/16/2018 06:14 PM, Jeff Young wrote:
> I started doing some by hand and Orson is right: tedious isn’t the half of 
> it.  I’ll wait for his script. ;)
> 
> 
>> On 16 Jul 2018, at 16:59, Wayne Stambaugh  wrote:
>>
>> My finger is on the delete key.  Fire when ready!
>>
>> On 7/16/2018 11:48 AM, Maciej Sumiński wrote:
>>> I have the script ready to run. It will just change all KiCad bug
>>> statuses from 'Fix Committed' to 'Fix Release'. I assume there are no
>>> bugs that are marked as 'Fix Committed', but not actually in the master
>>> branch, right? Are you ready for an infinite stream of bug tracker
>>> notifications? :>
>>>
>>> Cheers,
>>> Orson
>>>
>>> On 07/16/2018 05:13 PM, Wayne Stambaugh wrote:
 That would probably be the easiest solution with the least amount of
 risk.  Although you could not run it for point releases because bugs
 that are only valid for the development branch would get set to fix
 released which would not be correct.

 On 7/16/2018 11:08 AM, Maciej Sumiński wrote:
> It is terribly tedious to go through the bug list and change statuses
> one by one, so I offer to help with the bug report status fiddling. We
> may employ Janitor, but I guess it would be better to execute a simple
> script to change Fix Committed->Fix Released whenever we release a new
> version.
>
> Cheers,
> Orson
>
> On 07/16/2018 03:30 PM, Wayne Stambaugh wrote:
>> Hey Jeff,
>>
>> We have been manually changing the bug status from fix committed to fix
>> released after a new stable release.  AFAIK, the janitor does not handle
>> this.  I suppose the janitor could be modified to test for a new release
>> and change the tag for all bugs associated with that release.  That
>> would not be 100% accurate because there are bugs that have not been
>> associated with a branch but that would probably be easier than changing
>> them all manually.  I don't have a strong preference one way or the 
>> other.
>>
>> Wayne
>>
>> On 7/16/2018 9:20 AM, Jeff Young wrote:
>>> Hi Wayne,
>>>
>>> The other issue is that the Janitor is going to mark my fixes as Fix 
>>> Committed, and I don’t know if the auto-bug-release facility is smart 
>>> enough to check the milestone before converting Fix Committed to Fix 
>>> Released.  So we may need to do that first too.
>>>
>>> Cheers,
>>> Jeff.
>>>
 On 16 Jul 2018, at 14:15, Wayne Stambaugh  wrote:

 Jeff,

 As a general rule, we merge changes into the development branch and 
 then
 merge them into the stable release branch after they have been tested.
 In the past this has only been bug fixes so your case is slightly
 different.  The problem I see with merging your changes into the 5.1
 branch first is that they will not get as much testing as they would if
 you merged your changes into the development branch.  I would prefer
 that we merge changes into the development branch so that nightly 
 builds
 can be used to get some good testing.  Any bug fixes to your changes 
 can
 then be merged into the 5.1 branch.  Does anyone see any reason not to
 do it this way?

 Please do not merge your changes into the development branch just yet.
 Orson just fixed a bug and I'm considering retagging v5 to include 
 this fix.

 Cheers,

 Wayne

 On 7/16/2018 5:05 AM, Jeff Young wrote:
> Thanks, JP!  I’ll make the fix.
>
>> On 16 Jul 2018, at 09:24, jp charras  wrote:
>>
>> Le 16/07/2018 à 10:10, Jeff Young a écrit :
>>> Well, rats.  I couldn’t figure out why "git rebase —interactive" 
>>> wasn’t showing me any of my
>>> commits, and it turns out that I somehow accidentally merged them 
>>> all to origin/5.1 sometime last
>>> night.  Anyway, you don’t have to fetch my private branch to test 
>>> it anymore; the kicad 5.1 branch
>>> will do nicely.
>>>
>>> Let me know if the paged dialog issues are keeping anyone from 
>>> getting work done and I’ll try to
>>> figure out how to revert those commits.
>>
>> Hi, Jeff
>> The paged dialog issue is due to the fact the panels (pages) have an 
>> incorrect parent.
>> Currently, these panels have the dialog itself as parent.
>> They should have m_treebook (the wxTreeBook similar to a wxNotebook) 
>> as parent.
>>
>> (This change fixes the issue on W7)
>>
>>>
>>> Cheers,
>>> Jeff.
>>
>> -- 
>> Jean-Pierre CHARRA

Re: [Kicad-developers] 5.1 branch

[Maciej Sumiński]

I have the script ready to run. It will just change all KiCad bug
statuses from 'Fix Committed' to 'Fix Release'. I assume there are no
bugs that are marked as 'Fix Committed', but not actually in the master
branch, right? Are you ready for an infinite stream of bug tracker
notifications? :>

Cheers,
Orson

On 07/16/2018 05:13 PM, Wayne Stambaugh wrote:
> That would probably be the easiest solution with the least amount of
> risk.  Although you could not run it for point releases because bugs
> that are only valid for the development branch would get set to fix
> released which would not be correct.
> 
> On 7/16/2018 11:08 AM, Maciej Sumiński wrote:
>> It is terribly tedious to go through the bug list and change statuses
>> one by one, so I offer to help with the bug report status fiddling. We
>> may employ Janitor, but I guess it would be better to execute a simple
>> script to change Fix Committed->Fix Released whenever we release a new
>> version.
>>
>> Cheers,
>> Orson
>>
>> On 07/16/2018 03:30 PM, Wayne Stambaugh wrote:
>>> Hey Jeff,
>>>
>>> We have been manually changing the bug status from fix committed to fix
>>> released after a new stable release.  AFAIK, the janitor does not handle
>>> this.  I suppose the janitor could be modified to test for a new release
>>> and change the tag for all bugs associated with that release.  That
>>> would not be 100% accurate because there are bugs that have not been
>>> associated with a branch but that would probably be easier than changing
>>> them all manually.  I don't have a strong preference one way or the other.
>>>
>>> Wayne
>>>
>>> On 7/16/2018 9:20 AM, Jeff Young wrote:
 Hi Wayne,

 The other issue is that the Janitor is going to mark my fixes as Fix 
 Committed, and I don’t know if the auto-bug-release facility is smart 
 enough to check the milestone before converting Fix Committed to Fix 
 Released.  So we may need to do that first too.

 Cheers,
 Jeff.

> On 16 Jul 2018, at 14:15, Wayne Stambaugh  wrote:
>
> Jeff,
>
> As a general rule, we merge changes into the development branch and then
> merge them into the stable release branch after they have been tested.
> In the past this has only been bug fixes so your case is slightly
> different.  The problem I see with merging your changes into the 5.1
> branch first is that they will not get as much testing as they would if
> you merged your changes into the development branch.  I would prefer
> that we merge changes into the development branch so that nightly builds
> can be used to get some good testing.  Any bug fixes to your changes can
> then be merged into the 5.1 branch.  Does anyone see any reason not to
> do it this way?
>
> Please do not merge your changes into the development branch just yet.
> Orson just fixed a bug and I'm considering retagging v5 to include this 
> fix.
>
> Cheers,
>
> Wayne
>
> On 7/16/2018 5:05 AM, Jeff Young wrote:
>> Thanks, JP!  I’ll make the fix.
>>
>>> On 16 Jul 2018, at 09:24, jp charras  wrote:
>>>
>>> Le 16/07/2018 à 10:10, Jeff Young a écrit :
 Well, rats.  I couldn’t figure out why "git rebase —interactive" 
 wasn’t showing me any of my
 commits, and it turns out that I somehow accidentally merged them all 
 to origin/5.1 sometime last
 night.  Anyway, you don’t have to fetch my private branch to test it 
 anymore; the kicad 5.1 branch
 will do nicely.

 Let me know if the paged dialog issues are keeping anyone from getting 
 work done and I’ll try to
 figure out how to revert those commits.
>>>
>>> Hi, Jeff
>>> The paged dialog issue is due to the fact the panels (pages) have an 
>>> incorrect parent.
>>> Currently, these panels have the dialog itself as parent.
>>> They should have m_treebook (the wxTreeBook similar to a wxNotebook) as 
>>> parent.
>>>
>>> (This change fixes the issue on W7)
>>>

 Cheers,
 Jeff.
>>>
>>> -- 
>>> 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
>>
>
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@lists.launchpad.net
> Unsubscribe

Re: [Kicad-developers] 5.1 branch

[jp charras]

Le 16/07/2018 à 17:54, Wayne Stambaugh a écrit :
> I was really hoping just to fix the wxDC issues with GTK3 rather than
> implement GAL unless Tom implemented a wxDC GAL and that is all we
> expose for 5.1.  The primary goal here is to fix the GTK3 rendering
> issues so we can enable wxPython support again.  We need to limit our
> risk exposure for 5.1.
> 
> I'm assuming the printing is a v6 goal.

I am pretty sure wxDC on GTK3 is in fact just an interface with Cairo.

So a wxDC GAL is for me (but I can be wrong) is very near implementing GAL 
(using Cairo canvas) in
Eeschema, as long it uses the legacy tools.

Moreover, GAL in Eeschema will remove any specific code for OSX, at least in 
Eeschema (and page
layout editor).
This specific code creates also bugs and issues due to the very different 
behavior between OSX and
others OS.

So the risk exposure for 5.1 is high, but OTOH the benefit is high.
and the risk for 5.1 if nothing is done is higher.


> 
> On 7/16/2018 11:15 AM, Maciej Sumiński wrote:
>> Tom has already prepared a proof-of-concept eeschema with GAL rendering,
>> which still uses the legacy tools. I have some promising results
>> switching the printing system to Cairo GAL. Obviously we will face some
>> unexpected obstacles, but I have high hopes.
>>
>> Cheers,
>> Orson
>>
>> On 07/16/2018 03:40 PM, Wayne Stambaugh wrote:
>>> Yes, assuming we can get that to work without dragging in Phoenix.
>>>
>>> On 7/16/2018 9:27 AM, Jeff Young wrote:
 5.1 is also for the GTK3 fixes, right?

> On 16 Jul 2018, at 14:23, Wayne Stambaugh  wrote:
>
> On 7/16/2018 9:19 AM, Simon Richter wrote:
>> Hi,
>>
>> On 15.07.2018 13:39, Jeff Young wrote:
>>
>>> I renamed my 6.0 branch to 5.1, since most of what it contains goes 
>>> there.
>>
>> What is the difference between 5.1 and 6.0? What goes into which branch?
>>
>>   Simon
>>
>
> 5.1 is only for the UI refactoring Jeff is working on along with any bug
> fixes that get merged into the 5.0 branch.  Any new features such as the
> new schematic file formats or GALification of eeschema are v6 only.

-- 
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] 5.1 branch

[Jeff Young]

I started doing some by hand and Orson is right: tedious isn’t the half of it.  
I’ll wait for his script. ;)


> On 16 Jul 2018, at 16:59, Wayne Stambaugh  wrote:
> 
> My finger is on the delete key.  Fire when ready!
> 
> On 7/16/2018 11:48 AM, Maciej Sumiński wrote:
>> I have the script ready to run. It will just change all KiCad bug
>> statuses from 'Fix Committed' to 'Fix Release'. I assume there are no
>> bugs that are marked as 'Fix Committed', but not actually in the master
>> branch, right? Are you ready for an infinite stream of bug tracker
>> notifications? :>
>> 
>> Cheers,
>> Orson
>> 
>> On 07/16/2018 05:13 PM, Wayne Stambaugh wrote:
>>> That would probably be the easiest solution with the least amount of
>>> risk.  Although you could not run it for point releases because bugs
>>> that are only valid for the development branch would get set to fix
>>> released which would not be correct.
>>> 
>>> On 7/16/2018 11:08 AM, Maciej Sumiński wrote:
 It is terribly tedious to go through the bug list and change statuses
 one by one, so I offer to help with the bug report status fiddling. We
 may employ Janitor, but I guess it would be better to execute a simple
 script to change Fix Committed->Fix Released whenever we release a new
 version.
 
 Cheers,
 Orson
 
 On 07/16/2018 03:30 PM, Wayne Stambaugh wrote:
> Hey Jeff,
> 
> We have been manually changing the bug status from fix committed to fix
> released after a new stable release.  AFAIK, the janitor does not handle
> this.  I suppose the janitor could be modified to test for a new release
> and change the tag for all bugs associated with that release.  That
> would not be 100% accurate because there are bugs that have not been
> associated with a branch but that would probably be easier than changing
> them all manually.  I don't have a strong preference one way or the other.
> 
> Wayne
> 
> On 7/16/2018 9:20 AM, Jeff Young wrote:
>> Hi Wayne,
>> 
>> The other issue is that the Janitor is going to mark my fixes as Fix 
>> Committed, and I don’t know if the auto-bug-release facility is smart 
>> enough to check the milestone before converting Fix Committed to Fix 
>> Released.  So we may need to do that first too.
>> 
>> Cheers,
>> Jeff.
>> 
>>> On 16 Jul 2018, at 14:15, Wayne Stambaugh  wrote:
>>> 
>>> Jeff,
>>> 
>>> As a general rule, we merge changes into the development branch and then
>>> merge them into the stable release branch after they have been tested.
>>> In the past this has only been bug fixes so your case is slightly
>>> different.  The problem I see with merging your changes into the 5.1
>>> branch first is that they will not get as much testing as they would if
>>> you merged your changes into the development branch.  I would prefer
>>> that we merge changes into the development branch so that nightly builds
>>> can be used to get some good testing.  Any bug fixes to your changes can
>>> then be merged into the 5.1 branch.  Does anyone see any reason not to
>>> do it this way?
>>> 
>>> Please do not merge your changes into the development branch just yet.
>>> Orson just fixed a bug and I'm considering retagging v5 to include this 
>>> fix.
>>> 
>>> Cheers,
>>> 
>>> Wayne
>>> 
>>> On 7/16/2018 5:05 AM, Jeff Young wrote:
 Thanks, JP!  I’ll make the fix.
 
> On 16 Jul 2018, at 09:24, jp charras  wrote:
> 
> Le 16/07/2018 à 10:10, Jeff Young a écrit :
>> Well, rats.  I couldn’t figure out why "git rebase —interactive" 
>> wasn’t showing me any of my
>> commits, and it turns out that I somehow accidentally merged them 
>> all to origin/5.1 sometime last
>> night.  Anyway, you don’t have to fetch my private branch to test it 
>> anymore; the kicad 5.1 branch
>> will do nicely.
>> 
>> Let me know if the paged dialog issues are keeping anyone from 
>> getting work done and I’ll try to
>> figure out how to revert those commits.
> 
> Hi, Jeff
> The paged dialog issue is due to the fact the panels (pages) have an 
> incorrect parent.
> Currently, these panels have the dialog itself as parent.
> They should have m_treebook (the wxTreeBook similar to a wxNotebook) 
> as parent.
> 
> (This change fixes the issue on W7)
> 
>> 
>> Cheers,
>> Jeff.
> 
> -- 
> 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.launc

Re: [Kicad-developers] 5.1 branch

[Wayne Stambaugh]

My finger is on the delete key.  Fire when ready!

On 7/16/2018 11:48 AM, Maciej Sumiński wrote:
> I have the script ready to run. It will just change all KiCad bug
> statuses from 'Fix Committed' to 'Fix Release'. I assume there are no
> bugs that are marked as 'Fix Committed', but not actually in the master
> branch, right? Are you ready for an infinite stream of bug tracker
> notifications? :>
> 
> Cheers,
> Orson
> 
> On 07/16/2018 05:13 PM, Wayne Stambaugh wrote:
>> That would probably be the easiest solution with the least amount of
>> risk.  Although you could not run it for point releases because bugs
>> that are only valid for the development branch would get set to fix
>> released which would not be correct.
>>
>> On 7/16/2018 11:08 AM, Maciej Sumiński wrote:
>>> It is terribly tedious to go through the bug list and change statuses
>>> one by one, so I offer to help with the bug report status fiddling. We
>>> may employ Janitor, but I guess it would be better to execute a simple
>>> script to change Fix Committed->Fix Released whenever we release a new
>>> version.
>>>
>>> Cheers,
>>> Orson
>>>
>>> On 07/16/2018 03:30 PM, Wayne Stambaugh wrote:
 Hey Jeff,

 We have been manually changing the bug status from fix committed to fix
 released after a new stable release.  AFAIK, the janitor does not handle
 this.  I suppose the janitor could be modified to test for a new release
 and change the tag for all bugs associated with that release.  That
 would not be 100% accurate because there are bugs that have not been
 associated with a branch but that would probably be easier than changing
 them all manually.  I don't have a strong preference one way or the other.

 Wayne

 On 7/16/2018 9:20 AM, Jeff Young wrote:
> Hi Wayne,
>
> The other issue is that the Janitor is going to mark my fixes as Fix 
> Committed, and I don’t know if the auto-bug-release facility is smart 
> enough to check the milestone before converting Fix Committed to Fix 
> Released.  So we may need to do that first too.
>
> Cheers,
> Jeff.
>
>> On 16 Jul 2018, at 14:15, Wayne Stambaugh  wrote:
>>
>> Jeff,
>>
>> As a general rule, we merge changes into the development branch and then
>> merge them into the stable release branch after they have been tested.
>> In the past this has only been bug fixes so your case is slightly
>> different.  The problem I see with merging your changes into the 5.1
>> branch first is that they will not get as much testing as they would if
>> you merged your changes into the development branch.  I would prefer
>> that we merge changes into the development branch so that nightly builds
>> can be used to get some good testing.  Any bug fixes to your changes can
>> then be merged into the 5.1 branch.  Does anyone see any reason not to
>> do it this way?
>>
>> Please do not merge your changes into the development branch just yet.
>> Orson just fixed a bug and I'm considering retagging v5 to include this 
>> fix.
>>
>> Cheers,
>>
>> Wayne
>>
>> On 7/16/2018 5:05 AM, Jeff Young wrote:
>>> Thanks, JP!  I’ll make the fix.
>>>
 On 16 Jul 2018, at 09:24, jp charras  wrote:

 Le 16/07/2018 à 10:10, Jeff Young a écrit :
> Well, rats.  I couldn’t figure out why "git rebase —interactive" 
> wasn’t showing me any of my
> commits, and it turns out that I somehow accidentally merged them all 
> to origin/5.1 sometime last
> night.  Anyway, you don’t have to fetch my private branch to test it 
> anymore; the kicad 5.1 branch
> will do nicely.
>
> Let me know if the paged dialog issues are keeping anyone from 
> getting work done and I’ll try to
> figure out how to revert those commits.

 Hi, Jeff
 The paged dialog issue is due to the fact the panels (pages) have an 
 incorrect parent.
 Currently, these panels have the dialog itself as parent.
 They should have m_treebook (the wxTreeBook similar to a wxNotebook) 
 as parent.

 (This change fixes the issue on W7)

>
> Cheers,
> Jeff.

 -- 
 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.

Re: [Kicad-developers] 5.1 branch

[Seth Hillbrand]

No time like the present!

-S

Am Mo., 16. Juli 2018 um 08:49 Uhr schrieb Maciej Sumiński <
maciej.sumin...@cern.ch>:

> I have the script ready to run. It will just change all KiCad bug
> statuses from 'Fix Committed' to 'Fix Release'. I assume there are no
> bugs that are marked as 'Fix Committed', but not actually in the master
> branch, right? Are you ready for an infinite stream of bug tracker
> notifications? :>
>
> Cheers,
> Orson
>
> On 07/16/2018 05:13 PM, Wayne Stambaugh wrote:
> > That would probably be the easiest solution with the least amount of
> > risk.  Although you could not run it for point releases because bugs
> > that are only valid for the development branch would get set to fix
> > released which would not be correct.
> >
> > On 7/16/2018 11:08 AM, Maciej Sumiński wrote:
> >> It is terribly tedious to go through the bug list and change statuses
> >> one by one, so I offer to help with the bug report status fiddling. We
> >> may employ Janitor, but I guess it would be better to execute a simple
> >> script to change Fix Committed->Fix Released whenever we release a new
> >> version.
> >>
> >> Cheers,
> >> Orson
> >>
> >> On 07/16/2018 03:30 PM, Wayne Stambaugh wrote:
> >>> Hey Jeff,
> >>>
> >>> We have been manually changing the bug status from fix committed to fix
> >>> released after a new stable release.  AFAIK, the janitor does not
> handle
> >>> this.  I suppose the janitor could be modified to test for a new
> release
> >>> and change the tag for all bugs associated with that release.  That
> >>> would not be 100% accurate because there are bugs that have not been
> >>> associated with a branch but that would probably be easier than
> changing
> >>> them all manually.  I don't have a strong preference one way or the
> other.
> >>>
> >>> Wayne
> >>>
> >>> On 7/16/2018 9:20 AM, Jeff Young wrote:
>  Hi Wayne,
> 
>  The other issue is that the Janitor is going to mark my fixes as Fix
> Committed, and I don’t know if the auto-bug-release facility is smart
> enough to check the milestone before converting Fix Committed to Fix
> Released.  So we may need to do that first too.
> 
>  Cheers,
>  Jeff.
> 
> > On 16 Jul 2018, at 14:15, Wayne Stambaugh 
> wrote:
> >
> > Jeff,
> >
> > As a general rule, we merge changes into the development branch and
> then
> > merge them into the stable release branch after they have been
> tested.
> > In the past this has only been bug fixes so your case is slightly
> > different.  The problem I see with merging your changes into the 5.1
> > branch first is that they will not get as much testing as they would
> if
> > you merged your changes into the development branch.  I would prefer
> > that we merge changes into the development branch so that nightly
> builds
> > can be used to get some good testing.  Any bug fixes to your changes
> can
> > then be merged into the 5.1 branch.  Does anyone see any reason not
> to
> > do it this way?
> >
> > Please do not merge your changes into the development branch just
> yet.
> > Orson just fixed a bug and I'm considering retagging v5 to include
> this fix.
> >
> > Cheers,
> >
> > Wayne
> >
> > On 7/16/2018 5:05 AM, Jeff Young wrote:
> >> Thanks, JP!  I’ll make the fix.
> >>
> >>> On 16 Jul 2018, at 09:24, jp charras 
> wrote:
> >>>
> >>> Le 16/07/2018 à 10:10, Jeff Young a écrit :
>  Well, rats.  I couldn’t figure out why "git rebase —interactive"
> wasn’t showing me any of my
>  commits, and it turns out that I somehow accidentally merged them
> all to origin/5.1 sometime last
>  night.  Anyway, you don’t have to fetch my private branch to test
> it anymore; the kicad 5.1 branch
>  will do nicely.
> 
>  Let me know if the paged dialog issues are keeping anyone from
> getting work done and I’ll try to
>  figure out how to revert those commits.
> >>>
> >>> Hi, Jeff
> >>> The paged dialog issue is due to the fact the panels (pages) have
> an incorrect parent.
> >>> Currently, these panels have the dialog itself as parent.
> >>> They should have m_treebook (the wxTreeBook similar to a
> wxNotebook) as parent.
> >>>
> >>> (This change fixes the issue on W7)
> >>>
> 
>  Cheers,
>  Jeff.
> >>>
> >>> --
> >>> 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:

Re: [Kicad-developers] 5.1 branch

[Wayne Stambaugh]

I was really hoping just to fix the wxDC issues with GTK3 rather than
implement GAL unless Tom implemented a wxDC GAL and that is all we
expose for 5.1.  The primary goal here is to fix the GTK3 rendering
issues so we can enable wxPython support again.  We need to limit our
risk exposure for 5.1.

I'm assuming the printing is a v6 goal.

On 7/16/2018 11:15 AM, Maciej Sumiński wrote:
> Tom has already prepared a proof-of-concept eeschema with GAL rendering,
> which still uses the legacy tools. I have some promising results
> switching the printing system to Cairo GAL. Obviously we will face some
> unexpected obstacles, but I have high hopes.
> 
> Cheers,
> Orson
> 
> On 07/16/2018 03:40 PM, Wayne Stambaugh wrote:
>> Yes, assuming we can get that to work without dragging in Phoenix.
>>
>> On 7/16/2018 9:27 AM, Jeff Young wrote:
>>> 5.1 is also for the GTK3 fixes, right?
>>>
 On 16 Jul 2018, at 14:23, Wayne Stambaugh  wrote:

 On 7/16/2018 9:19 AM, Simon Richter wrote:
> Hi,
>
> On 15.07.2018 13:39, Jeff Young wrote:
>
>> I renamed my 6.0 branch to 5.1, since most of what it contains goes 
>> there.
>
> What is the difference between 5.1 and 6.0? What goes into which branch?
>
>   Simon
>

 5.1 is only for the UI refactoring Jeff is working on along with any bug
 fixes that get merged into the 5.0 branch.  Any new features such as the
 new schematic file formats or GALification of eeschema are v6 only.

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

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

Re: [Kicad-developers] 5.1 branch

[Maciej Sumiński]

Tom has already prepared a proof-of-concept eeschema with GAL rendering,
which still uses the legacy tools. I have some promising results
switching the printing system to Cairo GAL. Obviously we will face some
unexpected obstacles, but I have high hopes.

Cheers,
Orson

On 07/16/2018 03:40 PM, Wayne Stambaugh wrote:
> Yes, assuming we can get that to work without dragging in Phoenix.
> 
> On 7/16/2018 9:27 AM, Jeff Young wrote:
>> 5.1 is also for the GTK3 fixes, right?
>>
>>> On 16 Jul 2018, at 14:23, Wayne Stambaugh  wrote:
>>>
>>> On 7/16/2018 9:19 AM, Simon Richter wrote:
 Hi,

 On 15.07.2018 13:39, Jeff Young wrote:

> I renamed my 6.0 branch to 5.1, since most of what it contains goes there.

 What is the difference between 5.1 and 6.0? What goes into which branch?

   Simon

>>>
>>> 5.1 is only for the UI refactoring Jeff is working on along with any bug
>>> fixes that get merged into the 5.0 branch.  Any new features such as the
>>> new schematic file formats or GALification of eeschema are v6 only.
>>>
>>> ___
>>> 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
> 




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

Re: [Kicad-developers] 5.1 branch

[Wayne Stambaugh]

That would probably be the easiest solution with the least amount of
risk.  Although you could not run it for point releases because bugs
that are only valid for the development branch would get set to fix
released which would not be correct.

On 7/16/2018 11:08 AM, Maciej Sumiński wrote:
> It is terribly tedious to go through the bug list and change statuses
> one by one, so I offer to help with the bug report status fiddling. We
> may employ Janitor, but I guess it would be better to execute a simple
> script to change Fix Committed->Fix Released whenever we release a new
> version.
> 
> Cheers,
> Orson
> 
> On 07/16/2018 03:30 PM, Wayne Stambaugh wrote:
>> Hey Jeff,
>>
>> We have been manually changing the bug status from fix committed to fix
>> released after a new stable release.  AFAIK, the janitor does not handle
>> this.  I suppose the janitor could be modified to test for a new release
>> and change the tag for all bugs associated with that release.  That
>> would not be 100% accurate because there are bugs that have not been
>> associated with a branch but that would probably be easier than changing
>> them all manually.  I don't have a strong preference one way or the other.
>>
>> Wayne
>>
>> On 7/16/2018 9:20 AM, Jeff Young wrote:
>>> Hi Wayne,
>>>
>>> The other issue is that the Janitor is going to mark my fixes as Fix 
>>> Committed, and I don’t know if the auto-bug-release facility is smart 
>>> enough to check the milestone before converting Fix Committed to Fix 
>>> Released.  So we may need to do that first too.
>>>
>>> Cheers,
>>> Jeff.
>>>
 On 16 Jul 2018, at 14:15, Wayne Stambaugh  wrote:

 Jeff,

 As a general rule, we merge changes into the development branch and then
 merge them into the stable release branch after they have been tested.
 In the past this has only been bug fixes so your case is slightly
 different.  The problem I see with merging your changes into the 5.1
 branch first is that they will not get as much testing as they would if
 you merged your changes into the development branch.  I would prefer
 that we merge changes into the development branch so that nightly builds
 can be used to get some good testing.  Any bug fixes to your changes can
 then be merged into the 5.1 branch.  Does anyone see any reason not to
 do it this way?

 Please do not merge your changes into the development branch just yet.
 Orson just fixed a bug and I'm considering retagging v5 to include this 
 fix.

 Cheers,

 Wayne

 On 7/16/2018 5:05 AM, Jeff Young wrote:
> Thanks, JP!  I’ll make the fix.
>
>> On 16 Jul 2018, at 09:24, jp charras  wrote:
>>
>> Le 16/07/2018 à 10:10, Jeff Young a écrit :
>>> Well, rats.  I couldn’t figure out why "git rebase —interactive" wasn’t 
>>> showing me any of my
>>> commits, and it turns out that I somehow accidentally merged them all 
>>> to origin/5.1 sometime last
>>> night.  Anyway, you don’t have to fetch my private branch to test it 
>>> anymore; the kicad 5.1 branch
>>> will do nicely.
>>>
>>> Let me know if the paged dialog issues are keeping anyone from getting 
>>> work done and I’ll try to
>>> figure out how to revert those commits.
>>
>> Hi, Jeff
>> The paged dialog issue is due to the fact the panels (pages) have an 
>> incorrect parent.
>> Currently, these panels have the dialog itself as parent.
>> They should have m_treebook (the wxTreeBook similar to a wxNotebook) as 
>> parent.
>>
>> (This change fixes the issue on W7)
>>
>>>
>>> Cheers,
>>> Jeff.
>>
>> -- 
>> 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
>

 ___
 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://launchpa

Re: [Kicad-developers] 5.1 branch

[Maciej Sumiński]

It is terribly tedious to go through the bug list and change statuses
one by one, so I offer to help with the bug report status fiddling. We
may employ Janitor, but I guess it would be better to execute a simple
script to change Fix Committed->Fix Released whenever we release a new
version.

Cheers,
Orson

On 07/16/2018 03:30 PM, Wayne Stambaugh wrote:
> Hey Jeff,
> 
> We have been manually changing the bug status from fix committed to fix
> released after a new stable release.  AFAIK, the janitor does not handle
> this.  I suppose the janitor could be modified to test for a new release
> and change the tag for all bugs associated with that release.  That
> would not be 100% accurate because there are bugs that have not been
> associated with a branch but that would probably be easier than changing
> them all manually.  I don't have a strong preference one way or the other.
> 
> Wayne
> 
> On 7/16/2018 9:20 AM, Jeff Young wrote:
>> Hi Wayne,
>>
>> The other issue is that the Janitor is going to mark my fixes as Fix 
>> Committed, and I don’t know if the auto-bug-release facility is smart enough 
>> to check the milestone before converting Fix Committed to Fix Released.  So 
>> we may need to do that first too.
>>
>> Cheers,
>> Jeff.
>>
>>> On 16 Jul 2018, at 14:15, Wayne Stambaugh  wrote:
>>>
>>> Jeff,
>>>
>>> As a general rule, we merge changes into the development branch and then
>>> merge them into the stable release branch after they have been tested.
>>> In the past this has only been bug fixes so your case is slightly
>>> different.  The problem I see with merging your changes into the 5.1
>>> branch first is that they will not get as much testing as they would if
>>> you merged your changes into the development branch.  I would prefer
>>> that we merge changes into the development branch so that nightly builds
>>> can be used to get some good testing.  Any bug fixes to your changes can
>>> then be merged into the 5.1 branch.  Does anyone see any reason not to
>>> do it this way?
>>>
>>> Please do not merge your changes into the development branch just yet.
>>> Orson just fixed a bug and I'm considering retagging v5 to include this fix.
>>>
>>> Cheers,
>>>
>>> Wayne
>>>
>>> On 7/16/2018 5:05 AM, Jeff Young wrote:
 Thanks, JP!  I’ll make the fix.

> On 16 Jul 2018, at 09:24, jp charras  wrote:
>
> Le 16/07/2018 à 10:10, Jeff Young a écrit :
>> Well, rats.  I couldn’t figure out why "git rebase —interactive" wasn’t 
>> showing me any of my
>> commits, and it turns out that I somehow accidentally merged them all to 
>> origin/5.1 sometime last
>> night.  Anyway, you don’t have to fetch my private branch to test it 
>> anymore; the kicad 5.1 branch
>> will do nicely.
>>
>> Let me know if the paged dialog issues are keeping anyone from getting 
>> work done and I’ll try to
>> figure out how to revert those commits.
>
> Hi, Jeff
> The paged dialog issue is due to the fact the panels (pages) have an 
> incorrect parent.
> Currently, these panels have the dialog itself as parent.
> They should have m_treebook (the wxTreeBook similar to a wxNotebook) as 
> parent.
>
> (This change fixes the issue on W7)
>
>>
>> Cheers,
>> Jeff.
>
> -- 
> 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

>>>
>>> ___
>>> 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
> 




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

Re: [Kicad-developers] 5.1 branch

[jp charras]

Hi Jeff,

I just played with a few of your 5.1 changes.

Many are good, but the new netclass management is not as efficient as the 
current dialog:

- Modifying the netclass of a lot of nets is very tedious: the change must be 
done for each net
(this is the major issue).
- we cannot see easily the list of nets, as the netclass filter was removed.
However the net filter is a good idea.

I am also thinking the "Board Setup" menu should be in the main menu bar, not 
in the file menu (this
is a very important setting, not related to a file management)


Thanks for your work.

-- 
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] 5.1 branch

[Wayne Stambaugh]

On 7/16/2018 10:37 AM, jp charras wrote:
> Le 16/07/2018 à 16:09, Jeff Young a écrit :
>> I keep seeing issues with “incorrect” ratsnests on the kicad.info 
>>  forums.  Can
>> we put the curved ratsnests into 5.1?
> 
> This artifact exists only in Legacy mode, due to the XOR mode used to draw 
> them.
> curved ratsnests (it can be a good idea) need to be seriously tested, 
> especially considering
> calculation time on large boards.

If it seems to work well enough during development, I could give it the
nod for inclusion in 5.1 one but I don't want anyone to get their hopes
set on it for now.

> 
>>
>>
>>> On 16 Jul 2018, at 14:54, Jeff Young >> > wrote:
>>>
>>> Cool.  I’ll wait a few more days to make sure everything is settled down 
>>> and then merge the 5.1
>>> stuff to master.
>>>
>>> Should we go ahead and start making the Fix Committed bugs Fix Released, or 
>>> do we want to wait for
>>> the release announcement?
>>>
 On 16 Jul 2018, at 14:30, Wayne Stambaugh >>> > wrote:

 Hey Jeff,

 We have been manually changing the bug status from fix committed to fix
 released after a new stable release.  AFAIK, the janitor does not handle
 this.  I suppose the janitor could be modified to test for a new release
 and change the tag for all bugs associated with that release.  That
 would not be 100% accurate because there are bugs that have not been
 associated with a branch but that would probably be easier than changing
 them all manually.  I don't have a strong preference one way or the other.

 Wayne

 On 7/16/2018 9:20 AM, Jeff Young wrote:
> Hi Wayne,
>
> The other issue is that the Janitor is going to mark my fixes as Fix 
> Committed, and I don’t know
> if the auto-bug-release facility is smart enough to check the milestone 
> before converting Fix
> Committed to Fix Released.  So we may need to do that first too.
>
> Cheers,
> Jeff.
>
>> On 16 Jul 2018, at 14:15, Wayne Stambaugh > >
>> wrote:
>>
>> Jeff,
>>
>> As a general rule, we merge changes into the development branch and then
>> merge them into the stable release branch after they have been tested.
>> In the past this has only been bug fixes so your case is slightly
>> different.  The problem I see with merging your changes into the 5.1
>> branch first is that they will not get as much testing as they would if
>> you merged your changes into the development branch.  I would prefer
>> that we merge changes into the development branch so that nightly builds
>> can be used to get some good testing.  Any bug fixes to your changes can
>> then be merged into the 5.1 branch.  Does anyone see any reason not to
>> do it this way?
>>
>> Please do not merge your changes into the development branch just yet.
>> Orson just fixed a bug and I'm considering retagging v5 to include this 
>> fix.
>>
>> Cheers,
>>
>> Wayne
>>
>> On 7/16/2018 5:05 AM, Jeff Young wrote:
>>> Thanks, JP!  I’ll make the fix.
>>>
 On 16 Jul 2018, at 09:24, jp charras >>> >
 wrote:

 Le 16/07/2018 à 10:10, Jeff Young a écrit :
> Well, rats.  I couldn’t figure out why "git rebase —interactive" 
> wasn’t showing me any of my
> commits, and it turns out that I somehow accidentally merged them all 
> to origin/5.1 sometime
> last
> night.  Anyway, you don’t have to fetch my private branch to test it 
> anymore; the kicad 5.1
> branch
> will do nicely.
>
> Let me know if the paged dialog issues are keeping anyone from 
> getting work done and I’ll try to
> figure out how to revert those commits.

 Hi, Jeff
 The paged dialog issue is due to the fact the panels (pages) have an 
 incorrect parent.
 Currently, these panels have the dialog itself as parent.
 They should have m_treebook (the wxTreeBook similar to a wxNotebook) 
 as parent.

 (This change fixes the issue on W7)

>
> Cheers,
> Jeff.

 -- 
 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] 5.1 branch

[jp charras]

Le 16/07/2018 à 16:09, Jeff Young a écrit :
> I keep seeing issues with “incorrect” ratsnests on the kicad.info 
>  forums.  Can
> we put the curved ratsnests into 5.1?

This artifact exists only in Legacy mode, due to the XOR mode used to draw them.
curved ratsnests (it can be a good idea) need to be seriously tested, 
especially considering
calculation time on large boards.

> 
> 
>> On 16 Jul 2018, at 14:54, Jeff Young > > wrote:
>>
>> Cool.  I’ll wait a few more days to make sure everything is settled down and 
>> then merge the 5.1
>> stuff to master.
>>
>> Should we go ahead and start making the Fix Committed bugs Fix Released, or 
>> do we want to wait for
>> the release announcement?
>>
>>> On 16 Jul 2018, at 14:30, Wayne Stambaugh >> > wrote:
>>>
>>> Hey Jeff,
>>>
>>> We have been manually changing the bug status from fix committed to fix
>>> released after a new stable release.  AFAIK, the janitor does not handle
>>> this.  I suppose the janitor could be modified to test for a new release
>>> and change the tag for all bugs associated with that release.  That
>>> would not be 100% accurate because there are bugs that have not been
>>> associated with a branch but that would probably be easier than changing
>>> them all manually.  I don't have a strong preference one way or the other.
>>>
>>> Wayne
>>>
>>> On 7/16/2018 9:20 AM, Jeff Young wrote:
 Hi Wayne,

 The other issue is that the Janitor is going to mark my fixes as Fix 
 Committed, and I don’t know
 if the auto-bug-release facility is smart enough to check the milestone 
 before converting Fix
 Committed to Fix Released.  So we may need to do that first too.

 Cheers,
 Jeff.

> On 16 Jul 2018, at 14:15, Wayne Stambaugh  >
> wrote:
>
> Jeff,
>
> As a general rule, we merge changes into the development branch and then
> merge them into the stable release branch after they have been tested.
> In the past this has only been bug fixes so your case is slightly
> different.  The problem I see with merging your changes into the 5.1
> branch first is that they will not get as much testing as they would if
> you merged your changes into the development branch.  I would prefer
> that we merge changes into the development branch so that nightly builds
> can be used to get some good testing.  Any bug fixes to your changes can
> then be merged into the 5.1 branch.  Does anyone see any reason not to
> do it this way?
>
> Please do not merge your changes into the development branch just yet.
> Orson just fixed a bug and I'm considering retagging v5 to include this 
> fix.
>
> Cheers,
>
> Wayne
>
> On 7/16/2018 5:05 AM, Jeff Young wrote:
>> Thanks, JP!  I’ll make the fix.
>>
>>> On 16 Jul 2018, at 09:24, jp charras >> >
>>> wrote:
>>>
>>> Le 16/07/2018 à 10:10, Jeff Young a écrit :
 Well, rats.  I couldn’t figure out why "git rebase —interactive" 
 wasn’t showing me any of my
 commits, and it turns out that I somehow accidentally merged them all 
 to origin/5.1 sometime
 last
 night.  Anyway, you don’t have to fetch my private branch to test it 
 anymore; the kicad 5.1
 branch
 will do nicely.

 Let me know if the paged dialog issues are keeping anyone from getting 
 work done and I’ll try to
 figure out how to revert those commits.
>>>
>>> Hi, Jeff
>>> The paged dialog issue is due to the fact the panels (pages) have an 
>>> incorrect parent.
>>> Currently, these panels have the dialog itself as parent.
>>> They should have m_treebook (the wxTreeBook similar to a wxNotebook) as 
>>> parent.
>>>
>>> (This change fixes the issue on W7)
>>>

 Cheers,
 Jeff.
>>>
>>> -- 
>>> Jean-Pierre CHARRAS



-- 
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] 5.1 branch

[Wayne Stambaugh]

I can't think of any reason not to change the fix committed bug reports
to fix released so if you have the time, have at it.

On 7/16/2018 9:54 AM, Jeff Young wrote:
> Cool.  I’ll wait a few more days to make sure everything is settled down and 
> then merge the 5.1 stuff to master.
> 
> Should we go ahead and start making the Fix Committed bugs Fix Released, or 
> do we want to wait for the release announcement?
> 
>> On 16 Jul 2018, at 14:30, Wayne Stambaugh  wrote:
>>
>> Hey Jeff,
>>
>> We have been manually changing the bug status from fix committed to fix
>> released after a new stable release.  AFAIK, the janitor does not handle
>> this.  I suppose the janitor could be modified to test for a new release
>> and change the tag for all bugs associated with that release.  That
>> would not be 100% accurate because there are bugs that have not been
>> associated with a branch but that would probably be easier than changing
>> them all manually.  I don't have a strong preference one way or the other.
>>
>> Wayne
>>
>> On 7/16/2018 9:20 AM, Jeff Young wrote:
>>> Hi Wayne,
>>>
>>> The other issue is that the Janitor is going to mark my fixes as Fix 
>>> Committed, and I don’t know if the auto-bug-release facility is smart 
>>> enough to check the milestone before converting Fix Committed to Fix 
>>> Released.  So we may need to do that first too.
>>>
>>> Cheers,
>>> Jeff.
>>>
 On 16 Jul 2018, at 14:15, Wayne Stambaugh  wrote:

 Jeff,

 As a general rule, we merge changes into the development branch and then
 merge them into the stable release branch after they have been tested.
 In the past this has only been bug fixes so your case is slightly
 different.  The problem I see with merging your changes into the 5.1
 branch first is that they will not get as much testing as they would if
 you merged your changes into the development branch.  I would prefer
 that we merge changes into the development branch so that nightly builds
 can be used to get some good testing.  Any bug fixes to your changes can
 then be merged into the 5.1 branch.  Does anyone see any reason not to
 do it this way?

 Please do not merge your changes into the development branch just yet.
 Orson just fixed a bug and I'm considering retagging v5 to include this 
 fix.

 Cheers,

 Wayne

 On 7/16/2018 5:05 AM, Jeff Young wrote:
> Thanks, JP!  I’ll make the fix.
>
>> On 16 Jul 2018, at 09:24, jp charras  wrote:
>>
>> Le 16/07/2018 à 10:10, Jeff Young a écrit :
>>> Well, rats.  I couldn’t figure out why "git rebase —interactive" wasn’t 
>>> showing me any of my
>>> commits, and it turns out that I somehow accidentally merged them all 
>>> to origin/5.1 sometime last
>>> night.  Anyway, you don’t have to fetch my private branch to test it 
>>> anymore; the kicad 5.1 branch
>>> will do nicely.
>>>
>>> Let me know if the paged dialog issues are keeping anyone from getting 
>>> work done and I’ll try to
>>> figure out how to revert those commits.
>>
>> Hi, Jeff
>> The paged dialog issue is due to the fact the panels (pages) have an 
>> incorrect parent.
>> Currently, these panels have the dialog itself as parent.
>> They should have m_treebook (the wxTreeBook similar to a wxNotebook) as 
>> parent.
>>
>> (This change fixes the issue on W7)
>>
>>>
>>> Cheers,
>>> Jeff.
>>
>> -- 
>> 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
>

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

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

Re: [Kicad-developers] 5.1 branch

[Jeff Young]

I keep seeing issues with “incorrect” ratsnests on the kicad.info 
 forums.  Can we put the curved ratsnests into 5.1?


> On 16 Jul 2018, at 14:54, Jeff Young  wrote:
> 
> Cool.  I’ll wait a few more days to make sure everything is settled down and 
> then merge the 5.1 stuff to master.
> 
> Should we go ahead and start making the Fix Committed bugs Fix Released, or 
> do we want to wait for the release announcement?
> 
>> On 16 Jul 2018, at 14:30, Wayne Stambaugh  wrote:
>> 
>> Hey Jeff,
>> 
>> We have been manually changing the bug status from fix committed to fix
>> released after a new stable release.  AFAIK, the janitor does not handle
>> this.  I suppose the janitor could be modified to test for a new release
>> and change the tag for all bugs associated with that release.  That
>> would not be 100% accurate because there are bugs that have not been
>> associated with a branch but that would probably be easier than changing
>> them all manually.  I don't have a strong preference one way or the other.
>> 
>> Wayne
>> 
>> On 7/16/2018 9:20 AM, Jeff Young wrote:
>>> Hi Wayne,
>>> 
>>> The other issue is that the Janitor is going to mark my fixes as Fix 
>>> Committed, and I don’t know if the auto-bug-release facility is smart 
>>> enough to check the milestone before converting Fix Committed to Fix 
>>> Released.  So we may need to do that first too.
>>> 
>>> Cheers,
>>> Jeff.
>>> 
 On 16 Jul 2018, at 14:15, Wayne Stambaugh  wrote:
 
 Jeff,
 
 As a general rule, we merge changes into the development branch and then
 merge them into the stable release branch after they have been tested.
 In the past this has only been bug fixes so your case is slightly
 different.  The problem I see with merging your changes into the 5.1
 branch first is that they will not get as much testing as they would if
 you merged your changes into the development branch.  I would prefer
 that we merge changes into the development branch so that nightly builds
 can be used to get some good testing.  Any bug fixes to your changes can
 then be merged into the 5.1 branch.  Does anyone see any reason not to
 do it this way?
 
 Please do not merge your changes into the development branch just yet.
 Orson just fixed a bug and I'm considering retagging v5 to include this 
 fix.
 
 Cheers,
 
 Wayne
 
 On 7/16/2018 5:05 AM, Jeff Young wrote:
> Thanks, JP!  I’ll make the fix.
> 
>> On 16 Jul 2018, at 09:24, jp charras  wrote:
>> 
>> Le 16/07/2018 à 10:10, Jeff Young a écrit :
>>> Well, rats.  I couldn’t figure out why "git rebase —interactive" wasn’t 
>>> showing me any of my
>>> commits, and it turns out that I somehow accidentally merged them all 
>>> to origin/5.1 sometime last
>>> night.  Anyway, you don’t have to fetch my private branch to test it 
>>> anymore; the kicad 5.1 branch
>>> will do nicely.
>>> 
>>> Let me know if the paged dialog issues are keeping anyone from getting 
>>> work done and I’ll try to
>>> figure out how to revert those commits.
>> 
>> Hi, Jeff
>> The paged dialog issue is due to the fact the panels (pages) have an 
>> incorrect parent.
>> Currently, these panels have the dialog itself as parent.
>> They should have m_treebook (the wxTreeBook similar to a wxNotebook) as 
>> parent.
>> 
>> (This change fixes the issue on W7)
>> 
>>> 
>>> Cheers,
>>> Jeff.
>> 
>> -- 
>> 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
> 
 
 ___
 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.l

Re: [Kicad-developers] 5.1 branch

[Wayne Stambaugh]

Yes, assuming we can get that to work without dragging in Phoenix.

On 7/16/2018 9:27 AM, Jeff Young wrote:
> 5.1 is also for the GTK3 fixes, right?
> 
>> On 16 Jul 2018, at 14:23, Wayne Stambaugh  wrote:
>>
>> On 7/16/2018 9:19 AM, Simon Richter wrote:
>>> Hi,
>>>
>>> On 15.07.2018 13:39, Jeff Young wrote:
>>>
 I renamed my 6.0 branch to 5.1, since most of what it contains goes there.
>>>
>>> What is the difference between 5.1 and 6.0? What goes into which branch?
>>>
>>>   Simon
>>>
>>
>> 5.1 is only for the UI refactoring Jeff is working on along with any bug
>> fixes that get merged into the 5.0 branch.  Any new features such as the
>> new schematic file formats or GALification of eeschema are v6 only.
>>
>> ___
>> Mailing list: https://launchpad.net/~kicad-developers
>> Post to : kicad-developers@lists.launchpad.net
>> Unsubscribe : https://launchpad.net/~kicad-developers
>> More help   : https://help.launchpad.net/ListHelp
> 

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

Re: [Kicad-developers] 5.1 branch

[Jeff Young]

Cool.  I’ll wait a few more days to make sure everything is settled down and 
then merge the 5.1 stuff to master.

Should we go ahead and start making the Fix Committed bugs Fix Released, or do 
we want to wait for the release announcement?

> On 16 Jul 2018, at 14:30, Wayne Stambaugh  wrote:
> 
> Hey Jeff,
> 
> We have been manually changing the bug status from fix committed to fix
> released after a new stable release.  AFAIK, the janitor does not handle
> this.  I suppose the janitor could be modified to test for a new release
> and change the tag for all bugs associated with that release.  That
> would not be 100% accurate because there are bugs that have not been
> associated with a branch but that would probably be easier than changing
> them all manually.  I don't have a strong preference one way or the other.
> 
> Wayne
> 
> On 7/16/2018 9:20 AM, Jeff Young wrote:
>> Hi Wayne,
>> 
>> The other issue is that the Janitor is going to mark my fixes as Fix 
>> Committed, and I don’t know if the auto-bug-release facility is smart enough 
>> to check the milestone before converting Fix Committed to Fix Released.  So 
>> we may need to do that first too.
>> 
>> Cheers,
>> Jeff.
>> 
>>> On 16 Jul 2018, at 14:15, Wayne Stambaugh  wrote:
>>> 
>>> Jeff,
>>> 
>>> As a general rule, we merge changes into the development branch and then
>>> merge them into the stable release branch after they have been tested.
>>> In the past this has only been bug fixes so your case is slightly
>>> different.  The problem I see with merging your changes into the 5.1
>>> branch first is that they will not get as much testing as they would if
>>> you merged your changes into the development branch.  I would prefer
>>> that we merge changes into the development branch so that nightly builds
>>> can be used to get some good testing.  Any bug fixes to your changes can
>>> then be merged into the 5.1 branch.  Does anyone see any reason not to
>>> do it this way?
>>> 
>>> Please do not merge your changes into the development branch just yet.
>>> Orson just fixed a bug and I'm considering retagging v5 to include this fix.
>>> 
>>> Cheers,
>>> 
>>> Wayne
>>> 
>>> On 7/16/2018 5:05 AM, Jeff Young wrote:
 Thanks, JP!  I’ll make the fix.
 
> On 16 Jul 2018, at 09:24, jp charras  wrote:
> 
> Le 16/07/2018 à 10:10, Jeff Young a écrit :
>> Well, rats.  I couldn’t figure out why "git rebase —interactive" wasn’t 
>> showing me any of my
>> commits, and it turns out that I somehow accidentally merged them all to 
>> origin/5.1 sometime last
>> night.  Anyway, you don’t have to fetch my private branch to test it 
>> anymore; the kicad 5.1 branch
>> will do nicely.
>> 
>> Let me know if the paged dialog issues are keeping anyone from getting 
>> work done and I’ll try to
>> figure out how to revert those commits.
> 
> Hi, Jeff
> The paged dialog issue is due to the fact the panels (pages) have an 
> incorrect parent.
> Currently, these panels have the dialog itself as parent.
> They should have m_treebook (the wxTreeBook similar to a wxNotebook) as 
> parent.
> 
> (This change fixes the issue on W7)
> 
>> 
>> Cheers,
>> Jeff.
> 
> -- 
> 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
 
>>> 
>>> ___
>>> Mailing list: https://launchpad.net/~kicad-developers
>>> Post to : kicad-developers@lists.launchpad.net
>>> Unsubscribe : https://launchpad.net/~kicad-developers
>>> More help   : https://help.launchpad.net/ListHelp
>> 


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

Re: [Kicad-developers] 5.1 branch

[Wayne Stambaugh]

Hey Jeff,

We have been manually changing the bug status from fix committed to fix
released after a new stable release.  AFAIK, the janitor does not handle
this.  I suppose the janitor could be modified to test for a new release
and change the tag for all bugs associated with that release.  That
would not be 100% accurate because there are bugs that have not been
associated with a branch but that would probably be easier than changing
them all manually.  I don't have a strong preference one way or the other.

Wayne

On 7/16/2018 9:20 AM, Jeff Young wrote:
> Hi Wayne,
> 
> The other issue is that the Janitor is going to mark my fixes as Fix 
> Committed, and I don’t know if the auto-bug-release facility is smart enough 
> to check the milestone before converting Fix Committed to Fix Released.  So 
> we may need to do that first too.
> 
> Cheers,
> Jeff.
> 
>> On 16 Jul 2018, at 14:15, Wayne Stambaugh  wrote:
>>
>> Jeff,
>>
>> As a general rule, we merge changes into the development branch and then
>> merge them into the stable release branch after they have been tested.
>> In the past this has only been bug fixes so your case is slightly
>> different.  The problem I see with merging your changes into the 5.1
>> branch first is that they will not get as much testing as they would if
>> you merged your changes into the development branch.  I would prefer
>> that we merge changes into the development branch so that nightly builds
>> can be used to get some good testing.  Any bug fixes to your changes can
>> then be merged into the 5.1 branch.  Does anyone see any reason not to
>> do it this way?
>>
>> Please do not merge your changes into the development branch just yet.
>> Orson just fixed a bug and I'm considering retagging v5 to include this fix.
>>
>> Cheers,
>>
>> Wayne
>>
>> On 7/16/2018 5:05 AM, Jeff Young wrote:
>>> Thanks, JP!  I’ll make the fix.
>>>
 On 16 Jul 2018, at 09:24, jp charras  wrote:

 Le 16/07/2018 à 10:10, Jeff Young a écrit :
> Well, rats.  I couldn’t figure out why "git rebase —interactive" wasn’t 
> showing me any of my
> commits, and it turns out that I somehow accidentally merged them all to 
> origin/5.1 sometime last
> night.  Anyway, you don’t have to fetch my private branch to test it 
> anymore; the kicad 5.1 branch
> will do nicely.
>
> Let me know if the paged dialog issues are keeping anyone from getting 
> work done and I’ll try to
> figure out how to revert those commits.

 Hi, Jeff
 The paged dialog issue is due to the fact the panels (pages) have an 
 incorrect parent.
 Currently, these panels have the dialog itself as parent.
 They should have m_treebook (the wxTreeBook similar to a wxNotebook) as 
 parent.

 (This change fixes the issue on W7)

>
> Cheers,
> Jeff.

 -- 
 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
>>>
>>
>> ___
>> Mailing list: https://launchpad.net/~kicad-developers
>> Post to : kicad-developers@lists.launchpad.net
>> Unsubscribe : https://launchpad.net/~kicad-developers
>> More help   : https://help.launchpad.net/ListHelp
> 

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

Re: [Kicad-developers] 5.1 branch

[Jeff Young]

5.1 is also for the GTK3 fixes, right?

> On 16 Jul 2018, at 14:23, Wayne Stambaugh  wrote:
> 
> On 7/16/2018 9:19 AM, Simon Richter wrote:
>> Hi,
>> 
>> On 15.07.2018 13:39, Jeff Young wrote:
>> 
>>> I renamed my 6.0 branch to 5.1, since most of what it contains goes there.
>> 
>> What is the difference between 5.1 and 6.0? What goes into which branch?
>> 
>>   Simon
>> 
> 
> 5.1 is only for the UI refactoring Jeff is working on along with any bug
> fixes that get merged into the 5.0 branch.  Any new features such as the
> new schematic file formats or GALification of eeschema are v6 only.
> 
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp


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

Re: [Kicad-developers] 5.1 branch

[Wayne Stambaugh]

On 7/16/2018 9:19 AM, Simon Richter wrote:
> Hi,
> 
> On 15.07.2018 13:39, Jeff Young wrote:
> 
>> I renamed my 6.0 branch to 5.1, since most of what it contains goes there.
> 
> What is the difference between 5.1 and 6.0? What goes into which branch?
> 
>Simon
> 

5.1 is only for the UI refactoring Jeff is working on along with any bug
fixes that get merged into the 5.0 branch.  Any new features such as the
new schematic file formats or GALification of eeschema are v6 only.

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

Re: [Kicad-developers] 5.1 branch

[Jeff Young]

Hi Wayne,

The other issue is that the Janitor is going to mark my fixes as Fix Committed, 
and I don’t know if the auto-bug-release facility is smart enough to check the 
milestone before converting Fix Committed to Fix Released.  So we may need to 
do that first too.

Cheers,
Jeff.

> On 16 Jul 2018, at 14:15, Wayne Stambaugh  wrote:
> 
> Jeff,
> 
> As a general rule, we merge changes into the development branch and then
> merge them into the stable release branch after they have been tested.
> In the past this has only been bug fixes so your case is slightly
> different.  The problem I see with merging your changes into the 5.1
> branch first is that they will not get as much testing as they would if
> you merged your changes into the development branch.  I would prefer
> that we merge changes into the development branch so that nightly builds
> can be used to get some good testing.  Any bug fixes to your changes can
> then be merged into the 5.1 branch.  Does anyone see any reason not to
> do it this way?
> 
> Please do not merge your changes into the development branch just yet.
> Orson just fixed a bug and I'm considering retagging v5 to include this fix.
> 
> Cheers,
> 
> Wayne
> 
> On 7/16/2018 5:05 AM, Jeff Young wrote:
>> Thanks, JP!  I’ll make the fix.
>> 
>>> On 16 Jul 2018, at 09:24, jp charras  wrote:
>>> 
>>> Le 16/07/2018 à 10:10, Jeff Young a écrit :
 Well, rats.  I couldn’t figure out why "git rebase —interactive" wasn’t 
 showing me any of my
 commits, and it turns out that I somehow accidentally merged them all to 
 origin/5.1 sometime last
 night.  Anyway, you don’t have to fetch my private branch to test it 
 anymore; the kicad 5.1 branch
 will do nicely.
 
 Let me know if the paged dialog issues are keeping anyone from getting 
 work done and I’ll try to
 figure out how to revert those commits.
>>> 
>>> Hi, Jeff
>>> The paged dialog issue is due to the fact the panels (pages) have an 
>>> incorrect parent.
>>> Currently, these panels have the dialog itself as parent.
>>> They should have m_treebook (the wxTreeBook similar to a wxNotebook) as 
>>> parent.
>>> 
>>> (This change fixes the issue on W7)
>>> 
 
 Cheers,
 Jeff.
>>> 
>>> -- 
>>> 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
>> 
> 
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp


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

Re: [Kicad-developers] 5.1 branch

[Simon Richter]

Hi,

On 15.07.2018 13:39, Jeff Young wrote:

> I renamed my 6.0 branch to 5.1, since most of what it contains goes there.

What is the difference between 5.1 and 6.0? What goes into which branch?

   Simon




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

Re: [Kicad-developers] 5.1 branch

[Wayne Stambaugh]

Jeff,

As a general rule, we merge changes into the development branch and then
merge them into the stable release branch after they have been tested.
In the past this has only been bug fixes so your case is slightly
different.  The problem I see with merging your changes into the 5.1
branch first is that they will not get as much testing as they would if
you merged your changes into the development branch.  I would prefer
that we merge changes into the development branch so that nightly builds
can be used to get some good testing.  Any bug fixes to your changes can
then be merged into the 5.1 branch.  Does anyone see any reason not to
do it this way?

Please do not merge your changes into the development branch just yet.
Orson just fixed a bug and I'm considering retagging v5 to include this fix.

Cheers,

Wayne

On 7/16/2018 5:05 AM, Jeff Young wrote:
> Thanks, JP!  I’ll make the fix.
> 
>> On 16 Jul 2018, at 09:24, jp charras  wrote:
>>
>> Le 16/07/2018 à 10:10, Jeff Young a écrit :
>>> Well, rats.  I couldn’t figure out why "git rebase —interactive" wasn’t 
>>> showing me any of my
>>> commits, and it turns out that I somehow accidentally merged them all to 
>>> origin/5.1 sometime last
>>> night.  Anyway, you don’t have to fetch my private branch to test it 
>>> anymore; the kicad 5.1 branch
>>> will do nicely.
>>>
>>> Let me know if the paged dialog issues are keeping anyone from getting work 
>>> done and I’ll try to
>>> figure out how to revert those commits.
>>
>> Hi, Jeff
>> The paged dialog issue is due to the fact the panels (pages) have an 
>> incorrect parent.
>> Currently, these panels have the dialog itself as parent.
>> They should have m_treebook (the wxTreeBook similar to a wxNotebook) as 
>> parent.
>>
>> (This change fixes the issue on W7)
>>
>>>
>>> Cheers,
>>> Jeff.
>>
>> -- 
>> 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
> 

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

Re: [Kicad-developers] 5.1 branch

[Jeff Young]

Thanks, JP!  I’ll make the fix.

> On 16 Jul 2018, at 09:24, jp charras  wrote:
> 
> Le 16/07/2018 à 10:10, Jeff Young a écrit :
>> Well, rats.  I couldn’t figure out why "git rebase —interactive" wasn’t 
>> showing me any of my
>> commits, and it turns out that I somehow accidentally merged them all to 
>> origin/5.1 sometime last
>> night.  Anyway, you don’t have to fetch my private branch to test it 
>> anymore; the kicad 5.1 branch
>> will do nicely.
>> 
>> Let me know if the paged dialog issues are keeping anyone from getting work 
>> done and I’ll try to
>> figure out how to revert those commits.
> 
> Hi, Jeff
> The paged dialog issue is due to the fact the panels (pages) have an 
> incorrect parent.
> Currently, these panels have the dialog itself as parent.
> They should have m_treebook (the wxTreeBook similar to a wxNotebook) as 
> parent.
> 
> (This change fixes the issue on W7)
> 
>> 
>> Cheers,
>> Jeff.
> 
> -- 
> 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] 5.1 branch

[jp charras]

Le 16/07/2018 à 10:10, Jeff Young a écrit :
> Well, rats.  I couldn’t figure out why "git rebase —interactive" wasn’t 
> showing me any of my
> commits, and it turns out that I somehow accidentally merged them all to 
> origin/5.1 sometime last
> night.  Anyway, you don’t have to fetch my private branch to test it anymore; 
> the kicad 5.1 branch
> will do nicely.
> 
> Let me know if the paged dialog issues are keeping anyone from getting work 
> done and I’ll try to
> figure out how to revert those commits.

Hi, Jeff
The paged dialog issue is due to the fact the panels (pages) have an incorrect 
parent.
Currently, these panels have the dialog itself as parent.
They should have m_treebook (the wxTreeBook similar to a wxNotebook) as parent.

(This change fixes the issue on W7)

> 
> Cheers,
> Jeff.

-- 
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] 5.1 branch

[Jeff Young]

Well, rats.  I couldn’t figure out why "git rebase —interactive" wasn’t showing 
me any of my commits, and it turns out that I somehow accidentally merged them 
all to origin/5.1 sometime last night.  Anyway, you don’t have to fetch my 
private branch to test it anymore; the kicad 5.1 branch will do nicely.

Let me know if the paged dialog issues are keeping anyone from getting work 
done and I’ll try to figure out how to revert those commits.

Cheers,
Jeff.


> On 16 Jul 2018, at 08:45, Eeli Kaikkonen  wrote:
> 
> 
> 
> ma 16. heinäk. 2018 klo 8.48 Nick Østergaard (oe.n...@gmail.com 
> ) kirjoitti:
> Can you edit anything on them? Can you provide a screenshot of the 
> preferences dialog?
> 
> 
> https://drive.google.com/file/d/1eq26OWT7TDeBTnbyAfUpUckT5V6MuwU8/view?usp=sharing
>  
> 
>  

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

Re: [Kicad-developers] 5.1 branch

[Eeli Kaikkonen]

ma 16. heinäk. 2018 klo 8.48 Nick Østergaard (oe.n...@gmail.com) kirjoitti:

> Can you edit anything on them? Can you provide a screenshot of the
> preferences dialog?
>
>
https://drive.google.com/file/d/1eq26OWT7TDeBTnbyAfUpUckT5V6MuwU8/view?usp=sharing
___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] 5.1 branch

[Nick Østergaard]

Can you edit anything on them? Can you provide a screenshot of the
preferences dialog?

søn. 15. jul. 2018 23.15 skrev Eeli Kaikkonen :

>
>
> su 15. heinäk. 2018 klo 14.39 Jeff Young (j...@rokeby.ie) kirjoitti:
>
>> I renamed my 6.0 branch to 5.1, since most of what it contains goes there.
>>
>> Has anyone had a chance to try out the paged dialogs (Preferences and
>> Board Setup) on Windows or Linux?  They weren’t working for Nick (disabled
>> panels).
>>
>
> Works here in Ubuntu 17.10.
>
> Application: kicad
> Version: (5.0.0-rc3-dev-86-g2eeed8ee3-dirty), release build
> Libraries:
> wxWidgets 3.0.3
> libcurl/7.55.1 OpenSSL/1.0.2g zlib/1.2.11 libidn2/2.0.2 libpsl/0.18.0
> (+libidn2/2.0.2) librtmp/2.3
> Platform: Linux 4.13.0-46-generic x86_64, 64 bit, Little endian, wxGTK
> Build Info:
> wxWidgets: 3.0.3 (wchar_t,wx containers,compatible with 2.8) GTK+ 2.24
> Boost: 1.62.0
> OpenCASCADE Community Edition: 6.8.0
> Curl: 7.55.1
> Compiler: GCC 7.2.0 with C++ ABI 1011
>
> Build settings:
> USE_WX_GRAPHICS_CONTEXT=OFF
> USE_WX_OVERLAY=OFF
> KICAD_SCRIPTING=ON
> KICAD_SCRIPTING_MODULES=ON
> KICAD_SCRIPTING_WXPYTHON=ON
> KICAD_SCRIPTING_ACTION_MENU=OFF
> BUILD_GITHUB_PLUGIN=ON
> KICAD_USE_OCE=ON
> KICAD_USE_OCC=OFF
> KICAD_SPICE=OFF
>
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp
>
___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] 5.1 branch

[Eeli Kaikkonen]

su 15. heinäk. 2018 klo 14.39 Jeff Young (j...@rokeby.ie) kirjoitti:

> I renamed my 6.0 branch to 5.1, since most of what it contains goes there.
>
> Has anyone had a chance to try out the paged dialogs (Preferences and
> Board Setup) on Windows or Linux?  They weren’t working for Nick (disabled
> panels).
>

Works here in Ubuntu 17.10.

Application: kicad
Version: (5.0.0-rc3-dev-86-g2eeed8ee3-dirty), release build
Libraries:
wxWidgets 3.0.3
libcurl/7.55.1 OpenSSL/1.0.2g zlib/1.2.11 libidn2/2.0.2 libpsl/0.18.0
(+libidn2/2.0.2) librtmp/2.3
Platform: Linux 4.13.0-46-generic x86_64, 64 bit, Little endian, wxGTK
Build Info:
wxWidgets: 3.0.3 (wchar_t,wx containers,compatible with 2.8) GTK+ 2.24
Boost: 1.62.0
OpenCASCADE Community Edition: 6.8.0
Curl: 7.55.1
Compiler: GCC 7.2.0 with C++ ABI 1011

Build settings:
USE_WX_GRAPHICS_CONTEXT=OFF
USE_WX_OVERLAY=OFF
KICAD_SCRIPTING=ON
KICAD_SCRIPTING_MODULES=ON
KICAD_SCRIPTING_WXPYTHON=ON
KICAD_SCRIPTING_ACTION_MENU=OFF
BUILD_GITHUB_PLUGIN=ON
KICAD_USE_OCE=ON
KICAD_USE_OCC=OFF
KICAD_SPICE=OFF
___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] 5.1 branch

[jp charras]

Le 15/07/2018 à 13:39, Jeff Young a écrit :
> I renamed my 6.0 branch to 5.1, since most of what it contains goes there.
> 
> Has anyone had a chance to try out the paged dialogs (Preferences and Board 
> Setup) on Windows or Linux?  They weren’t working for Nick (disabled panels).
> 
> Cheers,
> Jeff.

These dialogs are not working for me (W7 32 bits).
I confirm panels are disabled.

A strange behavior of the About dialog:
It works fine called from Kicad manager.
But called from eeschema, pcbnew or page layour editor, the first and last 
pages (information and
license) are incorrectly shown:
the Html text looks like it could be displayed in a usual wxTextControl, not a 
html window.
However none of html tags are displayed, so it is not displayed as a ASCII text.
Other pages are correctly displayed.


-- 
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