IMO, we did an SDK parity release because: 1) we wanted to assure customers that we weren't going to break anything or do anything crazy wild with the code 2) there were lots of pieces that needed integration (TLF, MXMLC, OSMF, BlazeDS, etc) 3) we wanted to make sure we had everything we needed from Adobe. 4) we need to make sure we got the licensing and other mechanics worked out
I think folks may trust us by now, so it may not be worth making a parity release. -Alex On 8/1/13 11:11 PM, "Cyrill Zadra" <cyrill.za...@gmail.com> wrote: >Hi Erik > >It think it would be great to release soon a first FlexUnit under Apache. > >There are still a few things to do. I'd say we need decide if we just >create a parity release (like sdk 4.8 release) or already add some of >the pull requests: > >https://issues.apache.org/jira/browse/FLEX-33488 > >Cyrill > >On Wed, Jul 31, 2013 at 1:18 PM, Erik de Bruin <e...@ixsoftware.nl> wrote: >> Great work Cyrill! >> >> Are you planning on doing a release or will that be some time in the >>future? >> >> EdB >> >> >> >> On Wed, Jul 31, 2013 at 2:55 AM, Cyrill Zadra <cyrill.za...@gmail.com> >>wrote: >>> Hi >>> >>> Finally FlexUnit jenkins job is up and running. >>> >>> Job details and results can be found here -> >>> https://builds.apache.org/job/flex-flexunit/ >>> >>> Cyrill >> >> >> >> -- >> Ix Multimedia Software >> >> Jan Luykenstraat 27 >> 3521 VB Utrecht >> >> T. 06-51952295 >> I. www.ixsoftware.nl
