| 1 |
/* $Id: README.txt,v 1.2 2008/05/31 05:12:59 sun Exp $ */
|
| 2 |
|
| 3 |
-- SUMMARY --
|
| 4 |
|
| 5 |
Upgrade Status module was designed to provide an easy way tell when your website
|
| 6 |
is ready to be upgraded to the next Drupal version. The module will compile a
|
| 7 |
list of your projects along with a status, which can be one of the following:
|
| 8 |
|
| 9 |
* Available: A stable release of this project is available.
|
| 10 |
* In development: A development release of this project is available, which can
|
| 11 |
be installed for testing purposes.
|
| 12 |
* Not ported yet: There are no releases available for this project.
|
| 13 |
|
| 14 |
Clicking on any of the modules' boxes will expand the area and show you a link
|
| 15 |
to download the new version of the project, as well as read its release notes.
|
| 16 |
|
| 17 |
If one or more of your installed modules are not yet ported to a new Drupal
|
| 18 |
major version, you should
|
| 19 |
|
| 20 |
1) search the modules' issue queue for already existing issues that might
|
| 21 |
contain a patch, and test that patch yourself. See
|
| 22 |
http://drupal.org/patch/apply for further information.
|
| 23 |
|
| 24 |
2) go ahead and install Coder module (http://drupal.org/project/coder), use its
|
| 25 |
code review rules for migrating a module to the new Drupal version, create a
|
| 26 |
patch, and file a new issue against that project with your patch attached.
|
| 27 |
See http://drupal.org/patch/create for further information.
|
| 28 |
|
| 29 |
If you've checked your projects out from CVS, you will need the CVS Deploy
|
| 30 |
module (http://drupal.org/project/cvs_deploy) in order for this module to be
|
| 31 |
able to read versions.
|
| 32 |
|
| 33 |
|
| 34 |
For a full description visit the project page:
|
| 35 |
http://drupal.org/project/upgrade_status
|
| 36 |
Bug reports, feature suggestions and latest developments:
|
| 37 |
http://drupal.org/project/issues/upgrade_status
|
| 38 |
|
| 39 |
|
| 40 |
-- REQUIREMENTS --
|
| 41 |
|
| 42 |
* Update Status
|
| 43 |
http://drupal.org/project/update_status
|
| 44 |
|
| 45 |
|
| 46 |
-- INSTALLATION --
|
| 47 |
|
| 48 |
* Install as usual, see http://drupal.org/node/70151 for further information.
|
| 49 |
|
| 50 |
|
| 51 |
-- USAGE --
|
| 52 |
|
| 53 |
* Go to Administer >> Logs >> Available updates >> Upgrade status and check the
|
| 54 |
status of your installed modules.
|
| 55 |
|
| 56 |
|
| 57 |
-- CONTACT --
|
| 58 |
|
| 59 |
Current maintainers:
|
| 60 |
* Daniel F. Kudwien (sun) - dev@unleashedmind.com
|
| 61 |
|
| 62 |
|
| 63 |
This project has been sponsored by:
|
| 64 |
* UNLEASHED MIND
|
| 65 |
Specialized in consulting and planning of Drupal powered sites, UNLEASHED
|
| 66 |
MIND offers installation, development, theming, customization, and hosting
|
| 67 |
to get you started. Visit http://www.unleashedmind.com for more information.
|
| 68 |
|