From: Petr Vorel <pvorel@suse.cz>
To: Cyril Hrubis <chrubis@suse.cz>
Cc: Xiao Yang <yangx.jy@cn.fujitsu.com>,
Richard Palethorpe <rpalethorpe@suse.com>,
ltp@lists.linux.it
Subject: Re: [LTP] [PATCH 4/5] doc: Add Release procedure
Date: Tue, 26 Sep 2023 15:39:31 +0200 [thread overview]
Message-ID: <20230926133931.GA159673@pevik> (raw)
In-Reply-To: <ZRLEmWtn8zaz9dL0@yuki>
Hi Cyril,
> Hi!
> > This slightly outdated document exists in LTP wiki, start versioning it
> > in the original repository. The only unversioned file in the wiki is
> > now Home.rest.
NOTE: "slightly outdated"
...
> > +3. Prepare tarballs
> > +-------------------
> > +[source,sh]
> > +--------------------------------------------------------------------
> > +cd ..
> > +git clone ltp ltp-full-YYYYMMDD
> > +cd ltp-full-YYYYMMDD
> > +# Update mce-inject submodule
> ^
> We do have a couple of submodules now, so this should be updated
I wanted to put my changes into separate commit, that's why I here just added
the original content. But if it makes more sense, I'll squash my change (next
commit) into this one.
> > +git submodule init
> > +git submodule update
> > +# Generate configure script
> > +make autotools
> > +# Prepare the archives
> > +cd ..
> > +tar -cjf ltp-full-YYYYMMDD.tar.bz2 ltp-full-YYYYMMDD --exclude .git
> > +tar -cJf ltp-full-YYYYMMDD.tar.xz ltp-full-YYYYMMDD --exclude .git
> > +--------------------------------------------------------------------
> > +
> > +4. Upload the tarballs to GitHub
> > +--------------------------------
> > +
> > +Click on 'releases' then switch to 'tags' then click on 'Add release notes' there should be 'Attach binaries ...' link at the bottom of the page.
> > +
> > +Don't forget to upload md5 and sha-1 sums for the tarballs as well.
> > +
> > +5. Send release announcement
> > +----------------------------
> > +
> > +Have a look at http://sourceforge.net/p/ltp/mailman/message/34429656/ to get the idea how it should look.
> ^
> This is now outdated, I guess that we should
> include a template rather than this?
I updated this in next commit to
https://lore.kernel.org/ltp/ZGNiQ1sMGvPU_ETp@yuki/
NOTE: I trust lore more than to our LTP ML - maybe we leave it one day, but I can use
link to our ML if you want. Or should I paste some text instead/with the link?
Kind regards,
Petr
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2023-09-26 13:39 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-20 9:53 [LTP] [PATCH 0/5] Release scripts and docs Petr Vorel
2023-09-20 9:53 ` [LTP] [PATCH 1/5] tools: Add a script for tagging the release Petr Vorel
2023-09-20 9:53 ` [LTP] [PATCH 2/5] tools: Add script for creating tarballs and metadata Petr Vorel
2023-09-20 9:53 ` [LTP] [PATCH 3/5] doc: Rename files to names from ltp.wiki.git Petr Vorel
2023-09-26 11:47 ` Cyril Hrubis
2023-09-20 9:53 ` [LTP] [PATCH 4/5] doc: Add Release procedure Petr Vorel
2023-09-26 11:46 ` Cyril Hrubis
2023-09-26 13:39 ` Petr Vorel [this message]
2023-09-20 9:53 ` [LTP] [PATCH 5/5] doc: Update release procedure Petr Vorel
2023-09-20 15:29 ` Petr Vorel
2023-09-20 15:39 ` Petr Vorel
2023-09-24 0:35 ` Li Wang
2023-09-24 21:14 ` Petr Vorel
2023-09-25 2:31 ` Li Wang
2023-09-25 12:50 ` Petr Vorel
2023-09-27 6:44 ` Petr Vorel
2023-09-26 12:14 ` Cyril Hrubis
2023-09-26 13:54 ` Petr Vorel
2023-09-26 14:23 ` Cyril Hrubis
2023-09-26 15:29 ` Petr Vorel
2023-09-21 8:18 ` [LTP] [PATCH 0/5] Release scripts and docs Li Wang
2023-09-21 8:43 ` Jan Stancek
2023-09-22 16:13 ` Petr Vorel
2023-09-26 12:22 ` Cyril Hrubis
2023-09-26 13:46 ` Petr Vorel
2023-09-26 13:48 ` Cyril Hrubis
2023-09-26 12:16 ` Cyril Hrubis
2023-09-26 13:41 ` Petr Vorel
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=20230926133931.GA159673@pevik \
--to=pvorel@suse.cz \
--cc=chrubis@suse.cz \
--cc=ltp@lists.linux.it \
--cc=rpalethorpe@suse.com \
--cc=yangx.jy@cn.fujitsu.com \
/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