[os-infrastructure] State of the onion
David Tondreau
david.tondreau at ingres.com
Fri Jun 6 12:06:15 PDT 2008
Joe,
If you read all three paragraphs I put in the e-mail from the Mozilla
site, you will find that the last paragraph speaks specifically to
source code. The process it articulates is identical to the process
that is on the page you referred me to. Even that page says:
"When you have a patch, submit it to Bugzilla
<http://bugzilla.mozilla.org> as an attachment to that bug. We're
big believers in code review, so before code is checked in to the
CVS Repository it must be reviewed by the appropriate module owner
<http://www.mozilla.org/owners.html> or one of his peers."
David
On 06/06/2008 02:40 PM, Joe Abbate wrote:
> Hi David,
>
> David Tondreau wrote:
>> *Mozilla*
>>
>> Publicly accessible /read/only/ repository via CVS. Internally, they
>> decided in late 2007 to use Mercurial. Encourages download of source
>> code via tarball. From the Mozilla web site, here is the Mozilla
>> process for externally submitting a bug (read this entire thing):
>>
>> "CVS is used to manage the documents on our web site. To submit
>> changes to a current document you can either use CVS to check out
>> the document <http://www.mozilla.org/contribute/writing/cvs#access>
>> and create a patch with cvs diff -u or you can click the "Edit this
>> page" link at the bottom of the document you are changing to make a
>> patch with Doctor.
>
> I think you're looking at the wrong place for Mozilla, see
> http://www.mozilla.org/hacking/life-cycle.html. The above refers to
> the maintenance of website documents for mozilla.org.
>
> Joe
> _______________________________________________
> opensource-infrastructure mailing list
> opensource-infrastructure at lists.ingres.com
> http://lists.ingres.com/mailman/listinfo/opensource-infrastructure
>
More information about the opensource-infrastructure
mailing list