How to make the Package index more useful

At 06:10 PM 10/2/2007 -0700, Vern Muhr wrote:
>Content-class: urn:content-classes:message
>Content-Type: multipart/alternative;
>        
boundary="----_=_NextPart_001_01C8055A.3AF0387D"
>
>Greetings,
>
>I check the package index almost every day. More and
more it seems 
>to be filled with every single change that occurs to a
few code 
>basees (Zope, Plone, etc) no matter how trivial. I don't
understand 
>why these development teams don't have their own SIG to
post this 
>stuff to. It does makes sense to post major new releases
to the 
>Package Index. Often now, it seems that these minor
package changes 
>bump other packages off the bottom of the visible list,
or at least 
>make it a task to find anything of interest.

May I suggest using an RSS reader, such as Bloglines or
Google 
Reader?  These services will show you a complete history of
changes, 
without any ability for you to "miss" anything.

_______________________________________________
Catalog-SIG mailing list
Catalog-SIGpython.org
h
ttp://mail.python.org/mailman/listinfo/catalog-sig