Re: Question about procedures

"Tim McLaughlin" <[email protected]>
Newsgroups gmane.comp.web.zope.coders
Message-ID <[email protected]>
What should we do if no discussion ensues on zope-dev?  Go ahead and
make the commit to the trunk if it's backwards compatible?

Thanks,
Tim

martin f krafft wrote:
| Dear coders,
|
| I am new; I just got my account today and am thus a little shakey wrt 
| policies and such. Thus, let me ask you with respect to a specific 
| example whether I can just commit to the trunk like that:
|
| The following patch is a follow-up to the one I submitted to the 
| collector yesterday (331). Am I allowed to commit patches of this 
| nature "just like that" (given proper testing and the like), or should

| these be discussed up front and/or committed to my own branch instead?

Depends.  If you are fixing an obvious typo, then go ahead and commit,
after ensuring that all tests pass.  If you are changing behavior in a
non-backwards-compatible way (which the first part of your patch does),
then you likely need either a collector issue (to document the
rationale), or some discussion / consensus on the list, which might then
result in a collector issue.	

--
Tim McLaughlin 
Chief Technology Officer 
Siteworx, Inc. Innovative internet solutions. 
703.964.0300 ext. 208
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.