On 13 June 2012 09:14, Steve <[email protected]> wrote:
> Also, it's kind of hard (or unclear how) to fork the project and submit
> patches. While the web site is being updated, updates to the Contribute page
> would be nice. (Or a move off of Google Code for the canonical repo.)
At the moment there is no formal process. You create an issue and
provide the patch / fork details there.
Google Code doesn't support automated pull requests like
bitbucket/github. I think that's a big failing and a reasonable
motivation to move to bitbucket, but that's probably just a
distraction from doing more productive things. It might also make the
website maintenance simpler too - at the moment I'm the only (active)
person with access to update the website. If it was hosted via
bitbucket with post-commit hooks then things would be simpler. Also,
we need to fix or replace epydoc as I cannot make it work - which is
why the website hasn't been updated in quite some time. I am still
trying but I suspect I'll be tossing it out and using Sphinx soon.
I believe the biggest hurdle in getting a 1.2 release out is that the
cocoa port needs to be merged into the default branch. Once that's
done I'd be happy to push out a source 1.2 release.
Richard
--
You received this message because you are subscribed to the Google Groups
"pyglet-users" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/pyglet-users?hl=en.
