Migration to github
Locked
 
|
I started the export process from google code to github.
Will keep you all posted. Johan _______________________________________________ seaside-dev mailing list [hidden email] http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev |
|
|
First step (the easy one): https://github.com/SeasideSt/googlecode-seaside-export
_______________________________________________ seaside-dev mailing list [hidden email] http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev |
|
|
On Wed, Mar 25, 2015 at 4:23 PM, Johan Brichau <[hidden email]> wrote:
> First step (the easy one): > https://github.com/SeasideSt/googlecode-seaside-export - I can't find the wiki - milestones don't map to GitHub milestones - we have both labes "Bite-Size" and "BiteSize" - there is no mapping from GoogleCode to GitHub users Cheers Philippe _______________________________________________ seaside-dev mailing list [hidden email] http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev |
|
|
As I said, step 1 was easy… the real work only starts now.
- I can't find the wiki this one is in the wiki branch, I found instructions for moving them to github wiki [1]
that’s sad indeed :(
that’s some info we loose, indeed, but were you really expecting that? The export is just about not loosing the info. imho, this is also the time to sort out the issues we still want to keep tracking _______________________________________________ seaside-dev mailing list [hidden email] http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev |
|
|
btw…
says it is a java repository just pointing it ;) Esteban
_______________________________________________ seaside-dev mailing list [hidden email] http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev |
|
|
that’s because it is a java repository (really, take a look what was in the svn repo on google code…)
The *real* Seaside github project does not, obviously. Anyway, this is just to recover the issues and the wiki. I will actually move them to the real Seaside repo and delete this guy.
_______________________________________________ seaside-dev mailing list [hidden email] http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev |
|
|
In reply to this post by Johan Brichau-2
The (bare-bones) export of the wiki got added to the Seaside project: Tobias gave me a link to a project that can move the issues, so I will probably do that next. Johan _______________________________________________ seaside-dev mailing list [hidden email] http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev |
|
|
In reply to this post by Johan Brichau-2
On Thu, Mar 26, 2015 at 11:05 AM, Johan Brichau <[hidden email]> wrote:
> As I said, step 1 was easy… the real work only starts now. > > - I can't find the wiki > > this one is in the wiki branch, I found instructions for moving them to > github wiki [1] So can we export again? > - there is no mapping from GoogleCode to GitHub users > > that’s some info we loose, indeed, but were you really expecting that? Uhm, Google? I mean not automatically but at least have to option to provide a file that does the mapping. > The export is just about not loosing the info. > imho, this is also the time to sort out the issues we still want to keep > tracking Sure. Cheers Philippe _______________________________________________ seaside-dev mailing list [hidden email] http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev |
|
|
In reply to this post by Johan Brichau-2
On Thu, Mar 26, 2015 at 6:09 PM, Johan Brichau <[hidden email]> wrote:
> > On 26 Mar 2015, at 11:05, Johan Brichau <[hidden email]> wrote: > > - I can't find the wiki > > this one is in the wiki branch, I found instructions for moving them to > github wiki [1] > > > The (bare-bones) export of the wiki got added to the Seaside project: > https://github.com/SeasideSt/Seaside/wiki That looks OK. We had no structure on Google Code so we can't really expect much. What's not optimal is that the links on the release pages go to the google code issue tracker. But since it's all .md files now we should be able to fix this with a script. Cheers Philippe _______________________________________________ seaside-dev mailing list [hidden email] http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev |
|
|
The wiki pages are indeed fine.
Moving the issues from the export project to the Seaside project proves to be a whole different story. At the very least, we have to accept that the issue export is just to preserve the issue in *some* state (i.e. not being cleanly mapped to github labels, milestones, users, etc.). I think it’s OK, given that the essential info is preserved and that I do not have time to try implementing a better mapping. But I want to get rid of the export project and move the issues to SeasideSt/Seaside. I can move issue by issue using [1], which seems relatively OK except that there is no batch move feature (yet). I moved 1 closed issue to see how the result looks like. I tried using another script [2], but that moves closed issues back to the open state, which is a no-go for me. It actually did not work either when I tried it. I also looked at the github API to implement something myself, but that will require more time. Maybe I will leave the issues in the export project for now and wait for a better solution. Johan
_______________________________________________ seaside-dev mailing list [hidden email] http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev |
|
|
In finally did it the other way around: I renamed the existing Seaside project on github to Seaside-old and renamed the google-code-export project to become the Seaside project.
In that way, the issues list remains as it was exported from Google code. I also made a Grease project on github. All is on I also edited those parts of the website necessary to redirect people to the github issue tracker. What remains to be done: - adapt the ‘make a release’ instructions - cleanup the wiki Mind that the github projects are mirroring the code from the smalltalkhub repositories only (for now).
_______________________________________________ seaside-dev mailing list [hidden email] http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev |
«
Return to Seaside Development
|
1 view|%1 views
| Free forum by Nabble | Edit this page |