Coffee on the Keyboard

Last week could have gone better. We tried to push SUMO 2.1 twice only to realize we had some issues with respect to replication that need to get ironed out.

We think we have a fix for these issues and are rounding out the tests for that fix, but we won’t really know unless we can test in a replicated environment. There are bugs open for IT to help us with that, and get replication set up for our staging server.

As Morgamic said, we’ll gather info, document, learn and innovate, then repeat next time.

And, as “unsuccessful” pushes go, these went really well. Both times we gave it an hour, then were able to back everything out and reset in another half-hour, coming in well under the downtime window.

Last week

• Tried to push 2.1, twice. It didn’t take.
• Filed IT bugs re: replication in staging.
• Started thinking about Q3 goals.
• Got the 2.2 (“questions”) branch rolling on Hudson.
• Helped get people on the same page w/r/t 2.3 deliverables and timeline. (At least we’ll say I helped.)
• Got all the people working on chat together.
• Worked out a potential solution to our replication issues with Jeff and Erik.
• Triaged 2.2—only about 5 bugs got moved out.
• Reviewed 2.2 UI work, and a number of subsequent patches.

This week (me)

• Have a timeline in place for 2.1 and 2.2.
• Figure out replication in staging with IT.
• Work out roughly what Q3 will look like.
• 1.5.5.1.
• Get enough sleep.

This week (team)

• Fix our replication issues.
• Continue on 2.2 and accelerate.
• Work with Cheng and Howse to get the AAQ done.

I missed last week. I blame the holiday on Monday. Also Erik started, which is very exciting!

Tomorrow afternoon is our planned push for SUMO 2.1, which is our new discussion forum component, and migrating the old data into that component. This is huge, since it’s the first new component serving content creation. (We’ve been running search results on Kitsune for a while now.)

Everything on our staging server feels faster on the Kitsune pages than the old pages. I can’t quite count to 2 loading a Kitsune page. I can usually get to 3 on a Tiki page. That in itself is a huge win, to me. On top of the speed, we’ve made some big leaps in our infrastructure and have done a lot of work that will directly enable 2.2, our support questions milestone

Last two weeks

• Closed out and reviewed a number of 2.1 bugs. Really, I lost count. It’s been fantastic to see the work spread out across the team.
• Got 2.1 ready to go out tomorrow!(!!)
• Fixed a number of small and last-minute 2.1 bugs.
• Helped Paul finish out the data migration work so he could focus on his last final and graduate! (Congrats, Paul!)
• Built avatars for users without them.
• Got email notifications to go out with some help from Jeremy.
• Welcomed Erik. Helped him get all the development environment stuff worked out.

This week (me)

• Get everyone introduced to Rypple.
• Navigate a smooth 2.1 launch.
• Poll the team about a SUMOdev on-site.
• Finish reviewing Ricky’s 2.2 UI work.
• Triage 2.2 and focus the bugs.
• Help everyone figure out deliverables and timelines for 2.3 mockups as best I can. (Mostly I’ve done what I can here, I think.)

This week (team)

• Launch 2.1. Smoothly.
• Go go go on 2.2. On staging the day (evening?) after 2.1 launches.
• Start spreading around reviews more.
• Help triage 2.2 and focus it.