Hello. On Tue, 2013-11-19 at 07:58, Carsten Haitzler wrote: > On Mon, 18 Nov 2013 20:25:22 +0000 "Eoff, Ullysses A" > <ullysses.a.e...@intel.com> said: > > > Attached are our EFL/ELM Alpha 1 Manual Testing Results on Wayland. Enjoy > > ;-) > > and all i care about is... > > there are bug tasks for all failures. good stuff! :) i know a whole bevvy of > them are already solved. :)
Lets also say thank you here because I can imagine that doing a full manual QA run is some work. Thank you Ullysses and your team. I really appreciate that you are doing this and bringing the problem all back into our bugtracker. It would be great if we could get such a run also for our upcoming 1.9 release cycle. Its only three months in total so let me know if you have any specific needs that we could help with. I would think that maybe doing a run after each of our two merge windows would make sense. That gives us the reports we can work on inthe stabilization phases. Is that ok timing wise or will it put to much load on your team? I have know idea how long such a manual run takes. I would tag the tree after every merge window and cut some tarballs. Both of these could be used as reference. More details here: https://phab.enlightenment.org/w/efl_and_elementary_1_9/ regards Stefan Schmidt ------------------------------------------------------------------------------ Rapidly troubleshoot problems before they affect your business. Most IT organizations don't have a clear picture of how application performance affects their revenue. With AppDynamics, you get 100% visibility into your Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro! http://pubads.g.doubleclick.net/gampad/clk?id=84349351&iu=/4140/ostg.clktrk _______________________________________________ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
