Re: Release Apache Flex Installer 3.4

Hi Alex, I think it is a good idea to have 3.3.1 instead 3.4. Thanks, Piotr 2018-04-12 17:16 GMT+02:00 Alex Harui : > Hi Piotr, > > I think I didn't use the right certificate for 3.2 so folks moving to 3.3 > had a problem. As long as you use the right certificates for 3.4 there > shouldn't be

Re: Release Apache Flex Installer 3.4

Hi Piotr, I think I didn't use the right certificate for 3.2 so folks moving to 3.3 had a problem. As long as you use the right certificates for 3.4 there shouldn't be a problem. It occurs to me that we might want to call this release 3.3.1 instead of 3.4 since it is a single bug fix release, bu

Re: Release Apache Flex Installer 3.4

Hi Alex, IMO something rings into my head that we have had some problems with sign certificates last time. Do you recall something ? Thanks, Piotr 2018-04-12 10:25 GMT+02:00 Alex Harui : > I would skip last call and cut the RC. But yes, use SHA512 with a .sha512 > suffix. > > My 2 cents, > -Al

Re: Release Apache Flex Installer 3.4

I would skip last call and cut the RC. But yes, use SHA512 with a .sha512 suffix. My 2 cents, -Alex On 4/12/18, 12:48 AM, "Piotr Zarzycki" wrote: >Hi Guys, > >Since I was able to fix issue with OSMF I would like to prepare release >candidate. Should I go through the LAST CALL ? Can I omit it a

Release Apache Flex Installer 3.4

Hi Guys, Since I was able to fix issue with OSMF I would like to prepare release candidate. Should I go through the LAST CALL ? Can I omit it and just prepare RC1 ? I should also sign sources by SH1 yes ? Thanks, -- Piotr Zarzycki Patreon: *https://www.patreon.com/piotrzarzycki

Re: FLEX-35381 - Fix failing OSMF installer

It looks like it was my problem with playerglobal. I'm sorry for the noise. Thanks, Piotr 2018-04-11 19:33 GMT+02:00 Piotr Zarzycki : > Maybe it is simply MD5 mismatch issue because playerglobal got update. I > will check tomorrow! > > Thanks, > Piotr > > > On Wed, Apr 11, 2018, 3:18 PM Piotr Za