Nov 09
18
Clay Dev, 10′s Framework Series
Clay is still coming along. I’m in the planning stages of setting up a Git repo on SourceForge. I’m trying to decide the best way to start it out, considering I plan to spawn several projects from the framework. My main concern is to setup the repos so I can move along in development without leaving users behind. I will likely manage 2 repos, stable and unstable, and only do work in the unstable repos. Each repo will have branches that make them run parallel, which will end up being merged into the main branches and eventually into the stable repo for release. I will likely create more permanent branches for the offshoot projects, such as a CMS and perhaps some specialized suites. That way I can merge changes into the offshoot projects, without building up the framework itself.
I’ve already played around with a few ideas for 2.0, so I will likely have an experimental branch for it that will eventually be merged into the unstable branch and it starts all over. My main thing with the development process is to make sure everything runs parallel up to a certain point. I feel if I make clear distinctions between what versions mean and actually give them meaning, then we wont have to worry about maintaining full backward compatibility. We can move forward and make progress without having to worry about leaving developers behind. For instance, I plan to release a 0.4.x as an alpha, move to beta at 0.5, and keep going toward 1.0. 1.x will run through 1.3 and 2.x development will open as 1.4 alpha. 1.3 would remain the supported version until 2.0 became ready for release.
I’m still working on the “Framework for the 10′s” series and will hopefully publish part 1 this weekend. I’ve been working on a whitepaper for it, I just have to decide how to break it up into articles. Once the series is published I’ll publish the whitepaper as a whole.