Modules - start your porting
Hi all. It would be very helpful if module maintainers could soon start porting their modules to Drupal 6. Some big, important modules require multiple people to get this job done right (e.g. Views, CCK, ...). Let's help these maintainers. Porting modules now: - helps our beta testers run their sites to Drupal6 and report bugs. - identify hidden API limitations in core that only surface when modules start using new features (fapi, actions, etc.). the longer we wait, the harder it gets to make even minor API changes in 6. If you have reasons not to port now, then don't. But please don't use this thread to convince others to also wait. Porting early is a generous act which we want to encourage. The API will change very little now, so seize the day! -moshe
On Tue, Jul 03, 2007 at 03:34:48PM -0400, Moshe Weitzman wrote:
Hi all. It would be very helpful if module maintainers could soon start porting their modules to Drupal 6. Some big, important modules require multiple people to get this job done right (e.g. Views, CCK, ...). Let's help these maintainers.
And if someone is lazy like me: http://drupal.org/node/114774 -- GPG-Key: 0xA3FD0DF7 - 9F73 032E EAC9 F7AD 951F 280E CB66 8E29 A3FD 0DF7 Debian User and Developer. Homepage: www.foolab.org
On Jul 3, 2007, at 3:34 PM, Moshe Weitzman wrote:
It would be very helpful if module maintainers could soon start porting their modules to Drupal 6.
Agreed! To that end, now that the freeze is upon us, we really *must* make a final decision on my proposal for CVS branches: http://drupal.org/node/147493 The "DRUPAL-5" branch has been the source of much confusion in the contrib repo in terms of how it interacts with the release system. If you doubt this, I will get angry, since I've spent *dozens* of hours (re)explaining this to people via email, IRC and in the issue queues. I'm proposing we completely prevent anyone from creating a "DRUPAL-6" branch. Instead, when they're ready to branch their code for the 6.x-1.* series, they make a "DRUPAL-6--1" branch, just like they would make a "DRUPAL-6--2" branch for the 6.x-2.* series... This will help them remember that "DRUPAL-6--1" is only for 6.x-1.* code, and if they're doing something that's slated for a different series, it belongs in a different branch. Please comment in the issue: http://drupal.org/project/comments/add/147493 Ultimately, this is "RTBC", namely, it needs Dries's final approval or rejection. ;)
Some big, important modules require multiple people to get this job done right (e.g. Views, CCK, ...). Let's help these maintainers.
/me whimpers in the corner, wondering if help will be forthcoming to port project*... ;) Cheers, -Derek
Derek Wright wrote:
/me whimpers in the corner, wondering if help will be forthcoming to port project*...
Will it be better or worse than Views? =) (Mostly because the port is where I want to do a bunch of API changes so that all of the bumpy transitions are in the same place)
participants (4)
-
Derek Wright -
Earl Miles -
Mohammed Sameer -
Moshe Weitzman