← Back to team overview

kicad-developers team mailing list archive

Re: Proper way to report bugs on branches


You can also report the bug including the version info from your branch
(especially if your branch is public) -- if the bug is clearly not with
your code, it should be easy for others to reproduce it.

What I do to make things simpler is to keep several working copies of KiCad
around, so I don't have to completely switch branches and rebuild whenever
I change from master to a feature branch, or master to 5.1, etc.
Of course, this takes more storage space, but if you have room for it, I
recommend this approach.

You are right about the overbar bug, you can work around it by writing ~CS~
instead of ~CS for now.


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

> 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.
> Brian
> 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.
> -Jon
> On Mon, Jan 27, 2020 at 7:10 PM Brian Piccioni <
> brian@xxxxxxxxxxxxxxxxxxxxx> wrote:
>> Hello
>> I have been using Kicad while working on re-annotation (hopefully
>> Alexander's merge request will soon be accepted and I can dust off mine).
>> I have been using branches of the current master. I have noticed a few
>> 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?
>> Brian
>> _______________________________________________
>> 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