Thanks everyone for the feedback on this. Given the positive response I'm going to go ahead and create a branch called "wookie-1.x".
The next steps would be: - in the wookie-1.x branch, move the current revision from 0.15 to 1.0, and make a release - in the trunk, start work on migrating to the new project/sub-projects structure and the Maven build process for 2.x. Volunteers very welcome :) S On 29 Jan 2014, at 11:07, Steve Lee wrote: >> On 01/24/2014 11:11 AM, Scott Wilson wrote: >> >>> Hi everyone, >>> >>> I think its time we talked about the future direction for Wookie. >>> >>> Right now we have pretty good stability of the current codebase, so much >>> so that I'm personally loath to make any changes given how well it seems to >>> perform. >>> >>> However, I think we do want to make some pretty big changes, such as: >>> >>> - moving from internal db storage to a service provider interface design >>> - replacing persistent widget instances with Shindig-style encrypted >>> tokens >>> - moving from simple API keys to a more robust access token system for >>> API access >>> - replacing DWR with another solution for data sharing >>> - moving from Ant to Maven for build and deployment >>> >>> To move forward I think we need to make the current codebase a stable >>> release branch, only updated for critical bugfixes and security updates, >>> while we move onto working on a 2.0 release in trunk.
PGP.sig
Description: This is a digitally signed message part
