Re: The 'less-RC' process explained

I've changed 'consensus' to 'agreement' and removed the bit about the reporter doing the fix. Justin, thank you for your contribution. Please keep in mind this is not a legal document, only a rough outline of a process. Now let's move on, I'm sure everyone will agree more than enough time has bee

Re: CodeCoverage Utility Issue

On 12/2/14, 2:10 PM, "Darrell Loverin" wrote: >Hi Alex, > >I’m hoping you can help me with an issue I’m seeing with the CodeCoverage >utility you donated. > >I’m running a mustella test with the coverage server running. What I’m >seeing is the LocalConnection send() method seems to stop working

CodeCoverage Utility Issue

Hi Alex, I’m hoping you can help me with an issue I’m seeing with the CodeCoverage utility you donated. I’m running a mustella test with the coverage server running. What I’m seeing is the LocalConnection send() method seems to stop working part way thru the test. On the CodeCoveragePreloadSWF

Re: The 'less-RC' process explained

Understood. Go tweak the wording on the wiki until you’re happy that it reads correctly. I don’t think anyone would have issues with that. If anyone wants to then tweak it further, great. That’s what wikis are for! ;-) On Dec 3, 2014, at 12:04 AM, Justin Mclean wrote: > Hi, > >> I don’t thin

Re: The 'less-RC' process explained

Hi, > I don’t think Erik was trying to be so precise with his wording. I just want to make sure we're not trying to introduce consensus for releases via this new process. It really needs to be made clear that releases are by majority approval only (ie 3+1 more +1s than -1s) not consensus (3 +1s

Re: Debugging Tests

Just FYI: With the help of Piotr, I managed to get set up to debug the tests. It looks to me that the float is not being composed in the parcel for some reason, but I’m going to have to spend time to track down exactly what’s wrong. I’ll spend some more time on that tomorrow. FWIW, I fixed an

Re: The 'less-RC' process explained

Justin, I don’t think Erik was trying to be so precise with his wording. I think we’re all aware of policy already. Why don’t you fix any wording you feel is inaccurate? If anyone has issues with your corrections, the wording can be reverted and/or discussed. Thanks, Harbs On Dec 2, 2014, at

Re: The 'less-RC' process explained

Hi, I'd like to see a few corrections/changes to this process as described. Re "packaged and signed by a representative of the organization and voted to be valid by the contributors of the project." - as per Apache policy anyone can make a release (but it would be hard if you were not a committ

Audio echo cancellation not working

I have an flex audio chat app and get a bad echo from anyone using speakers & mic, headsets don't cause it. I"m using RTMP, using getEnhancedMicrophone(), following all the suggestions and have experimented with all the settings. I get a NetConnection to my freeswitch server and create NetStreams

Re: [LESS-RC] fix on develop or release branch?

Well, the wiki basically already says this. Fred brought up an alternative, which I thought we should discuss, but since nearly everyone agrees with the existing approach, I think the Wiki is fine as is. Thanks, EdB On Tue, Dec 2, 2014 at 6:46 PM, Mihai Chira wrote: > Shall we make a wiki no

Re: [LESS-RC] fix on develop or release branch?

Shall we make a wiki note of the decision? On 2 December 2014 at 17:45, Erik de Bruin wrote: > Seems like a clear consensus to me: all features in 'develop' go into > 'release', where we fix and merge back into 'develop'. > > Thanks everyone: nice, concise thread, clear resolution. I'm lovin' it

Re: [LESS-RC] fix on develop or release branch?

Seems like a clear consensus to me: all features in 'develop' go into 'release', where we fix and merge back into 'develop'. Thanks everyone: nice, concise thread, clear resolution. I'm lovin' it ;-) EdB On Tue, Dec 2, 2014 at 6:21 PM, Kessler CTR Mark J wrote: > I'm for freezing new addition

Re: Flex SDK Installer broken on Mac OS?

We hope to fix this in the next release of the installer. There are a number of workarounds to try. One is to download the binary package, unzip/untar it and use Apache Ant to run installer.xml. However, you need to use the installer.xml from 4.13.0. Another is to try the AddAIRToSDK.sh in the

RE: [LESS-RC] fix on develop or release branch?

I'm for freezing new additions to the release branch once its created. Allow bug fixes to be applied to the release branch until an RC is cut. Merge the successful fixes back to the development branch -Mark -Original Message- From: Erik de Bruin [mailto:e...@ixsoftware.nl] Sent: Tue

Re: [LESS-RC] fix on develop or release branch?

Erik, > As the RM for this release I tend to lean towards NOT adding features > to the 'release' branch after it has been cut, and to commit bug fixes > to the 'release' branch. I follow this same model myself. The 'release' branch is considered untouchable for the most part during a RC period,

Re: Tour de Flex Mobile

