Apache Flex is about to become the main distributor for the open source
project Flex. It was before at Adobe.
As long as the current version contains only bugfixes, I'd say: 4.6.x -
As soon as there are new features 4.7
and as soon as there are major new concepts 5.x.
But that being said: I think more important would be what is included in
the flex release: The current flex release
contains a lot, compiler, tons of libraries, just ... a lot.
Might it be a good idea to split the versioning? According to the maven
projects?
Then it would mean: Flex Charting Components 5.0 is when there are new
concepts in the charting system.
That way progress could be published in faster intervals (and (unit)
testing might be easier).
yours
Martin.
On 19/01/2012 01:49, Omar Gonzalez wrote:
Perhaps we should try to have some sort of agreement with the Adobe folks
that would result in reserving the 4.6.x version numbers for any possible
updates they may need to do to that branch.
Updates and changes done by Apache that are still based on the 4.x
architecture should probably fall under 4.7.x, which would retain also the
original "spark.components..." namespace.
Then if/when we make major feature additions or architectural changes we
can move to Flex 5.x, at which point we can revisit the possibility of
moving the namespace over to "org.apache.flex...".
Just my initial thoughts.
-omar
