Since they're running Zope, and didn't bother disabling the example installs, join the ad-hoc online community that is cybertriallawer.com's guestbook:
Isn't it ironic that we are using the random NY Times registration generator to read an article about random registration data? Sort of proves the point, doesn't it?
One solution to avoid patching problem is to use continuous integration. It's an integration technique that builds your source multiple times a day, getting all the latest source code from the CVS tree, and building from that code. If anything fails, the offending developer gets warned. Mozilla uses the same thing, calling it TinderBox. It's one of the principles of Extreme Programming, and seems to work quite well at our company.
Slashdot Mirror
Since they're running Zope, and didn't bother disabling the example installs, join the ad-hoc online community that is cybertriallawer.com's guestbook:
http://www.cybertriallawyer.com/acl_users/Examples/GuestBook
Google appears to block Safari and Camino, but not Firefox.
They're called buymusic, not playmusic...
Yes, I've read about that one...
Isn't it ironic that we are using the random NY Times registration generator to read an article about random registration data? Sort of proves the point, doesn't it?
What would happen if the wayback machine starts archiving its own site?
5 minutes with the new browser under Mac OS X, surfing slashdot and mozillazine and the darn thing crashed on me!
What is their exact definition of a 'final' release?
One solution to avoid patching problem is to use continuous integration. It's an integration technique that builds your source multiple times a day, getting all the latest source code from the CVS tree, and building from that code. If anything fails, the offending developer gets warned. Mozilla uses the same thing, calling it TinderBox. It's one of the principles of Extreme Programming, and seems to work quite well at our company.