Although Django's release cycle is generally date-based, we also try to keep our release dates flexible to account for bugfixing time. At the beginning of the development sprints at PyCon a few weeks ago, over 300 tickets were still open on the Django 1.2 milestone. Now it's down to 120 (we've been clearing out, on average, about ten tickets a day), but that's still a lot more than we're comfortable shipping; as a result, we're pushing back the final 1.2 release a bit.

The poster describes what the user needs (obviously, a phone and a service that allows to scan QR code), the different steps to make it work (I like the “Confirm the Internet connection” phase) and a warning that you should check with your mobile phone carrier what would be the price of such transaction. As usual with technological innovations, the stake-holders try to help potential users and give a large amount of details that make the poster as long as the schedule poster. Of course there are two supposed expectations from this long description: (1) Teaching people how to use a technical objects (the QR code scanning process that can help to get real-time information), (2) Once the lesson learned it will be OK to remove this description and only keep the two QR codes.