Clumsy sed fixed...

[irc/freenode/web-7.0.git] / content / news / 2003-08-03-scheduled-maintenance-ircd-upgrade-3.markdown

diff --git a/content/news/2003-08-03-scheduled-maintenance-ircd-upgrade-3.markdown b/content/news/2003-08-03-scheduled-maintenance-ircd-upgrade-3.markdown
index 6a8af8cf338a577bc385daa0ef298871e49c7b76..12bbacaed75a6455d35b045490a6dfa52b8b34c7 100644 (file)
--- a/content/news/2003-08-03-scheduled-maintenance-ircd-upgrade-3.markdown
+++ b/content/news/2003-08-03-scheduled-maintenance-ircd-upgrade-3.markdown
@@ -2,6 +2,12 @@ author: christel
 date: 2003-08-03 21:12:49+00:00
 slug: scheduled-maintenance-ircd-upgrade-3
 title: '[Scheduled Maintenance] IRCD Upgrade'
+---
+
+Hi, all.  Yesterday at about 10pm UTC we posted a global notice to let people know that we were considering an upgrade this weekend to pre-1.0.32 dancer-ircd.  We continue to experience clonebot attacks, and the additional features in the new release will be helpful. We directed people to channel **#upgrade** and asked for questions and feedback. After answering questions and taking comments for about an hour, it seemed that the response to the idea of trying the upgrade was pretty favorable.
+
+The release candidate code can be found  [here](http://source.freenode.net/%7Easuffield/dancer/dancer-ircd/1.0/pre/dancer-ircd-1.0.31+pre23.tar.gz),  and we provided information on new server features in a  [previous news item](http://freenode.net/news-2003-05-28.shtml).  It seems from our experience in this and other development cycles that the only real way to get production-load testing in dancer-ircd 1.0 is to go ahead and try the conversion, once we're pretty certain we have reliable code.  The code looks fine in the test environment, and delaying will not help us with kiddie attacks.
+
 The plan is to try today (Sunday in most venues), converting the small European servers and Australia and a couple of small servers in the US, and then the larger servers in the main rotation. The old protocol is not fully-compatible with the new protocol, so servers which have been converted will be connected to other converted servers, but we'll have two networks until the conversion is complete.  It could take a couple of hours if all goes well.
 
 Obviously, there is no guarantee we'll be successful.  If need be, we'll back up to the 1.0 environment, which should take about a half hour. If we're able to stay up using pre-1.0.32, we'll just do a bit of cleanup next weekend, which may involve restarting the servers one at a time, but should not require a partition of the network.