You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@roller.apache.org by "David Johnson (JIRA)" <ji...@apache.org> on 2014/08/16 21:33:18 UTC
[jira] [Resolved] (ROL-2032) Test Roller 5.1 with blogs.apache.org
database & themes
[ https://issues.apache.org/jira/browse/ROL-2032?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
David Johnson resolved ROL-2032.
--------------------------------
Resolution: Done
Fix Version/s: 5.1
Done. Here's what I reported by to the mailing list:
I had some success testing 500-to-510 upgrade script against rollerweblogger.org and blogs.apache.org.
With rollerweblgger.org, I had to use a custom version of the script because the schema there is a mix of 5.0 and 5.1 stuff. Everything went fine and blogging features seem to be working.
With blogs.apache.org, I did the database upgrade manually, as I expect the Infrastructure will do and the migration script hit an error and exited with it hit that drop-index call for "folder_namefolderid_uq." I was able to omit that statement and get the rest of the upgrade to run successfully. I added a comment to the upgrade script template to note that the drop may fail, just so folks know it might be a problem -- it won't bea problem for people who choose the automatic install, which is what we encourage in the install guide.
I had to do some work to upgrade the two ASF themes used on blogs.apache.org, but after that, things looked good and I think we'll be ready when the blogs.apache.org chooses to upgrade.
> Test Roller 5.1 with blogs.apache.org database & themes
> -------------------------------------------------------
>
> Key: ROL-2032
> URL: https://issues.apache.org/jira/browse/ROL-2032
> Project: Apache Roller
> Issue Type: Bug
> Components: Installation & Configuration
> Affects Versions: 5.1
> Reporter: David Johnson
> Assignee: David Johnson
> Fix For: 5.1
>
>
> Bring up Roller 5.1 with local copy of the blogs.apache.org database, make sure that migration goes well.
--
This message was sent by Atlassian JIRA
(v6.2#6252)