Re: Build/release query (was Communication)



> Delivered-To: gnome-doc-list gnome org
> Subject: Re: Build/release query (was Communication)
> To: Gnome Doc list <gnome-doc-list gnome org>
> Content-Transfer-Encoding: 7bit
> Mime-Version: 1.0
> X-BeenThere: gnome-doc-list gnome org
> X-Loop: gnome-doc-list gnome org
> X-Mailman-Version: 2.0.12
> List-Help: <mailto:gnome-doc-list-request gnome org?subject=help>
> List-Post: <mailto:gnome-doc-list gnome org>
> List-Subscribe: <http://mail.gnome.org/mailman/listinfo/gnome-doc-list>, 
<mailto:gnome-doc-list-request gnome org?subject=subscribe>
> List-Id: GNOME documentation issues <gnome-doc-list.gnome.org>
> List-Unsubscribe: <http://mail.gnome.org/mailman/listinfo/gnome-doc-list>, 
<mailto:gnome-doc-list-request gnome org?subject=unsubscribe>
> List-Archive: <http://mail.gnome.org/archives/gnome-doc-list/>
> 
> On Tue, 2002-09-24 at 04:17, Pat Costello wrote:
> > So, does everyone make a public announcement every time you do a putback, 
just 
> > in case there is a knock-on effect on some other item in the same module? 
> > Clearly, not. Therefore, the incident with the user guide putback was not a 
> > communication issue, rather a generic process issue. 
> > 
> 
> The communication issue is in not letting the maintainer know when
> committing changes that would break the building of the module.
> 
> Chris

Right. Well, Sun Microsystems is logged in the Doctable as the maintainer for 
the User Guide. Is there a misunderstanding between "Documentation Maintainer" 
and "Module Maintainer"? 

Pat




[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]