news.html 2.0 KB

12345678910111213141516171819202122232425262728293031323334353637383940414243444546474849505152535455565758596061
  1. <!--#include file="header.html" -->
  2. <ul>
  3. <li> <b>17 August 2005, uClibc 0.9.28 Released</b>
  4. <br>
  5. CodePoet Consulting is pleased to announce the release of uClibc 0.9.28.
  6. You are probably used to this by now, but this release is NOT binary
  7. compatible with uClibc 0.9.27 or any earlier release, so be prepared to
  8. recompile your software if you are still using an old version of uClibc.
  9. <p>
  10. Updated uClibc development systems built using uClibc 0.9.28, along
  11. with the <a href="http://buildroot.uclibc.org/">uClibc buildroot</a>
  12. and source code used to compile these development systems will be released
  13. later this evening, along with
  14. <a href="http://ltp.sourceforge.net/">Linux Test Project test suite</a>
  15. results demonstrating how uClibc is doing. Contributions of LTP test
  16. suite run results using uClibc are welcome...
  17. <p>
  18. As usual the
  19. <a href="http://www.uclibc.org/downloads/uClibc-0.9.28.tar.bz2">source code for this release</a>
  20. is available <a href="http://www.uclibc.org/downloads/">here</a>.
  21. <p>
  22. <li><b>13 January 2005 -- Bug and Patch Tracking</b><p>
  23. Bug reports sometimes get lost when posted to the mailing list. The
  24. developers of uClibc are busy people, and have only so much they can keep
  25. in their brains at a time. In my case, I'm lucky if I can remember my own
  26. name, much less a bug report posted last week... To prevent your bug report
  27. from getting lost, if you find a bug in uClibc, please use the
  28. <a href="http://bugs.uclibc.org/">shiny new Bug and Patch Tracking System</a>
  29. to post all the gory details.
  30. <p>
  31. The same applies to patches... Regardless of whether your patch
  32. is a bug fix or adds spiffy new features, please post your patch
  33. to the Bug and Patch Tracking System to make certain it is
  34. properly considered.
  35. <p> <li> <b>Old News</b>
  36. <br>
  37. <a href="/oldnews.html">Click here to read older news</a>
  38. <p>
  39. </ul>
  40. <!--#include file="footer.html" -->