Build failed in Jenkins: royale-asjs_MXTests #1219

See -- [...truncated 1003.21 KB...] [mxmlc] scanning for overrides: ObjectUtil [mxmlc] scanning for overrides: SolidBorderUtil [mxmlc]

Build failed in Jenkins: royale-asjs_MXTests #1218

See Changes: [noreply] Update GroupBase.as [harbs] Update issue#486 (part2) prevent currentStateChange event to be fired if --

Re: Nightly Build Server going offline

I was only thinking about temporary distribution of the nightly build while the CI server is offline. I'm not sure it makes sense to always copy the nightly build somewhere else. I think the bandwidth would add up. I'm mainly asking if anyone thinks it would be a problem if the nightly builds

Re: Branches and Commits and Cherry-Picking

On 10/5/19, 7:08 AM, "Carlos Rovira" wrote: Hi Alex, - release: Here's where I see differences. Once we decided we want to release, is because develop has the final state to cut a release. No more commits are needed for that release. So once a RM start the process and

Build failed in Jenkins: royale-asjs_MXTests #1217

See -- [...truncated 1004.23 KB...] [mxmlc] scanning for overrides: ObjectUtil [mxmlc] scanning for overrides: SolidBorderUtil [mxmlc]

Re: Nightly Build Server going offline

Hi Alex, you're talking about just storing nightly builds? what about using some free storage out there, like a google drive, dropbox, or other service like this. We can create an "apacheroyale" account and share credentials in private. El sáb., 5 oct. 2019 a las 2:18, Alex Harui () escribió: >

Re: Branches and Commits and Cherry-Picking

Hi Alex, I'm with the article exposed in [1], I think I'm using it since 2010. But I think we have a different interpretation of a release branch. For what I saw for almost 10 years using git is that we have: - master: Is the "stable" branch with "released" content. So latest release can be