Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Joel Brobecker <brobecker@adacore.com>
To: Pierre Muller <muller@ics.u-strasbg.fr>, gdb-patches@sourceware.org
Subject: Re: Update ARI pages
Date: Wed, 24 Oct 2007 20:42:00 -0000	[thread overview]
Message-ID: <20071024204058.GO764@adacore.com> (raw)
In-Reply-To: <20071024200449.GH10943@caradoc.them.org>

> I played around with this for a bit.  Eventually I realized that
> this is in our release checklist already.  It's right below the
> bit that says how to update the online documentation.  Joel,
> you've been doing that bit - any particular reason you didn't
> do the ARI too?

No, I just missed it!

> Joel, I stumbled on the scary set of shell scripts in
> ~gdbadmin/gdb-release.

Ah, the cat is out of the bag... I wrote these scripts in preparation
to the gdb-6.7 release, wanted to have a couple of release cycles done
with them before I announced them. The number of scripts is indeed
scary, but this is mostly because there are lots of little steps to go
through during the release. Each step pretty much has its own script
(more or less).

The idea is that the scripts act as two things:
  - An electronic reminder of all the actions to be done, where I need
    to acknowledge all actions I'm supposed to do before the script
    moves on.  This is to avoid forgetting about the ARI for instance...
  - Do automatically what can easily be done automatically.

The conjunction of the two dramatically reduce the amount of time
it takes to produce a release (creating the branch took about 1h,
and so did producing the gdb-6.7 release).

The entry point for the scripts is one single script, called "release.sh".
It knows what you've done so far, and just picks up where you left.

I am not going to write more about this for now, as this is a bit
off topic for this thread. I intend to contribute this to GDB eventually
and re-write the documentation accordingly (describe the release process
as well as the internals of the scripts).

>   /bin/sh ~/ss/update-web-ari \
>           ~ftp/pub/gdb/releases/gdb-6.7.tar.bz2 \
>            $PWD/www \
>            /www/sourceware/htdocs/gdb/download/ari \
>            gdb

New script added :), so it should not be forgotten again. I ran
the new script manually, and checked the results on the web,
which seem fine. Let me know if there are some errors.

-- 
Joel


  reply	other threads:[~2007-10-24 20:41 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-10  9:07 [RFA] gdb_ari.sh patch to eliminate wrong critical errors Pierre Muller
2007-10-10 12:18 ` 'Daniel Jacobowitz'
2007-10-10 14:52   ` Ulrich Weigand
2007-10-10 15:04     ` 'Daniel Jacobowitz'
2007-10-10 15:27   ` Jim Blandy
2007-10-10 15:51     ` Mark Kettenis
2007-10-11  8:55   ` Update ARI pages Pierre Muller
2007-10-11 14:20     ` 'Daniel Jacobowitz'
2007-10-11 16:53       ` Joel Brobecker
2007-10-15  9:23         ` Pierre Muller
2007-10-24 20:07     ` 'Daniel Jacobowitz'
2007-10-24 20:42       ` Joel Brobecker [this message]
2007-10-24 21:06         ` Daniel Jacobowitz
2007-10-25  7:55         ` Pierre Muller
2007-10-11 19:41 ` [RFA] gdb_ari.sh patch to eliminate wrong critical errors Ulrich Weigand
2007-10-15 12:15   ` Pierre Muller
2007-10-15 13:47     ` 'Daniel Jacobowitz'
2007-10-15 13:50     ` Ulrich Weigand
2007-10-15 14:13       ` Ulrich Weigand

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=20071024204058.GO764@adacore.com \
    --to=brobecker@adacore.com \
    --cc=gdb-patches@sourceware.org \
    --cc=muller@ics.u-strasbg.fr \
    /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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox