Personally, if the author/maintainer of any library claims it is maintained/up-to-date, I say trust them. Most people are pretty honest about the status of their projects. But it does require a positive response to really make this claim.<br>
<br><div class="gmail_quote">On Sat, Nov 28, 2009 at 12:03 PM, Aaron Watters <span dir="ltr"><<a href="mailto:arw1961@yahoo.com">arw1961@yahoo.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class="im"><br>
><br>
> On Thu, Nov 26, 2009 at 1:02 PM, Chris McDonough <<a href="mailto:chrism@plope.com">chrism@plope.com</a>><br>
> wrote:<br>
> > <a href="http://wiki.python.org/moin/WebFrameworks" target="_blank">http://wiki.python.org/moin/WebFrameworks</a><br>
> seems to be the place where folks<br>
> > are registering their respective web frameworks.<br>
> ><br>
> > I'd like to move some of the frameworks which are<br>
> currently in the various<br>
> > categories which haven't been active in a few years.<br>
> In particular, I'd<br>
> > like to move any framework which hasn't had a release<br>
> since the beginning of<br>
> > 2008 (arbitrary) into the "Discontinued / Inactive"<br>
> framework category. I'd<br>
> > be willing to do the work to make sure I wasn't moving<br>
> one that actually<br>
> > *did* have releases past that but just hadn't updated<br>
> the page.<br>
> ><br>
> > Any dissent?<br>
> ><br>
> > - C<br>
<br>
</div>Why not call them "apparently stable"<br>
versus "under active development"? Is the<br>
cgi module "discontinued"?<br>
<br>
I'm a little sensitive on this topic<br>
because people tell me that Gadfly is "inactive"<br>
or "discontinued"<br>
but it still does what it does<br>
as documented very well.<br>
<br>
Frequent releases may actually be a sign of<br>
bugginess and bad design.<br>
If you suspect a project is really dead, maybe you<br>
could try to contact the authors and ask about<br>
what they think.<br>
<br>
-- Aaron Watters<br>
<br>
===<br>
BTW, I think "Release early, release often" is nonsense<br>
because it means you are probably releasing<br>
something buggy and unstable which will just alienate<br>
your users, who will never come back to see the better<br>
version.<br>
<div><div></div><div class="h5"><br>
_______________________________________________<br>
Web-SIG mailing list<br>
<a href="mailto:Web-SIG@python.org">Web-SIG@python.org</a><br>
Web SIG: <a href="http://www.python.org/sigs/web-sig" target="_blank">http://www.python.org/sigs/web-sig</a><br>
Unsubscribe: <a href="http://mail.python.org/mailman/options/web-sig/ianb%40colorstudy.com" target="_blank">http://mail.python.org/mailman/options/web-sig/ianb%40colorstudy.com</a><br>
</div></div></blockquote></div><br><br clear="all"><br>-- <br>Ian Bicking | <a href="http://blog.ianbicking.org">http://blog.ianbicking.org</a> | <a href="http://topplabs.org/civichacker">http://topplabs.org/civichacker</a><br>