https://issues.apache.org/jira/browse/FLEX-34650 https://issues.apache.org/jira/browse/FLEX-34651 https://issues.apache.org/jira/browse/FLEX-34652 Os melhores cumprimentos, [image: ASSINATURA WaveMaps] [image: Inline images 1] cmonte...@wavesolutions.pt | www.wavesoluti

Re: Flex SDK Installer broken on Mac OS?

Hi, > Due to a glitch in our CI server, we were not aware that there was an > update to the Flash 15 file. I’ve updated the Installer data file and it > should now be able to install 4.13 with AIR/Flash 15. >> Tested some minutes ago, now every thing is fine and I have now a working AIR 15 + Flex

Re: [LESS-RC] fix on develop or release branch?

On 02/12/14 13:59, Erik de Bruin wrote: As the RM for this release I tend to lean towards NOT adding features to the 'release' branch after it has been cut, and to commit bug fixes to the 'release' branch. This. By cutting off the release branch, you are stating the features in that release. Bu

Re: [LESS-RC] fix on develop or release branch?

I read [1]. IMO, it is discussing a different topic. In fact, the previous chapter [3] is about release branches and talks about making fixes in the release branch. My takeaway is that [1] is about deciding what changes that have occurred in the develop branch since the last release should go in

[JIRA](FLEX-34649) Help needed for tlf bug

Hi guys, I'm trying to get to the bottom of a bug in tlf[1] which is surprisingly easy to reproduce and thus frequent. And because of my limited knowledge of tlf, I hit a dead end. I wrote all my current findings on the Jira ticket. I'm pretty sure that the "proper" fix will take more than just

Re: [FLEX-TLF] Building on Windows

I figured out the problem. flex-tlf has a build.properties file where the jvm.args are set; I¹m not sure why there is a setting in build.xml. The values for the jvm.args were too big for my little machine, so after I scaled them back I was able to build TLF. Peter On 12/2/14, 9:14 AM, "Subscripti

Re: Tour de Flex Mobile

Done. https://issues.apache.org/jira/browse/FLEX-34650 https://issues.apache.org/jira/browse/FLEX-34651 https://issues.apache.org/jira/browse/FLEX-34652 On 1 December 2014 at 23:33, OmPrakash Muppirala wrote: > Thanks, Alex! > > Carlos, please file your tickets against these components. > > Rega

Re: [FLEX-TLF] Building on Windows

i've had problems in the past building flex-sdk with java 1.7; i had to revert to 1.6 to get things working worth a try? Lee Burrows ActionScripter On 02/12/2014 14:10, Peter Ent wrote: Hi, I normally do everything on a Mac, but I need to re-sync things on my Windows machine. I've tried to

[FLEX-TLF] Building on Windows

Hi, I normally do everything on a Mac, but I need to re-sync things on my Windows machine. I've tried to build flex-tlf and I get an error that the Java Virtual Machine could not be created and "Could not reserve enough space for object heap". I edited the build.xml file and changed the value

Re: Clean up remote branches in git

Thank you. EdB On Tue, Dec 2, 2014 at 2:56 PM, Mihai Chira wrote: > Just removed the FLEX-34119 branch, which I had created and then > merged with develop. Thanks for the heads up. > > On 1 December 2014 at 18:11, Erik de Bruin wrote: >> Justin, >> >> I'd appreciate it if you read my emails b

[LESS-RC] fix on develop or release branch?

Hi, Fred brought up an interesting point in the other thread: should fixes during the release phase be made on 'develop' and then merged into 'release', or the other way around? This article [1] talks about deciding which features to include in a release, and it leans towards merging from 'develo

Re: Clean up remote branches in git

Just removed the FLEX-34119 branch, which I had created and then merged with develop. Thanks for the heads up. On 1 December 2014 at 18:11, Erik de Bruin wrote: > Justin, > > I'd appreciate it if you read my emails before you misquote me. When > quoting someone, it is polite to include the entire

Re: The 'less-RC' process explained

I considered that as well, but this project decided to follow this workflow [1]. That article suggests that bug fixes are made on the release branch and then (immediately) merged back into develop. That also makes sense, as the release branch will be as stable as possible, while develop may or may

RE: The 'less-RC' process explained

Hi Erick, Nice introduction, I just wanted to ask, it is written "Any issues found should be fixed - preferably by the reporter - and committed to the 'release' branch", why not fix on the dev branch and cherry picked onto the release one avoiding a merge back to the dev branch ? A nice article

Re: The 'less-RC' process explained

Excellent idea. I've added it to the Wiki text. EdB On Mon, Dec 1, 2014 at 9:04 PM, Alex Harui wrote: > I’m ok with it too. I would like to see a specific subject tag for the > way the RM "makes his intention” known. How about [LAST CALL]? That > would make it stand out from the usual email