El mié, 07-07-2010 a las 15:04 +0200, JR escribió: > [...] > My proposal: > - development with one version who is the "stable" version -> and this > version ist only modified for fixes > - another development version who is the "new features and other > modifications" version
I agree with that. I remember this topic was discarded in the summit, but in cases like this (the SSL problem it's pretty critic), I think that current release scheme has some limitations. I will keep using the 'development' or 'testing' branch anyway, but I understand that current scheme of "upgrade and rollback if something goes wrong" it's not suitable for everyone (for example, I couldn't afford it in my company). What do you think? Would it be possible/good review current release policy? Cheers, Juanjo -- jjm's home: http://www.usebox.net/jjm/ blackshell: http://blackshell.usebox.net/ ramble on: http://rambleon.usebox.net/ _______________________________________________ Cherokee mailing list [email protected] http://lists.octality.com/listinfo/cherokee
