Did you rebuild or did you just modify the previous builds?

http://svn.apache.org/repos/asf/incubator/roller/tags/ isn't very impressive currently, no 2.0.1 or 2.1 from the last release, and no 2.0.2 or 2.1.1 from this release. I know we're not releasing officially at Apache - but we need some way to build historical builds.

Looking at what I do have on disk (various RCs), the release looks good. The other differences I see are things that I think I recognise as RC issues fixed in those releases.

So +1, and can we have some tags?

Hen

On Tue, 14 Mar 2006, David M Johnson wrote:

VOTE to make emergency bug fix release:
  Roller 2.1.1
  Roller 2.0.2

Only code change in these releases: the 1.3 to 2.0 migration script
Existing 2.1 and 2.0.1 releases have been pulled from site

Background:

Brian Blakely discovered that the 1.3 to 2.0 migration script that was included in the Roller 2.0.1 and Roller 2.1 releases resets the weblogentry pubtime and updatetime fields, effectively destroying all blog entries by setting their dates to the current time. Since this is an extremely serious problem, I have pulled the Roller 2.0.1 and Roller 2.0.1 releases from the Roller download site at Java.Net.

Brian's bug report is here:
http://opensource2.atlassian.com/projects/roller/browse/ROL-1081

I have fixed this problem as described below, updated the CHANGES.txt files and created new releases Roller 2.0.2 and Roller 2.1.1 which are available at http://people.apache.org/~snoopdave/release_candidates

The change are in these files:
        WEB-INF/dbscripts/hsqldb/130-200-migration.sql
        WEB-INF/dbscripts/mysql/130-200-migration.sql
        WEB-INF/dbscripts/postgresql/130-200-migration.sql

These are the two changes:

- alter table weblogentry alter userid set default '';
+ alter table weblogentry alter userid set default '', pubtime=pubtime, updatetime=updatetime;

- update weblogentry set status='';
+ update weblogentry set status='', pubtime=pubtime, updatetime=updatetime;


- Dave

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to