news.html 7.5 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170
  1. <!--#include file="header.html" -->
  2. <h3>News</h3>
  3. <p>
  4. <ul>
  5. <li><b>1 June 2009 -- 2009.05 released</b>
  6. <p>The stable 2009.05 release is out - Thanks to everyone
  7. contributing and testing the release candidates. See the
  8. <a href="http://lists.busybox.net/pipermail/buildroot/2009-June/027640.html">announcement</a>
  9. or <a href="http://git.buildroot.net/buildroot/plain/CHANGES?id=2009.05">CHANGES</a>
  10. for more details, and go to the <a href="/downloads/">downloads page</a>
  11. to pick up the <a href="/downloads/buildroot-2009.05.tar.bz2">2009.05
  12. release</a>.</p>
  13. <li><b>27 May 2009 -- 2009.05-rc3 released</b>
  14. <p>We had a number of fixes post-RC2, so RC3 is out (see <a
  15. href="http://git.buildroot.net/buildroot/plain/CHANGES?id=2009.05_rc3">CHANGES</a>
  16. for details). Now is the moment to test and verify that everything
  17. is working for your favorite config - Expect a final 2009.05 very soon.</p>
  18. <p>Head to the <a href="/downloads/">downloads page</a> to pick up the
  19. <a href="/downloads/buildroot-2009.05-rc3.tar.bz2">2009.05-rc3
  20. release candidate</a>, and report any problems found to the <a
  21. href="lists.html">mailing list</a> or <a
  22. href="https://bugs.uclibc.org">bug tracker</a>.</p>
  23. <li><b>19 May 2009 -- 2009.05-rc2 released</b>
  24. <p>RC2 is out with more cleanups and bug fixes (see <a
  25. href="http://git.buildroot.net/buildroot/plain/CHANGES?id=2009.05_rc2">CHANGES</a>).
  26. Unless big issues are found, expect this to be the last release
  27. candidate before the release - So give it a good test.</p>
  28. <p>Head to the <a href="/downloads/">downloads page</a> to pick up the
  29. <a href="/downloads/buildroot-2009.05-rc2.tar.bz2">2009.05-rc2
  30. release candidate</a>, and report any problems found to the <a
  31. href="lists.html">mailing list</a> or <a
  32. href="https://bugs.uclibc.org">bug tracker</a>.</p>
  33. <li><b>14 May 2009 -- Buildroot.org</b>
  34. <p>Earl Levine has been so kind to donate the <b>buildroot.org</b>
  35. domain to us, so the website can now also be reached at <a
  36. href="http://www.buildroot.org">www.buildroot.org</a> (and git at
  37. <a href="http://git.buildroot.org/buildroot">git.buildroot.org</a>).
  38. Thanks a lot Earl!</p>
  39. <li><b>5 May 2009 -- 2009.05-rc1 released</b>
  40. <p>We have a new release candidate! Lots of changes all over the
  41. tree, see the <a
  42. href="http://git.buildroot.net/buildroot/plain/CHANGES?id=2009.05_rc1">CHANGES</a>
  43. file for details.
  44. <p>Head to the <a href="/downloads/">downloads page</a> to pick up the
  45. <a href="/downloads/buildroot-2009.05-rc1.tar.bz2">2009.05-rc1
  46. release candidate</a>, and report any problems found to the <a
  47. href="lists.html">mailing list</a> or <a
  48. href="https://bugs.uclibc.org">bug tracker</a>.</p>
  49. <li><b>3 May 2009 -- Moved to git</b>
  50. <p>We've moved the source code from <a
  51. href="http://subversion.tigris.org">Subversion</a> to <a
  52. href="http://git-scm.org">Git</a>. You can browse the repo online
  53. <a href="http://git.buildroot.net/buildroot">here</a>, and clone
  54. the repo using:
  55. <pre>git clone git://git.buildroot.net/buildroot</pre>
  56. See the <a href="/git.html">Git Access</a> page for more details.
  57. </p>
  58. <li><b>27 March 2009 -- new Logo</b>
  59. <p>We have a <a href="images/logo.png">logo</a>! We have so far
  60. been using the <a href="http://busybox.net">Busybox</a> logo on
  61. the website, as the website was a copy of the <a
  62. href="http://busybox.net">Busybox</a> one - But not anymore, we
  63. now have a shiny new logo of our own.</p>
  64. <li><b>12 February 2009 -- 2009.02 released</b>
  65. <p>The stable 2009.02 release is out - Thanks to everyone
  66. contributing and testing the release candidates. See the
  67. <a href="http://lists.busybox.net/pipermail/buildroot/2009-February/025974.html">announcement</a>
  68. for more details, and go to the <a href="/downloads/">downloads page</a>
  69. to pick up the <a href="/downloads/buildroot-2009.02.tar.bz2">2009.02
  70. release</a>.</p>
  71. <li><b>9 February 2009 -- 2009.02-rc4 released</b>
  72. <p>We had more than 50 changes since RC3, several of them
  73. toolchain related, so decided to make a RC4 as well. This is
  74. very much expected to be the final release candidate, so give it
  75. a good test and expect a final 2009.02 release this week unless
  76. critical issues are found.</p>
  77. <p>Head to the <a href="/downloads/">downloads page</a> to pick up the
  78. <a href="/downloads/buildroot-2009.02-rc4.tar.bz2">2009.02-rc4
  79. release candidate</a>, and report any problems found to the <a
  80. href="lists.html">mailing list</a> or <a
  81. href="https://bugs.uclibc.org">bug tracker</a>.</p>
  82. <li><b>31 January 2009 -- 2009.02-rc3 released</b>
  83. <p>RC3 is out with more cleanups and bug fixes. Unless big issues
  84. are found, expect this to be the last release candidate before the
  85. release - So give it a good test.</p>
  86. <p>Head to the <a href="/downloads/">downloads page</a> to pick up the
  87. <a href="/downloads/buildroot-2009.02-rc3.tar.bz2">2009.02-rc3
  88. release candidate</a>, and report any problems found to the <a
  89. href="lists.html">mailing list</a> or <a
  90. href="https://bugs.uclibc.org">bug tracker</a>.</p>
  91. <li><b>23 January 2009 -- 2009.02-rc2 released</b>
  92. <p>Another week, another release candidate with a bunch of
  93. cleanups and build fixes.</p>
  94. <p>Head to the <a href="/downloads/">downloads page</a> to pick up the
  95. <a href="/downloads/buildroot-2009.02-rc2.tar.bz2">2009.02-rc2
  96. release candidate</a>, and report any problems found to the <a
  97. href="lists.html">mailing list</a> or <a
  98. href="https://bugs.uclibc.org">bug tracker</a>.</p>
  99. <li><b>16 January 2009 -- Release candidate and new maintainer</b>
  100. <p>It has been a long time coming, but we finally have a new
  101. release candidate! - And a new maintainer to match (Peter Korsgaard).</p>
  102. <p>Head to the <a href="/downloads/">downloads page</a> to pick up the
  103. <a href="/downloads/buildroot-2009.02-rc1.tar.bz2">2009.02-rc1
  104. release candidate</a>, and report any problems found to the <a
  105. href="lists.html">mailing list</a> or <a
  106. href="https://bugs.uclibc.org">bug tracker</a>. The plan is to
  107. release 2009.02 in time for <a
  108. href="http://www.fosdem.org/2009/">FOSDEM</a>.</p>
  109. <li><b>16 July 2006 -- Buildroot mailing list</b>
  110. <p>Buildroot now has its own <a href=lists.html>mailing list</a>.</p>
  111. <li><b>21 February 2005 -- Buildroot webpage added</b><p>
  112. Buildroot is a set of Makefiles and patches that makes it easy generate a
  113. cross-compilation toolchain and root filesystem for your target Linux
  114. system using the <a href= "http://www.uclibc.org/">uClibc C library</a>.
  115. Buildroot is useful mainly for people working with small or embedded
  116. systems. Embedded systems often use processors that are not the regular
  117. x86 processors everyone is used to using on their PC. It can be PowerPC
  118. processors, MIPS processors, ARM processors, etc. And to be extra safe,
  119. you do not need to be root to build or run buildroot.
  120. <p>
  121. And as of today buildroot even has its own webpage, making it a first class
  122. citizen of uclibc.org and busybox.net, and more importantly, make it easy
  123. to find and point to buildroot.
  124. <p>
  125. If you find a bug in buildroot, or wish to submit a patch to fix a problem
  126. or add a shiny new feature, please use the <a
  127. href="https://bugs.uclibc.org/">Bug and Patch Tracking System</a> to post
  128. the details, to make certain your work is not lost.
  129. </ul>
  130. <!--#include file="footer.html" -->