Re: Help testing release candidate / mc-4.8.26-rc1

On Sun, 10 Jan 2021 15:52:22 +0100 (CET)
"Yury V. Zaytsev" <yury shurup com> wrote:

Hi there,

TLDR; I would appreciate if you could please test the following tarball on 
your systems and report any blocker regressions as compared to the 
previous 4.8.25 release:

$ sha256sum mc-4.8.25-154-g33c84e75e.tar.xz
ce5f965a9be603098eda65afd1aa149e285d903fe303fe907c6a5e88f28dd772  mc-4.8.25-154-g33c84e75e.tar.xz

I've built this tarball out of the latest master with translations from 
Transifex pulled in on a fresh Fedora 33 VM, which I'm also going to use 
to build the final release in about a week from now if nothing serious 
comes up.

Is there an option to tag release candidates just like releases and
name/upload tarballs into expected locations just like releases?

That would make pulling release candidates (at least) into Gentoo an
almost automatic action.

Otherwise I'm always spending some time to name candidate as 4.8.26_rc1
(or 4.8.25_p154, or something else) downstream to the point I decide not
to package candidates to avoid user confusion.



Attachment: pgp9XOlP9H0Qi.pgp
Description: Цифровая подпись OpenPGP

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]