On 2/24/06, Benson Wong <mostlygeek@gmail.com> wrote:
So some real world considerations:
1. Where is the long term roadmap to Drupal?
2. What is the long term support structure for Drupal - I spent $200,000 building Site X on Drupal 4.8, how do I maintain (security, new features, etc) it for 2 years?
3. I spent $15,000 building Module Y, for 4.7, what are my options for moving forward with 4.8, 4.9, etc.
4. And so on...
These considerations might not matter to geeks/developers adding in features, but it matters to people who depend on this software to provide them a solution. An similar situation, PHP3 disappeared quickly after PHP4 came out. PHP4 will be around for _years_, even after PHP6 comes out.
Drupal is headed in that same direction. My point is, the project needs more planning to balance reaction. Developers should be allowed to build any contribution they want, but core should not change so much as it breaks functionality between point releases.
Ben.
I completly agree with Ben. Due to many core changes i had to rewrite most of my development :( However, i have to admit the new FAPI is a great job and certainly won't change for years. Best regards