Re: status update

[Jason Pincin <chardros@linuxkb.org>]

OK - question for the group, and partial defense on my part.

Between commits by me, the site is usally broken horribly - because I am
doing a lot of work with the object code, which the entire site is based
on, and when I break something in the object code, usually everything is
broken.

So - should I commit between development sessions of mine, even when
everything is broken?  Or should I wait til things are right?  It doesn't
matter either way to me as it will not affect my local box.

Anyone have ANY ideas on this issue?

I'm open to suggestions...

Jason



On Mon, Nov 15, 1999 at 09:42:52AM -0800, Aaron Turner wrote:
> 
> One thing that Daniel mentioned to me which is a downside, is that certain
> people (*cough* Jason *cough*) have this nasty habbit of commiting their
> code about once a month. Forcing people to commit their code to test it,
> does have the nice side effect that they can't get away with this anymore.
> 
> 
> 
> On Mon, 15 Nov 1999, Jason Pincin wrote:
> 
> > Personally - I think the developer box-in-a-box is a grand idea.  
> > 
> > On Mon, Nov 15, 1999 at 09:18:07AM -0800, Aaron Turner wrote:
> > > 
> > > (me trying to do these to set a good example)
> > > 
> > > - Working on Devel documentation- specifically how to create a copy of
> > > dev.linuxkb.org on your system at home to aid in development.  Started
> > > writing scripts to automate this 4+ hour task to something more
> > > manageable.
> > > 
> > > - LBF bug hunting.  Damn, I thought it worked, and now it don't.  Sux
> > > 
> > > - Search.pm.  No updates.
> > > 
> > > I'm interested in hearing from everyone if it would be worthwhile for me
> > > to spend 10 hours or so creating a "developer box in a box" tarball.
> > > Basically you download a 30MB tarball (or so), and run ./install.sh and 10
> > > minutes later you've got a fully functional development system.  The other
> > > two options are:
> > > 
> > > 1) Code at home, but to test your code you have to commit/webupdate.
> > > 
> > > 2) Download 30MB's of source from various websites, and then follow a
> > > lengthy document which tells you how to compile and install everything.
> > > 
> > > --
> > > Aaron Turner, Core Developer       http://vodka.linuxkb.org/~aturner/
> > > Linux Knowledge Base Organization  http://linuxkb.org/
> > > Because world domination requires quality open documentation.
> > 
> > -- 
> > Jason
> > http://vodka.linuxkb.org/~chardros
> > 
> 
> --
> Aaron Turner, Core Developer       http://vodka.linuxkb.org/~aturner/
> Linux Knowledge Base Organization  http://linuxkb.org/
> Because world domination requires quality open documentation.

-- 
Jason
http://vodka.linuxkb.org/~chardros