Zsh Mailing List Archive
Messages sorted by: Reverse Date, Date, Thread, Author

Re: release management

Bart Schaefer (schaefer@xxxxxxxxxxxxxxxxxxxxxxx) wrote:
> 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've only just started using it, but it's obvious already that
Tanaka's repository is first-class, and as he's doing such a good job,
it's pointless duplicating effort elsewhere.  Tanaka, would you mind
if we started viewing your repository in a (more) official light?

> I can't reliably commit into (nor even update from, based on
> attempts with the server Tanaka has set up) a remote CVS repository.

Might this be because of its location?  Even if it isn't, presumably
in an ideal world you'd want to work offline, build up a collection of
patches, and then somehow commit them locally which would put them in
a queue to be delivered to zsh-workers or the repository next time you
went online.  This would be great for me too, another `56K at best, 0K
at worst, 2K most of the time' sufferer.  However, I just realised
that it's not possible.  From the CVS info documentation:

      Note: when CVS is accessing a remote repository, `commitinfo' will
   be run on the *remote* (i.e., server) side, not the client side (*note
   Remote repositories::.).

So to be able to commit offline and do some clever queuing you'd need
a local copy of the repository, which brings us back to the
connectivity problem.

I just had an idea.  Tanaka, if it's not too much to ask of you and
your machine, what would you say to adding an entry in your
$CVSROOT/CVSROOT/loginfo file something like this:

  ^zsh  rsync -rlpt -e ssh $CVSROOT/zsh zshmirror@xxxxxxxxxxxxxxxxxxxxxxx:

(or put the rsync command in your crontab)?  Then we would have an
exact, read-only[1] mirror of your repository which might be quicker
to access for some people.  (I'd have to set up the zshmirror account
first of course, but this would be no problem at all.)  Likewise if
someone has a machine in the USA which could act as another mirror
then that would presumably greatly help Bart and others.  I could then
also set up automated nightly rpm builds (a la Mozilla Tinderbox
idea), which would be quite cute.

Add to this some sort of automated e-mail notification of which
patches actually make it into the repository, and I think we're
getting near a setup which satisfies everyone -- those who want CVS
have it, and those who don't, don't need it.  Thoughts?


[1] I guess that it would be way too risky/complex having a two-way
    read-write mirror, unless the concurrency issues can be resolved
    easily in some very cunning way (by using the existing CVS locking
    mechanism somehow?)

Messages sorted by: Reverse Date, Date, Thread, Author