I think we've completed the majority of the web site discussion, and after my changes just committed, the latest pending are only about issues that are not release blocking. Right?
There have been many inputs about the website in the past 48 hours, and one about the rc's (but probably P3 -- about building on *nix, not users). I think all the website issues have been addressed with my posts just now. And we haven't had any consensus P1/P2 issues in Audacity code. I'm fine with another approximately 48 hours release review. Are we good for finalizing 2.0 release by 23:00 GMT on March 10? After all this time, and last minute (for 10 days!) alarms, are we good for that? Would March 11 be more comfortable? Let's get on with it. Thanks, Vaughan ------------------------------------------------------------------------------ Virtualization & Cloud Management Using Capacity Planning Cloud computing makes use of virtualization - but cloud computing also focuses on allowing computing to be delivered as a service. http://www.accelacomm.com/jaw/sfnl/114/51521223/ _______________________________________________ Audacity-translation mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/audacity-translation
