Yeah I would go for a 4.7 initial apache flex release too. Especially because i sense the general intension here is to release a few compatible versions first. It's just less confusing IMHO.
Arnoud On 18-01-2012, at 18:05, Peter Elst wrote: >> I had the same initial reaction... but we also have to remember that 4.6 >> is still Adobe Flex 4.6, and if this branch has security holes Adobe is >> going to want to close those. The only safe way of doing that is to patch >> 4.6.0 or 4.6.1, cause if Apache is at 4.7 and we've changed things they're >> trying to fix in 4.6 then we will have conflicts. >> > > > I would have preferred to see Adobe do those bug fixes in the Apache > project - can't see how it would legally work with the Flex trademark, nor > should I really worry about it probably ;) > > In that case I would vote for going with an Apache Flex 4.7 initial > release, and if possible wait for Adobe to confirm its finished its work on > Flex 4.6 so there's no Apache Flex 4.7 followed by a Adobe Flex 4.6.2. > > Would Adobe be open to sharing what they are fixing so work isn't > duplicated within Apache? > > - Peter Met vriendelijke groet, Arnoud Bos Artim interactive T +31 6 246 40 216 E arn...@artim-interactive.nl
