erma-core team mailing list archive

["Ray Krueger" <raykrueger@xxxxxxxxx>]

> So if Launchpad is prescriptive, Github would be the opposite. It supports
> Git tags and branches, but it is up to you to create a sensible release
> process with those tools. We would need to figure out where to host the
> binary files. Github's integrated wiki is one option.
>
> In either case, your best bet is probably to script the release process,
> perhaps as an Ant task. I couldn't say for certain, but I'd imagine that
> that script may be easier to write against Github, since all of its views of
> the codebase are driven from the repository itself. So, it would essentially
> just be a series of local Git commands followed by a push to the server.

Yeah, GitHub is really good source control point, but it isn't really
a "project hosting" site. For the hibernate-memcached project I host
the info and binaries at googlecode, but the source is on github.
I'd really love to get back to work on Mavenizing Erma. Maybe then we
just rely on the maven repository for binary hosting, and we can
maintain the site through the github wiki.