public inbox for dwz@sourceware.org
 help / color / mirror / Atom feed
From: Tom de Vries <tdevries@suse.de>
To: Mark Wielaard <mark@klomp.org>, dwz@sourceware.org, jakub@redhat.com
Subject: Re: [PATCH] Release process improvements
Date: Fri, 12 Mar 2021 10:05:53 +0100	[thread overview]
Message-ID: <b422129d-e30c-e491-6a3a-7637eec0594a@suse.de> (raw)
In-Reply-To: <34d02fbd208931b2c4d309208cbd6d847807c764.camel@klomp.org>

On 3/11/21 4:32 PM, Mark Wielaard wrote:
> Hi Tom,
> 
> On Mon, 2021-03-08 at 14:13 +0100, Tom de Vries wrote:
>> Also, I realized it could be useful to have a release checklist to go
>> through.
>>
>> So:
>> - Use $(cat VERSION) in contrib/release/upload-release.sh to get
>> version
>> - Add git push commands to contrib/release/do-release.sh
>> - Add README.release-checklist
>>
>> Any comments?
> 
> Thanks that looks very useful.
> The only thing I don't know how to do is:
> 
> +- Update web page ( https://sourceware.org/dwz/ ):
> +  - Add news item with hlink to release annoucement.
> +  - Add entry in release list.
> 
> Do you need shell access to sourceware for this, or is there a special
> git repo?

I've forwarded the instructions that I got to access a CVS repo, and
those work for me.

That email also contains a suggestion on how to move things to git,
which might be a nice improvement.  [ I don't really understand how to
go about that, maybe you understand the suggestion better?  Anyway,
otherwise, we can ask for clarifications. ]

Thanks,
- Tom


  reply	other threads:[~2021-03-12  9:05 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-08 13:13 Tom de Vries
2021-03-11 15:32 ` Mark Wielaard
2021-03-12  9:05   ` Tom de Vries [this message]
2021-03-27 22:54     ` Mark Wielaard
2021-03-28  8:21       ` Tom de Vries

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=b422129d-e30c-e491-6a3a-7637eec0594a@suse.de \
    --to=tdevries@suse.de \
    --cc=dwz@sourceware.org \
    --cc=jakub@redhat.com \
    --cc=mark@klomp.org \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).