missjwo

#!/usr/bin/env sh

##
#   Make your Mac feel like home...
#   Shoutout to @dtsn for being generally awesome and getting me started.
#
# install it:
#   curl -sL  https://gist.github.com/BenNunney/7219538/raw/f9b933cca93b67dd63a2d8b1eeebb69e87dc9591/feels-like-home.sh | sh
#

missjwo

Just dreamt of going to a conf to give a talk, but then on the day i get pulled for some shitty reason. @dshafik doesnt make it his session, but the organisers make me babysit a bunch of kids and leave the slot empty instead of asking me to fill it. 

I get really angry that i spent all this effort and money getting to the conf and the organiser tells me i should watch Orange is the New Black and it would explain it. 

I end up stood in the middle of a car park in this city, not wanting to walk in the same direction as the organisers. 

An attendee then finds me and tells me how i have inspired her and thanks me for the work ive done before and she asks me where im going. I tell her i wanted to go into the city to get food but didn't want to walk with the organisers. She offers to show me another way into town and I end up hanging out with her. 

She made the whole thing worth it. 

missjwo

Proposal for changing the WordPress versioning scheme

History

Currently, WordPress uses a incrementing numeric versioning system. XX.YY.ZZ could be read as ma.jor.patch which means version 4.8.1 can be read as version 48.1.

At the 2017 community summit, someone suggested that as WordPress project moves towards 5.0, that after 4.9 the versioning system should switch to semantic versioning by multiplying the versioning number by 10. This would mean the next version number after 4.9 woudl be version 50. The idea was shot down because if an end user is on 4.9 and then all of a sudden see the next version of WordPress was version 50; they would wonder where version 5-49 will freak out.

Proposal