HI,
> I'm still curious as to where it is written down so I don't forget next
> time when I put up FlexJS or Falcon rcs.
I took a look at a few other project in the release area and it's basically all
over the place. (There's even some RCs in the dist release area!) The important
thing obviousl
OK. I added following the pattern I saw in the sdk folder.
I'm still curious as to where it is written down so I don't forget next
time when I put up FlexJS or Falcon rcs.
-Alex
On 12/13/13 12:15 AM, "Justin Mclean" wrote:
>Hi,
>
>>
>>https://cwiki.apache.org/confluence/display/FLEX/Release+
Hi,
> https://cwiki.apache.org/confluence/display/FLEX/Release+Guide+for+the+SDK
> Should it be updated to also mention LICENSE?
The LICENSE file is above the rc directories there so there no need to change
the docs as there no need to add it every time you make a RC.
Thanks,
Justin
On 12/12/13 11:44 PM, "Justin Mclean" wrote:
>Hi,
>
>>> You might want to add a LICENSE file before calling a vote :-)
>> Crap. Which package(s) is it missing from?
>I didn't check the packages (yet), but there's normally one in the SVN
>tree.
I was following
https://cwiki.apache.org/confluenc
Hi,
>> You might want to add a LICENSE file before calling a vote :-)
> Crap. Which package(s) is it missing from?
I didn't check the packages (yet), but there's normally one in the SVN tree.
>> And while not essential a KEYs file is also useful.
> I thought KEYS weren't supposed to be in the pa
On 12/12/13 11:25 PM, "Justin Mclean" wrote:
>Hi,
>
>You might want to add a LICENSE file before calling a vote :-)
Crap. Which package(s) is it missing from? I'm seeing one when I expand
the src.tar.gz and -bin.zip
>
>And while not essential a KEYs file is also useful.
I thought KEYS weren't
Hi,
You might want to add a LICENSE file before calling a vote :-)
And while not essential a KEYs file is also useful.
Thanks,
Justin
n we won't be touching flex-utilities. We can't
>>check a zip in there. The packages will go on dist after a vote.
>
>Sorry, I meant "commit to dist".
>
>Maurice
>
>-Message d'origine-
>De : Alex Harui [mailto:aha...@adobe.com]
>Envoyé :
orry, I meant "commit to dist".
Maurice
-Message d'origine-
De : Alex Harui [mailto:aha...@adobe.com]
Envoyé : jeudi 12 décembre 2013 20:02
À : dev@flex.apache.org
Objet : Re: PixelBender and Builds.a.o
On 12/12/13 10:32 AM, "Maurice Amsellem"
wrote:
&
On 12/12/13 10:32 AM, "Maurice Amsellem"
wrote:
>>Another possibility is that we leave the PBK's where they are and simply
>>add new build targets to flex-sdk build script. That might be simpler
>>and gives us the option of >reverting back to a single package if we
>>find that we can someday.
es/pixel_bender, that could be used by other scripts...
WDYT?
Maurice
-Message d'origine-
De : Alex Harui [mailto:aha...@adobe.com]
Envoyé : jeudi 12 décembre 2013 19:06
À : dev@flex.apache.org
Objet : Re: PixelBender and Builds.a.o
Another possibility is that we leave the PBK&#
;TLF.
>
>Is that correct ?
Yup. See my other reply. It might be best to just add new targets to the
SDK build scripts.
>
>Maurice
>
>-Message d'origine-
>De : Alex Harui [mailto:aha...@adobe.com]
>Envoyé : jeudi 12 décembre 2013 18:56
>À : dev@flex.apache.org
@adobe.com]
Envoyé : jeudi 12 décembre 2013 18:56
À : dev@flex.apache.org
Objet : Re: PixelBender and Builds.a.o
I was going to move (not copy) the pbks out to flex-utilities. Today we
already pull in source from flex-tlf repo when making a release package.
I think it will work if I do essenti
implies the build file in dist would fetch the pbk sources from git,
>>which means cloning the whole git flex-sdk repo for 10 source files...
>>
>>So it's git clone for 10 files, or duplicate source, but for files that
>>won't change much.
>>
>>WDYT?
>
git flex-sdk repo for 10 source files...
>
>So it's git clone for 10 files, or duplicate source, but for files that
>won't change much.
>
>WDYT?
>
>Maurice
>
>-Message d'origine-
>De : Alex Harui [mailto:aha...@adobe.com]
>Envoyé : jeudi 12 déce
t's git clone for 10 files, or duplicate source, but for files that won't
change much.
WDYT?
Maurice
-Message d'origine-
De : Alex Harui [mailto:aha...@adobe.com]
Envoyé : jeudi 12 décembre 2013 18:20
À : dev@flex.apache.org
Objet : Re: PixelBender and Builds.a.o
>
>-----Message d'origine-
>De : Alex Harui [mailto:aha...@adobe.com]
>Envoyé : jeudi 12 décembre 2013 17:44
>À : dev@flex.apache.org
>Objet : Re: PixelBender and Builds.a.o
>
>I agree with most of it except:
>
>A) we can't auto-commit to dist. I believe only
ying to detail the steps, in case it needs to
be done later (by anyone who want to).
Hoping the infra will fix the current issue...
Maurice
-Message d'origine-
De : Alex Harui [mailto:aha...@adobe.com]
Envoyé : jeudi 12 décembre 2013 17:44
À : dev@flex.apache.org
Objet : Re: Pixe
is the easiest, and it does not break any
>Apache rule.
>
>Maurice
>
>-Message d'origine-
>De : Alex Harui [mailto:aha...@adobe.com]
>Envoyé : jeudi 12 décembre 2013 15:40
>À : dev@flex.apache.org
>Objet : Re: PixelBender and Builds.a.o
>
>
>
>On 1
On 12/12/2013 16:27, Maurice Amsellem wrote:
What option in 4) I think a) is the easiest, and it does not break any Apache
rule.
But it makes these files even more special than they already are.
The installers job is to fetch dependencies of the SDK and do the right
thing with them, so adding
ckMD5+unzip step in flex sdk installer
Is that correct?
What option in 4) I think a) is the easiest, and it does not break any Apache
rule.
Maurice
-Message d'origine-
De : Alex Harui [mailto:aha...@adobe.com]
Envoyé : jeudi 12 décembre 2013 15:40
À : dev@flex.apache.org
Objet :
On 12/12/13 5:03 AM, "Maurice Amsellem"
wrote:
>I am trying to understand the steps below:
>
>Where would the pbk => pbj compilation take place ?
In the build script for this "project".
>
>Where would the pbj be stored after the build , if the build does not
>occur on the CI?
On the same serve
age d'origine-
De : Alex Harui [mailto:aha...@adobe.com]
Envoyé : mercredi 11 décembre 2013 22:49
À : dev@flex.apache.org
Objet : Re: PixelBender and Builds.a.o
It is probably worth waiting for response from Justin.
Any volunteers to do the work? I think the steps are:
1) copy the p
nvoyé : mercredi 11 décembre 2013 20:10
>À : dev@flex.apache.org
>Objet : PixelBender and Builds.a.o
>
>Thanks to Maurice, we have a pretty good idea of why Jenkins on
>builds.a.o is not able to build the Flex SDK. Unfortunately, it isn't
>clear that infra knows how t
Agree with the upstream package. Sounds like a good solution, and rather easy
to put in place.
Maurice
-Message d'origine-
De : Alex Harui [mailto:aha...@adobe.com]
Envoyé : mercredi 11 décembre 2013 20:10
À : dev@flex.apache.org
Objet : PixelBender and Builds.a.o
Thanks to Ma
On Wed, Dec 11, 2013 at 11:30 AM, Alex Harui wrote:
>
>
> On 12/11/13 11:25 AM, "OmPrakash Muppirala" wrote:
>
> >On Wed, Dec 11, 2013 at 11:09 AM, Alex Harui wrote:
> >
> >> Thanks to Maurice, we have a pretty good idea of why Jenkins on
> >>builds.a.o
> >> is not able to build the Flex SDK.
s/hardware/gg463353.aspx + click
on the "download" button
google for "Session 0 isolation".
Regards,
Maurice
-Message d'origine-
De : Maurice Amsellem [mailto:maurice.amsel...@systar.com]
Envoyé : mercredi 11 décembre 2013 20:27
À : dev@flex.apache.org
Obj
On 12/11/13 11:25 AM, "OmPrakash Muppirala" wrote:
>On Wed, Dec 11, 2013 at 11:09 AM, Alex Harui wrote:
>
>> Thanks to Maurice, we have a pretty good idea of why Jenkins on
>>builds.a.o
>> is not able to build the Flex SDK. Unfortunately, it isn't clear that
>> infra knows how to fix it or ca
process could be run out of session, which is not the case with JNLP (the
window is closed when you close the session).
Maurice
-Message d'origine-
De : Erik de Bruin [mailto:e...@ixsoftware.nl]
Envoyé : mercredi 11 décembre 2013 20:21
À : dev@flex.apache.org
Objet : Re: PixelBe
On Wed, Dec 11, 2013 at 11:09 AM, Alex Harui wrote:
> Thanks to Maurice, we have a pretty good idea of why Jenkins on builds.a.o
> is not able to build the Flex SDK. Unfortunately, it isn't clear that
> infra knows how to fix it or can fix it given how they want to run that
> server.
>
I will g
I'm not sure if it is worth more time to find out why it stopped working.
It could be the server was not running as a service until a recent reboot,
or some recent upgrade of Jenkins broke the option that should have
allowed the service to use a window.
But if we are going to abandon builds.a.o fo
Your solution sounds good, and I like the "bring Linux up to par" part.
What I still can't figure out is why the builds stopped working
suddenly a week ago, with Gavin maintaining he never changed a thing.
Well, I guess it doesn't really matter. I hope Om gets his VM online
soon, so we can leave b
Thanks to Maurice, we have a pretty good idea of why Jenkins on builds.a.o
is not able to build the Flex SDK. Unfortunately, it isn't clear that
infra knows how to fix it or can fix it given how they want to run that
server.
Meanwhile, I'm still trying to get access to the PB compiler source, but
33 matches
Mail list logo
