Beng Tan

This morning (in my local timezone), I received word of a security vulnerability in an upstream component of ProsePoint. In this case, it was SA-CONTRIB-2009-046 - Date - Cross Site Scripting (http://drupal.org/node/534636) and it affects the Drupal Date module.

For most security updates, I simply patch ProsePoint, test, and release. It takes a few hours, but otherwise I just churn the handle. Usually the release is out within about 12 hours of the disclosure of the original announcement, well within the self-imposed 24 hours response time.

Since the early beginnings of ProsePoint, we've been using Launchpad Answers as a place for people to ask questions and receive general support. At the time, we were fully concentrated on getting ProsePoint to a usable state, and Launchpad Answers was a ready-made solution, so we gave it a try. It was worked fairly well, but we have since found that ... how shall we say it ... Answers was a bit limiting.

The ProsePoint website is under redevelopment, and will likely remain so for at least the month of January as changes are rolled out in stages. Prior visitors may have already noticed there is a completely new theme.

During this period, some pages may become slightly out of date, or some cosmetic bugs may arise. The timeliness of ProsePoint releases (and their respective release notes) will not be affected.

Please be patient with us as we prepare ProsePoint for the next exciting stage of existence. Thank you.

Over the last few weeks, we've received questions from interested users about ProsePoint themes, particularly about how ProsePoint themes differs from Drupal themes, and how to customise the default theme that comes with ProsePoint (tma2). After a few ad-hoc replies, we've decided it was time to devote some attention to ProsePoint themeing.

In hindsight, we always knew users would enquire about themes, we knew users will want to change something about their theme. We just didn't expect it to happen yet.

My bad. I botched up the ProsePoint 0.07 release, and had to re-release it.

It was a small mistake - the updates server destination for the ProsePoint modules was pointing to drupal.org instead of prosepoint.org, with the result that update status was displaying incorrect information.

That's been fixed now. However, instead of releasing the fix as a 0.08, I repackaged 0.07.