Re: Flex SDK release

Looks ok to me. Thanks, -Alex On 3/13/17, 8:50 PM, "Nicholas Kwiatkowski" wrote: >Forgot to include those in the batch. If it looks good, I will set >everything to publish at 10am EDT tomorrow. > >-Nick > >On Mon, Mar 13, 2017 at 3:43 PM, Alex Harui

Re: Flex SDK release

Forgot to include those in the batch. If it looks good, I will set everything to publish at 10am EDT tomorrow. -Nick On Mon, Mar 13, 2017 at 3:43 PM, Alex Harui wrote: > Hi Nick, > > Shouldn' these pages be reflecting the update? > >

Re: Flex SDK release

Hi Nick, Shouldn' these pages be reflecting the update? http://flex.staging.apache.org/download-binaries.html http://flex.staging.apache.org/download-source.html -Alex On 3/13/17, 12:06 PM, "Nicholas Kwiatkowski" wrote: >Looks like the installer is updated (per

Re: Flex SDK release

Looks like the installer is updated (per Alex), and everything else is ready to go. Are we good to publish and announce? -Nick On Mon, Mar 13, 2017 at 12:54 AM, Alex Harui wrote: > It didn't seem like Nick updated the installer, so I made the changes I > think we need. > >

Re: Flex SDK release

It didn't seem like Nick updated the installer, so I made the changes I think we need. On 3/12/17, 2:48 PM, "Justin Mclean" wrote: >HI, > >Looks like everything good to go. Just waiting if someone can do this fix >the installer script before announcing. > >Thanks,

Re: Flex SDK release

Everything is staged and ready to go. I've shelved the asdocs updating on the website because it will bury the possible fix for FLEX-35156. -Nick On Fri, Mar 10, 2017 at 5:04 PM, Justin Mclean wrote: > Hi, > > > I've grabbed a few of these. I'll work on them as soon

Re: Flex SDK release

HI, Looks like everything good to go. Just waiting if someone can do this fix the installer script before announcing. Thanks, Justin 1. https://issues.apache.org/jira/browse/FLEX-35156

Re: Flex SDK release

Hi, > I've grabbed a few of these. I'll work on them as soon as the binaries and > source on up on the repos. Much appreciated. Looks like most of the mirrors will have them now [1] (towards the bottom) and if not by the end of the day. Thanks, Justin 1. https://www.apache.org/mirrors/

Re: Flex SDK release

I've grabbed a few of these. I'll work on them as soon as the binaries and source on up on the repos. -Nick On Fri, Mar 10, 2017 at 1:38 AM, Justin Mclean <jus...@classsoftware.com> wrote: > Hi, > > Can any one help out with these activities as part of the Flex SDK rel

Re: Flex SDK release

Hi, > I would add also to this activities post on our blog - It seems to be dead a > bit. I think there a JIRA for that as well, if not when It’s back up I’ll add one. Our whole site really needs fresh content or rather people willing to help out with that. Thanks, Justin

Re: Flex SDK release

Hi Justin, I would add also to this activities post on our blog - It seems to be dead a bit. Piotr - Apache Flex PMC piotrzarzyck...@gmail.com -- View this message in context: http://apache-flex-development.247.n4.nabble.com/Flex-SDK-release-tp60329p60331.html Sent from the Apache

Flex SDK release

Hi, Can any one help out with these activities as part of the Flex SDK release [1][2][3]. They are updating the installer script, update the web site and the AS docs. Thanks, Justin PS looks like JIRA may of just gone off the air so these links may not work. 1. https://issues.apache.org/jira

Re: Installer.xml changes needed (was Re: New Flex SDK release)

iginal message-- > >From: OmPrakash Muppirala > >Date: Thu, Nov 3, 2016 11:31 AM > >To: dev@flex.apache.org; > >Subject:Re: Installer.xml changes needed (was Re: New Flex SDK release) > > > >Interestingly, I was able to simply unzip the .dmg

Re: Installer.xml changes needed (was Re: New Flex SDK release)

an AT 4G LTE smartphone > >-- Original message-- >From: OmPrakash Muppirala >Date: Thu, Nov 3, 2016 11:31 AM >To: dev@flex.apache.org<mailto:dev@flex.apache.org>; >Subject:Re: Installer.xml changes needed (was Re: New Flex SDK release) > >Interestingly, I was able

Re: New Flex SDK release

