[Mono-dev] github workflow proposals

Rodrigo Kumpera kumpera at gmail.com
Tue Jul 27 17:42:14 EDT 2010

On Tue, Jul 27, 2010 at 6:22 PM, Geoff Norton <gnorton at novell.com> wrote:

> Github takes the first line from the commit message to build this page:
> http://github.com/mono/mono/commits/master
> I think we should modify our current commit messages to not just be the
> change log entries, but have a 1 line summary of the patch first like this:
> http://github.com/mono/mono/commit/5ab946450584e127878d7abbedeeca2688ef032f

I like this change, otherwise github's build page is pretty unusable.

> Additionally,  I think we should implement a policy that all "work
> branches" are made in user forks; and the only people who should be making
> branches in the mainline github are QA for release managment practices.
> thoughts?
It doesn't make any sense to have work/feature branches on the central
repository given we're using git. It's much easier and cleaner to simply
have them on personal forks. One might not like dealing with extra remotes,
but that would be a burnen only to mantainers  merging code from

I have another proposition to make. Can we stop using Changelog files? Those
can be generated from the commit logs for tarballs and releases without
losing anything at all. Commit messages would still have to be at least as
informative as they currently are.

Not having Changelog files resolve 90%+ of our sources of conflicts and make
the forkqueue much more useful. If we are to move to a DVCS style of
development, this will be a big barrier otherwise.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.ximian.com/pipermail/mono-devel-list/attachments/20100727/d9fe8aad/attachment.html 

More information about the Mono-devel-list mailing list