El 24/03/15 a las 12:12, Christian Grobmeier escribió: > we have volunteers for the next months. Why not discussing what we > should do? > > My first preference would be: craft a release. > I forgot what was missing back then, but it would be great to find out > from the mail archives and create jira issues for the open things. Maybe > Ali could help here, as he was the RM for the last try. > > The next thing would maybe be more technical. Can you throw in some > concrete ideas what could be achieved in small steps? > I guess "refactoring everything" is not a good start :) > > Regards, > > Christian >
>From my point of view there are several "basic" bugs that should be addressed: - The wave edition should work in major/modern browsers. - There are several concurrent edition and persist issues (Yuri mentioned it). - It seems that some edition shortcuts are broken since the akaplanov Profiling functionality: https://reviews.apache.org/r/22776/ (as a workaround I reverted FocusManager.java in my branch). - Inbox search issues (unread counts, etc) in other storages different that memory. - The gwt superdev mode should work (editor, wavehardness, and full client) so new developers can contribute easily. - For that, we should upgrade to gwt 2.7. Review 22776 also affects this: there is a wip patch in this list. - The tests (including gwt-test) should pass without errors. - There are a lists of issues related with gadgets (some are missing or broken, browser compatibility issues, it seems to me that gmodules.com gadget server should be replaced by a new one maintained by us). If edition+concurrent-edit+shortcuts+persistence+gadgets does not work correctly, people would prefer to use a simple non-concurrent html TextArea instead of wave :O) Greetings, Vicente
