[clue-admin] CVS Publishing Script

[grant johnson]

The reason we use the tags is that the latest version is not always
what we want.  Often there is something that needs to go right away,
while other things are not done yet.  We often still commit things
that are not done to allow colaborative work on them.

I do not understand why it is a bad thing to have the CVS folders
available to the world.  The information in them should be benign. 
CVSROOT=/home/cvsroot or :pserver:anonymous at localhost:/home/cvsroot 
Nothhing all that secret or security dangerous there, especially if it
is a locally mounted FS, even if it is a pserver, if it is publically
open, someone who wants in will have already port scanned 2401.

As for limiting who can and cannot tag, it is easy, if you need it,
let me know.  There is one thing I want in exchange, though.  It is
under the GPL, so, if you make it cooler......


On Fri, 17 Dec 2004 00:32:06 -0700, Jed S. Baer <thag at frii.com> wrote:
> On Thu, 16 Dec 2004 21:55:36 -0500
> grant johnson wrote:
> 
> > Do not do a -D in the export, it is TOO limiting.  Do the export by
> > tag!  Create a tag that means the current dev or test or production
> > site, then create more that denote each logical version, then you can
> > roll forward or back through version easily while keeping everything
> > in sync, and allowing you to release one thing, while working on
> > another in colaboration.
> 
> Is that a voice from the past I hear? :)
> 
> Tags are a bit cumbersome for the way we update the site right now.
> Sometimes I do several updates in quick succession -- not often, but it
> happens. And I haven't found any need to roll forward/backward.
> 
> > We do this via CVS with 150 developers on a multi-terabyte database
> > project with a 1GB+ CVS repostory.  i can help with the details if you
> > like.  It rocks.  Everyone can commit, but only release managers are
> > allowed to do the tags that cause the promotions, define the releases,
> > or assign releases to environments.  It is actually very easy to do.
> 
> And on the CLUE website, every commit gets immediately promoted to
> "production". And it's usually immediately following this that I notice a
> typo or spelling error, and do a second one within about 5 minutes.
> 
> I'd be interested in how it's possible to limit tagging to a subset of
> those with commit privileges. Not that we have that as an issue here, but
> it'd be good to tuck into some corner of my brain, where, I hope, it won't
> get lost in the fog.
> 
> jed
> --
> http://s88369986.onlinehome.us/freedomsight/
> 
> ... it is poor civic hygiene to install technologies that could someday
> facilitate a police state. -- Bruce Schneier
> _______________________________________________
> CLUE-admin mailing list
> CLUE-admin at clue.denver.co.us
> http://clue.denver.co.us/mailman/listinfo/clue-admin
> 
>