Mailing-List: contact general-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: general@incubator.apache.org
From: Bolke de Bruin <bdbruin@gmail.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Subject: Re: Airflow voting on release artifacts
Date: Tue, 25 Apr 2017 10:43:09 +0200
References: <CABYbY7fV-2RRB=-KQbJvUJLFe4zpahh_yEqPqWKug0ekZue_Og@mail.gmail.com>
 <CAEWfVJ=WRU0ee1B+xC9UgvSH-eQP7jN72-yZqm60swFPnP_grQ@mail.gmail.com>
To: general@incubator.apache.org
In-Reply-To: <CAEWfVJ=WRU0ee1B+xC9UgvSH-eQP7jN72-yZqm60swFPnP_grQ@mail.gmail.com>
Message-Id: <1CFD701C-3FAF-44C8-8328-F976F4BC7B44@gmail.com>
archived-at: Tue, 25 Apr 2017 08:43:25 -0000

Hi Bertrand,

> On 25 Apr 2017, at 09:04, Bertrand Delacretaz =
<bdelacretaz@codeconsult.ch> wrote:
>=20
> Hi,
>=20
> On Mon, Apr 24, 2017 at 10:18 PM, Chris Riccomini =
<criccomini@apache.org> wrote:
>> ...Hitesh recently raised the issue that the artifact that passes the =
vote
>> MUST be the one that we actually release...
>=20
> Yes in terms of having the same binary digests and signatures, but
> renaming the files is fine IMO, especially for removing an -rc suffix
> which makes total sense. I would just add that step to your release
> process documentation to make it clear.
>=20
>> ...Rename/rebuild after final vote (This is what Airflow is doing, =
and Beam
>> does this, I believe)...
>=20
> I'd say rename yes but rebuild no, in order to keep the same digests
> and signatures.
>=20

As mentioned earlier, that seems not to be possible. The metadata =
(filename) and version information inside the package need to be in =
sync. This how the python build tools and python ecosystem works.

- Bolke.=

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org