Our current Modules are all in sdk 3.3 So far all is good. We hope that if we decide to introduce modules later down the track the were solely built using sdk 4+ that this would not be painful.
We hope that we will not have to use the 4+ sdk to compile our 3.3 modules against in this scenario? Have I been to vague? even if this is not the issue you were directly referring to? Thanks, Bjorn --- In flexcoders@yahoogroups.com, Matt Chotin <mcho...@...> wrote: > > I wouldn't say there's an exact methodology. We have some elements of agile > (like iterations, unit tests, ability to respond to feedback and adjust), but > as a platform we also need to make sure we have specifications, assigned > Quality Engineers, schedules, etc. So if you're looking for "we use scrum" > you won't get that, it's a combination of practices necessary for a team that > works with a large number of stakeholders. > > Matt > > > On 5/6/09 12:10 PM, "Vivian Richard" <kanps...@...> wrote: > > > > > > > Matt just a question regarding your software development process- > what exact methodology do you guys(you flex team) follow to develop > the Flex platform? > > On Wed, May 6, 2009 at 1:23 PM, Matt Chotin <mcho...@... > <mailto:mchotin%40adobe.com> > wrote: > > > > > > Are you building apps in a modular fashion where those modules need to > > support different Flex versions? Do you have nightmares where Alex is > > explaining SecurityDomains and ApplicationDomains and > > SWFLoader.loadForCompatibility? > > > > Please let me know (email me at mcho...@... <mailto:mchotin%40adobe.com> ), > > we're trying to evaluate > > some pain points and whether I need to bribe the Player team to solve them > > ASAP or if it can wait a release. > > > > Matt > > > > >
