I support this idea, because it is both best for the players and also for us (it is never good to develop something under great time pressure).
Of course on first sight it looks a little embarassing and also may make us feel uncomfortable. But to be honest: We all have been in such a situation before, nobody is perfect. Things like that just happen. There is no reason to point to someone and say "You messed it all up!". I'd say we make the best out of it and follow Dave's suggestion. Greetings Yogi >David White wrote >I think that the multiplayer lobby in 1.8 has seen insufficient testing >to be used in a product as mature as Wesnoth. It seems like it's going >to take a while to fix it up and make it production-ready. > >When such a thing happens, my view is that the change should be rolled >back, until the feature is ready, and then it can be re-introduced. As >such, I suggest that we apply the patch silene prepared which rolls the >lobby changes back. Then, after sufficient testing and re-work, the new >lobby can be re-introduced. > >Are there any thoughts, concerns, or objections to this approach? > >Regards, > >David _______________________________________________ Wesnoth-dev mailing list Wesnoth-dev@gna.org https://mail.gna.org/listinfo/wesnoth-dev
