kicad-developers team mailing list archive

[Ian McInerney <Ian.S.McInerney@xxxxxxxx>]

To add on to this, the hotkey validation architecture that I have been
building up to take care of the many issues surrounding the
duplicate/invalid hotkeys (and also the fact that they can exist due to a
user's hotkey settings from prior versions) will require new strings since
I have error prompts. If this is something that should go in 5.1.3, then
string changes will need to be allowed.

I hope to have a patch set based on master put together in the next few
days for people to test, and if you want to include it in 5.1.3 I can trim
down the patch set to work on the 5.1 (I believe that some changes may not
cherrypick easily from master to 5.1).

-Ian

On Sun, Jun 9, 2019 at 3:27 PM Seth Hillbrand <seth@xxxxxxxxxxxxx> wrote:

> On 2019-05-22 16:37, Wayne Stambaugh wrote:
> > We are getting a decent set of bug fixes in the 5.1 branch so we should
> > seriously start thinking about a 5.1.3 stable release by the end of
> > June.  What I would like to see is push to fix some of the outstanding
> > 5.1 bugs[1] and then do a string freeze in the middle of June.  If you
> > see a bug that is code that you are familiar with, please consider
> > fixing it.  There will be plenty of time to work on v6.  Thanks again
> > everyone for your continued efforts.
>
> Hi Wayne-
>
> Are we considering string changes for 5.1.3?  I had thought our policy
> was no string changes for the minor bug fix releases.  If we do have
> string changes, I'll push a couple additional mods to the 5.1.3 branch
> that clarify actions.
>
> Could we also get a 5.1.4 tag for bugs that are lower priority/harder
> implementations?
>
> -Seth
>
> _______________________________________________
> 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
>