Thanks Nick!
Yes, I figured that nothing it going into 5.0.2 that won't be in 5.1 but,
on the off-chance that we're delayed in 5.1, I'm glad to have a place to
address 5.0 bugs.
-S
Am Mi., 5. Sep. 2018 um 13:46 Uhr schrieb Nick Østergaard :
> Hi Seth
>
> I have made the milestone, currently
Hi Seth
I have made the milestone, currently with this description.
"For stuff we don't really need to block 5.0.1 and we would like to
backport to 5.0..."
I am not sure we need this milestone, I thought we went for 5.1.0. But
as I am far behind with the emails, I created it anyways to not
Hi Nick/Wayne-
Can we get a 5.0.2 milestone in the bug tracker? Since 5.0.1 is nearing,
I'd like a new milestone for the 5.0 series to put low-priority bugs that
affect 5.0.
Thanks-
Seth
___
Mailing list: https://launchpad.net/~kicad-developers
Post
I'm fine with this going into 5.1 as long as we are not changing the
board file format which doesn't appear to be the case with these changes.
On 06/22/2018 10:28 AM, Jeff Young wrote:
> The dialog work started life as eradicating the g_UserUnit global
> variable so that the different apps
Nick,
Thanks for taking care of this. It was on my list. There is one
caveat. We will need to be diligent about what changes we allow into
5.0.1 versus 5.1.0. Please keep in mind that micro releases are bug fix
only so no string or feature changes. Minor feature and string changes
will have
Hello Seth
I have created the following milestone names:
5.1.0
This is for fixes that are backportable from master, it could be string
fixes and minor features.
5.0.1
Post release fixes that does not involve string changes.
Att. Wayne, I would like you to say this is ok, or if we should use
Hi Devs-
Can we get a v5.1 milestone on the bug tracker? I'd like to start
separating the items we are planning for the point release from the the v6
release. That way we can begin to discuss which belong where.
It would probably be useful to also have a 5.0.1 milestone that we can
assign
7 matches
Mail list logo
