| Message ID | 20230920095318.340582-5-pvorel@suse.cz |
|---|---|
| State | Changes Requested |
| Headers | show |
| Series | Release scripts and docs | expand |
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. > > Signed-off-by: Petr Vorel <pvorel@suse.cz> > --- > doc/LTP-Release-Procedure.asciidoc | 67 ++++++++++++++++++++++++++++++ > 1 file changed, 67 insertions(+) > create mode 100644 doc/LTP-Release-Procedure.asciidoc > > diff --git a/doc/LTP-Release-Procedure.asciidoc b/doc/LTP-Release-Procedure.asciidoc > new file mode 100644 > index 000000000..cd7682fb8 > --- /dev/null > +++ b/doc/LTP-Release-Procedure.asciidoc > @@ -0,0 +1,67 @@ > +LTP Release Procedure > +===================== > + > +This page contains quick summary of what needs to be done to do a LTP release. It's expected that LTP git is frozen and git HEAD was properly tested and that LTP git tree is cloned to a directory named 'ltp'. > + > +NOTE: The string YYYYMMDD should be substituted to the current date. > + > +1. Tag the git > +-------------- > + > +[source,sh] > +-------------------------------------------------------------------- > +cd ltp > +echo YYYYMMDD > VERSION > +git commit -s -m 'LTP YYYYMMDD' VERSION > +git tag -a YYYYMMDD -m 'LTP YYYYMMDD' > +-------------------------------------------------------------------- > + > +2. Push changes to github > +------------------------- > +[source,sh] > +-------------------------------------------------------------------- > +git push > +git push --tags > +-------------------------------------------------------------------- > + > +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 > +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? > +The announcement is send to: > + > +* ltp at lists.linux.it > +* linux-kernel at vger.kernel.org > +* libc-alpha at sourceware.org > + > +CCed to: > + > +* lwn at lwn.net > +* akpm at linux-foundation.org > +* torvalds at linux-foundation.org. > \ No newline at end of file > -- > 2.40.1 >
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
diff --git a/doc/LTP-Release-Procedure.asciidoc b/doc/LTP-Release-Procedure.asciidoc new file mode 100644 index 000000000..cd7682fb8 --- /dev/null +++ b/doc/LTP-Release-Procedure.asciidoc @@ -0,0 +1,67 @@ +LTP Release Procedure +===================== + +This page contains quick summary of what needs to be done to do a LTP release. It's expected that LTP git is frozen and git HEAD was properly tested and that LTP git tree is cloned to a directory named 'ltp'. + +NOTE: The string YYYYMMDD should be substituted to the current date. + +1. Tag the git +-------------- + +[source,sh] +-------------------------------------------------------------------- +cd ltp +echo YYYYMMDD > VERSION +git commit -s -m 'LTP YYYYMMDD' VERSION +git tag -a YYYYMMDD -m 'LTP YYYYMMDD' +-------------------------------------------------------------------- + +2. Push changes to github +------------------------- +[source,sh] +-------------------------------------------------------------------- +git push +git push --tags +-------------------------------------------------------------------- + +3. Prepare tarballs +------------------- +[source,sh] +-------------------------------------------------------------------- +cd .. +git clone ltp ltp-full-YYYYMMDD +cd ltp-full-YYYYMMDD +# Update mce-inject submodule +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. + +The announcement is send to: + +* ltp at lists.linux.it +* linux-kernel at vger.kernel.org +* libc-alpha at sourceware.org + +CCed to: + +* lwn at lwn.net +* akpm at linux-foundation.org +* torvalds at linux-foundation.org. \ No newline at end of file
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. Signed-off-by: Petr Vorel <pvorel@suse.cz> --- doc/LTP-Release-Procedure.asciidoc | 67 ++++++++++++++++++++++++++++++ 1 file changed, 67 insertions(+) create mode 100644 doc/LTP-Release-Procedure.asciidoc