Hi Guys,

Have noted that you are updating the dev version of starterkit to be compatible with the campaignion dev with regard to class renames and moving some classes around. It's great that these changes are being made!

Just wanted to ask a question about versioning policy. The makefiles included in the distro drupal-org.make and drupal-org-core.make still refer to the stable version of campaignion. I guess I was wondering if they should be tracking the dev version if you're making changes that only are compatible with dev campaignion. But I don't know enough about distributing a distro on d.o. to know if updating the makefiles has some other side effect that is undesireable.

Should there be some policy there, or is the dev version not the place to worry about keeping the pieces all synchronized until a release is planned?

Comments

torotil’s picture

torotil CreditAttribution: torotil at more onion commented

Hi,

yes that's a bit tricky and I think there is no good solution to it.

Using campaignion-dev in campaignion_starterkit-dev would mean that I'd have to switch to an fixed release for each campaignion_starterkit-release. That's one extra-todo for every release.

Internally we're using a list of dev-modules (=modules developed/maintained by more-onion that have changed since their last release) and dbuild.py allows us to --override those modules with the current checkouts.

Also breaking changes (like those from the last weeks) are not that common anyway. I see that they may be an annoyance for contributors though.

Thanks for bringing up the issue. I'll get back to you once I've thought about it some more.

torotil’s picture

torotil CreditAttribution: torotil at more onion commented

Sorry for the long silence. I still don't see a better solution for the makefiles. It might be time we'd publish our dbuild.py-files in some way.