Hi, > I'd like to get FLEX-34880 done for this release. If I work on it in > the weekend, would it be too late, you think? That will be fine, it will be a little while before we make a release candidate and vote on it. Thanks, Justin

Re: Installer.xml changes needed (was Re: New Flex SDK release)

OmPrakash Muppirala > >Date: Thu, Nov 3, 2016 11:31 AM > >To: dev@flex.apache.org; > >Subject:Re: Installer.xml changes needed (was Re: New Flex SDK release) > > > >Interestingly, I was able to simply unzip the .dmg file and inspect its > >contents. It simply has

Re: Installer.xml changes needed (was Re: New Flex SDK release)

;From: OmPrakash Muppirala >Date: Thu, Nov 3, 2016 11:31 AM >To: dev@flex.apache.org; >Subject:Re: Installer.xml changes needed (was Re: New Flex SDK release) > >Interestingly, I was able to simply unzip the .dmg file and inspect its >contents. It simply has a folder called A

Re: New Flex SDK release

> If there are any issues you want to see fixed in this release please add them > to this subtask [2] in the release JIRA. I'd like to get FLEX-34880 done for this release. If I work on it in the weekend, would it be too late, you think?

Re: Installer.xml changes needed (was Re: New Flex SDK release)

: New Flex SDK release) Interestingly, I was able to simply unzip the .dmg file and inspect its contents. It simply has a folder called AIR SDK: https://snag.gy/i8gNmu.jpg Also of interest is the fact that I have been using only the .zip files in the NPM FlexJS installer. That seems to work fine

Re: Installer.xml changes needed (was Re: New Flex SDK release)

or may not be the latest. > > > > > > Sent from my LG G3, an AT 4G LTE smartphone > > > > > > -- Original message-- > > > *From: *OmPrakash Muppirala > > > *Date: *Thu, Nov 3, 2016 10:10 AM > > > *To: *dev@flex.apache.org; > > > *Subjec

Re: Installer.xml changes needed (was Re: New Flex SDK release)

gt; > I believe the zip and tar will go away or may not be the latest. > > > > Sent from my LG G3, an AT 4G LTE smartphone > > > > -- Original message-- > > *From: *OmPrakash Muppirala > > *Date: *Thu, Nov 3, 2016 10:10 AM > > *To: *dev@flex.apache.or

Re: Installer.xml changes needed (was Re: New Flex SDK release)

gt; > I believe the zip and tar will go away or may not be the latest. > > Sent from my LG G3, an AT 4G LTE smartphone > > -- Original message-- > *From: *OmPrakash Muppirala > *Date: *Thu, Nov 3, 2016 10:10 AM > *To: *dev@flex.apache.org; > *Subject:*Re: Installe

Re: Installer.xml changes needed (was Re: New Flex SDK release)

@flex.apache.org; Subject:Re: Installer.xml changes needed (was Re: New Flex SDK release) I still see the zip file available here https://fpdownload.macromedia.com/pub/labs/flashruntimes/air/AdobeAIRSDK.zip On Nov 3, 2016 9:54 AM, "Alex Harui" <aha...@adobe.com> wrote: > > > O

Re: Installer.xml changes needed (was Re: New Flex SDK release)

And I still see the adl.exe inside the zip file: https://snag.gy/uSrbL5.jpg On Thu, Nov 3, 2016 at 10:10 AM, OmPrakash Muppirala wrote: > I still see the zip file available here > > https://fpdownload.macromedia.com/pub/labs/flashruntimes/ > air/AdobeAIRSDK.zip > > On Nov

Re: Installer.xml changes needed (was Re: New Flex SDK release)

I still see the zip file available here https://fpdownload.macromedia.com/pub/labs/flashruntimes/air/AdobeAIRSDK.zip On Nov 3, 2016 9:54 AM, "Alex Harui" wrote: > > > On 11/3/16, 9:35 AM, "omup...@gmail.com on behalf of OmPrakash Muppirala" >

Re: Installer.xml changes needed (was Re: New Flex SDK release)

On 11/3/16, 9:35 AM, "omup...@gmail.com on behalf of OmPrakash Muppirala" wrote: >I can take this work up. Depending on how much work this would take and >amy available bandwidth, this could take a while. > >Do you know what exactly needs

Re: Installer.xml changes needed (was Re: New Flex SDK release)

; We need to decide how urgent this issue is, but I'm assuming for now that > folks want to see the next Flex SDK release work with Adobe AIR 24 and > later. > > -Alex > > >

