Google Code

[Mestre Lion]

As google code is shutting down, do you guys have any suggestion on what to do?

I propose we a use Singularity github account I created a few years ago as the official repository : https://github.com/singularity

It contains 4 repositories, one for the game itself https://github.com/singularity/singularity and the others for its music.

Phil Bordelon, FunnyMan and myself are already registered as owners, and Uneron as a member with commit access. If anyone knows Evil Mr Henry github account (does he have any?) I'll gladly add him too.

The website would have to be updated to the new repository URL, as well as package metadata for the many linux distributions (Ubuntu, Debian, etc). I also suggest we migrate the currently open (and still valid) issues/bugs to github.

So what do you guys think? Suggestions, comments?
ML

[Mestre Lion]

About Google Code shutting down:

http://google-opensource.blogspot.com.br/2015/03/farewell-to-google-code.html

https://code.google.com/p/support/wiki/ReadOnlyTransition

[Jon Schlueter]

On Wed, Aug 26, 2015 at 5:50 AM, Mestre Lion <singu...@rodrigosilva.com> wrote:

As google code is shutting down, do you guys have any suggestion on what to do?

I propose we a use Singularity github account I created a few years ago as the official repository : https://github.com/singularity

Yes this sounds like a good idea!

 

It contains 4 repositories, one for the game itself https://github.com/singularity/singularity and the others for its music.

Phil Bordelon, FunnyMan and myself are already registered as owners, and Uneron as a member with commit access. If anyone knows Evil Mr Henry github account (does he have any?) I'll gladly add him too.

The website would have to be updated to the new repository URL, as well as package metadata for the many linux distributions (Ubuntu, Debian, etc). I also suggest we migrate the currently open (and still valid) issues/bugs to github.

Yep, if you need help migrating I'm interested.

Jon

[Evil Mr Henry]

Yeah, we should probably do something about that. I just registered as
evilmrhenry

I'm a bit busy right now, but let me know if you need me to push any
buttons.

> --
>
> ---
> You received this message because you are subscribed to the Google
> Groups "endgame-singularity-dev" group.
> To unsubscribe from this group and stop receiving emails from it, send
> an email to endgame-singulari...@googlegroups.com
> <mailto:endgame-singulari...@googlegroups.com>.
> For more options, visit https://groups.google.com/d/optout.

[Mestre Lion]

Great! I've added you as owner

I believe the github part is all set up, as I did it years ago. But it was mostly unused, so with the new official status perhaps suggestions and requests  of improvements will arise.

Only buttons to be pushed would be to update many URLs in http://www.emhsoft.com/singularity/ to point to the new repository.  Not only to the code but perhaps to the music packs too.

The hard part are the issues/bug tracker... in a perfect world, Google Code would allow the "Export to Github"  migration feature to export only the issues to an existing github repository (have anyone tested this with another google code repo?). Once in github, we could close the outdated issues. We could also add the bugs from Debian and Ubuntu, to keep all bugs in a single place.

[Evil Mr Henry]

Github stuff looks correct on my end.

I updated the dev links. The downloads look a bit tricky, though. It
appears to me that github doesn't really deal with binary releases all
that well. My first instinct is to just rehost the binaries on my site.
(It's not like they're that large.)

Thoughts?

[Jon Schlueter]

On Wed, Aug 26, 2015 at 8:52 PM, Evil Mr Henry <evilm...@emhsoft.com> wrote:

Github stuff looks correct on my end.

I updated the dev links. The downloads look a bit tricky, though. It appears to me that github doesn't really deal with binary releases all that well. My first instinct is to just rehost the binaries on my site. (It's not like they're that large.)

Thoughts?

 

Maybe host old downloads on your site and get latest tag in github soon to make it easier for packaging to pull from there

Jon

[Mestre Lion]

Github does not have a separate binary downloads section anymore, but we could do what I have done with E:S music: create repositories for them ;) and github does have a feature that automatically creates a .zip (or .tar.gz) archive out of a git repository tagged commits with release versions.

I've just created an empty repository for that: https://github.com/singularity/singularity-windows

As for commit workflow, a basic idea is:

- Each commit is a release version, tagged so Github picks it for download. Delete (or overwrite) the previous binaries on each release, so that at any given time the repository would only contain files from the current version.

- Optionally, create an `{old|all|previous}_{releases|versions}` directory in another branch (`releases` ?), and move old releases there once a new version is released. It's very important that `master` branch does *not* contain anything but the current release.

- The idea is that Downloads pick only the current version, while a repository clone would have them all.

I'll try to set this up over the weekend... send suggestions and comments on details to improve this workflow. Also, send me the links for the binaries, all versions if possible (website, dropbox?)

PS: regardless of github, having the binaries also at the website is a good idea

[evilm...@emhsoft.com]

I'll let you manage that. The old downloads should all be linked from the
main Endgame page on my site. (Personally, I'd be fine with just moving
over the source versions, and only retaining Win/Mac binaries for the last
few releases.)

> --
>
>
> ---
> You received this message because you are subscribed to the Google Groups
> "endgame-singularity-dev" group.
> To unsubscribe from this group and stop receiving emails from it, send an

> email to endgame-singulari...@googlegroups.com. For more
> options, visit https://groups.google.com/d/optout.
>

[Mestre Lion]

By the way, can we have detailed instructions on how to build a windows binary? It could be in the README.txt, or in a separate file (build.txt? install.txt?). That way anyone cloning the repository would have instructions on how to build and install the game from source in each platform. We could even automate the process of creating the `.exe`

[Evil Mr Henry]

I thought we had that already?

I don't see it in the repo.

After looking around, I found it here: (last comment)
https://code.google.com/p/endgame-singularity/issues/detail?id=19&can=1&q=release

Weirdly, I don't see that file in the repo, and the log doesn't have any
commits that delete the file. So, that's weird. I guess put the file
back? It's rather important.

> --
>
> ---
> You received this message because you are subscribed to the Google
> Groups "endgame-singularity-dev" group.
> To unsubscribe from this group and stop receiving emails from it, send
> an email to endgame-singulari...@googlegroups.com

> <mailto:endgame-singulari...@googlegroups.com>.

[Evil Mr Henry]

By the way, all Singularity links and downloads on the main site should
now be correct, and pointing towards local files.