The last 7.x beta was in October 2010 - http://drupal.org/node/945528

The last commit to 7.x was a month ago.

We also have this list of patches to be ported: http://drupal.org/project/issues/memcache?status=15&version=7.x

To get towards a stable 7.x release, I'd suggest we take the same approach we did with 1.8/1.9:

- release 7.x-1.x-beta3 - we could do that without any code changes, just as a marker. Make it clear there are known issues and ask for help with the queue.

- Once that's released, sync all tests between 6.x and 7.x so they're consistent (as much as possible).

- Commit/port any patches that fix test failures/critical issues first - this gives us a code base that's at least functionally equivalent to 6.x.

- Possibly release another beta at this point.

- Continue with ports between 6.x and 7.x.

- Once there are no ports or critical issues between 6.x and 7.x, we could release 7.x-1.0 (if patches go into 6.x-1.9 before then this could be co-ordinated with a 6.x-1.10 release).

At some point we should start requiring patches to be applied to both branches (or consistently 7.x first at least), but that's probably something to do after 7.x is caught up a bit.

Comments

catch’s picture

catch
he/him
Primary language English
commented

- Once that's released, sync all tests between 6.x and 7.x so they're consistent (as much as possible).

This is now done.

catch’s picture

catch
he/him
Primary language English
commented

Here's a new suggestion:

Syncing every issue between Drupal 6 and Drupal 7 is probably 20-40 hours of work, it's unlikely we'll have both branches in sync for a while yet.

However we know that 7.x memcache branch works mostly fine (at least compared to several stable Drupal 6 releases).

So I'm thinking instead of more betas, why not release a 7.x-0.1 (to make it clear it's not feature complete yet). We can get bugs fixed in the 7.x-0.x series, then forward port features like stampede protection and stats to new 7.x-1.x beta/rc releases after that, then release 7.x-1.0.

This doesn't change how stable the branch actually is, but it might prevent some complaints about the 7.x branch not being 'production ready' yet, while people still post brand new bug reports for < 6.x-1.9 which is silly on both sides.

berdir’s picture

berdir
Primary language German
Location Switzerland
commented
Status: Active » Fixed

We do have a 7.x-0.1 now and are quickly moving towards a 7.x-1.0, so I think this issue can be marked as fixed?

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.