So this module is a bit odd, since it basically contains only the field migrate code. However, right now the only way to get at this code is through a 7.x-2.x-*dev* release, which is basically terrifying to any average person, regardless of how well it might work. :\ paints actually a pretty rosy picture; apart from the multigroup update path, there aren't any other critical issues. #1262808: Performance for content_migrate field data looks like a really nice performance improvement, too.

Porting status of contrib is cited as the #1 reason people aren't adopting D7, so a stable release of CCK would be awesome. I was wondering if it would be possible to tag issues in the queue as D7 stable release blocker if they're something that needs to be fixed before that happens, so we could try and get some helping hands on them?


greggles’s picture

Title: Blockers to a 7.x-2.0 release? » Blockers to a 7.x-2.0 stable release?

It would be great to get even a 7.x-2.0-beta1 or rc1 release.

I looked for critical bugs and it seems like there are just 2 right now.

colan’s picture

Version: 7.x-2.x-dev » 7.x-3.x-dev
Issue summary: View changes

I'm doing some maintenance on this project now that I'm working on a D6 -> D7 migration. What's confusing is that there's a 7.x-2.x-dev node, but no 7.x branches in Git. Until now, things have been committed to master.

To try and clean things up, I just created a 7.x-3.x branch (so as not to go below the latest 6.x version), and an alpha1 for what's currently in master.

I'll put out a beta for RTBCed issues once I get them committed.

colan’s picture

I just added an alpha2 with those RTBC issues commited. Once I confirm that the process works well enough, I can put out a beta then.

colan’s picture

Oh, and I'll tag anything I find that needs to be fixed before making this stable.

webchick’s picture

Awesome! Great to hear CCK is getting some love. :) Thanks, colan!

DamienMcKenna’s picture

Title: Blockers to a 7.x-2.0 stable release? » Plan for CCK 7.x-3.0 release
Component: Documentation » General
Category: Task » Plan
Priority: Major » Normal

It has only been ~4 years, no hurry.

colan’s picture

There are still a whole bunch of things that never got fixed. I'll check back here in another 4 years. ;)

rfay’s picture

Recommend a solution to the amazing data corruption (image URI overwrites) described in #1558192-22: Migrating image fields ended up swapping files to userpic