> > as it turns out that the engines concept from rails 2.3.x is totally > different then needed by communityEngine and will never be a fit for > CE if not CE itself change a lot. > What? The Engines plugin still works in 2.3, so it's a non-issue.
So my question is: why should I still start using CE today and > sticking to some outdated railsversion which could be a problem sooner > or later with some other code, not to mention you will lose all the > nice features the new rails relalease comes with This is incorrect. Just because we haven't released a 2.3 compatible version YET, doesn't mean we never will. The next version release of CE will be Rails 2.3 compatible. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "CommunityEngine" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/communityengine?hl=en -~----------~----~----~----~------~----~------~--~---
