Jonas Borgström wrote:
> On 3/25/09 9:04 AM, Noah Kantrowitz wrote:
>   
>> No, not sure how it would be ....
>>
>> If you want to add a test case for this particular thing, so write one  
>> and submit it. We have a pretty big unit and functional testing  
>> infrastructure. The point is that t.e.o isn't a test site and  
>> shouldn't be treated as such.
>>     
>
> I disagree. t.e.o has always been used for release testing and this is
> the first time it has had a major impact on the services t.e.o is
> supposed to provide. So I think the benefits by far outweighs the risks.
>   

A release candidate means "we think that this version is good for 
release". So it would even be contradictory to say so but not be 
confident enough to run it on t.e.o. Even more, we periodically upgrade 
t.e.o to latest of the stable branch, because the stable branch is just 
that, supposed to be "stable". I see no reason to not continue to do 
that. As jonas said, the benefits are greater than the risks here. 
Besides, the risks are not that great - if something goes wrong, we just 
fix it or, at worse, rollback a few revisions.

That being said, it would be nice if we could get some /real/ test 
environments on edgewall.org.
Indeed, the current "official" demo site on hosted-projects.com has a 
couple of problems:
 - it runs 0.10.5 - who cares about this version anymore ;-)
 - it's not spam protected

Ideally, the test environments should run the latest committed code (one 
for 0.11-stable, another for 0.12dev). Maybe the new server is beefy 
enough to allow those environments to run in a sandbox (chroot / vm)? If 
not, then running at least the same version as the one used for t.e.o 
itself should be doable without introducing additional security concerns.

-- Christian


--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Trac 
Development" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to 
[email protected]
For more options, visit this group at 
http://groups.google.com/group/trac-dev?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to