news.html 4.0 KB

12345678910111213141516171819202122232425262728293031323334353637383940414243444546474849505152535455565758596061626364656667686970717273747576777879808182838485868788899091
  1. <!--#include file="header.html" -->
  2. <ul>
  3. <li><b>12 February 2009 -- 2009.02 released</b>
  4. <p>The stable 2009.02 release is out - Thanks to everyone
  5. contributing and testing the release candidates. See the
  6. <a href="http://lists.busybox.net/pipermail/buildroot/2009-February/025974.html">announcement</a>
  7. for more details, and go to the <a href="/downloads/">downloads page</a>
  8. to pick up the <a href="/downloads/buildroot-2009.02.tar.bz2">2009.02
  9. release</a>.</p>
  10. <li><b>9 February 2009 -- 2009.02-rc4 released</b>
  11. <p>We had more than 50 changes since RC3, several of them
  12. toolchain related, so decided to make a RC4 as well. This is
  13. very much expected to be the final release candidate, so give it
  14. a good test and expect a final 2009.02 release this week unless
  15. critical issues are found.</p>
  16. <p>Head to the <a href="/downloads/">downloads page</a> to pick up the
  17. <a href="/downloads/buildroot-2009.02-rc4.tar.bz2">2009.02-rc4
  18. release candidate</a>, and report any problems found to the <a
  19. href="lists.html">mailing list</a> or <a
  20. href="http://bugs.uclibc.org">bug tracker</a>.</p>
  21. <li><b>31 January 2009 -- 2009.02-rc3 released</b>
  22. <p>RC3 is out with more cleanups and bug fixes. Unless big issues
  23. are found, expect this to be the last release candidate before the
  24. release - So give it a good test.</p>
  25. <p>Head to the <a href="/downloads/">downloads page</a> to pick up the
  26. <a href="/downloads/buildroot-2009.02-rc3.tar.bz2">2009.02-rc3
  27. release candidate</a>, and report any problems found to the <a
  28. href="lists.html">mailing list</a> or <a
  29. href="http://bugs.uclibc.org">bug tracker</a>.</p>
  30. <li><b>23 January 2009 -- 2009.02-rc2 released</b>
  31. <p>Another week, another release candidate with a bunch of
  32. cleanups and build fixes.</p>
  33. <p>Head to the <a href="/downloads/">downloads page</a> to pick up the
  34. <a href="/downloads/buildroot-2009.02-rc2.tar.bz2">2009.02-rc2
  35. release candidate</a>, and report any problems found to the <a
  36. href="lists.html">mailing list</a> or <a
  37. href="http://bugs.uclibc.org">bug tracker</a>.</p>
  38. <li><b>16 January 2009 -- Release candidate and new maintainer</b>
  39. <p>It has been a long time coming, but we finally have a new
  40. release candidate! - And a new maintainer to match (Peter Korsgaard).</p>
  41. <p>Head to the <a href="/downloads/">downloads page</a> to pick up the
  42. <a href="/downloads/buildroot-2009.02-rc1.tar.bz2">2009.02-rc1
  43. release candidate</a>, and report any problems found to the <a
  44. href="lists.html">mailing list</a> or <a
  45. href="http://bugs.uclibc.org">bug tracker</a>. The plan is to
  46. release 2009.02 in time for <a
  47. href="http://www.fosdem.org/2009/">FOSDEM</a>.</p>
  48. <li><b>16 July 2006 -- Buildroot mailing list</b>
  49. <p>Buildroot now has its own <a href=lists.html>mailing list</a>.</p>
  50. <li><b>21 February 2005 -- Buildroot webpage added</b><p>
  51. Buildroot is a set of Makefiles and patches that makes it easy generate a
  52. cross-compilation toolchain and root filesystem for your target Linux
  53. system using the <a href= "http://www.uclibc.org/">uClibc C library</a>.
  54. Buildroot is useful mainly for people working with small or embedded
  55. systems. Embedded systems often use processors that are not the regular
  56. x86 processors everyone is used to using on their PC. It can be PowerPC
  57. processors, MIPS processors, ARM processors, etc. And to be extra safe,
  58. you do not need to be root to build or run buildroot.
  59. <p>
  60. And as of today buildroot even has its own webpage, making it a first class
  61. citizen of uclibc.org and busybox.net, and more importantly, make it easy
  62. to find and point to buildroot.
  63. <p>
  64. If you find a bug in buildroot, or wish to submit a patch to fix a problem
  65. or add a shiny new feature, please use the <a
  66. href="http://bugs.uclibc.org/">Bug and Patch Tracking System</a> to post
  67. the details, to make certain your work is not lost.
  68. </ul>
  69. <!--#include file="footer.html" -->