Open-Beta Development Focus

[mark]

We're planning on launching open beta in mid-April.  That's about five weeks away at this point.  As such, I'm going to be going into a focused development mode starting in a few days.  What does this mean for you?  Well, it means you should keep the following things in mind:

 

* Everybody will be asked to take on bugs that are marked as 'blocking-open-beta' and prioritize those.

* I will only be doing reviews of patches that are for bugs in the open-beta list.  (Generally speaking.)

 

Does this mean nothing else will be done or worked on?  Not at all!  You are encouraged to work on whatever you find interesting.  I'd far rather have you working on something you want to work on that doesn't happen to be on the list than work on nothing at all.  :)

 

Also, Pau and Afuna will be reviewing everything they're comfortable with still.  It's just me that's hunkering down.

Any questions?  Fire away!
 

[bug 398] Discussion thread for bug 398

[denise]

This is the discussion thread for bug 398: Hash out golive process as it relates to translation items.

Let's build a spec here so we can get this fixed up ASAP.

(no subject)

[denise]

Have now:

* enabled target milestones in Bugzilla
* milestoned NEARLY EVERYTHING with when we should get it done by

Unmilestoned issues are either "I don't care, get it done whenever" (for minor things) or "prioritized past Q409" (for bigger things). Will work out best way to differentiate that sooner or later.

For information on how this all works, please see Roadmap on-wiki.

Basically, barring the special-case functional milestones of "B - Open Beta" and "L - Site Launch", "target milestone" means "we want to have this done by the end of this time period". From the Wiki:

Our two current milestones are functional: open beta and "site launch", which is when we will consider ourselves out of beta testing. After those milestones have passed, we'll use quarterly milestones: Q309, Q409, Q110, Q210, etc.

For the functional milestones, Target Milestone: Open Beta and Target Milestone: Site Launch means that the item should be finished before that goal.

For the date-based milestones, Target Milestone: QXXX means that the item should be finished by the final day of that quarter: "Q309" means that the item should be finished on or before September 30, 2009.

Blocking flags (blocking-open-beta+, blocking-launch+) means that the items are considered essential to that functional milestone.

It is entirely possible, and in fact expected, that "L - Site Launch" will extend into Q309 -- that's the overlap period between transition from functional milestones to date-based milestones. During that time, we'll be working on both sets of milestones.

(no subject)

[denise]

We'd like to participate in the Google Summer of Code, or at least submit a proposal to be accepted as a mentoring organization. What things do you guys think would be good candidates to put on our suggested projects page?

For instance:

* memories/bookmarks overhaul
* scheduled/draft posts
* GUI-izing the config/install process
* revamping the community maintainership model to Not Suck(tm)
* ...

Ideas?

EDIT: LJ's old Summer of Code page