zsh-workers
 help / color / mirror / code / Atom feed
From: "Bart Schaefer" <schaefer@candle.brasslantern.com>
To: zsh-workers@sunsite.auc.dk
Subject: Re: release management
Date: Wed, 3 Nov 1999 08:20:52 +0000	[thread overview]
Message-ID: <991103082052.ZM3082@candle.brasslantern.com> (raw)
In-Reply-To: <19991102165034.A12065@thelonious.new.ox.ac.uk>

On Nov 2,  4:50pm, Adam Spiers wrote:
} Subject: Re: release management
}
} I may be wrong, but it seems to me that the key developers amongst us
} don't feel an urgent need for some central CVS (or other)
} repository[0].  This is presumably because after years of hacking
} they're genuine gurus when it comes to applying patches of all
} different shapes, sizes and ages to zsh.

In my case, it's because I do all my zsh work at home, where my net
connection is only 56K at the best of times (usually slower).  I can't
reliably commit into (nor even update from, based on attempts with the
server Tanaka has set up) a remote CVS repository.  If patches stopped
appearing on the mailing list, I'd quickly be as far out of it as you
now believe yourself to be, or else I'd have to set up some kind of
two-stage download through a machine at the office. [*]

} trying to keep up to date is taking so much of the time I allocate for
} zsh hacking, that in the last few weeks[1] I've been unable to do
} anything useful
[...]
} [1] It's become harder since the regular intermediate releases stopped.

I'm trying to see to it that they haven't stopped, just gotten farther
apart, but I'm at if not over my limit on zsh-time.

} As I think I mentioned before, if no-one else wants to do it, just say
} the word and I'll immediately set it up myself on a reliable RedHat
} box[3], with write-access for whoever volunteers as coordinator.

Aside from the unresponsiveness of the staff at sunsite.auc.dk lately,
I think in fact that a volunteer coordinator is the missing bit.  We've
had several offers of places to put such a thing, but no one with the
bandwidth (time and network together) to run it.

} I could even set up a commit mechanism so that commits from anonymous
} read-only users would not get committed but instead forwarded to this
} list for approval, or similar.

I think something like this is going to be essential.

[*] To get the copy from which I made bart-8, I checked out from Tanaka's
    server while at work, then made a tarfile and scp'd that home.

-- 
Bart Schaefer                                 Brass Lantern Enterprises
http://www.well.com/user/barts              http://www.brasslantern.com


  reply	other threads:[~1999-11-03  8:21 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-10-27 14:40 Clint Adams
1999-10-27 14:50 ` Ollivier Robert
1999-10-27 14:52   ` Clint Adams
1999-11-02 16:50   ` Adam Spiers
1999-11-03  8:20     ` Bart Schaefer [this message]
1999-11-04 20:33       ` Adam Spiers
1999-11-04 20:39         ` Clint Adams
1999-11-04 20:47         ` Dan Nelson
1999-11-05  2:21           ` Tanaka Akira
1999-11-05 16:28             ` Adam Spiers
1999-11-05 20:21               ` Clint Adams
1999-11-05 22:39                 ` Dan Nelson
1999-11-06 11:35                   ` Adam Spiers
1999-11-08 14:18                   ` Clint Adams
1999-11-08 17:12                     ` Adam Spiers
1999-11-03  8:22 Sven Wischnowsky

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=991103082052.ZM3082@candle.brasslantern.com \
    --to=schaefer@candle.brasslantern.com \
    --cc=zsh-workers@sunsite.auc.dk \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/zsh/

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).