Just a quick note that the Mozilla Firefox Extended Support Release (ESR) is now available. The ESR is based on Mozilla Firefox 10, and is intended to be used by organizations that deploy Firefox in a managed desktop environment. You can read more about the Windows, Mac, and Linux installers from the Mozilla website, and additional information can be found in the Firefox ESR FAQ. Organizations who use the Firefox ESR are also strongly encouraged to join the Mozilla Enterprise User Working Group; a discussion group focused on sharing information related to Firefox deployments.
I work with a great group of people at Mozilla, and a large part of how we function is through peer reviews of ideas, code, and the execution on them. those reviews tend to focus on the negative, which can be incredibly demotivating. I’ve found that I’ve fallen into the trap of giving criticism but not praise on more than one occasion, and I want to nip making that a habit in the bud. having this little note front and centre reminds me to start with what I like and why, and then move on to what I find that could use improvement, and some of the options I see that can help get there.
as a good friend of mine says, “two yes, one no” takes you a long way. criticism alone is draining. letting people know what you think they’re doing well is just as important as what you think they aren’t, and combining the two makes for an overwhelmingly positive experience that people can act on.
Update: Asa put a calendar up that is much better, as it covers all release channels, not just the main line.
because I am always, always trying to figure out when a particular release of Firefox is coming out.
big-assed disclaimer: this assumes unwavering adherence to releasing every six weeks. I will update this page if something happens.
also, New Year’s Day in 2013 is gonna hurt.
…because the other day got up to 36-ish, it seemed like the best way to celebrate was to make chili at 11pm. it’s a staple recipe I got from lee when I was living in NYC, and it’s worth sharing. probably not in 36-degree weather, but I’ll leave that up to you.
NOTE: if your herbs/spices aren’t fresh, you are missing out.
- 2 tbsp butter. yes, butter.
- 2 tsp diced garlic
- 1 large white onion, sliced thin (or sweet vidalia)
- 2 celery stalks, ends trimmed, sliced 1/4″ thick
- 1-2 tbsp olive oil
- 2 lbs skinless boneless chicken breast, trimmed of fat and cut into 1/2 to 3/4 inch cubes (can also mix 50/50 with thighs for a richer flavour)
- 3 cups chicken stock – bonus points for using fresh, but they’re a pain in the ass if you don’t plan in advance
- 1 can white kidney beans
- 2-3 fresh jalapeÃ±o peppers
- 1/2 cup fresh, chopped cilantro
- 2 tbsp flour
- 2 tbsp (good) chili powder
- 2 tsp ground thyme
- 2 tsp garlic powder
- 2 tsp cumin
- 2 tsp cayenne pepper
- 1/2 lb old cheddar cheese (aged 2yrs or more)
- sour cream
- tortilla chips (we prefer the blue corn chips)
- sliced baguette, to wipe up the leftover goodness
In a large (4qt) casserole pot (you can use a sautÃ©e pan, too, it just means more clean up), melt butter over medium-high heat. SautÃ©e diced garlic for 2-3 minutes; reduce heat to medium, add celery and onion, and sautÃ©e until tender (abt 5 min). Reduce heat to low, add white kidney beans (pro-tip, turn can upside-down and shake vigorously for 10s or so before opening to loosen the settled and sticking to the bottom beans) and chicken stock. Stir occasionally, ensuring mixture doesn’t boil strongly (slow boil/simmer is what you’re aiming for). The mixture will look watery. Don’t worry.
In a large mixing bowl (I prefer a large ziploc bag, as it simplifies things), combine chicken seasoning ingredients and mix well. Add cubed chicken to mixture and mix, ensuring chicken is well-coated.
Heat skillet/large fry pan on medium-high (about 300F). Add olive oil to skillet, and allow to heat (but not to smoking). Add coated chicken mixture to skillet and cook until done, turning often and breaking up clumped pieces often. Add cooked chicken to simmering stock mix.
Bring stock and chicken mixture to a slow boil (don’t go above medium heat, you’ve got time), and cook for approximately one hour, stirring often to help reduce the liquid. While the stock is cooking, broil or grill the jalapeÃ±o peppers until the skin is well-charred. Remove the charred skin, cut the peppers lengthwise, remove the seeds, and dice (note that you may want to use gloves for this, and you do not want to rub your eyes.) Set aside.
After the hour is up, reduce chili to a simmer, and add diced jalapeÃ±os to mixture (this is an optional step). Add the diced chilis to taste in small increments; you can increase the heat pretty quickly, and don’t want to add it all in one shot and potentially ruin things.
Simmer for an additional half-hour, and add diced cilantro to mixture. Simmer for an additional 15-30 minutes, and the mixture should thicken up nicely.
Serve in bowls with a dollop of sour cream and grated white cheddar. Garnish with a sprig of cilantro. Crunchy baguettes on the side are also recommended.
Done. Serves four-six.
On June 14th 2011 Adobe released updates for its Flash, Reader, and Shockwave plugins to address critical security vulnerabilities in those products. Also getting in on the update fun recently was Microsoft, with a new version of Silverlight and Oracle, who released an update to Java last week that addressed 17 security vulnerabilities.
If you use any of these plugins, you should update them as soon as possible.
If you are unsure of what plugins you have installed and whether they need to be updated, you can visit Mozilla’s Plugin Check. Plugin Check is a web app which helps you identify what plugins you have installed, whether they need to be updated, and where to get the updates.
so, how was your long weekend?
this was the first weekend in a while where we didn’t feel we should be building an ark. we decided to tackle the front porch, which was originally going to be replacing some rotten railings, which exposed a rotten structural member (the post), which exposed some rotten decking, and some really rotten steps.
which is pretty much how it goes when you start a small project to “fix” something on the house. saturday was gorgeous, and I spent most of it going back and forth to and from our local home building centre. they were laughing at me by the end of the day, except for the part where they gave me 8′ boards labeled as 10′. not funny, especially when you discover it 5 minutes after the store closes.
in any event, we now have a porch that’s been rebuilt, new steps, and a new colour scheme/paint job. we’ll continue working on them over the next couple days to finish assembly and railing installation, but it looks pretty damn good. we’ve dumped the ivy green on the posts and porch floor, and replaced them with white and clay (the same colour as the siding) respectively, and it looks great.
thatgirl (right) done good this weekend, and didn’t kill me even though she could have a few times. meg (left) threw in her hands to help out, and this pic is of the two of them working on the new stairs I built, and some of the porch trim.
this weekend really wasn’t a holiday. in addition to rebuilding and painting the porch we: opened the pool (and installed everything); weeded and mowed the lawn (two wheelbarrows of &^#% dandelions, and that’s probably 1/3); repaired the trimmer and trimmed everything that needed trimming, including the 4ft grass in the ditch that’s still filled with all the fscking water from the last month; cleaned out the garage; stowed the tarp and cleaned and pressure-washed the pool deck area; gave the people from robaxacet some well-earned cash.
it was a good weekend, and we packed three weekends of work into one. and now, we’ll have a nice dinner and sleep like logs.
what’d you do?
Build Your Own Browser will undergo maintenance on Saturday, January 14th 2011. We’ll be updating all repacks and performing server maintenance, which will require extended downtime. The service should be available by 09:00 Eastern on Sunday January 15th 2011, but maintenance may run longer. If you have any comments, questions, or concerns regarding this maintenance, please let us know through the “Contact us” link in the Build Your Own Browser application.