From: Mark Wielaard <mark@klomp.org>
To: "Federico Mena Quintero" <federico@gnome.org>,
"Santiago Ruano Rincón" <santiago@debian.org>
Cc: bzip2-devel@sourceware.org,
Anibal Monsalve Salazar <anibal@debian.org>,
Anthony Fok <foka@debian.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: <b362ae8fc895d46a669a160257f27aa9d2f421ac.camel@klomp.org> (raw)
In-Reply-To: <3b31bd0d2d1119ce7ded04b383a0db7f0576c50b.camel@klomp.org>
On Wed, 2019-06-26 at 12:55 +0200, Mark Wielaard wrote:
> On Tue, 2019-06-25 at 21:22 -0500, Federico Mena Quintero wrote:
> > What do you think of me doing this:
> >
> > - Create a "bzip2-1.0" branch with the commits and contents of the
> > sourceware repo.
> >
> > - Sync the sources? Are there any changes in the gitlab master
> > branch
> > that you *don't* want?
> >
> > - Release 1.0.7 out of the bzip2-1.0 branch; deprecate that branch
> > immediately. Advertise it as targeting people who embed bzip2-1.0.6
> > in
> > their sources and probably already have customizations to the build
> > system themselves.
> >
> > - Continue with the current development in the master branch; I'll
> > probably release 1.1.0 as an experimental release with the new build
> > stuff and all the fixes. Advertise this as targeted to distros and
> > everything else.
> >
> > - Rust goes in a separate branch as usual; it's going to need some
> > big
> > changes to the new build system anyway.
>
> I would like to do the release from the sourceware.org git repo first
> as is. And only then create a 1.0.x branch from it. That way we have
> something that simply replaces the bzip.org releases and establishes
> https://sourceware.org/bzip2/ as new (or technically old) home for
> bzip2, have an official download location, updated regenerated manuals,
> etc. Then we can tweak the homepage through bzip2-htdocs.git to point
> to a future development tree if you don't like to use the sourceware
> bzip2.git repo as main development platform.
OK, lets go with this plan. There is this outstanding CVE and people
have been asking for a release to resolve it.
I'll run the prepare-release.sh and release-update.sh scripts creating
the 1.0.7 release and will then update bzip-htdocs.git to add a pointer
to the homepage for the current development future 1.1.x development
branch https://gitlab.com/federicomenaquintero/bzip2 for people who
want a new build system and more fixes.
I'll sent mail to the list when done.
Cheers,
Mark
next prev parent reply other threads:[~2019-06-27 18:01 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
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 [this message]
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=b362ae8fc895d46a669a160257f27aa9d2f421ac.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).