cotonti.com : Cotonti, Genesis or whatever? seditio 125 >.>

cotonti.com : Cotonti, Genesis or whatever? seditio 125 >.> https://www.cotonti.com Last topic posts Cotonti en Sun, 14 Dec 2025 04:54:20 -0000 Kilandor
But as with anything it doesn't mean it wont' have problems for some people, or maybe we missed some things.

And we do do bug fixes your just not familiar with our system, we don't do a lettering system like Seditio because its confusing and strange. #.#.0 means thats the meain (stable) release for that version for example 0.6.0 Is main verison 0.6.1 is bug fixes to that, and so on.

I mean Not attacking oliver as hes very busy. But i'm pointing out, 125 was first beta released 1 year 4 months ago(4-3-2008) "125 Resumed" notice(6-12-2009), its been 2 months since that was even started and no release, and its been 2 years 4 months since a "Stable" release(121).

I guess you have a different concept of what stable is, years between releases?

On a side note, we are going to better practice/test our releases in the future as we got away from a few things we previously did.]]> Fri, 21 Aug 2009 22:19:53 -0000 GHengeveld have to enable the new features. You can simply disable the folder storage mode and it's back to 2004 again.]]> Fri, 21 Aug 2009 18:40:05 -0000 Trustmaster
And we do have 2 branches now: stable (Genoa) and development (Siena). So new releases in Genoa (0.6.1, 0.6.2, 0.6.3) are only bug fixes, while Siena (0.7) is under heavy construction.

And as Lombi said, we tend to change major things fast in chase of 1.0 and other CMS which Seditio and Cotonti is far behind of, though this pursuit is never too fast since all we are "part-time" developers here.]]> Fri, 21 Aug 2009 15:02:24 -0000 Kingsley
Best example for me is the userfields: Simple and brilliant, and it gives the requested flexibility.
Even I (remember, am not a programmer) can think of better ways for the PFS. And I must admit that including js and all kinda forced me to pick up books and read in to it.

My final point is that activity at Neocrome isn't what it used to be. I mean, come on, last file on neocrome dates from 25-06-09...

if I were you I'd sit this one out. Simply because cotonti is worth it.]]> Fri, 21 Aug 2009 08:39:08 -0000 Lombi I understand your problems. It's hard to work if your base keeps changing.

But you must understand that this isnt going to be going on for ever. The main wish here is that we're moving towards 1.0 which is going to leave most of the obsolete logic (that's been unchanged since 2003) behind.

While this means that some things might get changed (for the better) in the following months it also means much higher possibilities for extensions and a better performance once the upgrade is done.

Leaving old obsolete logic behind and building something that's actually competitive to the other systems should be a huge priority if we want this CMS to be something, not just a "better version of Seditio".

Also please take into consideration that the reason that Seditio seems like a "stable environment" is solely because of the fact that there hasnt been a new version for, what, two years now?

If I turn specifically to the PFS engine, I cannot remember one single visible change from LDU 503 (when I started using the engine). So we've been stuck with it since 2004 (I'm just not sure if it changed before that) and we've only now begun to improve it.

Please dont think of this process as the system being unstable, but as progress and an evolution of a great CMS.]]> Fri, 21 Aug 2009 06:37:09 -0000 urlkiller
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:

(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.]]> Fri, 21 Aug 2009 06:14:36 -0000 GHengeveld
I'm not saying it's a bad thing, on the contrary. But I do feel we don't want to have a new release every month.]]> Thu, 13 Aug 2009 05:05:10 -0000 Trustmaster ]]> Thu, 13 Aug 2009 04:34:33 -0000 urlkiller
but i think i will wait until some stable and to rely on is there and take a peek in that...
maybe it IS better

until then i will freeze too all development on mediabay...

developers need a stable enviroment! keep them in your minds too! not only feature rich webapps.

so long...]]> Thu, 13 Aug 2009 04:16:42 -0000 Trustmaster
Actually, as you could notice we've put a "feature freeze" on Genoa branch to make it stable to rely on and write plugins for. 0.6.2 is coming this week and brings bug fixes only. So I don't think that Sed v125 is much more beneficial choice than Cot 0.6.

Anyways, it is your choice what to develop plugs for. I just want you to know that everyone from Cotonti DevTeam and people who know you since old Seditio days keep a great respect for you and the work you do. Once you decide to get back here, you will be welcomed. Don't hesitate to ask for help if you need some, or have your say to affect the way this CMS is built.]]> Thu, 13 Aug 2009 04:04:55 -0000 urlkiller but now after watching the post here in the forums i beginn to think about NOT developing anymore for cot.

the problem i encounter is to keep track with developments in the main engine and core features.
on top of that i dont know for what system i should write my plugins.

i thought that i will find some stable release here, but i found a site where some of the old spirit is missing. dont get me wrong its a cool thing to develop the sed system further but take a breath guys!

wasn't there a stable realease planned for this month?

never the less i will leave cot and to be true i never felt truly welcomed here...
kinda shity and kiddie....

bye bye guys!

btw. i will still develop plugins for the NEW seditio 125 system....]]> Thu, 13 Aug 2009 03:49:07 -0000