This is really excellent news! Thank you Wayne!
The webhook is already set, let's fix a few bugs to see if it works.
Just to remind you, there is a git config file that should ease marking
commits as bug fixes [1].
Cheers,
Orson
1. https://lists.launchpad.net/kicad-developers/msg25728.html
On
Let me tag 4.0.4 first since I'm hoping to roll out another stable
release soonish. I'll do this right now. I can push this release back
a few days until we get the 4 stable branch merged into the main kicad
git repo. Thanks for the help. Anyone else object to this? I'm
thinking about my
This package dev is fine with you waiting a few days for 4.0.4, but let's
not stretch out much more than that.
On Mon, Aug 22, 2016 at 9:21 AM, Chris Pavlina
wrote:
> On Mon, Aug 22, 2016 at 09:57:26AM -0400, Wayne Stambaugh wrote:
> > On 8/22/2016 9:53 AM, Clemens
Hello.
I think need to rename .bzrignore to .gitignore and to remove
.gitconfig.
P.S. I don't know but I have issue with this one when I use
~/.gitignore_global.
В Понедельник, 22 авг. 2016 в 5:36 , Wayne Stambaugh
написал:
Let me tag 4.0.4 first since I'm hoping to
I just tagged 4.0.4 so technically you can start creating packages
against it. I'm not sure of the status of the doc, lib, and translation
repos. I will try to make the announcement before I go out of town for
the weekend but I cannot promise that it will happen.
On 8/22/2016 10:50 AM, Adam
Feel free to procrastinate the announcement.
Since it seems we will reuse the 4.0.3 doc, lib and i18n but I they have
not been retagged yet, it is ok to delay it half a day. Alternately you
could make the announcement a draft and I can publish it when ready.
Den 22/08/2016 17.46 skrev "Wayne
In launchpad git bug tagged in commit message like :
bug #id
Launchpad give a link to.
В Понедельник, 22 авг. 2016 в 6:38 , Wayne Stambaugh
написал:
I just tagged 4.0.4 so technically you can start creating packages
against it. I'm not sure of the status of the doc,
The github mirror is useful to keep because its usually far faster
than launchpad and easier to deal with for personal development.
The benefit is that after someone does all their work on github, one
can simply push it back to launchpad with zero issues by just adding
another remote.
Bzr on the
I wasn't planning on migrating the stable 4 branch to git. I'm hoping
there wont be too many more 4 stable releases so I'm not sure it's worth
the effort.
On 8/21/2016 11:45 PM, kinichiro inoguchi wrote:
> Hi,
> Thanks for transitioning to git !
>
> Do you plan to move stable 4.0 blanch, too ?
There is one issue. I cannot associate series or milestone to a git
repo. This means the nifty timeline on the summary page doesn't work.
If you click on the product-git series, you will find there is no repo
association like there was with the bzr product repo. I don't know if
this something
On 8/22/2016 9:53 AM, Clemens Koller wrote:
> Hi, Wayne!
>
> On 2016-08-22 14:09, Wayne Stambaugh wrote:
>> I wasn't planning on migrating the stable 4 branch to git. I'm hoping
>> there wont be too many more 4 stable releases so I'm not sure it's worth
>> the effort.
>
> Ok, I was wondering...
On Mon, Aug 22, 2016 at 09:57:26AM -0400, Wayne Stambaugh wrote:
> On 8/22/2016 9:53 AM, Clemens Koller wrote:
> > Hi, Wayne!
> >
> > On 2016-08-22 14:09, Wayne Stambaugh wrote:
> >> I wasn't planning on migrating the stable 4 branch to git. I'm hoping
> >> there wont be too many more 4 stable
I'm used to git repo surgery enough to make the branch - if nobody else
does it before I get out of work tonight, I'll do it then.
As Shane says it should be very easy though, assuming there's nothing
funny going on.
On Mon, Aug 22, 2016 at 10:26:46AM -0400, Shane Burrell wrote:
> It should be
Hi, Wayne!
On 2016-08-22 14:09, Wayne Stambaugh wrote:
> I wasn't planning on migrating the stable 4 branch to git. I'm hoping
> there wont be too many more 4 stable releases so I'm not sure it's worth
> the effort.
Ok, I was wondering...
I was missing the stable branch, too - as well as all
On Mon, Aug 22, 2016 at 09:57:26AM -0400, Wayne Stambaugh wrote:
> On 8/22/2016 9:53 AM, Clemens Koller wrote:
> > Hi, Wayne!
> >
> > On 2016-08-22 14:09, Wayne Stambaugh wrote:
> >> I wasn't planning on migrating the stable 4 branch to git. I'm hoping
> >> there wont be too many more 4 stable
What Chris said is exactly what I'd ask for!
Adam Wolf
On Mon, Aug 22, 2016 at 9:13 AM, Chris Pavlina
wrote:
> On Mon, Aug 22, 2016 at 09:57:26AM -0400, Wayne Stambaugh wrote:
> > On 8/22/2016 9:53 AM, Clemens Koller wrote:
> > > Hi, Wayne!
> > >
> > > On 2016-08-22
It should be really easy. Create a branch and overlay stable 4 branch via
manual or checkout the hash mark you need and commit to branch. I
typically do a develop branch (bleeding edge) and branch of stable without
any issues and created stable in same fashion the first time.
On Mon, Aug 22,
FYI the guy syncing bzr to the kicad-source-mirror managed to make it work.
Although it seems like he only pushed the 4.0 branch once. There is a 4.0
branch in that. (Sorry I don't remember his name exactly now)
Den 22/08/2016 16.34 skrev "Chris Pavlina" :
> I'm used to
But need to close posibilities to create ISSUE or PR.
В Понедельник, 22 авг. 2016 в 6:59 , Mark Roszko
написал:
The github mirror is useful to keep because its usually far faster
than launchpad and easier to deal with for personal development.
The benefit is that after
On Mon, Aug 22, 2016 at 01:06:37PM -0400, Wayne Stambaugh wrote:
> I fine with keeping the github mirror. Someone will have to change the
> url from the obsolete bzr repo to the new git repo.
Many many thanks to all of you.
I am not (really) a dev but I think that this transition and all other
I only need a snapshot of the current 4 stable branch r6308 tag 4.0.4.
I'm the only one with commit access so I can guarantee it wont change.
If you update your stable 4 branch, I'll pull this into my repo and then
push it to the kicad repo as the stable 4 branch and then make the bzr
stable 4
Looks good to me. Wayne, I'd probably just pull from this if I were you.
On Mon, Aug 22, 2016 at 11:26:31PM +0200, Niki Guldbrand wrote:
> Hi Wayne.
>
> I have pushed an updated 4.0.x branch to github, please have a look and
> see if you can use it as is, or ... ?
>
>
> On man, 2016-08-22 at
Mostly asking Mário here - couple slight issues/questions with the
raytracer..
https://misc.c4757p.com/raytrace-example.png
1) Am I the only one getting missing chunks in the corner like that?
That happens very often for me.
2) Any necessary reason why it's so grainy?
I fine with keeping the github mirror. Someone will have to change the
url from the obsolete bzr repo to the new git repo.
On 8/22/2016 11:59 AM, Mark Roszko wrote:
> The github mirror is useful to keep because its usually far faster
> than launchpad and easier to deal with for personal
And need update the Wiki
https://github.com/KiCad/kicad-source-mirror/wiki
В Понедельник, 22 авг. 2016 в 7:16 , Eldar Khayrullin
написал:
But need to close posibilities to create ISSUE or PR.
В Понедельник, 22 авг. 2016 в 6:59 , Mark Roszko
Hi Again.
Forgot to provide a link to a description of the model, so here it is:
http://nvie.com/posts/a-successful-git-branching-model/
On man, 2016-08-22 at 20:12 +0200, Niki Guldbrand wrote:
> Hi All.
>
> I Have a copy of 4.0.x in my git repo at github [1], although I
> havent
> updated it
Hi Wayne.
I have pushed an updated 4.0.x branch to github, please have a look and
see if you can use it as is, or ... ?
On man, 2016-08-22 at 16:39 -0400, Wayne Stambaugh wrote:
> I only need a snapshot of the current 4 stable branch r6308 tag
> 4.0.4.
> I'm the only one with commit access so I
27 matches
Mail list logo