Mailing-List: contact dev-help@flex.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@flex.apache.org
From: Christofer Dutz <christofer.dutz@c-ware.de>
To: "dev@flex.apache.org" <dev@flex.apache.org>
Subject: AW: AW: AW: Will we have a new release out the door till 8th of
 September?
Thread-Topic: AW: AW: Will we have a new release out the door till 8th of
 September?
Thread-Index: AQHSAgBOs2Ae1bAZO06lzQibMOyvkKBgQomAgAARVdaAAAGRAIABH7+AgAB3RID//4ujAIAAdigA//+T7ACAARt33g==
Date: Wed, 31 Aug 2016 06:27:57 +0000
Message-ID: <c443ggwxh5txdhec8yewr2s1.1472624879788@email.android.com>
References: <D3E99155.7417B%aharui@adobe.com>
 <CACK5iZd_yCL_Ax1KUo_Y+PvjRPXkPZZMjHwrHffZmi713t8bnQ@mail.gmail.com>
 <000f425c.244356bd7931eda8@adobe.com>
 <CACK5iZdRirx6TH5r4+8iq4bMuguswG-5hwn-yO4_CrNRrj_8dw@mail.gmail.com>
 <D3EB3028.74290%aharui@adobe.com>
 <CACK5iZeA8ASQ712z1i2=pmQdnf_uUd_xzcBpaAHbRuv3NYWaPA@mail.gmail.com>
 <D3EB32CE.742AB%aharui@adobe.com>
 <CACK5iZdx_wCUNVrme0aBax3ydFdtZwWmu4BWze3sJ3Zpyk0uJA@mail.gmail.com>,<D3EB3831.742BD%aharui@adobe.com>
In-Reply-To: <D3EB3831.742BD%aharui@adobe.com>
Accept-Language: de-DE, en-US
Content-Language: de-DE
received-spf: None (protection.outlook.com: c-ware.de does not designate
 permitted sender hosts)
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: multipart/alternative;
	boundary="_000_c443ggwxh5txdhec8yewr2s11472624879788emailandroidcom_"
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-originalarrivaltime: 31 Aug 2016 06:27:57.8148
 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 9d387546-1437-4b89-846c-691d64a7e74d
X-MS-Exchange-Transport-CrossTenantHeadersStamped: HE1PR0501MB2425
archived-at: Wed, 31 Aug 2016 06:28:13 -0000

--_000_c443ggwxh5txdhec8yewr2s11472624879788emailandroidcom_
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable

Would be cool if we could add the urls to the flash placer content debugger=
s as currently I'm hard coding the url-scheme in the mavenizer code.

Chris


Von meinem Samsung Galaxy Smartphone gesendet.


-------- Urspr=FCngliche Nachricht --------
Von: Alex Harui <aharui@adobe.com>
Datum: 30.08.16 22:33 (GMT+01:00)
An: OmPrakash Muppirala <bigosmallm@gmail.com>
Cc: dev@flex.apache.org, harbs.lists@gmail.com
Betreff: Re: AW: AW: Will we have a new release out the door till 8th of Se=
ptember?

Well, right now, the install() methods have a request() call that is commen=
ted out in favor of a get() call.  The request call is set up to call the m=
irrors.cgi, the get() call is set up to grab the nightly.  If the install()=
 method could have a parameter passed to it, then we wouldn't have to comme=
nt out one path or the other and could just run with an additional paramete=
r to get the nightly, and no parameter hits the mirror.cgi.

I could imagine even more sophisticated code that grabs the latest release =
URLs from the same place as the installer so we don't have to update the np=
m scripts as often and maybe lets you choose a version, but that doesn't se=
em that important to me.

-Alex

From: "omuppi1@gmail.com<mailto:omuppi1@gmail.com>" <omuppi1@gmail.com<mail=
to:omuppi1@gmail.com>> on behalf of OmPrakash Muppirala <bigosmallm@gmail.c=
om<mailto:bigosmallm@gmail.com>>
Date: Tuesday, August 30, 2016 at 1:00 PM
To: Alex Harui <aharui@adobe.com<mailto:aharui@adobe.com>>
Cc: "dev@flex.apache.org<mailto:dev@flex.apache.org>" <dev@flex.apache.org<=
mailto:dev@flex.apache.org>>, "harbs.lists@gmail.com<mailto:harbs.lists@gma=
il.com>" <harbs.lists@gmail.com<mailto:harbs.lists@gmail.com>>
Subject: Re: AW: AW: Will we have a new release out the door till 8th of Se=
ptember?

Sure we could do that.  Can you give more requirements on how the command l=
ine switch would need to work?  I can try to add this as soon as possible.

Thanks,
Om

On Tue, Aug 30, 2016 at 12:57 PM, Alex Harui <aharui@adobe.com<mailto:aharu=
i@adobe.com>> wrote:
Om,