Installer.xml changes needed (was Re: New Flex SDK release)

for now that folks want to see the next Flex SDK release work with Adobe AIR 24 and later. -Alex

Re: New Flex SDK release

On 11/3/16, 1:12 AM, "Justin Mclean" wrote: >Hi, > >> One thing I would really be dleighted about, would be, if we could get >>rid of the patched libraries used in the sdk. >> However I don’t have any idea what sideeffects this would have. > >Way back I did look into

Re: New Flex SDK release

Hi, > This is the modified AwesomeUtils.as [1] which includes the update to > FontAwesome 4.7 and the MIT licence header that replaces the Apache license > header. Looks good to me. > Should I commit it to the 4.16.0 branch? Yep when ever you have time to do so that would be great. Thanks,

Re: New Flex SDK release

Hi Justin, Guess I would opt to work on that path, but I’m not going to put up with the build. So probably the path would be to migrate the FlexSDK to be buildable with maven and as soon as I have a stable system with good test coverage, to start cleaning this up. But at the moment I don’t

Re: New Flex SDK release

.n4.nabble.com/New-Flex-SDK-release-tp56153p56195.html Sent from the Apache Flex Development mailing list archive at Nabble.com.

Re: New Flex SDK release

Hi, > Should I replace the Apache license header by the MIT one or should I add > the MIT header under the Apache license header? Generally the changes have to be extensive to change the header on a file, translation from one language to another generaly doesn’t count. I’m not a lawyer but

Re: New Flex SDK release

347.n4.nabble.com/New-Flex-SDK-release-tp56153p56193.html Sent from the Apache Flex Development mailing list archive at Nabble.com.

Re: New Flex SDK release

Hi, > I'm also not a layer and I don't want to trigger another license disucssion > here but is it not enough to just add the MIT license text as additional > header to the affected files including the required copyright info? Yes that an option (and given as one on legal discuss). Given the

Re: New Flex SDK release

in context: http://apache-flex-development.247.n4.nabble.com/New-Flex-SDK-release-tp56153p56191.html Sent from the Apache Flex Development mailing list archive at Nabble.com.

Re: New Flex SDK release

Hi, > One thing I would really be dleighted about, would be, if we could get rid of > the patched libraries used in the sdk. > However I don’t have any idea what sideeffects this would have. Way back I did look into doing so but was going to be a lot of work for Bartik as Adobe made a large

Re: New Flex SDK release

