Resending to the list, sorry Brent for the duplicate.<br><br><div class="gmail_quote">---------- Forwarded message ----------<br>From: <b class="gmail_sendername">Braden Shepherdson</b> <span dir="ltr"><<a href="mailto:braden.shepherdson@gmail.com">braden.shepherdson@gmail.com</a>></span><br>
Date: Thu, Jul 30, 2009 at 5:44 PM<br>Subject: Re: [xmonad] Unmarking modules 'Unstable' in contrib<br>To: Brent Yorgey <<a href="mailto:byorgey@seas.upenn.edu">byorgey@seas.upenn.edu</a>><br><br><br>Even when our modules do change, they almost always change in a backward-compatible way, since we try to avoid breaking configs.<br>
<br>This sounds fine to me.<br><font color="#888888"><br>Braden Shepherdson<br>shepheb</font><div><div></div><div class="h5"><br><br><div class="gmail_quote">
On Thu, Jul 30, 2009 at 5:12 PM, Brent Yorgey <span dir="ltr"><<a href="mailto:byorgey@seas.upenn.edu" target="_blank">byorgey@seas.upenn.edu</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div>On Wed, Jul 29, 2009 at 08:10:52PM -0400, Adam Vogt wrote:<br>
> Hello,<br>
><br>
> Most (152/159) modules are marked as unstable in contrib. A good number of<br>
> these 'unstable' modules have not been modified since a number of releases.<br>
><br>
> Here's a rough total number of modules with a last-modified date (per year):<br>
><br>
> > (for x in `find .`; do; (darcs changes $x | tail -n 2 | head -n 1); done) > lastmod<br>
> > for x in {2007,2008,2009}; do; grep $x lastmod | wc -l; done<br>
> 64<br>
> 43<br>
> 17<br>
><br>
> I wouldn't trust those numbers, since the total falls short of 159, but the<br>
> point still stands: many so-called unstable modules have not changed in a<br>
> long time, which could make it difficult for users to avoid modules that<br>
> may actually change.<br>
><br>
> Does anybody mind if I change the oldest modules (unchanged since 1.5<br>
> years) to be stable?<br>
<br>
</div>Sounds good to me. I think most of the 'unstable' designations are<br>
because of cargo-culting someone else's module comments. That and the<br>
fact that by definition you would only change the stability<br>
designation when you are not changing anything. No one ever thinks<br>
"gee, it's been 6 months since I even thought about that module,<br>
better go back and change it to 'stable'". =)<br>
<font color="#888888"><br>
-Brent<br>
</font><div><div></div><div>_______________________________________________<br>
xmonad mailing list<br>
<a href="mailto:xmonad@haskell.org" target="_blank">xmonad@haskell.org</a><br>
<a href="http://www.haskell.org/mailman/listinfo/xmonad" target="_blank">http://www.haskell.org/mailman/listinfo/xmonad</a><br>
</div></div></blockquote></div><br>
</div></div></div><br>