Subscribe to this blog and receive notifications of new posts by email.
Join 2,363 other subscribers
IRC Hours: Mon @ 1600 UTC & Thurs @ 1500 UTC
IRC Hours: Tues and Fri @ 2100 UTC
Backup: Scott Taylor
IRC Hours: Mon @ 1900 UTC & Thur @ 1600 UTC
Lead: Dave Martin
IRC Hours: Mon & Thur @ 2000 UTC
Lead: Sergey Biryukov
Lead: Lance Willett
Backup: Konstantin Obenland
IRC Hours: Tues & Thur @ 1700 UTC
Post items as replies to suggest agenda items for dev chat on July 22, 2009.
Jane Wells, Mark Jaquith, Denis de Bernardy, and 3 others are discussing. Toggle Comments
Meta tables, per DD32 last week.
So, RT last week: the meta tables stuff.
Possibly re-discuss committer workflow with rboren (and ideally matt) around. I think the key points were made today, though.
Ryan won’t be at today’s meeting due to a family emergency. Let’s hold this until next week.
[...] them on the agenda outline posts on the WordPress development updates blog. For example, Jane is currently taking submissions for items to be discussed during the July 22nd meeting which is this Wednesday. So far, meta tables [...]
I have several suggestions – am I still in time?
Agenda already up when this comment posted, can add to next week.
Discuss change in time for meeting as per results of whenisgood.net
Already on agenda, above.
Discuss closure of 2.0.x branch—I want to write a post on the .org blog officially announcing it and touching on some of the reasons why the branch was difficult to support in the last couple of years (mostly because the time period was so long that it made it impossible to keep up with security changes that weren’t just tweaks, but total rethinks of the way we handle certain stuff).
Explain my high level idea for reworking capabilities/roles and discuss potential shortcomings.
I thought it was dropped from Debian already?
We started the 2.0 LTS branch before it went into Debian, IIRC. The two things weren’t completely linked. Debian involvement was a royal pain in the butt and had no upsides that I could see (as much as it pains me to say that about my favorite distro).
The main problem was that the security changes going into trunk were so huge and interconnected with other stuff that merging them into 2.0 was a daunting task, because it wouldn’t just be adapting a patch, but writing completely new code to solve the problem in a way that didn’t depend on all the new stuff available in trunk. It got to the point that we had to say “this minor security issue is just not solvable in the 2.0 branch without disruptive changes” and once enough of those piled up, it seemed like a lost cause.
Five years is an eternity in this space—it was an unrealistic goal from the outset.
← The blog for our Summer of Code students…
Dev chat time: apparently in Europe some… →
License / GPLv2
Hosted WordPress.com |
WordPress.TV Videos |
WordCamp Events |
BuddyPress Social Layer |
bbPress Forums |