Hi, And it turns out this is a know outstanding issue (for a while) and other people have the same issue :-( [1] Justin 1. https://github.com/FortAwesome/Font-Awesome/issues/5281

Re: New Flex SDK release

One thing I would really be dleighted about, would be, if we could get rid of the patched libraries used in the sdk. However I don’t have any idea what sideeffects this would have. Chris Am 03.11.16, 08:53 schrieb "Justin Mclean" : Hi, > Should we also

Re: New Flex SDK release

Hi, > Should we also take care of license issues cause we grab [2] and create a > new file of it [3]? [2] is MIT licensed so IMO it wouldn’t hurt it add a pointer of that MIT to our LICENSE file. That way all bases are covered. There is an issue here (similar with certain other 3rd parties) in

Re: New Flex SDK release

sdk/blob/develop/frameworks/projects/flatspark/src/flatspark/utils/AwesomeUtils.as -- View this message in context: http://apache-flex-development.247.n4.nabble.com/New-Flex-SDK-release-tp56153p56185.html Sent from the Apache Flex Development mailing list archive at Nabble.com.

Re: Icon fonts (was Re: New Flex SDK release)

Hi guys, Material icons (https://material.io/icons/) is available under Apache License. It can be a serious alternative to Font Awesome. Hope it helps. Regards, Fabrice Montfort 2016-11-03 11:08 GMT+04:00 Harbs : > In morre general terms: > > While we obviously cannot

Re: New Flex SDK release

Hi, > There will be still a community Version... Is this also incompatible with > Apache? The 4.7 community version is under a variety of license of which the code and font are under a compatible license [1]. Their documentation isn’t under a compatible license. Hopefully this will be the

Re: New Flex SDK release

es! Thanks, Olaf -- View this message in context: http://apache-flex-development.247.n4.nabble.com/New-Flex-SDK-release-tp56153p56181.html Sent from the Apache Flex Development mailing list archive at Nabble.com.

Re: New Flex SDK release

Hi, > I would update FontAwesome to the latest release so we have one more minor > change… You want to take care of [1]. I also noticed this the other week [2] which has raised almost $500,000! Sadly the license isn’t likely to be compatible with Apache. Thanks, Justin 1.

New Flex SDK release

HI, We’ve just starting on making a new Flex SDK release. You can follow the progress in this JIRA [1] If there are any issues you want to see fixed in this release please add them to this subtask [2] in the release JIRA. Please remember that Flex is run my volunteers, and a lot of effort

Re: New Flex SDK release

Hi, I created a JIRA to track the progress here [1]. If anyone want to help out please assign themselves one of the sub tasks. Thanks, Justin 1. https://issues.apache.org/jira/browse/FLEX-35146

Re: New Flex SDK release

Hi, > Are you thinking of this as a 4.16 or 4.15.1? I was thinking 4.16 but it doesn't really matter. Justin

Re: New Flex SDK release

Justin Mclean wrote > Hi, > It’s been quite a while (10 months!) since we’ve made a new Flex SDK > release, and there's a number of changes and fixes that have been made in > develop. > If no-one else want to be the release manager I’ll put my hand up for the > role. > Thank

Re: New Flex SDK release

On 11/1/16, 4:02 PM, "Justin Mclean" <jus...@classsoftware.com> wrote: >Hi, > >It’s been quite a while (10 months!) since we’ve made a new Flex SDK >release, and there's a number of changes and fixes that have been made in >develop. Are you thinking of this as a 4.16 or 4.15.1? -Alex

New Flex SDK release

Hi, It’s been quite a while (10 months!) since we’ve made a new Flex SDK release, and there's a number of changes and fixes that have been made in develop. If no-one else want to be the release manager I’ll put my hand up for the role. Thanks, Justin

Re: Next Flex SDK release

The new code had a successful build on the CI machine. The difference in the build time is less than I would have thought it would be. It looks like the tests are taking about 2 minutes less than they used to.[1] I guess that’s something, but I’m not sure it’s different enough for a general

Re: Next Flex SDK release

On 12/10/15, 4:13 AM, "Harbs" wrote: >The new code had a successful build on the CI machine. The difference in >the build time is less than I would have thought it would be. It looks >like the tests are taking about 2 minutes less than they used to.[1] > >I guess that’s

Re: Next Flex SDK release

OK. This is now fixed. Anyone have thoughts on performance checking to ensure that future performance degradation is caught? On Nov 18, 2015, at 7:53 AM, Alex Harui wrote: > 2) TLF Performance > https://issues.apache.org/jira/browse/FLEX-34769 > > I’d like to get an update

RE: Next Flex SDK release

thank you so freaking much for this one Harbs! -Original Message- From: Harbs [mailto:harbs.li...@gmail.com] Sent: Wednesday, December 09, 2015 2:38 PM To: dev@flex.apache.org Subject: Re: Next Flex SDK release OK. This is now fixed. Anyone have thoughts on performance checking

RE: Next Flex SDK release

nvm, saw your notes, didn't realize 4.9 was that fast! -Original Message- From: Jason Taylor [mailto:ja...@dedoose.com] Sent: Wednesday, December 09, 2015 3:22 PM To: dev@flex.apache.org Subject: RE: Next Flex SDK release Harbs, Flex SDK 13.0 was the last release where TLF worked

Re: Next Flex SDK release

Hi, > Anyone have thoughts on performance checking to ensure that future > performance degradation is caught? Usually I just add a couple of unit tests that assert the time run < some reasonable value. No idea how easy that is to do in this case. Thanks, Justin

RE: Next Flex SDK release

@flex.apache.org Subject: Re: Next Flex SDK release It looks like I don't need 4.6. There's a 3.0 branch in the Git repo which seems to have ti working correctly. On Dec 7, 2015, at 3:19 PM, Harbs <harbs.li...@gmail.com> wrote: > OK. I'm working on this, and I just added a comment to the JIR

Re: Mustella fixing (was Re: Next Flex SDK release)

On 12/8/15, 2:57 AM, "Kessler CTR Mark J" wrote: >If I remember correctly one of the main reasons we started embedding >fonts was to be able to rotate text on reports. The other being a >consistent font no matter the platform/browser. We had to embed a normal

RE: Mustella fixing (was Re: Next Flex SDK release)

fonts, we have 4 declarations in our css. With / without CFF for both the regular font and bold font. -Mark -Original Message- From: Alex Harui [mailto:aha...@adobe.com] Sent: Tuesday, December 08, 2015 11:11 AM To: dev@flex.apache.org Subject: Re: Mustella fixing (was Re: Next Flex SDK

Re: Mustella fixing (was Re: Next Flex SDK release)

On 24/11/15 19:00, OmPrakash Muppirala wrote: And do you think I can close this issue as fixed for now? The Mustella tests are still failing... Tom

Re: Next Flex SDK release

It looks like I don’t need 4.6. There’s a 3.0 branch in the Git repo which seems to have ti working correctly. On Dec 7, 2015, at 3:19 PM, Harbs wrote: > OK. I’m working on this, and I just added a comment to the JIRA with my > preliminary observations. Kind of

RE: Mustella fixing (was Re: Next Flex SDK release)

SDK release) On 12/7/15, 5:33 AM, "Tom Chiverton" <t...@extravision.com> wrote: >On 24/11/15 19:00, OmPrakash Muppirala wrote: >> And do you think I can close this issue as fixed for now? > >The Mustella tests are still failing... My understanding of the situatio

Re: Next Flex SDK release

OK. I’m working on this, and I just added a comment to the JIRA with my preliminary observations. Kind of interesting... I’m going to need to find the source of the old TLF to compare. I don’t want to use 4.9.1 because that code just had a band-aid. I assume Adobe's 4.6 code was working

Re: Mustella fixing (was Re: Next Flex SDK release)

I’ve never used charts, so I have no idea about RTL and the like. What was the issue with Spark? What about using Twitter to try and find out if anyone is using Spark Label in charts? Harbs On Nov 24, 2015, at 7:12 PM, Alex Harui wrote: > > > On 11/24/15, 12:06 AM,

Re: Mustella fixing (was Re: Next Flex SDK release)

On 11/24/15, 9:24 AM, "Harbs" wrote: >I’ve never used charts, so I have no idea about RTL and the like. What >was the issue with Spark? Back in July, I took a look [1] and it appeared that Charts used a TextField instead of a Spark Label to measure how much room there

Re: Mustella fixing (was Re: Next Flex SDK release)

On 11/24/15, 12:06 AM, "omup...@gmail.com on behalf of OmPrakash Muppirala" wrote: >On Mon, Nov 23, 2015 at 11:54 PM, Alex Harui wrote: > >> >> >> I decided to take a quick peek. It looks like a change was made to have >>

Re: Mustella fixing (was Re: Next Flex SDK release)

That's good to know. Can you please update this ticket with your comments so that we can go back and easily find it when such an issue arises in the future? https://issues.apache.org/jira/browse/FLEX-34909 And do you think I can close this issue as fixed for now? Thanks, Om On Tue, Nov 24,

Re: Mustella fixing (was Re: Next Flex SDK release)

On Mon, Nov 23, 2015 at 11:54 PM, Alex Harui wrote: > > > On 11/20/15, 9:05 AM, "omup...@gmail.com on behalf of OmPrakash Muppirala" > wrote: > > >>I took a look at one of the bad.png files from Charts and the fonts were >

Re: Mustella fixing (was Re: Next Flex SDK release)

On 11/20/15, 9:05 AM, "omup...@gmail.com on behalf of OmPrakash Muppirala" wrote: >>I took a look at one of the bad.png files from Charts and the fonts were >> rendering differently, although I also think I saw a small difference in >> the

Re: Mustella fixing (was Re: Next Flex SDK release)

On Nov 19, 2015 11:34 PM, "Alex Harui" wrote: > > Looks like Tom also has the magic, although I did reboot the server as > well to get past the repo access errors, but rebooting in the past wasn't > enough. > > Air and Mobile are passing, and I would say the SDK errors are

Mustella fixing (was Re: Next Flex SDK release)

OK. The last run failed, and was not in progress. I ran all four players in that folder and closed them. Let's see what happens on the next run Tom On 18/11/15 22:52, Alex Harui wrote: The mustella server has caught legitimate issues, most recently with some sort behavior changes. But yeah,

Re: Mustella fixing (was Re: Next Flex SDK release)

Looks like Tom also has the magic, although I did reboot the server as well to get past the repo access errors, but rebooting in the past wasn't enough. Air and Mobile are passing, and I would say the SDK errors are probably real errors: There are some Sort errors left over from some changes we

RE: Next Flex SDK release

I meant to go back and look at that one a while ago, guess it fell off my radar. I'll have a look at it tonight. -Mark -Original Message- From: Alex Harui [mailto:aha...@adobe.com] Sent: Wednesday, November 18, 2015 12:53 AM To: dev@flex.apache.org Subject: Re: Next Flex SDK release

Re: Next Flex SDK release

I've never seen a 'real' failure. It always seems to be Mustella screwing itself up. I don't have a Windows machine to chase them down with. Tom On 18/11/15 07:22, Justin Mclean wrote: Hi, The flex-sdk_mustella Jenkin's task does not currently pass: http://flex-mustella.cloudapp.net/

Re: Next Flex SDK release

On 11/15/15, 9:11 PM, "Justin Mclean" <jus...@classsoftware.com> wrote: >Hi, > >Now the FlexJS releases are just about to be announced, I think it's >about time we made a Flex SDK release as the previous one was released >was way back in March. > >Unless anyo

Re: Next Flex SDK release

The flex-sdk_mustella Jenkin's task does not currently pass: http://flex-mustella.cloudapp.net/ Tom On 16/11/15 05:11, Justin Mclean wrote: Is there any regression issues in 4.14/4.14.1 that anyone feels needs to be addressed before making a new release?

Re: Next Flex SDK release

Hi, > The flex-sdk_mustella Jenkin's task does not currently pass: > http://flex-mustella.cloudapp.net/ Does anyone know if the machine just need a bit of maintaince or are these do to real failures? I can see that the RC jobs have not run successfully for 7

Re: Next Flex SDK release

Hi, The JIRA (and sib tasks) for the next release can be found here [1], if you want to help out please assign yourself one of the subtasks. I’ve had a go at the contributors list and the fixed bugs, if anyone want to review the changes that would be a great help. Thanks, Justin 1.

Re: Next Flex SDK release

You had created such a flag, but enabling it causes lots of RTEs with the current code. I’d rather find the underlying cause of the problem which seems to be way too much recursion. I will try to take another look at this issue next week. On Nov 18, 2015, at 7:53 AM, Alex Harui

Next Flex SDK release

Hi, Now the FlexJS releases are just about to be announced, I think it's about time we made a Flex SDK release as the previous one was released was way back in March. Unless anyone else want to give it a go I’ll act as the release manager. Is there any regression issues in 4.14/4.14.1

[SDK] during prep phase, switch 'flex-sdk-release' to release branch

Hi, I'm looking for ideas or alternate viewpoints on the following: I plan to switch the 'flex-sdk-release' job, which produces the Nightly Builds, to the release branch, as soon as I cut one for the upcoming release. The idea behind this is that we give testers access to the pre-RC release

Re: [SDK] during prep phase, switch 'flex-sdk-release' to release branch

On 11/19/14, 8:01 AM, Erik de Bruin e...@ixsoftware.nl wrote: Hi, I'm looking for ideas or alternate viewpoints on the following: I plan to switch the 'flex-sdk-release' job, which produces the Nightly Builds, to the release branch, as soon as I cut one for the upcoming release. The idea

AW: [SDK] during prep phase, switch 'flex-sdk-release' to release branch

SNAPSHOT or develop SNAPSHOT. Just my 50ct to this ;-) Chris Von: Erik de Bruin e...@ixsoftware.nl Gesendet: Mittwoch, 19. November 2014 17:01 An: dev@flex.apache.org Betreff: [SDK] during prep phase, switch 'flex-sdk-release' to release branch Hi, I'm

Re: [SDK] during prep phase, switch 'flex-sdk-release' to release branch

Gesendet: Mittwoch, 19. November 2014 17:01 An: dev@flex.apache.org Betreff: [SDK] during prep phase, switch 'flex-sdk-release' to release branch Hi, I'm looking for ideas or alternate viewpoints on the following: I plan to switch the 'flex-sdk-release' job, which produces the Nightly Builds

Re: [SDK] during prep phase, switch 'flex-sdk-release' to release branch

'flex-sdk-release' to release branch Hi, I'm looking for ideas or alternate viewpoints on the following: I plan to switch the 'flex-sdk-release' job, which produces the Nightly Builds, to the release branch, as soon as I cut one for the upcoming release. The idea behind this is that we give

Re: [SDK] during prep phase, switch 'flex-sdk-release' to release branch

I’ll tweak the installer config for you. Just remind me when the build finishes so I can verify the URLs to the artifacts. Thanks. I won't start the new build job until after I cut the release branch, so that'll be a couple of weeks at least. EdB -- Ix Multimedia Software Jan