← Back to team overview

kicad-developers team mailing list archive

Re: Proper way to report bugs on branches


I am pretty sure, yes.

So I should recompile the master branch and try reproduce the bugs and report as normal?

Another example is one of the bugs is related to buses - if one of a list { SCL SCK ~CS RD} all items after and including CS have an over bar.


On 2020-01-27 7:14 p.m., Jon Evans wrote:
Can you reproduce these same issues on the master branch? Either the latest master, or the point on master at which your custom branch splits (i.e. the most recent rebase point) Doing so will absolutely rule out that there is anything about your branch related, and also make it easier to figure out what (master) commit is the relevant origin point for the bug report.


On Mon, Jan 27, 2020 at 7:10 PM Brian Piccioni <brian@xxxxxxxxxxxxxxxxxxxxx <mailto:brian@xxxxxxxxxxxxxxxxxxxxx>> wrote:


    I have been using Kicad while working on re-annotation (hopefully
    Alexander's merge request will soon be accepted and I can dust off

    I have been using branches of the current master. I have noticed a
    issues which I think are significant and not related to
    Alexander's work
    (or mine).

    For example, when I hit F8 in eeSchema to update my PCB it resolutely
    demands to update some of my resistor network symbols unless I select
    "Update footprint associations by existing references". This seems to
    happen no matter how many time I let it update those RNs.

    Should I used the standard bug reporting system or is there a special
    way to deal with these?


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

Follow ups