This is a bad practice and you should not do it:

[azurelunatic]

I am still very angry with whatever dick in product management felt that it was necessary or appropriate to combine the following two sentiments:

"I am so excited about the upcoming product release! The date has been pushed up! THIS IS WONDERFUL!"

"In order to accommodate the upcoming early release of this product, some features were dropped. This very popular feature was one of them."

This results in "I'M SO HAPPY YOU'RE NOT GETTING THE FEATURE YOU NEED TO DO WHATEVER IT IS THAT YOU DO, BUT AREN'T YOU GLAD YOU'LL BE GETTING A NEW CRAPPY VERSION SOONER?"

No. No, I am not happy, and I am angry that you are so happy about this. Please go rinse your inbox with an appropriately destructive kind of acid, and let's never speak of this again.

When announcing something that you know is going to be bad news, on the ticket for the feature in question, the early release of version mango-shitting-cockatoo (the upgrade from destructive-parrot) is a neutral thing at best, not a good thing. You can be as exited as you want on the main blog, or in the press releases, and you can link to the main blog or press releases, but on the bug itself, this is a neutral thing.

It might even be appropriate to apologize for the inconvenience and disappointment. But "I'm excited to announce", multiple exclamation points, and "cheers" in the ticket itself? What the actual fuck, man.

Comments

[asciident]

Ugh, I hate when they do that. Take your time and do it right.

[azurelunatic]

I'm not even opposed to an early release provided there's some evidence that they've put some thought into why -- but that much glee about it in the stuff that got dropped is beyond tacky.