Changing our release strategy?

[Christofer Dutz <ch...@c-ware.de>]

Hi,


As I have seen more and more dependencies between the different parts of the Flex ecosystem, I just added a diagram to our Wiki <https://cwiki.apache.org/confluence/display/FLEX/Subproject+Dependencies> https://cwiki.apache.org/confluence/display/FLEX/Subproject+Dependencies

I added the parts that I'm currently working on, so feel free to add your stuff :-)


I think we should start a release strategy in which we start releasing the parts that are blocking other parts first instead of releasing what's easy first and eventually having to push another release in when detecting problems with other parts up the stream.


What I will personally put more effort in, is finally releasing the Mavenizer. After that's done I could release Flexmojos 7.1 ... in my opinion BlazeDS should already be in a releasable state. If you don't let yourself be distracted by the completely out of date legacy Ant wrapper ... the Maven part with it's test suite runs fine (The failing tests, fail because on Apaches Jenkins there seem to be restrictions in spawning secondary VMs that open ports but I'll have another look at that). Releasing BlazeDS would eliminate one more Adobe dependency from the Installer that is causing some trouble currently.


In Squiggly I noticed some modules


Chris

AW: Changing our release strategy?

[Christofer Dutz <ch...@c-ware.de>]

Hi Justin,

forget my last sentence ;-) I noticed one project using some flex maven plugin I had never heard of before and thought it was Squiggly but as I couldn't find the module I wanted to post, I sort of forgot to delete that partial sentence.

Well then: Please help with the legal issues required to release BlazeDS :-)
I would even recommend to clean up the project and throw out the old stuff surrounding the "modules" directory, which seems to be the only part that's needed. I would like to tag BlazeDS and then move everything in the modules directory to become the new project root. This would eliminate the entire confusion.

Chris

________________________________________
Von: Justin Mclean <ju...@classsoftware.com>
Gesendet: Freitag, 5. September 2014 14:25
An: dev@flex.apache.org
Betreff: Re: Changing our release strategy?

Hi,

> What I will personally put more effort in, is finally releasing the Mavenizer. After that's done I could release Flexmojos 7.1 ... in my opinion BlazeDS should already be in a releasable state.
Legally releasable may be the issue here, as I said quite a few times happy to help out get this released.

>  Releasing BlazeDS would eliminate one more Adobe dependency from the Installer that is causing some trouble currently.
Yep all for that.

> In Squiggly I noticed some modules
There's no modules and basically zero required external dependancies  (other than the Flex SDK), so not sure what you mean there.

Thanks,
Justin

Re: Changing our release strategy?

[Justin Mclean <ju...@classsoftware.com>]

Hi,

> What I will personally put more effort in, is finally releasing the Mavenizer. After that's done I could release Flexmojos 7.1 ... in my opinion BlazeDS should already be in a releasable state.
Legally releasable may be the issue here, as I said quite a few times happy to help out get this released.

>  Releasing BlazeDS would eliminate one more Adobe dependency from the Installer that is causing some trouble currently.
Yep all for that.

> In Squiggly I noticed some modules
There's no modules and basically zero required external dependancies  (other than the Flex SDK), so not sure what you mean there.

Thanks,
Justin