[development] CVS contribtions/sandbox changes

[Earnie Boyd]

Quoting "Frando (Franz Heinzmann)" <frando at xcite-online.de>:

>
> > The bad stuff is people using it as a place to store modules and
> > themes, this has always been a bad idea as you loose out the option of
> > using issues tracker, versions, and they are rarely included in
> > searches for any new wide spread security vulnerabilities.
>
> Of course you should publish working code as a module or a theme. But 
> what about pre-alpha, not-yet-working code, experimental stuff, mere 
> ideas that you want to share?

The use of CVS branches comes to mind.  A cvs branch is created to 
place code for development of new features for already released 
modules.  You then merge the HEAD and release changes using cvs 
functionality to do so and then commit your changes as appropriate and 
then clean up the branch.


Earnie
http://for-my-kids.com

--
--
******************************************************************************
* The user of this server has agreed to allow the use of a trailer in the    *
* mail that he sends for advertising purposes.  This advertisment is added   *
* by the server and is not in the control of the user of our services.       *
******************************************************************************

Toshiba Satellite P105-S6114 Notebook
http://give-me-an-offer.com/offers/computers/laptop/toshiba

PlayStation 3 Auctions
http://give-me-an-offer.com/offers/auctions/au1

Samsung HP-S4253 42" High Definition Plasma TV
http://give-me-an-offer.com/offers/tv/plasma