By pobster on

Okay feeling pretty stupid so I've got to ask for help...

I made an initial commit of a module to BRANCH DRUPAL-4-6 which was fine, it was eventually packaged and available for download as a .tar - I noticed that when I commited a new version to CVS (using tortoise cvs in win xp btw) the .tar updated once or twice to the new version as well. But now... Nothing? I've updated lots of times since then and the .tar is still the same one from 5 days ago and my module is very progressed since then. Is this down to me? Or do the modules only get updated every now and then? I've not really understood particularly how this all work tbh... I just overwrite my old files in my cvs folder and click update, then commit... Should I be doing something with the BRANCH again? Like selecting cvs->branch->move/delete existing branch? Does that 'move over' my old code to the new stuff? Or should I be adding my new stuff to BRANCH MAIN? Bah :o) Just when I thought I knew what I was doing then I have alll these questions just to make absolutely sure ;o)

Please help! :o)

Thanks

Pobster
(Going to bed now, will hopefully read comments tomorrow morning!)

Comments

killes@www.drop.org’s picture

killes@www.drop.org commented

Which module?
--
Drupal services
My Drupal services

--
Drupal services
My Drupal services

pobster’s picture

pobster commented

tablemanager.module

In its current state it's pretty much complete. I just need to sort out the table sorting routines and implement a good way of having the user decide which columns to allow sort on, which one is default and whether to default to asc or desc order. Then it's aboslutely completely finished bar some tweaking with the CSV import. Anything I do to it after that will just be bug fix, new feature requests or upgrading to 4.7

Pobster

killes@www.drop.org’s picture

killes@www.drop.org commented

Here is what I think you should do:

1) get a checkout of the head branch
2) add your files there again
3) continue to fix bugs in the 4.6 branch and add new features and porting in the main branch
4) when done with porting to 4.7, branch from the head branch to the 4.7 branch using

cvs tag -b DRUPAL-4-7 tablemanager

(see allso FAQ.txt in the top level of the contrib repository (head branch))
--
Drupal services
My Drupal services

--
Drupal services
My Drupal services