incubator-flex-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "" <>
Subject AW: Review after first months of Apache Flex, new guidelines and keeping Flex alive
Date Tue, 05 Jun 2012 19:34:12 GMT
Atlassian Offers Open Source Projects the Full set of their tools free of charge. Even the
hosted "On Demand/Studio" Suite.

That's what we did with Flexmojos. What I find really nice about it, ist hat I don't have
to keep the stuff updated, backed up, etc. 

Mabe this would be an option for Flex too?


-----Urspr√ľngliche Nachricht-----
Von: Alex Harui [] 
Gesendet: Dienstag, 5. Juni 2012 18:54
Betreff: Re: Review after first months of Apache Flex, new guidelines and keeping Flex alive

On 6/5/12 7:59 AM, "Bertrand Delacretaz" <> wrote:
> Although the JIRA import problems need to be solved, I don't see what 
> prevents people from using the existing instance at 
> to go forward without 
> having to wait for that.
Folks are welcome to file new bugs there, but I thought we agreed we didn't want duplicate
issues to manage after the import happens.
> I assume issues created there can be linked to existing issues in the 
> Adobe Flex JIRA if that's still up, and if that's not the case we can 
> fairly easily host a static copy of that somewhere so that people can 
> find the required information.
Adobe JIRA is still up, but I am hearing that it won't be up forever.

What does it take to host a static copy, and, if we can have a standalone copy, why does it
have to be static?  I know it is a trade-off, but having our own JIRA instance still seems
to have more pro's than con's.  The likelihood of transferring instances between Flex and
other Apache projects seems minimal.

Maybe every large project going into the incubator should be required to contribute a server
and disk space.  Then it would be our own fault if we run out of space doing CI builds, we
can import SVN dumps whenever we want to, and we can have our own JIRA.

Alex Harui
Flex SDK Team
Adobe Systems, Inc.

View raw message