RE: Process for integrating outside patches into ilisp

Dan,

Thanks for the suggestion and the offer to use Cliki to keep track of
outstanding patches. However, Sourceforge already has a built-in
mechanism for recording Bugs, Support Requests, Patches and Feature
Requests and it would probably make more sense to utilize the
Sourceforge pages to keep track of fixes and enhancement requests. This
isn't being done (at least not consistently). Maybe that's ok since
ilisp is pretty stable; however, as you note in your message, it would
be easier to keep track of issues/patches/requests if they were recorded
in a more rigorous manner. (Note: this is not meant to criticize anyone,
especially not Paolo since I think he does a terrific job.) I think we
need to think about when and how entering additional information into
the standard Sourceforge tracking system makes sense and when it just
represents "busy work" for people.

--
Bill Clementson

> -----Original Message-----
> From: Daniel Barlow [mailto:[email protected]] 
> Sent: Monday, June 30, 2003 10:50 AM
> To: [email protected]
> Subject: Re: [Ilisp-devel] Process for integrating outside 
> patches into ilisp
> 
> 
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> Paolo Amoroso <[email protected]> writes:
> 
> > The current process for ILISP is an informal one. Patches 
> are mostly 
> > sent to one of our mailing lists, and they are dealt with 
> by whoever, 
> > among the maintainers, has some time to do it.
> 
> If you think it would help in any way to use the CLiki ilisp 
> page to keep a list of pointers to outstanding patches, 
> please feel free.  It might be easier to keep a list of 
> pointers into the mailing list archives there than it would 
> be to browse through geocrawler or gmane every time.
> 
> - -dan


-------------------------------------------------------
This SF.Net email sponsored by: Free pre-built ASP.NET sites including
Data Reports, E-commerce, Portals, and Forums are available now.
Download today and enter to win an XBOX or Visual Studio .NET.
http://aspnet.click-url.com/go/psa00100006ave/direct;at.asp_061203_01/01