Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.After an email exchange with Boris, I just committed a backport of the crud.inc split to the DRUPAL-5 branch. It now occurs to me that maybe I should have done that on a DRUPAL-5--2 branch. ;) However, given that up until now, profiles were encouraged to copy crud.inc into themselves, it didn't seem like a big deal to make a major change like this on the same branch -- folks using the old thing aren't going to be directly affected by the new release.
So, my question:
I'd like to cut a new official release now that there's an install_profile_api.module file in D5. Should I just call it 5.x-1.2 and be done with it? Or, should I fix up the backport I just did so that it's all on a DRUPAL-5--2 branch and call the next release 5.x-2.0? Any input from the other maintainers would be welcome.
Thanks,
-Derek
Comments
Comment #1
boris mann commentedI think 5.x-2 just to make it clear that there were major changes.
Comment #2
dwwOk, makes sense. I just created a DRUPAL-5--2 branch with the D5 version of install_profile_api.module and the crud.inc split, then backed out my changes to the DRUPAL-5 branch. See http://drupal.org/cvs?commit=154903. So, how about I make a 5.x-2.0-beta1 release?
Comment #3
boris mann commentedNice work on the issue queue communication. It's almost like you built the system!
Yes, go for it ... the rag tag band of install profile api developers usually randomly commits stuff and everyone uses dev checkouts. A little more discipline is good!
Comment #4
dwwhttp://drupal.org/node/339227