> 20b24fd8%7Cfa7b
> >>1b5a7b34438794aed2c178decee1%7C0%7C0%7C636450872576145644&
> sdata=izmdfwJFr
> >>v9uWxs3N7%2FLT9R4DOi5Bz5BTgP%2FTwM4veE%3D&reserved=0>
> >>
> >>
> >> From: Piotr Zarzycki
> &g
>>v9uWxs3N7%2FLT9R4DOi5Bz5BTgP%2FTwM4veE%3D&reserved=0>
>>
>> ____
>> From: Piotr Zarzycki
>> Sent: Tuesday, October 31, 2017 2:55:09 PM
>> To: dev@flex.apache.org
>> Subject: Re: [Discuss] Release Apache Flex and Apache Flex
he.org
> Subject: Re: [Discuss] Release Apache Flex and Apache Flex Installer
>
> How can I manually check those values ? cacheID="1a12cc0c-5576793ff665c"
> cacheID2="d16a2ff-5304155c7d928". If I could manually check everything in
> somehow I could proceed with re
elease Apache Flex and Apache Flex Installer
How can I manually check those values ? cacheID="1a12cc0c-5576793ff665c"
cacheID2="d16a2ff-5304155c7d928". If I could manually check everything in
somehow I could proceed with release and fix MD5Checker later.
1) I'm downloading
How can I manually check those values ? cacheID="1a12cc0c-5576793ff665c"
cacheID2="d16a2ff-5304155c7d928". If I could manually check everything in
somehow I could proceed with release and fix MD5Checker later.
1) I'm downloading Adobe Air
2) Compute MD5 myself yes ?
Later what am I doing with the
Alex,
It look like MD5Checker experiencing similar issue as installer. The
difference is that installer had out of memory in case of unzipping and
MD5Checker has that problem in case of loading url request.
When "redownload" is launched MD5Checker is being blown up! In order to fix
that maybe I w
You put in the md5 for that AIR SDK. What I do is make sure I can run
MD5Checker locally.
Then I stick in some other md5, publish sdk-installer-config-4.0.xml and
run MD5Checker locally.
It will tell you how to fix up the md5 as well as the cacheID value.
I've published some notes here:
https:/
Alex,
I'm asking what should I put in that tags a0a0ae42410c90315e895e1bcabfe896
of sdk-installer-config-4.0.xml file ?
Piotr
2017-10-31 18:57 GMT+01:00 Alex Harui :
> Hi Piotr,
>
> I'm not quite sure what you are asking. To add newer AIR SDKs to the list
> of choices, add new entries in sdk
Hi Piotr,
I'm not quite sure what you are asking. To add newer AIR SDKs to the list
of choices, add new entries in sdk-installer-config-4.0.xml on our
website. To get the Installer to offer a particular AIR SDK version as he
default, you also change a setting in sdk-installer-config-4.0.xml. To
Update version in the SDK and installer is done. I'm wondering now how can
I update installer to have the newest Adobe Air SDK version ? I see there
for Windows and Mac version md5, are we generate those ourselves ?
Thanks,
Piotr
2017-10-30 21:41 GMT+01:00 Carlos Rovira :
> Hi Piotr,
>
> I think
Hi Piotr,
I think maven has its own way to make releases, don't know how this fit
with our releases, but I think you must to do something like "mvn prepare
release" or something like that
2017-10-30 21:33 GMT+01:00 Alex Harui :
> Hi Piotr,
>
> Check the history of those files. See what we did f
Hi Piotr,
Check the history of those files. See what we did for the 4.14.1 release.
Also, while we did make a branch for 4.14.1, if you want to reuse the
4.16.0 release branch that would be fine with me.
-Alex
On 10/30/17, 1:02 PM, "Piotr Zarzycki" wrote:
>There is MxmlConfiguration and this
There is MxmlConfiguration and this is also I don't know how to fill. If
someone could that would be great!
Thanks, Piotr
2017-10-30 20:50 GMT+01:00 Piotr Zarzycki :
> Last question - How should I actually fill frameworks\projects\
> framework\src\mx\core\FlexVersion file ? If I have 4.16.1 ?
>
Last question - How should I actually
fill frameworks\projects\framework\src\mx\core\FlexVersion file ? If I have
4.16.1 ?
Thanks, Piotr
2017-10-30 20:40 GMT+01:00 Carlos Rovira :
> Hi Piotr,
> I agree that's better
> thanks for working on this! :)
>
> 2017-10-30 20:08 GMT+01:00 Piotr Zarzycki :
Hi Piotr,
I agree that's better
thanks for working on this! :)
2017-10-30 20:08 GMT+01:00 Piotr Zarzycki :
> I will try to update version to 4.16.1 on develop. There is only couple of
> fixed issues there. No reason jump to 4.17.
>
> 2017-10-30 17:46 GMT+01:00 Piotr Zarzycki :
>
> > Alex,
> >
> >
I will try to update version to 4.16.1 on develop. There is only couple of
fixed issues there. No reason jump to 4.17.
2017-10-30 17:46 GMT+01:00 Piotr Zarzycki :
> Alex,
>
> Exactly. That's why probably my strange questions. I will figure out how
> to do this and try to switch develop to 4.17 to
Alex,
Exactly. That's why probably my strange questions. I will figure out how to
do this and try to switch develop to 4.17 today.
Thank you for help!
2017-10-30 17:37 GMT+01:00 Alex Harui :
> Hi Piotr,
>
> That's interesting. I hadn't noticed that nobody upgraded the release
> version to 4.17
Hi Piotr,
That's interesting. I hadn't noticed that nobody upgraded the release
version to 4.17. We typically do that right after we release so that
nightly builds pick up the new release version and are easier to
distinguish from the actual release. So I suggest that you do that now
before cut
Hi Alex,
It almost explain my concerns. My additional concern is whether on that
branch I should change all the places in code where I see 4.16 to 4.17 ?
I would like to still create that branch, I believe I can make some
mistakes, even if there is not too much activity maybe someone is using
deve
Hi Piotr,
If you follow the pattern for release branch names you would call the
branch "release4.17.0". Typically, there are already changes in the
develop branch that you want to release. The purpose of release branches
has merely been to make sure changes that are not release-ready do not
inte
Carlos,
I will review the changes in framework and decide on Monday in what
direction go.
Thank you! :)
On Fri, Oct 27, 2017, 18:03 Carlos Rovira
wrote:
> If there's some delta, better to make a 4.16.1 instead a 4.17
>
> Thanks
>
> Carlos
>
>
>
> 2017-10-27 17:58 GMT+02:00 Alex Harui :
>
> >
Alex,
I'm creating a branch with "apacheflex4.17" and make there changes to 4.17
in code?
That was my concerns.
Piotr
On Fri, Oct 27, 2017, 18:03 Carlos Rovira
wrote:
> If there's some delta, better to make a 4.16.1 instead a 4.17
>
> Thanks
>
> Carlos
>
>
>
> 2017-10-27 17:58 GMT+02:00 Alex H
If there's some delta, better to make a 4.16.1 instead a 4.17
Thanks
Carlos
2017-10-27 17:58 GMT+02:00 Alex Harui :
> I'm not sure I understand the question.
>
> I think we make a new branch with the version number in the name each
> time. We could probably delete old branches once they get
I'm not sure I understand the question.
I think we make a new branch with the version number in the name each
time. We could probably delete old branches once they get merged with
develop and master.
HTH,
-Alex
On 10/27/17, 12:55 AM, "Piotr Zarzycki" wrote:
>Alex,
>
>I prefer create branch, b
Go for it!
> On Oct 27, 2017, at 8:27 AM, Piotr Zarzycki wrote:
>
> Hi Folks,
>
> Lately I was able to fix ugly bug [1] where on Windows Apache Flex
> Installer was failing to download Adobe Air greater than 23. Along with
> that fix I had to also make fix in SDK [2]. I believe this two critica
Alex,
I prefer create branch, but question if I do this on this branch I should
make the changes to 4.17 or we are testing still 4.16 by this branch ?
Om,
Yes it would be awesome if you could help with tests!
I will probably start from the installer.
Thanks, Piotr
2017-10-27 8:34 GMT+02:00 A
IMO, there is so little activity on the develop branch that a release
branch is not required.
Good luck,
-Alex
On 10/26/17, 11:08 PM, "omup...@gmail.com on behalf of OmPrakash
Muppirala" wrote:
>+1 please go ahead. I can help testing.
>
>I think the process for the Installer release are a bit
+1 please go ahead. I can help testing.
I think the process for the Installer release are a bit looser. You can
start the VOTE thread as soon as possible. Especially since this issue has
been around for a while.
Thanks,
Om
On Thu, Oct 26, 2017 at 10:27 PM, Piotr Zarzycki
wrote:
> Hi Folks,
Hi Folks,
Lately I was able to fix ugly bug [1] where on Windows Apache Flex
Installer was failing to download Adobe Air greater than 23. Along with
that fix I had to also make fix in SDK [2]. I believe this two critical
fixes is worth to release.
Anyone is against that to start release process ?
29 matches
Mail list logo
