[Bf-committers] [Bf-blender-cvs] SVN commit: /data/svn/bf-blender [14779] trunk/blender/release/scripts/ vrml97_export.py: Reverting vrml97_export.py to it' s state at revision 14751 because:

Martin Poirier theeth at yahoo.com
Sun May 11 04:55:43 CEST 2008


--- On Sat, 5/10/08, Joe Eagar <joeedh at gmail.com> wrote:

> From: Joe Eagar <joeedh at gmail.com>
> Subject: Re: [Bf-committers] [Bf-blender-cvs] SVN commit: /data/svn/bf-blender [14779] trunk/blender/release/scripts/ vrml97_export.py: Reverting vrml97_export.py to it' s state at revision 14751 because:
> To: "bf-blender developers" <bf-committers at blender.org>
> Date: Saturday, May 10, 2008, 10:45 PM
> Martin Poirier wrote:
> >
> > --- On Sat, 5/10/08, Campbell Barton
> <ideasman42 at gmail.com> wrote:
> >
> >   
> >> A good compromise would be to only apply fixes
> from the
> >> previous commits.
> >>     
> >
> > No compromise needed: Don't bypass maintainers.
> >
> > Maintainers and module owners are there for a reason.
> > Especially this close to release.
> >   
> I don't know. . .I think we need a time limit on
> maintainance stuff (I'm 
> not saying it would apply in this case, I have no idea. 
> but certainly 
> we have cases of people being "maintainers" but
> not actually being 
> active for years in areas of the code they maintain).

For inactive maintainers, sure, if they don't reply to queries.

But this isn't here nor there in this case.

Martin


      ____________________________________________________________________________________
Be a better friend, newshound, and 
know-it-all with Yahoo! Mobile.  Try it now.  http://mobile.yahoo.com/;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ


More information about the Bf-committers mailing list