Life changes

i finaly done gradeeated! Ain’t no one can say im an uneducated fool. They have to drop the adjective now. ;-) It’s time for me to bid a fond farewell (good riddance!) to graduate school.

In about a month, I’ll be moving to a magical, far away place where the sun is always shining and the air smells like warm root beer and the towels are oh so fluffy to start a new job. The job search took longer than I expected, but I ended up being really lucky. I had four favorites from among the list, and I hit a jackpot: got offers from three places, all from among those top four. I had a hard time choosing between them, knew that I’d be second guessing myself regardless of which one I picked, but ended up picking the postdoc position at Sandia National Laboratory last month (despite being a temporary position–maximum 6 years). I’ll be in the Thermal/Fluid Computational Engineering Sciences Department. It’s time for an exciting adventure!

I guess this means I’ll have to be removed from the Utah Open Source Planet, but GNOMErs should definitely expect to see me remain involved in GNOME. I’m sure the new job and home ownership will have some affect on how much I can be involved. I don’t know how much yet, but I do know that I’ll still be around. I’ll play it by ear and resign from some of my responsibilities when/if needed.

Reminder: The stable branch is still frozen

…and will be for the rest of forever. The hard code freeze is lifted with the .0 release, but API/ABI, feature, UI, and string freezes remain in effect.

It appears we (the release-team) have failed to communicate that any API/ABI, feature, UI, or string change or addition for the stable branch needs to be approved. I’ve been surprised multiple times in the past (most recently today) that there are developers who do not know that most freezes remain in effect after the .0 release goes out the door. This includes some pretty core hackers. Does anyone have suggestions on how we can make sure to get the word out better? (We’ve mentioned this fact on the 2.17 schedule next to the 2.18.0 release, on the new (which in general is the fastest way to get a reminder of which freezes are active during any cycle), and we have sent reminders in the past to devel-announce-list.)