From: Mark Wielaard <mark@klomp.org>
To: "Santiago Ruano Rincón" <santiago@debian.org>
Cc: bzip2-devel@sourceware.org,
Anibal Monsalve Salazar <anibal@debian.org>,
Anthony Fok <foka@debian.org>,
Federico Mena Quintero <federico@gnome.org>
Subject: Re: Releasing bzip2 1.0.7 and 1.1.0 ? Was: [PATCH] bzip2: Fix return value when combining --test,-t and -q.
Date: Tue, 01 Jan 2019 00:00:00 -0000 [thread overview]
Message-ID: <c7957e5d2135cb1430ea335d825f453dee1b5924.camel@klomp.org> (raw)
In-Reply-To: <e27ad880caefea8f5955dcd98ad04e9726205788.camel@klomp.org>
Hi,
On Tue, 2019-06-25 at 02:05 +0200, Mark Wielaard wrote:
> So what about we do a conservative release of 1.0.7 from the current
> sourceware.org bzip2.git and simultaneously do a 1.1.0 release from the
> gitlab hosted git repo? Referencing each other as the "classic" and
> "modern" bzip2 versions.
>
> Then we can keep the sourceware.org bzip2.git around for ultra
> conservative releases based on the current build "system" (that
> basically only takes new security issues), using 1.0.8, 1.0.9, etc. But
> encourage people towards the 1.1.1, 1.1.2, etc. releases for a more
> modern experience, if at all possible.
I just pushed the following commit:
commit f1e937776c5f331e24cc63a9d8e7ae9445a76761
Author: Mark Wielaard <mark@klomp.org>
Date: Tue Jun 25 19:22:37 2019 +0200
Add prepare-release.sh script.
Script to run to prepare a new release.
It will update the release number and tell you to update the
CHANGES file and to double check everything looks before doing
the release commit and tagging.
Afterwards you probably want to run release-update.sh to upload
the release and update the website at https://sourceware.org/bzip2/
There are embedded version strings and dates in a couple of places.
To keep the script simple remove some that aren't absolutely necessary.
README now just points to CHANGES.
README.COMPILATION.PROBLEMS only mentions the version once at the top.
bzip2.c only mentions the version once when doing --version.
manual.xml now doesn't have any embedded versions, just uses &bz-version;
everywhere.
With that I think we are ready to do a bzip2 1.0.7 release simply by running
./prepare-release.sh 1.0.7 and ./update-release.sh 1.0.7.
So if the above sounds like a good plan, then we can execute it now.
Push out bzip2 1.0.7 and put the 1.0.x branch in hibernation, just for
security or major bug fixes. Then we can concentrate on making sure
that a bzip2 1.1.X (or maybe even call it 2.0?) has a modern build
system and adds things like O_CLOEXEC support, etc.
Cheers,
Mark
next prev parent reply other threads:[~2019-06-25 18:09 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-01 0:00 Mark Wielaard
2019-01-01 0:00 ` Santiago Ruano Rincón
2019-01-01 0:00 ` Mark Wielaard
2019-01-01 0:00 ` Releasing bzip2 1.0.7 and 1.1.0 ? Was: " Mark Wielaard
2019-01-01 0:00 ` Mark Wielaard [this message]
2019-01-01 0:00 ` Federico Mena Quintero
2019-01-01 0:00 ` Mark Wielaard
2019-01-01 0:00 ` Federico Mena Quintero
2019-01-01 0:00 ` Mark Wielaard
2019-01-01 0:00 ` Mark Wielaard
2019-01-01 0:00 ` Federico Mena Quintero
2019-01-01 0:00 ` Mark Wielaard
2019-01-01 0:00 ` Some cherry-picks (Was: [PATCH] bzip2: Fix return value when combining --test,-t and -q.) Mark Wielaard
2019-01-01 0:00 ` Federico Mena Quintero
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=c7957e5d2135cb1430ea335d825f453dee1b5924.camel@klomp.org \
--to=mark@klomp.org \
--cc=anibal@debian.org \
--cc=bzip2-devel@sourceware.org \
--cc=federico@gnome.org \
--cc=foka@debian.org \
--cc=santiago@debian.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).