We'll treat it like all the other releases in the past: When a new version comes out, the previous version only gets security updates, if needed.
Actually, I was planning to whip up a 1.8.2 to address its problems with MySQL 5.5 if I can find the time. But certainly no new features.
bye, Dirk
why you seem to think it's necessary to continue with the 1.x line.
Having said that, I'd be interested to learn what you have in mind. Especially why you seem to think it's necessary to continue with the 1.x line. Please note that Geeklog 2.0.0 isn't really all that different from 1.x.
These are my plans:
- I would like to rip out the templating system and put in one of my one.
- Replace the WYSIWYG editor
- Build in better SEO defaults
- Tweak the database schema
I thought GL 2 was a complete recoding from the ground up?
These are my plans:
- I would like to rip out the templating system and put in one of my one.
- Replace the WYSIWYG editor
- Build in better SEO defaults
- Tweak the database schema
These are my plans:
- I would like to rip out the templating system and put in one of my one.
- Replace the WYSIWYG editor
- Build in better SEO defaults
- Tweak the database schema
I thought GL 2 was a complete recoding from the ground up?
That was the original plan. It even saw a release under the name of AptitudeCMS before it ran out of steam. In other words, that didn't work out. I even used it as an example in a presentation about why you should not rewrite your software from the ground up ;-)
Let me rephrase - when was AptitudeCMS replaced with Geeklog 2.0?
Does that make it clearer?