I'll start migrating the bugs/issues now.

I am planning to migrate the code/branches next weekend. This will take a long time, so make sure that you have pushed all your changes by Friday morning and then wait until I announce the completion of the move.

If you have branches that you are no longer working on, you can mark them as "Abandoned" to make it go a bit faster.

ETA: We also need to update the changelog before the move. Merge request is up.

Tracking branches

Busy indexing nil values

Top

Quote

I have created a project on GitHub for our migration project:

https://github.com/widelands/widelands/projects/1

Tasks that are sorted above "Migrate branches" can be started.

Busy indexing nil values

Top

Quote

We should not update that before the branches have moved, becaue people might end up with unmergeable branches on GitHub - I don't know if the import script would keep the git hashes stable. If people accidentally create a few new issues on Launchpad this week, they can always be copied over manually.

Busy indexing nil values

Top

Quote

https://www.widelands.org/wiki/GitPrimer/

You can still work on your own fork if you are more comfortable with that.

Busy indexing nil values

Top

Quote

Hmm, I rather prefer ssh over https for github, both should do but ssh will ot require username/password ... I will try this for a while.

And maybe we shoud start local branches and push them to github only when we are happy locally?

Here are the widelands where people may dwell, walking around care that evrythings well.

Top

Quote