Okay, you've made some updates, now it's time to update Drupal. This is the same technique you'll use to create your first "official" release (all your work so far has been in the "-dev" release that you created in the beginning).
But first, are you following my recommendations? Have you run the Coder review and fixed all the flags? Have you created a new translation template? Good for you!
Time to commit the files, if they haven't been already. Right-click on the module folder again and select CVS Commit. All of the files in your module folder will be selected automatically; make sure it also knows about files in subfolders (sometimes it forgets). These files will update the current "-dev" release. In the Comment field, add something like "Fixes for bug #123456" and press OK.
Note that it may take several hours before an updated "-dev" release is available - this is normal.
Hint: Don't close your issues yourself; mark them "fixed." After a week or so of inactivity, the DO system will close it for you. When you see that happen, it is a reasonably good assumption you didn't cause any new problems and you can proceed with creating an official release.
DRUPAL-6--1-1
DRUPAL-5--1-1
DRUPAL-4-7--1-1<
An official release will generally be available within five minutes of being committed.
You've seen that little link next to the release identifier; well you get to maintain that now. Click on that link, or the "Edit" next to it, and, strangely enough, you will see an "Edit" tab. You know what to do.
Recent comments
12 years 5 weeks ago
12 years 5 weeks ago
12 years 16 weeks ago
12 years 21 weeks ago
12 years 44 weeks ago
13 years 2 weeks ago
13 years 9 weeks ago
13 years 9 weeks ago
13 years 15 weeks ago
13 years 18 weeks ago