By drupalnesia on

Ok, I have modified my module and I want to update the dev version of my module.
How to do it? I am using TortoiseCVS. I have tried to use "CVS Commit" but I see my dev version still not updated in drupal.org/project/.

⋅ Categories: Drupal 6.x

Comments

pobster’s picture

pobster commented

http://lmgtfy.com/?q=drupal+cvs+module+maintainers&l=1

Pobster

drupalnesia’s picture

drupalnesia commented

Still I can not find how to update the Dev version of my module. The link you gave me only tell how to create a new dev branch.

pobster’s picture

pobster commented

Actually it tells you everything you need to know, I get the feeling you just don't know what it is that you're reading?...

If you check out the dev version, then committing will update the dev version.

This'll make everything clearer (hopefully!) substitute the module name for your own;

http://drupal.org/project/gamertags/cvs-instructions

Pobster

drupalnesia’s picture

drupalnesia commented

Ok, let's me write the scenario here:

  1. Suppose I have 6.x-1.0-BETA2 on drupal.org
  2. On the local PC, I have edit the module, but before release 6.x-1.0-BETA3 I want to submit my changes to 6.x-1.x-dev

What do you mean by "check out the dev version"? How do I check out the dev version? Because when I do check out then I will receive the current version (in this case is 6.x-1.0-BETA2) and this will REPLACE all of my changes.

Also, in the "CVS Instructions" tab says:

Updating the development copy from the server

   1. From within the development copy:
      cvs update -dPr DRUPAL-6--1

Does above instruction mean I just need to run "cvs update -dPr DRUPAL-6--1" to sending my local changes to dev version on the server?

WARNING! After running "cvs update -dPr DRUPAL-6--1" then all of my changes gone! All modified files REPLACE by 6.x-1.0-ALPHA1 version!

pobster’s picture

pobster commented

You're reading ahead of what it is you need to know. Just take a little time to understand what it is that CVS is there for. You've checked out the wrong version initially to work on. So... Check out the dev version into a different folder, then just copy over what's in it with your changes and commit. Then (if you want) check out the dev version into where you actually want it to reside and delete the temporary folder.

CVS and SVN are great for versioning but the initial understanding learning curve of terminology and usage is quite high even for experienced developers who've never used it before. It's too much for me to explain everything here, but just understand that; in the majority of cases you'd work on the dev (HEAD) branch of a project then you'd tag it for a minor release (eg. DRUAPL-6--1-0-BETA2). This means that the dev version which Drupal packages automatically every night is always reflected and any time you wish to tag a release you do it off the development branch (obviously making a release/ release notes on the Drupal project page as well).

Pobster