They might already be translated being mostly standard lo open source
licences.
Hi,
> Justin, are you ready to cut an RC2?
Done.
http://people.apache.org/~jmclean/Apache%20Flex%20Installer%20RC2/
Justin
Hi,
>>> Justin, are you ready to cut an RC2?
RELEASE_GUIDE instructions need updating (2.0.1 vs 2.0.0) I'll change and check
in.
Justin
Hi,
> Justin, are you ready to cut an RC2?
Can do if the satellite uplink is up for it. ;-)
Justin
Hi,
A lot of people like and use intelliJ.
Justin
Hi,
> Well, that group would need approval from Apache to use Flex anywhere in the
> name of the installer, but yeah, an independent group of folks can certainly
> go off and create their own installer.
Seems less of an issue than the process that is currently being suggested.
Worse case it can b
HI,
> We are taking something from SVN and consuming it in a binary distribution
> that we've deployed to our site and telling the world to use it.
Not exactly it is optional - it's only used if you don't specify a config file
via the command line.
> But in this case, there is code involved
It's
Hi,
> -From [1], a release is "anything that is published beyond the group that
> owns it.". Putting the config.xml on the site to be consumed by one of our
> binaries makes it part of a release and requires a vote before it happens.
It published on the Flex web site by Flex committers give acces
Hi,
> I'm not sure Apache Flex is allowed to use Github as a end-run around Apache
> policy.
The installer would not belong to Apache but be a separate project that is
worked on by people who want to give users of the Flex SDK an easy way to
install it. All it does it take the binary kit from
Hi,
> Are you suggesting that the workflow is to use the -config switch for
> testing? Then we are not testing the final configuration.
The same XML file would be uploaded so we would be testing the final config.
Again this is a program to help users download the binaries to use in their IDE
HI,
> I don't see why our binary distributions would be a problem to host
> anywhere... The added stuff the installer downloads -- we can't host
> those, but the binary stuff should be ok.
The binary kit as produced by Apache is fine and could be hosted anywhere,
what I meant was a complete zi
Hi,
Also keep in mind is that the installer is provided as a convenience for SDK
users to download the binary kit and all 3rd party required pieces and get it
working in there IDE with a mimimum of trouble. While supporting multiple
versions to download etc would be a nice to have feature it's
Hi,
I'm not sure there's a reason to set the Flash Player version for the SDK other
than the mimimum version.
The Flash player version can be set on a project by project basis when using an
IDE, an SDK compiled for 11.1 can be compiled into a project that uses 11.1 -
11.6.
I'm not tested a S
Hi,
> 2) Is this a correct implementation? I'm wondering how would we test the
> next release. As soon as you replace/update that .xml file so we can test
> the next installer we are forcing everyone to suddenly start taking the next
> version. I understand you are saying we don't need to "test
Hi,
> How does the UI handle choosing which version to download?
Currently it downloads the latest Flex version. If it was to download previous
version it would need to get them fro the archive and need to be configured
with multiple URLs.
I think it was decided not to do this as having 4.9 not
Hi,
> Is there a specific reason why we are targeting FP 11.1 as opposed to 11.4 or
> 11.5?
To not force people to update Flash Player and change the minimum player level
the Flex confg file.
The SDK will work with 11.4 and 11.5 but currently uses no 11.4 or 11.5
features so there no real need
Hi,
>> Would you consider the disclaimer page to be part of the source?
> The DISCLAIMER file is in the source kit for incubating releases.
I was referring to the disclaimer link in the application not the DISCLAIMER
file.
> Source kits are (potentially filtered) dumps of what is in SVN.
And th
Hi,
> Apache only officially releases (and we are voting on) a source distribution
> for the installer.
Would a run time loaded config file be really considered part of that source?
Basically it's the same as the build.properties for the Flex SDK. While the
build.properties is part of the sour
HI,
> Can we actually release this source if we don't have it pointing to the
> final dist folder for 4.9?
I think we can and that's not an issue.
Only the XML file would need to change which in not in the installer directory.
http://incubator.apache.org/flex/sdk-installer-config-2.0.xml
The ins
Hi,
The OSX version of the installer can be found here:
https://people.apache.org/~jmclean/Apache%20Flex%20Installer%20RC1/
Thanks,
Justin
Hi,
> I have fixed those issues and checked it in. Please give it a run through
> and see everything works as it should.
Bandwidth a bit slow here (took 3 or so hours to run last time) but it starts
up fine.
I've just recompiled and put up the .dmg files at the same place as before.
Start the
Hi,
> Fixing these issues is in my to-do list. Should I give it a go before we
> cut an RC?
Up to you. I don't think they are required for a RC as it works fine without
those minor changes.
> I have a few hours available before I go out partying for the
> new year.
Been there done that, it's af
Hi,
> Great! So you mind tagging trunk with 2.0 RC1?
You might have to do it I got an SVN error. May because of my slow connection.
I tried twice same error.
svn: '/repos/asf/!svn/bc/1427276/incubator/flex/utilities/trunk' path not
found: 404 Not Found (https://svn.apache.org)
I also running th
Hi,
> Justin, any luck with your issue?
Yep sorted. Made a few minor mods to the build files and notes as well (see
checkins).
Here you go one dmg and associated files:
https://people.apache.org/~jmclean/Apache%20Flex%20Installer%20RC1/
Thanks,
Justin
Hi,
> Any chance you are pointing to a Windows AIR SDK and not the Mac SDK for
> AIR?
Thanks that looks like it was it. I download a clean AIR 3.4 SDK from Adobe and
it included the files I must of got mixed up with versions along the line
somewhere.
Justin
[
https://issues.apache.org/jira/browse/FLEX-5?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13541541#comment-13541541
]
Justin Mclean commented on FLEX-5:
--
Updated scripts and README svn che
[
https://issues.apache.org/jira/browse/FLEX-4?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Justin Mclean resolved FLEX-4.
--
Resolution: Fixed
Fix Version/s: Adobe Flex SDK Next
> AIRSDK version numb
[
https://issues.apache.org/jira/browse/FLEX-4?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13541540#comment-13541540
]
Justin Mclean commented on FLEX-4:
--
Updated to AIR 3.4 svn checkin 142
Hi,
Can anyone confirm that both of these scripts work on windows (in the develop
branch).
From what I can see the constructFlexForIDE.sh takes an ApacheFlex SDK and
copies into it the bit needed by FB from a 4.6 SDK. You end up with AIR 3.1
this way. makeApacheFlexForFlashBuilder.bat does the
Hi,
> Does it compile in Flash Builder?
No it fails as well looks like there's hard coded paths in the project files.
/Applications/Adobe Flash Builder 4.6/sdks/4.8.0 does not exist.
> How did you create the flex sdk for flash builder? Using the script or the
> installer?
The make IDE script fr
Hi,
I'm getting a different error:
packagenative:
[java] SDK is missing file
/Users/justinmclean/Documents/air/mac/AdobeAIRSDK/lib/nai/bin/naip
BUILD FAILED
/Users/justinmclean/Documents/Adobe Flash Builder 4.6/Apache Flex
Utilities/installer/build.xml:203: Java returned: 5
Looking at th
Hi,
> I am using Apache Flex 4.8 to build the installer. Which means AIR 3.1,
> right?
I think we should be using AF 4.9/AIR 3.4 - be nice if the SDK and installer
were in sync.
Justin
Hi,
> Are you sure you have checked out utilities/trunk/common/ as well?
OK it wasn't clear to me that you need to check out all of the utilities trunk
rather than just the installer directory.
We'll need to add instructions to the README on how to checkout the project.
What version of AIR ar
Hi,
> Are you sure you have checked out utilities/trunk/common/ as well?
Nope as that's not included in the build instructions.
It says to check out source and just run this:
ant build [-DFLEX_HOME=/path/to/apache/flex/sdk] [-DAIR_HOME=/path/to/air/sdk]
How/where does this need to be check ou
Hi,
BTW for a RC we'd need to remove the incubating DISCLAIMER and RELEASE_NOTES
need a license header.
Justin
Hi,
Looks like something isn't quite right in the build file on OSX.
[mxmlc] command line: Error: unable to open
'/Users/justinmclean/Documents/Adobe Flash Builder 4.6/Apache Flex
Installer/../common/src'
Any idea why the ".." is in there?
Justin
Hi,
> Great. I am available in case you run into any issues.
Having a few compile issues right now (issue with air-config.xml) - should be
sorted soon.
Thanks,
Justin
Hi,
> Trunk is good to go.
Any reason we're working in trunk and not develop? Seems a little inconsistent.
> I have created the source kits and windows binary kit. We just need the Mac
> binaries now.
Just sync up SVN and I'll have a go at making one now.
Thanks,
Justin
HI,
> I am ready to put out an RC1 for voting. I need a committer with a Mac to
> build and sign a .dmg file for the Mac installer.
I can do that if needed. Have you tagged RC1 in some way or should I just use
trunk?
Justin
Hi,
>> Are the instructions on this page for the binary release correct? Should it
>> mention makeFlexSDKForFlashBuilder.sh?
>> http://incubator.apache.org/flex/download.html
> Is the issue getting it to work in FB or other IDE?
Just getting it to work I think it may be AIR related:
"I tried ins
Hi,
> Those files that were already changed probably aren't in the commit for the
> merge since there were no diffs.
But as they were initially modified their history would of been carried over
into the release branch when I created it, so don't think we've lost any
history.
Justin
Hi,
Seen a couple of complaints on twitter with people having issue
installing/compiling.
Are the instructions on this page for the binary release correct? Should it
mention makeFlexSDKForFlashBuilder.sh?
http://incubator.apache.org/flex/download.html
Thanks,
Justin
Hi,
> Did you revert the trunk checkins that shouldn't have been checked in?
No just overrode anything in conflict with the release version, everything
should of been in develop/release anyway. (ie same changes checked in twice)
Justin
Hi,
> I did a full checkout of trunk, and merge no longer gave that error but it
> took so long it timed out.
Looks like if you check out on people.a.o it works, I'll do a merge, check in
and tag. Anything that in conflict I'll take the the release version (there a
few things).
Thanks,
Justin
Hi,
> the code up in decent shape, maybe there are some other devs out there that
> dislike the current asdoc and maybe would like to run there documentation
> with a new and really fast documentor that is forgiving.
I played about with the existing asdocs and it's very painful to modify, so I'm
Hi,
> Did you already open up a ticket with infra to get that looked at?
No but I have now:
https://issues.apache.org/jira/browse/INFRA-5708
Thanks,
Justin
Hi,
> I will try to work on the installer v2 RC very soon.
I forgot we will have to vote on the installer (before releasing it) so it's
realistically going to be a week or more before we can officially announce 4.9
if we go down this path.
Perhaps we just announce it now and say new installer
Hi,
> You can see the diagram for the nvie model here:
> http://nvie.com/posts/a-successful-git-branching-model/
Yep and you can see master being tagged which is same as our trunk.
Justin
Hi,
> Make a tag from the release branch, not the develop branch.
Only issue here is that branch may be be around as long as the trunk or
develop. Trunk is what's supports to contains the last stable release so make
more sense for it to be tagged. (IMO)
But yep get the point re not tagging dev
Hi,
Still to do:
1. Place release in correct location ie /dist not /dist/incubation (OK for now
I think)
2. Official announcement to various lists
3. Sync release branch to production
4. Tag trunk with "Apache Flex 4.9.0"
Have I forgotten anything?
Currently 3 is broken for some reason (SSL ha
Hi,
Do we want to hold off on making an official release announcement (on various
lists etc etc) until we have an installer that supports 4.9? I assume that's
the way most people are going to install it.
Justin
> Did you push those changes in the CMS?
No I was waiting for it to reviewed mirrors to mostly have the new files.
If you've not done so you can publish it.
Thanks
Justin
Hi,
> OK, I hope we don't get in trouble for that (non-incubating artifacts in the
> incubator folder),
I wouldn't think so. Just revert the change?
Justin
Hi,
Yep I can see it already make it to these mirrors:
http://www.eu.apache.org/dist/incubator/flex/
http://www.us.apache.org/dist/incubator/flex/
And it's reached France:
http://mirrors.ircam.fr/pub/apache/incubator/flex/
And probably a few other places, not in the Australian mirrors yet but th
Hi,
> Crap. While waiting for the upload I saw this on [2]. So I guess this
> isn't going to work out.
That's OK for now.
4.9.0 is currently in the incubator directory (which I assume will be mirrored)
and we can use that until we sort out the exact process.
Thanks,
Justin
Hi,
> Maybe I have enough karma as PMC Chair. I made a release/flex directory and
> it seemed to work. See if you can svn add to it.
Not sure I have SVN access. My understanding was you just copied the files
across to the dist directory and it got mirrored after 24 hours or so.
If I do this:
Hi,
I've added some information to the web site for the 4.9 release, if someone
could review and make it live I'd appreciate it.
Paged edited include index, download and timeline.
Thanks,
Justin
Hi,
> AFAICT, they haven't serviced the main TLP JIRA so I'm not surprised. I
> assume you tried to make the directory?
Yep - permission denied :-)
> I've seen some emails indicating that dist is automatically archived. Is it
> not already in the archive?
To be honest I don't even know were th
Hi,
> I got the same error trying to do an svn update.
I was about to do a full check out of both trunk and develop with no issues
over a slow link, but the merge dry run gave that error. I've not seen the
issue before.
It seem to happen at random times, ie some times it would get further th
Hi,
Currently there no top level flex directory in www.apache.org/dist. I've raised
a JIRA issue for this:
https://issues.apache.org/jira/browse/INFRA-5706
Until that's resolve I've placed the 4.9 release here:
http://www.apache.org/dist/incubator/flex/4.9.0/
Does anyone know where the 4.8.0 re
Hi,
72 hours have passed since the Apache Flex 4.9 RC7 vote was opened and the
results are now in:
4 + 1 binding votes by
Justin Mclean
Nicholas Kwiatkowski
OmPrakash Muppirala
Alex Harui
0 -1 votes
As there are at least 3 more positive votes than negative votes Apache Flex 4.9
RC7 is now
Hi,
Can someone be kind enough to run this from the base of a clean checked out
trunk and mail the output to the list.
svn --dry-run merge
https://svn.apache.org/repos/asf/incubator/flex/sdk/branches/release4.9
This is a dry run so no changes will occur it will just tell you what changes
wil
Hi,
> I only checked the first file, but diff says it is the same, so not sure why
> you are getting a conflict. Are you using the -reintegrate option?
No I'm not, as far as I'm aware:
1. --reintegrate is not required in SVN 1.6+
2. We don't want to use --reintegrate as the release branch stil
Hi,
I've updated;
https://cwiki.apache.org/confluence/display/FLEX/Release+Guide+for+the+SDK
In particular to take into account the develop and release branches.
This a slight issue with tagging the release as the release is built from the
release branch, but I assume we would want to tag the t
Hi,
Just doing a dry run of the merge of release into develop and Im getting a
large number of conflicts with mustella baseline images.
Anyone have any idea why and if it's an issue? Perhaps they were checked into
the wrong branch or both branches and the develop branch after the release
branc
+1 (binding)
Hi,
> You could upload the .asc file to your home directory on
> people.apache.org as well.
It's also here (which I forgot about).
https://people.apache.org/keys/committer/jmclean.asc
Thanks,
Justin
Hi,
My keys can also be found here:
http://pgp.mit.edu:11371/pks/lookup?op=vindex&search=0xE0F28593AEEAD151
Justin
Hi,
> Justin, I dont see your PGP key here [1]
My key can be found at teh bottom of this file:
http://svn.apache.org/viewvc/incubator/flex/sdk/branches/release4.9/KEYS?view=markup
But as part of the release, in future, I think we should add the KEYs file to
the release candidate to make things
Hi,
Any comments, questions or issues with the RC7 release just reply to this
thread.
Thanks,
Justin
Hi,
This is a Apache Flex 4.9.0 release candidate 7. Please see the RELEASE_NOTES
and the README.
Fixed in this release candidate:
- Fix minor issue with 2 files failing rat license test
- Minor changes to README
The release candidate can be found here;
http://people.apache.org/~jmclean/Apache
Hi,
> I don't see a vote thread for RC7.
Looks like it was rejected as spam :-(
Technical details of permanent failure:
Google tried to deliver your message, but it was rejected by the recipient
domain. We recommend contacting the other email provider for further
information about the cause
Hi,
> I don't see a vote thread for RC7.
It was sent. You don't see email you send appear on the list (gogole gmail
issue I think), but I can't see it in the archive either. I resend - thanks for
pointing that out.
> It would be better if we have discussion about RC7 in its own thread.
Agreed
Hi,
> I'll give RC7 a whirl tomorrow if I get a chance before heading out for the
> holiday.
Thanks + enjoy. Here's hoping I'll not be making RC8 on christmas day (tomorrow
for me) :-)
Justin
Hi,
> Windows 7, tested RC6 with the binary distro and from building it from
> source.
Thanks for that info, I'm on OSX so good to know it fine on windows as well.
There is only very minor differences between the RC6 and RC7 and none that
effect the actual SDK. Minor changes to the README and bu
Hi,
> I didn't verify the RAT or that jazz, but the source and binary builds seem
> good. My last-minute-check of my projects seem good.
Good to know, what OS did you use? and did you use the SDK installer or not?
Thanks,
Justin
Hi,
> I'm ready for the next RC.
RC7 is released.
> Let me know if you need help
Thanks - all good for now I think.
Justin
Hi,
> I saw your checkin. I agree that is the right thing to do. I ran ant main
> release and rat is clean.
Same here rat is fine, it compiles and md5 hashes are correct.
> I'm ready for the next RC. Let me know if you need help.
Just uploading now - almost done after 2 hours.
Thanks,
Justin
I take a look at this today
Hi,
> Rat-check failed with two issues. I'm fixing that now and running rat again
> (takes about an hour). I also fixed a minor issue in the README since we're
> going to have to re-kit again.
It does look like it related to as_docs, at a guess the en_US locale is hard
coded in the clean and t
Hi,
> Strangely, on this run, RAT caught packages.dita files in rpc and
> textlayout. It is too late at night for me to figure out why there were not
> in the first
> rat report. Maybe you have a better knowledge of what these files are for.
XML generated files I think when creating the asdocs?
Hi,
This is a Apache Flex 4.9.0 release candidate 6. Please see the RELEASE_NOTES
and the README.
Fixed in this release candidate:
- Fix so that the release build compiles the experimental projects (issue with
empty.properties being removed from binary package)
The release candidate can be fo
Hi,
>incubator/flex/sdk/branches/release4.9/README (props changed)
>
> incubator/flex/sdk/branches/release4.9/frameworks/projects/apache/compile-config.xml
>(props changed)
Assume nothing changed in the above 2 files?
Thanks,
Justin
Hi,
> What's your last day before you take off?
Satellite internet connection up and running, it's slow but working (0.3 Mbps
down/0.1 Mbps up and 1 second ping time) so as long as I don't have to upload
too many new RCs should be OK.
Thanks,
Justin
Hi,
I just checked the signature files for the binaries in RC6 directory and they
are correct.
Thanks,
Justin
Just change the end of the release URL from 5 to 6
Just waiting a late plane. Just in case there was an issue I made a full
RC6 feel free to use that.
[
https://issues.apache.org/jira/browse/FLEX-33323?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13537791#comment-13537791
]
Justin Mclean commented on FLEX-33323:
--
Just a suggestion. Why not just tes
Hi,
Any chance we can get something about the graduation up on the Flex blog?
http://blogs.adobe.com/flex/
Even if it's after the holiday period and by then it could have info about the
new 4.9 release as well.
Thanks,
Justin
Hi,
Nick Burch just posted a message to the small events list about the BarCamp,
Hackathon and a few other small community events happening around the
ApacheConEU conference.
Anyone want to help out?
Is there any interest creating a Flex themed event of some sort?
Is anyone actually going along
HI,
> Then it shouldn't be downloaded the files every time. Does it start with
> a clean directory and fetch everything from svn or just fetch changes?
It only fetches the SVN changes, strategy is set to "use svn update as much as
possible".
Looks like it reusing the workspace as well so not
Hi,
> We have the "Discard Old Builds" option selected. Should we try
> keeping old builds? That should help with download issues, perhaps?
It keeps the last 7 day of builds up to a maximum of 10. Untick that and the
machine will likely run out of disk space fairly quickly (happened once befor
Hi,
Fairly certain clean and not a super-clean, looking at the script it does the
following:
ant clean main source-release
Now we have mustella/checkin tests working we probably should add
binary-release to that.
Each Jenkins runs is in it own workspace so I think that's why it downloads
eac
Hi,
> In the binary kit, frameworks/build.xml does not build cleanly.
I've fixed, tested and checked in changes that fix this issue (rename
blank.properties to experimental.properties).
I don't think this is a major enough issue to stop the current vote so I've
just replaced the binary packages
Hi,
> Can you add other paths to the GitHub sub-task?
Can't recall them of the top of my head and they are not documented on our site
that I could find.
>> Content on the web site re check out code etc ect
> The first sub-task is supposed to cover the website and SVN, IIUC.
I was referring to t
Hi,
No need for infra to be involve with Jenkins (hopefully), we can edit the
config there and change the SVN paths.
There quite a few more github paths that need to change as well as we have
other projects than the SDK.
> Can anyone think of other things that need migrating?
Content on the w
Hi,
>> And if you decide to rekit I think you should mention in the README that
>> although we have graduated we are still using incubator urls - which will
>> redirect after we've been moved.
Already there (lines 15 + 16):
The Apache Flex project has just graduated to be a top level Apache
Hi,
> Why bother releasing as 'incubating' after we have graduated. Can we wait
> until our top level domain is up and running before we release?
That's probably a few weeks to a month away at a guess. I see no need to have
one rely on the other.
> I am sure we are not going to get enough test
Hi,
> Well if you built in the tree you had an empty.properties in each locale
> directory which you don't have on the kit.
Found the issue the stage-locales target is removing all empty.properties files
- anyone know why?
Hi,
> I always unzipped both the source and binary kits and built them before I
> announced them.
Perhaps I didn't quite have a clean tree, or that clean/super-clean isn't
cleaning up everything? I'll look into it.
The binaries are for convenience only really but I agree you should be able to
1 - 100 of 1228 matches
Mail list logo
