Home ›
Making a new release for your updated Drupal moduleMaking a new release for your updated Drupal module
Submitted by Benjamin Melançon on August 3, 2007 - 7:08am
Making a new release, using CVS tags and all that stuff you have to do, for your updated Drupal module. This should work for youth theme or install profile, also.
If you've been following the Agaric method of committing a project to Drupal's CVS you'll have a folder with a checkout for each of the Drupal versions you are maintaining your module for.
Just navigate to the one where you need to make changes, such as:
Ebony:~/workspace/agaricdrupal/registration_role/contrib-5.x-1.x
Barring weirdness it should be a simple matter of making necessary changes (OK, that might be complex) and, when you're happy (or bored) with your module in your local test environment, committing it.
cvs commit -m "commit message with credit as appropriate here"
then, if you're ready, preferably after the dev release has been tested, create a release by tagging the module.
Just a matter of best practice, even though we're presumably up-to-date, having just committed:
Ebony:~/workspace/agaricdrupal/registration_role/contrib-5.x-1.x ben$ cvs update -dP -r DRUPAL-5
Then, tag it! If you're current release on your project page (such as http://drupal.org/project/registration_role ) is 5.x-1.1 you'll probably want to release it as 1.2 using this cvs command:
cvs tag DRUPAL-5--1-2
That looks like this (.DS_Store is a Mac cruft file):
Ebony:~/workspace/agaricdrupal/registration_role/contrib-5.x-1.x ben$
cvs tag DRUPAL-5--1-2
? .DS_Store
? registration_role-menufix.patch
? registration_role.module_lines_screwy_in_vi
? test
cvs tag: Tagging .
T README.txt
T registration_role.info
T registration_role.module
Um, your module will probably have a lot fewer unused and ignored files in its directory...
Wait, you're not done!
For people to be able to see and download your latest official release, you have create a release through drupal.org.
You can do this on the module page itself when logged in (don't click edit, just scroll down below the existing releases and below "View all releases" you, as the maintainer, will have a special option, "Add new release") or from the My projects page: http://drupal.org/project/user
Make your release and within 12 hours it will be on your project page, replacing the last release for that branch, for all to see and download.
Making a new release, using CVS tags and all that stuff you have to do, for your updated Drupal module. This should work for youth theme or install profile, also.
If you've been following the Agaric method of committing a project to Drupal's CVS you'll have a folder with a checkout for each of the Drupal versions you are maintaining your module for.
Just navigate to the one where you need to make changes, such as:
Ebony:~/workspace/agaricdrupal/registration_role/contrib-5.x-1.x
Barring weirdness it should be a simple matter of making necessary changes (OK, that might be complex) and, when you're happy (or bored) with your module in your local test environment, committing it.
cvs commit -m "commit message with credit as appropriate here"
then, if you're ready, preferably after the dev release has been tested, create a release by tagging the module.
Just a matter of best practice, even though we're presumably up-to-date, having just committed:
Ebony:~/workspace/agaricdrupal/registration_role/contrib-5.x-1.x ben$ cvs update -dP -r DRUPAL-5
Then, tag it! If you're current release on your project page (such as http://drupal.org/project/registration_role ) is 5.x-1.1 you'll probably want to release it as 1.2 using this cvs command:
cvs tag DRUPAL-5--1-2
That looks like this (.DS_Store is a Mac cruft file):
Ebony:~/workspace/agaricdrupal/registration_role/contrib-5.x-1.x ben$
cvs tag DRUPAL-5--1-2
? .DS_Store
? registration_role-menufix.patch
? registration_role.module_lines_screwy_in_vi
? test
cvs tag: Tagging .
T README.txt
T registration_role.info
T registration_role.module
Um, your module will probably have a lot fewer unused and ignored files in its directory...
Wait, you're not done!
For people to be able to see and download your latest official release, you have create a release through drupal.org.
You can do this on the module page itself when logged in (don't click edit, just scroll down below the existing releases and below "View all releases" you, as the maintainer, will have a special option, "Add new release") or from the My projects page: http://drupal.org/project/user
Make your release and within 12 hours it will be on your project page, replacing the last release for that branch, for all to see and download.
Comments
Post new comment