Wouldn't it be possible to setup an old Jira of the same version Adobe used and then upgrade that version to the one apache uses ... export the issues and provide Apache with that dump? But I agree that importing that many issues is problematic because it does tend to hang the system. But I can't see why Apache doesn't want you to use the Rest interface. With this you would have the opportunity to controll the load that is passed to Apache. Just by adding simple "waits" after every issue. Even with a wait of 2 seconds it would be possible to enter all of them within one day ... think this shouldn't cause any noticable stress on their Jira instance.
Chris -----Ursprüngliche Nachricht----- Von: Alex Harui [mailto:aha...@adobe.com] Gesendet: Dienstag, 5. Juni 2012 09:21 An: flex-dev@incubator.apache.org Betreff: Re: AW: Review after first months of Apache Flex, new guidelines and keeping Flex alive Apache JIRA has been unable to accept our import file of old Adobe bugs, and Apache Infra doesn't want us to use REST or SOAP to jam 30000 issues in there. Apache JIRA was recently upgraded to see if that will help. On 6/5/12 12:05 AM, "christofer.d...@c-ware.de" <christofer.d...@c-ware.de> wrote: > Hi, > > Just a short question ... what problems are you actually having with > Jira? Is it the availability of an instance? The migration of Issues > allready reported to Adobe? ... I would assume there is a huge bunch > of old issues that should be migrated into the Apache Flex Jira. After > stepping in to continue work on Flexmojos, one of my first tasks was > to migrate the Sonatype Jira Issues to the new Flexmojos Jira ... I > created a Java based tool that does this via REST interface (And a lot > of hand-written Json requests). So If this is indeed your main problem with > Jira, just contact me and I'll send you my migrator code. > > I too have seen several developers turn their backs on Flex, but those > were mainly people that never really got very far in learning Flex. > For me and my company Flex is still ultra-important and will be for > the future. That's also one of the reasons for me taking over in the > Flexmojos project. For me the change of Flex mooving to Apache offers > more chances than risks. I know the first start will be hard, as it > allways is as soon as you are presented a huge pile of code that you > now have to start maintaining, but I guess on the long run there will be by > far mor benefits from it. Just to name some: > - Perhaps Flex SDK will eventually be available for Maven > - Freely available Automation will eventually make more and better > tools available > - Mabe some day we will have a Profiler that will work in other IDEs > (Don't know if this is a Flex or a FB + FP thing) > > Well those were my 50ct :-) > > Chris > > > > > -----Ursprüngliche Nachricht----- > Von: Justin Mclean [mailto:jus...@classsoftware.com] > Gesendet: Dienstag, 5. Juni 2012 04:44 > An: flex-dev@incubator.apache.org > Betreff: Re: Review after first months of Apache Flex, new guidelines > and keeping Flex alive > > Hi, > > I also had hoped we would be a lot further along in the process by now. > There's a variety of reasons for this, but it's just mostly it's that > things just have taken a lot longer than everyone originally expected. > > We are still trying to sort out the JIRA infrastructure (there been > work on this and last I heard they were about to do a test import > again), the full Mustalla test suite (Adobe have donated the checkin > tests and tests for > button) and working the parity 4.6 SDK release (which need to abide by > certain fairly restrictive conditions to what can/cant be packaged in > it). While I couldn't predict when those 3 things will be complete > significant progress have been made on all of them. > > Adobe does have full time resources (Alex and Carol) working on > further donations and getting the first parity release out the door > and others are helping where they can/as required. > > Once these 3 items are complete (JIRA, testing framework, initial > parity > release) we'll likely to see a lot more activity from current > committers and Flex SDK users and then Adobe resources can work on > donation of other parts of Flex SDK that are yet to be donated (like > automation, new spark components, new compiler etc). > > I have quite a few things I would like to work on (time permitting) > but without JIRA and a full testing framework it's difficult to be > able to commit patches and new code to the SDK. > >> - We are attached to an application that could die at anytime as have >> already happened Flash Catalyst, Flash Player Debugger for Linux and >> others. > The Flex SDK is not a product as such so can't suffer the same fate as > say Catalyst. The Flash Player is still being supported by Adobe and > is part of Adobe's future plans. I assume you've seen the FlashPlayer > roadmap for the next several versions of the Flash Player? > http://www.adobe.com/devnet/flashplatform/whitepapers/roadmap.html > >> - there is a really fast movement from people that loved Flex to >> technologies such as javascript + html5 + css3, including some core people >> from Apache Flex. > Some of the "core" people are exploring the use of other technologies > but that is normal, being a programmer/developer mean continual > learning and playing about with new technologies. I been using > Javascript since way back in the IE3/Netscape days and I'll use it > again but that doesn't mean I'm moving away from Flex. :-) > >> - some flex projects are becoming ghosts (no commits for quite some >> time) > Any projects in particular? I know for instance FlexLib hasn't been > getting a lot of love but that was the case well before Flex moved to > Apache. as3 commons on the other hand is in active development. One > way to try and fix this would be to try and get people from this list > involved in contributing to those projects. > >> - blogs about flex are dying or moving to other technologies > IMO Blogs tend to written about new "exciting" emerging technologies. > Flex as a mature and proven technology doesn't attract the large > audience that most bloggers want. > > Thanks, > Justin -- Alex Harui Flex SDK Team Adobe Systems, Inc. http://blogs.adobe.com/aharui
