Help Stress Test The New Slashdot

Here's you chance to generate wasteful http traffic without even having to run unpatched IIS! We're ready to test Banjo, our new fancy setup w/ new code and new hardware. We plan to keep testing until we think the system is ready. You are also welcome to submit Bug Reports, although it would be helpful if you skimmed the list of bugs before submitting new ones so we don't have 300 of you tell us that your user info page has other people's comments listed on it again. The new hardware is mostly in place, but the code hasn't been fully optimized yet, so run your wgets... write your bots... whatever makes you happy, but please don't be malicious: just try to load and submit web pages. And don't be surprised, its gonna go up and down like a yo yo as we fix things.

Change list

[ergo98]

Is there a list of advantages/improvements of the new version?

Hope for Banjo

[zsazsa]

Seeing as it's down and I'm not willing to download the code and test it out, I'll just complain here (I don't see it in the CHANGES file):

I hope to GOD that the new version of Slashdot will include the actual YEAR in comments, stories, and everything else. I realize that for stories and comments we can look up in the year for the (non-Y2K compliant) year, but it's just annoying.

I am sick of:

Posted by CmdrTaco on Thursday August 16, @11:13AM

by BigBlockMopar ([e-mail]) on Thursday August 16, @11:21AM CST (#5)

(not that I have anything against CmdrTaco and BigBlockMopar)

and

You have moderator access and 5 points. Welcome to the those of you just joining: please read the moderator guidelines for instructions. (updated 9.9!)
After clicking it is revealed that this is September 9th, 1999, almost TWO YEARS AGO.

I should probably be bitching to people who actually do the code (or fix it my own self) but I just have to vent. After a couple years it starts to build up. :)

Goodbye karma!

Re:Not a flamebait but..

[boaworm]

The thing with testing things live is that the programmers are biased, they know what weaknesses there are, and they know what "is" working. This makes them a bad group to test.

This goes for every good software development team, external testing is VITAL in order to maintain quality. Try to make a good product, let the actual users test the product, help them submit improvement proposals/bug reports, and prepare to recode the whole thing :-)