0.9.6 development closed (branches/095dev will be deleted)

Alright, in the interest of progress, I now declare 0.9.6 feature development (and the 095dev branch we’ve been contributing to in SVN) closed. No new language strings or features or tweaks to features. Only bugs that must be fixed in the short-term (30-90 days) will be made to 0.9.6 from this point forward, and these will need to be made in the new 0.9.6 branch located at branches/0.9.6/. If you have any outstanding work in progress in any of the SVN branches related to 0.9.6, please contact me immediately to discuss. branches/095dev will be deleted very soon, so please contact me if you have something fixed that you feel must get in before 0.9.6 final release (bugs only please).

Everyone else that is interested should prepare to shift focus to 0.9.7 development. You can collaborate on development of this path in branches/opengeek for now. However, I’ll be setting up branches/0.9.7 ASAP, following some pending merges from the recent 0.9.6 commits, in preparation to make all of our development branches public. I will follow-up with another post about how I will be creating branches/private/ to house any branches we do not want exposed publicly. So, if you have code in branches/ that you do not want made public, please make plans to migrate your branch to this branches/private/ sub-directory. I will be updating the ACLs within the next 48hrs to expose the root of branches and limit private access to team members, and will notify everyone again before this is done.

Finally, I will also be following up with a post detailing what we’ve been doing, as well as where we really need help to get 0.9.7 ready for beta release.

Let me know if you have any questions, suggestions, etc...

:D

Folks it’s about to start getting really really fun.

For those of you already looking at 0.9.7, remember: it’s not done.

There’s still a lot left to be done in the manager (Jason will talk about that) and there are probably (well, actually, definitely) sections that are broken, since the model is completely different.

But, overall, I think you’ll really like the changes - everything is much easier to develop.

Here’s a few guiding principles about 097 and the future:

[*] Zero template limitations — native MODx templates or Smarty will be native. Any other system can be implemented. Standards compliant XHTML/CSS sites are a definite given just like they have been for years.
[*] Extendable by design — modern OOP design means you can override the core functionality without hacking the core with a clear, simple upgrade path. Make MODx fit your workflow and needs, not the other way around.
[*] Custom application framework — a consistent, well documented API
[*] Database agnostic — MySQL, Postgres, sqlite, MSSQL, Oracle ... or any other database for which a PDO driver exists
[*] Database optimized — our xPDO ORM / abstraction layer balances simplicity and abstraction, while taking advantage of each individual database engines performance potential ... it’s not overly-genericized to the least common denominator
[*] Optimized parsing — recursion without regex
[*] Search optimization platform — friendly URL support out of the box and robust Sitemaps protocol support
[*] Unlimited hierarchy — there really are times when just a few levels deep doesn’t cut it
[*] JS library neutrality — any Ajax library can be supported
[*] Ubiquitous deployment — support all the way back to PHP 4.3.x (and maybe earlier)

096 is going to be released very soon. 097 will be in beta shortly thereafter (it’s been in development for over a year).

Also consider that with 097 Contexts make subsites and multi-site support from a single install possible. Similarly, xPDO makes it possible to generate APIs to access data simply that’s stored in other platforms. In fact, we’ve used it internally to replace osCommerce’s catalog display system, convert entire Mambo sites to MODx, access Wordpress content and more.

I’m ready to start getting my hands dirty again. Great work so far guys. I will watch for the list of things to help on.

I got a fever... and the only cure is more 0.9.7 cowbell.

-sD-
Dr. Scotty Delicious, Scientist.

GREAT news guys!

Quote from: Dr. at Apr 25, 2007, 11:33 PM

I got a fever... and the only cure is more 0.9.7 cowbell.

-sD-
Dr. Scotty Delicious, Scientist.

hrm, I am feeling a little temperature too

Would it be possible that during this transition, we convert all files to a consistent file format? I notice that some of the files have a DOS eol style and others have UNIX an so forth. Mixing formats confuses SVN and editors will end up with code conflicts just becuase the file format is different.

This is something that I would be able to do, but seeing as it is a large modification it would be difficult to do without the agreement of all programmers because they would have to check-in and update all their WCs to this new revision.

Quote from: sirlancelot at Apr 26, 2007, 12:29 PM

Would it be possible that during this transition, we convert all files to a consistent file format? I notice that some of the files have a DOS eol style and others have UNIX an so forth. Mixing formats confuses SVN and editors will end up with code conflicts just becuase the file format is different.

This is something that I would be able to do, but seeing as it is a large modification it would be difficult to do without the agreement of all programmers because they would have to check-in and update all their WCs to this new revision.

All the new files should be changed to use UNIX-style endings. Make sure your editors are set to that.