Mailing-List: contact dev-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@lucene.apache.org
Received-SPF: neutral (nike.apache.org: local policy)
Received-SPF: pass (google.com: domain of hossman_lucene@fucit.org designates
 10.68.211.202 as permitted sender) client-ip=10.68.211.202;
Date: Tue, 21 Feb 2012 10:00:14 -0800 (PST)
From: Chris Hostetter <hossman_lucene@fucit.org>
To: dev@lucene.apache.org
Subject: Re: CMS peer review process
In-Reply-To: <1329381091277-3749488.post@n3.nabble.com>
Message-ID: <alpine.DEB.2.00.1202210956190.25491@bester>
References: <1329381091277-3749488.post@n3.nabble.com>
User-Agent: Alpine 2.00 (DEB 1167 2008-08-23)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII


: What shall be the procedure of peer review of CMS website changes? Is it
: examine patches in JIRA just like source code is, or is it to commit changes
: and observe them on the staging server http://lucene.staging.apache.org/ ? 
: (or perhaps it depends)

"it depends"

the biggest value of hte CMS is making small rapid changes -- just like 
small bug fixes, you shouldn't need peer review to make small tweaks, if 
people don't like it they can revert.

If you are making seriously large substantial changes (ie: "i think we 
should completley re-org the site like this...") then i think patches in 
Jira make sense 

...both of thse situations are just like they use to be in the forrest 
days from a review process.

the new middle ground we have is the "staging site" ... if you have a 
change that you think is simple and not relaly worth a prolonged 
discussion over a patch, but you'd still like to have at least one other 
set of eyeballs on, edit it and push it to staging -- then ask for review 
on email/irc.  worst case scenerio someone else comes along to make a 
minor edit and sees your changes on staging ... which is an automatic 
review if they then choose to "publish" both their changes and yours.


-Hoss

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org