On Jan 28, 2008 4:22 PM, Thomas Bruederli roundcube@gmail.com wrote:
till wrote:
So how many more mergers of 0.1-versions do we need? I'd say we throw out a 0.1 ASAP then. :-)
I'd like to release 0.1-stable from the current trunk. Therefore we need to fix the open tickets assigned to that milestone.
Ok, good to know. So I guess we finish the current merge and then focus on the important tickets in trac. :O
After that, the merged devel-vnext can replace the trunk version if it works exactly the same as 0.1-stable. Test cases are required here!
How are we gonna go about this? I was thinking of doing a couple Selenium tests for example, there is a Firefox extension to "record" them and then convert them to phpUnit. But how would we test the rest? Any ideas?
The changes in devel-vnext are mostly code style plus a few new classes and auto-loading. If merging gets too complicated we could also copy the new things from devel-vnext one by the other into the current trunk and test continuously.
I don't think it's so much easier the other way around. I believe there were a few more things, but anyway I think we are almost there. ;-)
Till _______________________________________________ List info: http://lists.roundcube.net/dev/