Supported web 2.0 workloads
To better support common Web 2.0 workloads, we're looking to identify common and popular stacks
Blueprint information
- Status:
- Complete
- Approver:
- Jos Boumans
- Priority:
- Low
- Drafter:
- Clint Byrum
- Direction:
- Approved
- Assignee:
- Clint Byrum
- Definition:
- Approved
- Series goal:
- Accepted for maverick
- Implementation:
-
Implemented
- Milestone target:
-
maverick-alpha-3
- Started by
- Thierry Carrez
- Completed by
- Clint Byrum
Whiteboard
Status:
memcached/
Complexity:
maverick-alpha-3: 2
Work items for maverick-alpha-2:
memcached - MIR (LP: #586634): DONE
libmemcached2 - MIR (LP: #586638): DONE
varnish - ensure 2.1.2 or later syncs into universe: DONE
libmemcached2 - python-libmemcached - pylibmc supersedes it and was synced recently from debian: DONE
libmemcached2 - libmemcached-
gearman - python-libgearman - package for universe (LP: #594469) awaiting sponsorship: DONE
Work items for maverick-alpha-3:
main - seed memcached and libmemcached into main: DONE
libmemcached2 - libmemcached-ruby - package for universe: POSTPONED
gearman - php5-gearman - package for universe (awaiting Debian sponsorship): DONE
gearman - gearman-java - package for universe: POSTPONED
varnish - ensure latest upstream is synced: DONE
libmemcached2 - libmemcached-
gearman - python-libgearman - upload to mentors and secure sponsorship: DONE
gearman - python-libgearman - sync from debian: DONE
mathiaz review/ 20100526
- looks good to me
jib review 20100526:
* Don't think we need to MIR the php bindings, especially given the comments in the wiki spec
* I can't really argue with this, removed (SpamapS)
* Would appreciate an estimated complexity
* Suggested subcycle: Alpha3 - low risk
* Suggested priority: 1 for memcache/
SpamapS 20100527:
* MIR's for memcached/
