Slashdot Mirror

Any reason why the article points at Mozilla's in-use Bugzilla rather than the Bugzilla project page?

Given some of the above comments, this needs saying. This is a fun contest, and the prize is small. Anyone who tries to spam the database in any way will only mean that we can't have this fun any more. So please don't. And it won't work anyway, because we'll notice and stop you.

If you have an automatic bug creation script, please point it at Landfill, the Bugzilla test installation, which needs all the test bugs it can get :-)

Gerv

And I just tried [www.bugzilla.org], and it worked fine

I wasn't aware of www.bugzilla.org. I was referring to bugzilla.mozilla.org, which just refused me.

Sorry, links to Bugzilla from Slashdot are disabled.

Crafty stuff. Shame you didn't make your reference to Bugzilla a link, so we could see it in action.

And I just tried it, and it worked fine, so maybe they put a traffic limit on it too?

These are the ingredients to make large projects successful from a technical point of view. At the company I work for, we have literally hundreds of people working in the same source tree using P4. It manages merges, versioning, and works flawlessly over the internet (well VPN anyway). It is also much, much faster at syncing to the the depot than CVS because the server keeps track of those files that you are editing and does not need to do diffs with the local filesystem. This is very helpful during crunchtime where you might want to sync serveral times a day (and you have about 10000 files in the system). Also, until your locally edited files are resolved with changes in the depot you cannot submit them, so you don't have the problem of ordering patches properly.

For the second part, I highly reccommend that you have automated build and tests that run after changes have been submitted. You can see how this is done en mass on the mozilla.org site. Also, developers should have access to the same build and test infrastructure on their machines so they can do the build and test before they check in their code.

Finally, you need a good bug tracking system. You might try Bugzilla.

Good luck,
Sam

Bugzilla
cvsweb phorums