Twitter and the developers who use its platform haven’t been on the best of terms lately.

The company has cracked down on developers who’d made Twitter clients that essentially replicate Twitter’s own features, like posting and reading tweets. It has released a new, more restrictive application programming interface (API). It has given the cold shoulder to LinkedIn and disconnected india app developer IFTTT. It has enforced rules that have left some startups feeling angry, confused, and desperate.

Now it’s trying to soften the blow of its many API changes, with a calendar showing what’s in the Twitter API pipeline.

It’s a useful gesture, because much of the outcry over Twitter’s API and rule enforcement has come from developers who simply weren’t aware of (or didn’t pay attention to) Twitter’s many, repeated signals about what it’s going to do.

Twitter stresses that the calendar is not a replacement for the full firehose of information on @TwitterAPI and the Twitter developers’ blog. You might read the company’s developer rules of the road for good measure too.

Currently, the calendar lists just two upcoming items: Retirement of the @Anywhere API, and, much more significant, the retirement of Twitter API 1.0. Both happen on March 5, 2013.

Mark your calendars.

Mayan calendar photo by NY-P/Shutterstock.