Hi Roman, thanks, for your answer. I am fine with it!
Next to a bug: The release proposition does not contain a valid key: The bigtop.repo.asc file should contain the gpg key which signed the repository. It i.e. your public key, not a detached signature. (Using your public key I sucessfully installed packages ;-) Greetings Olaf > Am 30.03.2017 um 17:24 schrieb Roman Shaposhnik <[email protected]>: > > On Wed, Mar 29, 2017 at 10:54 PM, Olaf Flebbe <[email protected]> wrote: >> Hi Roman, >> >> Thanks for you efforts! CI looks really good now. >> >> What was the consensus for the BIGTOP-2716 ? > > I honestly think it isn't a blocker and it seems that nobody put > a strong argument forward to the contrary. Thus it is now pushed > to 1.3.0. > >> We only support the current bigtop/slaves docker images, knowing it will >> break if regenerated? Fine for me. > > That is correct. As was mentioned -- we should add it to the release notes > once we announce the release. > > Does this answer your question? > > Thanks, > Roman.
signature.asc
Description: Message signed with OpenPGP
