Added "clone", improved recent changes, fixed AAV & Solr, shipped new stable release

[Igal Koshevoy]

We're still looking for someone to help meet up with Joe to look at
Upcoming import issues, see this thread for details: http://bit.ly/2OjI2O

However, I made some progress elsewhere:
* Added a feature to "clone" an event. It lets you create a new
event based on an existing one. You'll find this in the an event's
sidebar. I used this to effortlessly create a flurry of new pdxfunc and
pdxruby meetings. The workflow is: search for an existing event, clone
it to get a new event form prefilled with the existing event's contents,
update the fields, and save. It's a quick and easy way to manually
create future events without relying on problematic programmatic recurrence.
* Improved recent changes UI. Each entry now has a human-readable
title rather than a record ID. And I've reorganized the columns to read
from left-to-right.

I also shipped a new stable release that contains code I've confirmed is
reliable in production, along with a fix so that creating a new DB and
migrating it will work again:
* v0.20090928
* [DEPENDENCY] + [MIGRATION] Implemented new data versioning and
management system that can track and rollback deletes and more, replaces
`acts_as_versioned` with `PaperTrail`.
* Fixed how Solr determines what port to connect to, it will now
always check the `config/solr.yml`.

-igal

[gabrielle]

On Thu, Oct 1, 2009 at 3:34 PM, Igal Koshevoy <ig...@pragmaticraft.com> wrote:
>    * Added a feature to "clone" an event. [...] It's a quick and easy way to manually

> create future events without relying on problematic programmatic recurrence.

Most excellent, Igal! Can't wait to check it out.

gabrielle