Is there a way to pick up command line parameters so we could use a =96nigh=
tly flag to test against the nightly CI server instead of the mirrors so we=
 could have both code-paths in the repo and wouldn't have to remember to re=
vert some of this code?

-Alex

From: "omuppi1@gmail.com<mailto:omuppi1@gmail.com>" <omuppi1@gmail.com<mail=
to:omuppi1@gmail.com>> on behalf of OmPrakash Muppirala <bigosmallm@gmail.c=
om<mailto:bigosmallm@gmail.com>>
Date: Tuesday, August 30, 2016 at 12:53 PM

To: Alex Harui <aharui@adobe.com<mailto:aharui@adobe.com>>
Cc: "dev@flex.apache.org<mailto:dev@flex.apache.org>" <dev@flex.apache.org<=
mailto:dev@flex.apache.org>>, "harbs.lists@gmail.com<mailto:harbs.lists@gma=
il.com>" <harbs.lists@gmail.com<mailto:harbs.lists@gmail.com>>
Subject: Re: AW: AW: Will we have a new release out the door till 8th of Se=
ptember?

I just looked over your changes.  Looks fine to me.  We should remember to =
revert the hardcoded paths of falcon/flexjs binaries to the mirror urls onc=
e we push the release out.

Then we can test the npm flexjs distribution one last time and push the mod=
ule out to npmjs.org<http://npmjs.org>

Thanks for pushing this out.  It would have taken quite a long time for me =
to figure out all the changes.

Regards,
Om

On Tue, Aug 30, 2016 at 12:47 PM, Alex Harui <aharui@adobe.com<mailto:aharu=
i@adobe.com>> wrote:
OK, I just pushed changes that seem to work with the nightly build.  I thin=
k we have to update the scripts once more once the final release is out on =
the mirrors.  Then is there a final step where we publish this module to th=
e uber Node registry?

I would like to have at least one more PMC member review the release before=
 we cut RCs.  I will post more information in the Last Call thread in case =
folks are filtering for that.

-Alex

From: "omuppi1@gmail.com<mailto:omuppi1@gmail.com>" <omuppi1@gmail.com<mail=
to:omuppi1@gmail.com>> on behalf of OmPrakash Muppirala <bigosmallm@gmail.c=
om<mailto:bigosmallm@gmail.com>>
Date: Monday, August 29, 2016 at 12:37 PM
To: Alex Harui <aharui@adobe.com<mailto:aharui@adobe.com>>
Cc: "dev@flex.apache.org<mailto:dev@flex.apache.org>" <dev@flex.apache.org<=
mailto:dev@flex.apache.org>>, "harbs.lists@gmail.com<mailto:harbs.lists@gma=
il.com>" <harbs.lists@gmail.com<mailto:harbs.lists@gmail.com>>

Subject: Re: AW: AW: Will we have a new release out the door till 8th of Se=
ptember?

Locally, you can test by simply running:

Install: npm install -g
Uninstall: npm uninstall flexjs -g

If you want to test the one deployed on npm, you need to run:
Install: npm install flexjs -g
Uninstall: npm uninstall flexjs -g

Installing will add the flexjs module to:

Windows: C:\Users\<username>\AppData\Roaming\npm\node_modules\flexjs\
Mac: /usr/local/lib/node_modules/flexjs/examples/flexjs/

On Mon, Aug 29, 2016 at 12:31 PM, Alex Harui <aharui@adobe.com<mailto:aharu=
i@adobe.com>> wrote:
How do you test changes?

Sent from my LG G3, an AT&T 4G LTE smartphone

------ Original message------
From: OmPrakash Muppirala
Date: Mon, Aug 29, 2016 11:30 AM
To: dev@flex.apache.org<mailto:dev@flex.apache.org>;
Cc: Harbs;
Subject:Re: AW: AW: Will we have a new release out the door till 8th of Sep=
tember?

Still on it.  Sorry it turned out to be more work than I thought.  Hope to
get it done soon.

Unless someone wants to jump in and help out.  Looks like most of the
changes are in this file:

https://github.com/apache/flex-utilities/blob/develop/npm-flexjs/dependenci=
es/ApacheFalcon.js

Thanks,
Om

On Mon, Aug 29, 2016 at 7:19 AM, Alex Harui <aharui@adobe.com<mailto:aharui=
@adobe.com>> wrote:

>
>
> On 8/29/16, 12:31 AM, "Christofer Dutz" <christofer.dutz@c-ware.de<mailto=
:christofer.dutz@c-ware.de>> wrote:
>
> >So what's the state on this?
>
> I was hoping to hear from Om that the npm was working again.  And I was
> hoping to hear from at least one more PMC member that they checked the
> release packages and they looked ok.  Have you done that?  Plus, at least
> 3 PMC members were on the road last week.  I'd like to get a vote going b=
y
> Tuesday or Wednesday.  I might be able to work on the npm stuff, but I've
> never done it before.
>
> -Alex
>
>


--_000_c443ggwxh5txdhec8yewr2s11472624879788emailandroidcom_--