A public test server and stable server
It would be great if you set up a public testing server on which you would roll out changes and new features before putting it on the production server. People could be moved to this server on an opt in basis, so the stable server would be the standard.
I am sure many people would volunteer to try out the bleeding edge of Plurk development, but I also believe a lot more would love the stability of a server running only code that has been publicly tested.
Furthermore this would make is possible for all the hard working translaters to have a relatively complete translation ready when the changes move to the stable server, so the international versions aren't always as lacking as they are now.
I am sure many people would volunteer to try out the bleeding edge of Plurk development, but I also believe a lot more would love the stability of a server running only code that has been publicly tested.
Furthermore this would make is possible for all the hard working translaters to have a relatively complete translation ready when the changes move to the stable server, so the international versions aren't always as lacking as they are now.
2
people like this idea
I like this idea!
Tell me when this idea gets some attention.
The more people who like this idea, the more it gets noticed.
The more people who like this idea, the more it gets noticed.
Create a customer community for your own organization
Plans starting at $19/month
-
Inappropriate?Generally, doing a public and test server is pretty hard to do in practice and only a few web applications have this setup (the only web-application I know that have a "developer" version is Facebook - and that's mostly because of Facebook applications). Plus, users are _really_ bad at spotting bugs and they'll only notice and report bugs that affect the core service.
Anyway, the past week issues have not been related to committing "new features", but due to unexpected errors in the database sector.
I am pretty confident thought that this situation will improve in the near future as we are currently installing new hardware.
Regards,
Amir -
Inappropriate?I wasn't thinking about the current issues in particular. I think at least some of us would spot at least some errors from time to time, and that would be of quite som value to you.
I'm thinking about the caching issues, replicating and disappearing plurks, and such things. -
Inappropriate?We currently have a test suite that we plan to extend to cover more things.
I think it's far more effective than hoping that users are going to spot errors.
For example, a bug in friend notification system can be really hard to spot for a user, since it requires two user's to interact with each other before a bug is spotted. In an automated test suite one can test these things easily (with caching turned on) and check that it follows some rules, e.g. if user A befriends user B, then alerts should be +1 for B and B should have a friend notification from A. etc.
Regards,
Amir -
Inappropriate?Ok, I was thinking of it more as an extra thing on top of what you already do, not as a replacement of your current testing. Feel free not to do it, but I think the idea is good :-)
Loading Profile...



EMPLOYEE