Author: ronvoe122
Date: 2006-12-28 07:29:13-0800
New Revision: 10402
Modified:
trunk/ (props changed)
trunk/MIGRATION
trunk/README
Log:
Merged revisions 10375-10376 via svnmerge from
http://scarab.tigris.org/svn/scarab/branches/release/b21
........
r10375 | ronvoe122 | 2006-12-01 18:32:45 +0100 (Fr, 01 Dez 2006) | 1 line
Added migration notes for b21.
........
r10376 | ronvoe122 | 2006-12-01 18:42:59 +0100 (Fr, 01 Dez 2006) | 7 lines
Shortened the README:
- removed the hint to use cygwin on windows, it seems to be obsolete
(i had never the need for cygwin to compile and run Scarab)
- removed the confession that the user admin screen is crap,
that statement helps nobody.
- removed the section about db permissions. This is the domain of the
dba and she should know about it.
........
Modified: trunk/MIGRATION
Url: http://scarab.tigris.org/source/browse/scarab/trunk/MIGRATION?view=diff&rev=10402&p1=trunk/MIGRATION&p2=trunk/MIGRATION&r1=10401&r2=10402
==============================================================================
--- trunk/MIGRATION (original)
+++ trunk/MIGRATION 2006-12-28 07:29:13-0800
@@ -4,7 +4,7 @@
This document outlines data migration between versions of Scarab.
It aplies only for already existing installations, which are upgrading
-to b20. If you are building a fresh repository, you don't need to
+to b21. If you are building a fresh repository, you don't need to
follow this document.
This document is organized from most recent version to old version.
@@ -19,19 +19,82 @@
CONTENTS OF THIS FILE
-1. Upgrading the database from b19 (and a20) to b20
+1. Upgrading the database from b20 to b21
1.1 The quick step migration procedure
1.2 Details of the migration tasks
- 1.3 Upgrading from a20-dev or b20-dev (with Conditions) to released a20
2. Migrating from older releases
- 2.1 Upgrading from b18 and older versions
- 2.2 Upgrading from b15 to b16
- 2.3 Upgrading from b13 to b14
- 2.4 Upgrading from b13 -> cvs head -> b14
-
+ 2.1 Upgrading the database from b19 (and a20) to b20
+ 2.1.1 The quick step migration procedure
+ 2.1.2 Details of the migration tasks
+ 2.1.3 Upgrading from a20-dev or b20-dev (with Conditions) to released a20
+ 2.2 Upgrading from b18 and older versions
+ 2.3 Upgrading from b15 to b16
+ 2.4 Upgrading from b13 to b14
+ 2.5 Upgrading from b13 -> cvs head -> b14
,-----------------------------------------------------------------------.
-| 1. Upgrading the database from b19 (and a20) to b20 |
+| 1. Upgrading the database from b20 to b21 |
+'-----------------------------------------------------------------------'
+
+,-----------------------------------------------------------------------.
+| 1.1 The quick step migration procedure |
+'-----------------------------------------------------------------------'
+
+0. We assume, you have already built the b21 web application
+ either with Ant or with Maven.
+
+1. Change to the build/ directory of your generated web application.
+ From there run the database migration procedure as follows:
+
+ $ ant migrate-from-b20
+
+2. REMEMBER: Not all the information is inside the database!
+
+ If you're migrating a running Scarab, you'll want to check
+ that your attachments' directory and your search indexes are in their
+ supposed place after migration.
+
+ You can use the "scarab.attachments.repository" property to get you files
+ in an absolute folder outside Scarab's root directory.
+
+ It's also a good idea to recreate the search indexes after migrating
+ the system. Use 'Admin - Update search index' option in Scarab.
+
+,-----------------------------------------------------------------------.
+| 1.2 Details of the migration tasks |
+'-----------------------------------------------------------------------'
+
+This migration contains following database relevant modifications:
+
+ * SCB1640, SCB1672: Allow deleting issues,
+ Permissions for commenting and deleting issues
+ * mysql-upgrade-1.0b20-1.0b21-1.sql:
+ * new columns to allow deleting issues
+ * new seperated permissions for commenting and deleting issues
+
+ * New NotificationManager, which can be configured per activity type
+ and aggregates activities before sending emails for it
+ * mysql-upgrade-1.0b20-1.0b21-2.sql:
+ * new tables:
+ SCARAB_NOTIFICATION_STATUS
+ SCARAB_NOTIFICATION_FILTER
+ SCARAB_DEFAULT_NOTIFICATION_FILTER
+
+ * SCB1565: Include 'last modified' and 'creation' information in search results
+ * mysql-upgrade-1.0b20-1.0b21-3.sql:
+ * new column in SCARAB_R_MODULE_USER_ATTRIBUTE to store the 'internal attributes'
+ * dump and recreation of SCARAB_ISSUE with the new column (LAST_TRANS_ID) filled
+
+,-------------------------------------------------------------------------.
+| 2. Migrating from older releases |
+'-------------------------------------------------------------------------'
+
+This section deals with migration from older (pre b20) releases. You must
+ensure your system follow all the migration steps from your current version
+to b20, so you can then follow the procedure explained in 1.1
+
+,-----------------------------------------------------------------------.
+| 2.1 Upgrading the database from b19 (and a20) to b20 |
'-----------------------------------------------------------------------'
The migration to b20 contains following database relevant modifications:
@@ -43,9 +106,8 @@
Additionally, some improvements have been made since a20 was released
that will require an small database modification.
-
,-----------------------------------------------------------------------.
-| 1.1 The quick step migration procedure |
+| 2.1.1 The quick step migration procedure |
'-----------------------------------------------------------------------'
0. We assume, you have already built the b20 web application
@@ -79,7 +141,7 @@
the system. Use 'Admin - Update search index' option in Scarab.
,-----------------------------------------------------------------------.
-| 1.2 Details of the migration tasks |
+| 2.1.2 Details of the migration tasks |
'-----------------------------------------------------------------------'
1.) basic workflow capabilities
@@ -140,9 +202,9 @@
from where it is executed.
-,-------------------------------------------------------------------------.
-| 1.3 Upgrading from a20-dev or b20-dev (with Conditions) to released a20 |
-'-------------------------------------------------------------------------'
+,---------------------------------------------------------------------------.
+| 2.1.3 Upgrading from a20-dev or b20-dev (with Conditions) to released a20 |
+'---------------------------------------------------------------------------'
If you happen to be a user of a dev version between b19 and a20 supporting
the "conditional required attributes" feature, and you've used it, you will
@@ -218,15 +280,7 @@
WHERE ATTRIBUTE_ID = 0;
,-------------------------------------------------------------------------.
-| 2. Migrating from older releases |
-'-------------------------------------------------------------------------'
-
-This section deals with migration from older (pre b19) releases. You must
-ensure your system follow all the migration steps from your current version
-to b19, so you can then follow the procedure explained in 1.1
-
-,-------------------------------------------------------------------------.
-| 2.1 Upgrading from b18 and older versions |
+| 2.2 Upgrading from b18 and older versions |
'-------------------------------------------------------------------------'
If you upgrade from a release before b18, first migrate
@@ -279,7 +333,7 @@
These are no longer supported in any form.
,-------------------------------------------------------------------------.
-| 2.2 Upgrading from b15 to b16 |
+| 2.3 Upgrading from b15 to b16 |
'-------------------------------------------------------------------------'
Use the Ant data migration task:
@@ -290,7 +344,7 @@
,-------------------------------------------------------------------------.
-| 2.3 Upgrading from b13 to b14 |
+| 2.4 Upgrading from b13 to b14 |
'-------------------------------------------------------------------------'
With the latest release of Scarab b14, we have added new functionality
@@ -349,7 +403,7 @@
have the same domain for each module.
,-------------------------------------------------------------------------.
-| 2.4 Upgrading from b13 -> cvs head -> b14 |
+| 2.5 Upgrading from b13 -> cvs head -> b14 |
'-------------------------------------------------------------------------'
If you have upgraded from b13 to CVS head of Scarab before b14 was
Modified: trunk/README
Url: http://scarab.tigris.org/source/browse/scarab/trunk/README?view=diff&rev=10402&p1=trunk/README&p2=trunk/README&r1=10401&r2=10402
==============================================================================
--- trunk/README (original)
+++ trunk/README 2006-12-28 07:29:13-0800
@@ -10,8 +10,6 @@
directory. Note that a great deal of relevant information can be found in
the installation guide (see next section).
-
-
,-----------------------------------------------------------------------.
|Getting the installation guide |
'-----------------------------------------------------------------------'
@@ -29,7 +27,6 @@
maven xdoc:transform
-
The documentation set will be generated to
$SCARAB_ROOT/target/docs
@@ -38,30 +35,6 @@
$SCARAB_ROOT/target/docs/howto/build-howto.html
-
-
-,-----------------------------------------------------------------------.
-| W I N D O W S N O T E S |
-'-----------------------------------------------------------------------'
-
-Building Scarab on standard Win32 systems could be made easier and
-more failsafe. Volunteers to help with this effort are appreciated.
-Below are some notes that you will need to take into consideration
-when attempting to build Scarab. These notes do not apply to building
-Scarab on Unix systems.
-
-* We highly recommend that you install Cygwin instead of using
- the .bat files. The reason is that our primary focus is currently
- on Unix systems and not on running Scarab on Win32 systems.
- Volunteers to port shell scripts and keep things up to date
- are appreciated.
-
- You find the Cygwin package at
-
- <http://sources.redhat.com/cygwin/>
-
-
-
,-----------------------------------------------------------------------.
| K N O W N I S S U E S |
'-----------------------------------------------------------------------'
@@ -84,10 +57,7 @@
desire to have transparent cross database support (ie: don't send us
Oracle specific changes).
-#4. The user administration screens are buggy, badly coded and need to
- be completely redone.
-
-#5. Microsoft SQL Server requires you to edit the SQL scripts after
+#4. Microsoft SQL Server requires you to edit the SQL scripts after
generating them in the /target directory.
- Change all BIGINT's to INT's
@@ -98,24 +68,6 @@
the /lib directory.
- For more information see http://scarab.tigris.org/mssql.html
-
---------------------
-Database permissions
---------------------
-
-Things get a little tricky if you create the database with one user, and
-then Scarab connects as a different user. The problem is one of database
-permissions: Scarab requires full rights to all the tables in the Scarab
-database. Unfortunately, it seems that the permissions can only be
-granted on a per-table basis. There may be a script in the future that
-helps update the table permissions, but for now it has to be done
-manually.
-
-Of course, if Scarab connects as the user that created the database,
-you won't have this problem at all!
-
-
-
,-----------------------------------------------------------------------.
| Q U E S T I O N S / P R O B L E M S |
'-----------------------------------------------------------------------'
lmpx.com only provides a reader for public news (NNTP) servers. It is not
affiliated with the servers or forums shown here and is not responsible for
the content of articles, which is written by their respective authors.