kicad-developers team mailing list archive

[Adam Wolf <adamwolf@xxxxxxxxxxxxxxxxxxxx>]

Hi folks,

I know how much of a pain it was to migrate our bugs last time.  There is
actually a lot of valuable information in our tracker, and I definitely
agree with Wayne that it all needs to be migrated.

For the past few months, I have been tinkering in private with a script to
copy over our bugs to Github issues.

In private, because every time we mention git on the mailing list we do
nothing else for the next 3 days :)

After the post 4.0.0 relaxation break :), I will post what I have and see
if anyone wants to take it further, or if I should keep tinkering with it.

If you want to volunteer to help, have no illusions that a Git migration
will happen the moment you are done, but it will help!

I do, however, believe KiCad would benefit from a tighter Git integration
for footprints and modules, rather than the current Github integration, but
I also suspect this is a lot of work.  I know at least 4 people on the list
are interested in this, and we have all mostly postponed mapping this
potential feature set out until after 4.0.0.  If this is something people
want to discuss, it should be a different thread for sure.

Adam Wolf
Cofounder and Engineer
W&L

On Sat, Dec 5, 2015, 10:55 AM Wayne Stambaugh <stambaughw@xxxxxxxxx> wrote:

> Here are my thoughts on this.  Lauchpad already has experimental support
> for git (although I haven't tested it yet), which would be an easier
> path to git without losing our bug history.  I don't know what the
> Launchpad devs git migration plans are so this could be an issues.  If
> someone can write a macro to convert our bug tracker history to github,
> I would be much more amicable to switching over to github.  In any
> event, I'm in no hurry to make the change and will not make that call
> until I'm sure we have all of our bases covered.
>
> On 12/5/2015 2:44 AM, Cirilo Bernardo wrote:
> >
> >
> > On Sat, Dec 5, 2015 at 6:31 PM, Eldar Khayrullin
> > <eldar.khayrullin@xxxxxxx <mailto:eldar.khayrullin@xxxxxxx>> wrote:
> >
> >     Hello. What about a full migration Kicad prj management to Github:
> >     -bug tracker
> >     -pull request
> >     -and other tasty things.
> >
> >     And then maybe will use git `submodules` for third-party libs
> >     instead store srcs of libs in kicad src.
> >
> >
> > (a) I've used git submodules and I agree with other experienced coders
> > that it's not as useful
> > as you might imagine. (b) Some Launchpad maintainers were working on
> > tools to migrate
> > all lp-bzr projects to lp-git, but I haven't heard anything since their
> > announcement earlier in
> > the year. From my point of view migration to github wouldn't be bad as
> > long as we maintain
> > all the history and bug reports and of course that someone else does the
> > migration and
> > checking. :)  bzr is one tool which I won't miss when it's gone.
> >
> > - Cirilo
> >
> >
> >     _______________________________________________
> >     Mailing list: https://launchpad.net/~kicad-developers
> >     Post to     : kicad-developers@xxxxxxxxxxxxxxxxxxx
> >     <mailto:kicad-developers@xxxxxxxxxxxxxxxxxxx>
> >     Unsubscribe : https://launchpad.net/~kicad-developers
> >     More help   : https://help.launchpad.net/ListHelp
> >
> >
> >
> >
> > _______________________________________________
> > 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
> >
>
>
> _______________________________________________
> 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
>