Prepare for release

[oweals/busybox.git] / docs / busybox.net / news.html

diff --git a/docs/busybox.net/news.html b/docs/busybox.net/news.html
index 3744d2c63646e61700c0107bc1c1148a7614e945..b5c2be7d965c333a19e1b095dc45e7a03d9ab4da 100644 (file)
--- a/docs/busybox.net/news.html
+++ b/docs/busybox.net/news.html
@@ -3,6 +3,30 @@
 
 <ul>
 
+  <li><b>26 July 2004 -- BusyBox 1.0.0-rc2 released</b><p>
+
+    Here goes release candidate 2...
+    <p>
+    The <a href="downloads/Changelog">changelog</a> has all the details.
+    And as usual you can <a href="downloads">download busybox here</a>.
+
+    <p>Have Fun!
+
+    <p>
+    On a less happy note, My 92 year old grandmother (my dad's mom) passed away
+    yesterday (June 19th).  The funeral will be Thursday in a little town about
+    2 hours south of my home.  I've checked and there is absolutely no way I
+    could be back in time for the funeral if I attend <a
+    href="http://www.linuxsymposium.org/2004/">OLS</a> and give my presentation
+    as scheduled.
+    <p>
+    As such, it is with great reluctance and sadness that I have come
+    to the conclusion I will have to make my appologies and skip OLS
+    this year.
+    <p>
+
+
+  <p>
   <li><b>20 July 2004 -- BusyBox 1.0.0-rc1 released</b><p>
 
     Here goes release candidate 1...  This fixes all (most?) of the problems
@@ -10,19 +34,24 @@
     kernel modules with 2.6.x kernels should be working much better.
     <p>
 
-    I <b>really</b> want to get BusyBox 1.0.0 released soon and I see no reason
-    real reason why the 1.0.0 release shouldn't happen with things pretty much as is.
-    Remember, please do not bother to send in patches adding cool new features
-    at this time.  Only bug-fix patches will be accepted.  It would also be
-    <b>very</b> helpful if people could continue to review the BusyBox
-    documentation and submit improvements.
+    I <b>really</b> want to get BusyBox 1.0.0 released soon and I see no real
+    reason why the 1.0.0 release shouldn't happen with things pretty much as
+    is.  BusyBox is in good shape at the moment, and it works nicely for
+    everything that I'm doing with it.  And from the reports I've been getting,
+    it works nicely for what most everyone else is doing with it as well.
+    There will eventually be a 1.0.1 anyway, so we might as well get on with
+    it.  No BusyBox is not perfect.  No piece of software ever is.  And while
+    there is still plenty that can be done to improve things, most of that work
+    is waiting till we can get a solid 1.0.0 release out the door....
     <p>
 
-    If you have submitted a bug-fixing patch to the busybox mailing list and no
-    one has emailed you explaining why your patch was rejected, it is safe to
-    say that your patch has been lost or forgotten.  That happens sometimes.
-    Please re-submit your patch or bug report to the BusyBox mailing list, and
-    be sure to put "[PATCH]" at the beginning of the email subject line!
+    Please do not bother to send in patches adding cool new features at this
+    time.  Only bug-fix patches will be accepted.  If you have submitted a
+    bug-fixing patch to the busybox mailing list and no one has emailed you
+    explaining why your patch was rejected, it is safe to say that your patch
+    has been lost or forgotten.  That happens sometimes.  Please re-submit your
+    bug-fixing patch to the BusyBox mailing list, and be sure to put "[PATCH]"
+    at the beginning of the email subject line!
 
     <p>
     The <a href="downloads/Changelog">changelog</a> has all the details.