No I completely disagree. Lets keep everything on the main trunk as development, then can make branches for the releases.
That is what we decided on before. Lets stick to it! So, we are working towards 0.9. Don't get me wrong, updates and changes great and welcome aiki founder! But, just want to make sure we don't split a bunch of energy, then you go away. So lets stick with development and not make any more official branches, but when we make a release, yes, lets make a branch of the release. Speaking of which, we should get aiki 0.9 done. Bassel, how much can you be online now? If all you do is help on aiki, great! We only have like 5 developers, so its silly to do kernel style development. Lets keep it simple, keep track of our changes, and commit. Then when we get closer to release push for stability, yes, for big changes, please all make branches, but lets not make some rule that will divide energy. Ok? Lets keep code coming in! Jon -- Jon Phillips ✳ http://fabricatorz.com ✳ skype: kidproto ✳ irc: rejon +1.415.830.3884 (global) ✳ +86-187-1003-9974 (beijing) _______________________________________________ Mailing list: https://launchpad.net/~aikiframework-devel Post to : [email protected] Unsubscribe : https://launchpad.net/~aikiframework-devel More help : https://help.launchpad.net/ListHelp
