Форумы / Unrelated / Offtopic / Cotonti, Genesis or whatever? seditio 125 >.>

ok!

i agree partly with koradhil about the new versions. sure its good to know that a system is developed further. and it is cool to see the activity and bugfixes. but the lack of some stable developer branches is a thing that bothers me most while developing plugins.

for example. a new pfs system is developed while iam working on a "old" version. then when iam done with the plugin the pfs system the plugin was build for is obsolete. as a developer iam asking myself the question if i really WANT develop for this system under this circumstances because it will never be finished that way.

at every project i was involved in the past 10 years with we had a stable release and some developers versions. most of the time, except for heavy bugs, we had over a year or so a stable enviroment. after that period we got a new version wich was 100% backwards compatible...

so maybe some sort of reorganising wouldnt be bad.
(this fits better in the version numbers topic i guess)

i would like to have something like this:

I. stable version (i.e.: 0.6)
II. stable dev branch (i.e.: 0.6.1)
IIa. different bug fixing branches (i.e.: 0.6.1-a)
IIb. different bug fixing branches (i.e.: 0.6.1-b)
IIc. different bug fixing branches (i.e.: 0.6.1-c)
IId. different bug fixing branches (i.e.: 0.6.1-d)

(and after all bugs are fixed in version 0.6.1 it converts to 0.7 final release and everything starts from the beginning with different numbers)
(ok, ok, i know this comes directly from the c sharp multi developrs manual )


for now i WILL freeze everthing regarding cot. i will watch a few weeks and see what happens.
i will still develop a bit in the background and try to make it fit after we got something that seems more reliable then the current versions.