From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on dcvr.yhbt.net X-Spam-Level: X-Spam-Status: No, score=-3.3 required=3.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_HI, SPF_HELO_NONE,SPF_PASS shortcircuit=no autolearn=ham autolearn_force=no version=3.4.2 Received: from metis.ext.pengutronix.de (metis.ext.pengutronix.de [IPv6:2001:67c:670:201:290:27ff:fe1d:cc33]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by dcvr.yhbt.net (Postfix) with ESMTPS id 638F51F9FE for ; Thu, 4 Mar 2021 20:34:00 +0000 (UTC) Received: from ptx.hi.pengutronix.de ([2001:67c:670:100:1d::c0]) by metis.ext.pengutronix.de with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1lHufR-0002gd-N9; Thu, 04 Mar 2021 21:33:53 +0100 Received: from ukl by ptx.hi.pengutronix.de with local (Exim 4.92) (envelope-from ) id 1lHufR-0000AJ-38; Thu, 04 Mar 2021 21:33:53 +0100 Date: Thu, 4 Mar 2021 21:33:52 +0100 From: Uwe =?utf-8?Q?Kleine-K=C3=B6nig?= To: Eric Wong Cc: meta@public-inbox.org Subject: Re: public-inbox in Debian Message-ID: <20210304203352.pd5mcg5pw4u2epzl@pengutronix.de> References: <20210304070601.mpige7mkw3xp7e6l@pengutronix.de> <20210304081235.GA4144@dcvr> <20210304092124.ssx2bgduyuqojzh2@pengutronix.de> <20210304185735.GB19350@dcvr> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="oodisjbm23xlwfme" Content-Disposition: inline In-Reply-To: <20210304185735.GB19350@dcvr> X-SA-Exim-Connect-IP: 2001:67c:670:100:1d::c0 X-SA-Exim-Mail-From: ukl@pengutronix.de X-SA-Exim-Scanned: No (on metis.ext.pengutronix.de); SAEximRunCond expanded to false X-PTX-Original-Recipient: meta@public-inbox.org List-Id: --oodisjbm23xlwfme Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hello Eric, On Thu, Mar 04, 2021 at 06:57:35PM +0000, Eric Wong wrote: > Uwe Kleine-K=F6nig wrote: > > On Thu, Mar 04, 2021 at 08:12:35AM +0000, Eric Wong wrote: > > > Uwe Kleine-K=F6nig wrote: > > > I've been trying to get a new release out ASAP but there's too > > > much left to do :< > > >=20 > > > > https://tracker.debian.org/news/1234849/accepted-public-inbox-160-1= -all-source-into-unstable-unstable/ > > >=20 > > > Any particular reason the package is 1.6.0-1 despite the > > >=20 > > > "* Include changes from upstream bugfix release 1.6.1" > > >=20 > > > change entry? Anyways, no big deal and thanks again for all > > > your work. > >=20 > > Funny you ask. I chose to do it that way because I expected that an > > eventual 1.7.0 release won't include 1.6.1 as an ancestor and I thought > > it a good idea to have my upstream branch to be fast-forward only. >=20 > Actually, I merged 1.6.1 back into the tip of whatever branch > I was using and pushed it to master: >=20 > d49c0789d208e66121bfb68ff0c48d7612a7cd8e ("Merge remote-tracking branch '= origin/lei' into eidx") > 8862c33ae93eea1af6246cd3c7a81e0a122186bf ("Merge tag 'v1.6.1' into eidx") Ah, so this makes it easier for me. Will fix the versioning in the next upload. > Btw, since there's bb928d88ed4c72241a8d76bc792cdbd798e44470 > ("www: use PublicInbox::WwwStream") sitting in the stable-1.6 > branch, would it be helpful to release v1.6.2 at some point? I have that patch already included in 1.6.0-1. :-) So the gain of you releasing a 1.6.2 with that patch is that it becomes more obvious that this patch is already included in the Debian package (assuming I fix the versioning as I intend to do). Having said that I think it's only sensible to release 1.6.2 if 1.7.0 will take some time. Unless 1.7.0 is utterly broken I'd prefer to package that instead of 1.6.2. > I think 8b39c0757a7d6d62ff7f432c13ef4c497f1c804e > ("ds: import croak properly") is worth pushing to stable-1.6, > maybe others... Sounds similar to the WwwStream patch. I didn't notice a breakage though. > Also, I'd appreciate if you or anybody else helps writing > release notes (in the form of what's in Documentation/RelNotes/) > since it's a bit of a drag for me. That's understandable, I don't like writing documentation either :-) I think I'm of no good help here, as I don't follow the development closely and would rather consume instead of produce a release note. Best regards Uwe --=20 Pengutronix e.K. | Uwe Kleine-K=F6nig | Industrial Linux Solutions | https://www.pengutronix.de/ | --oodisjbm23xlwfme Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQEzBAABCgAdFiEEfnIqFpAYrP8+dKQLwfwUeK3K7AkFAmBBRC0ACgkQwfwUeK3K 7AmbOAgAh4pwUZ+F3Iccvm4TpKX8ElDk9iBAt9XJNX6Lkvnjue0ZyQ/naOR8vIA3 BUpfKAUJcJ9pcjyerB0Pruf6RHaDfm/RCs9g/9jP1xfIT62heTn5mDaxkqs7YZJT ejcjodK9CU+dex/C59T/Mtt5rTW9zEOrFYcL1DnWSbHJ2dKiI+KKgGeevGUc09xy Mj/Ej1j2atJ9vo9j0zqfaZz6PdFCnPzVmIENEgLRKPooojowhIU1/gxrm8HkCJWy 1Q+r/ysc/5WCdQNtiBxtzG3/E/3lNkMDWdAqi91RKhfvq8xoEE8BGTAanw818Ngc 0/S3//n2cel1HrLmXt3LHVdGJ2gB1w== =qOAt -----END PGP SIGNATURE----- --oodisjbm23xlwfme--