On 26/01/2014 10:40, Scott Wilson wrote:
On 24 Jan 2014, at 12:22, Paul Sharples wrote:
On 24/01/2014 10:11, 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.
What do you think?
+1 from me. I think this sounds like a sensible plan. Some of the things we
have been discussing for a while (such as replacing DWR) are major changes, so
a new v2.0 development branch seems the logical way forward, while keeping our
current version alive.
So do you think it would be better to have the stable version in trunk, and do
2.0x as a branch?
Sorry I wasn't clear. As long as we can still build/release the v1.0
codebase periodically wherever it is (branch or trunk) then I'm not
bothered either way. Unless there are some gotchas we've not thought
of, I can't think of any off hand.
Paul
Paul
S
