That's also my opinion. If we KNOW that the next delivery will be 4.11.1, why name it 4.12, and rename it 4.12 just before the delivery ?
Now, if a release will not necessary have an update (as was the case e.g. for 4.10), then the above does not stand. Maurice -----Message d'origine----- De : Tianzhen Lin [mailto:[email protected]] Envoyé : vendredi 8 novembre 2013 15:16 À : [email protected] Objet : Re: SDK 4.11 service pack ? I wonder if we may have any target release cycles, for example 2 months between the release of 4.x and 4.x+1. If so, any fixes designed to release between release cycles could use the 4.x.y theme. For that matter, without knowing all the efforts going on, I tend to have an impression that the service pack may be better called as 4.11.1, and containing only well known errors reported since 4.11 My two cents. Tangent On Nov 7, 2013, at 8:44 PM, Maurice Amsellem wrote: > From the ones I have worked on : > > - FLEX-33813 Flex Incorrectly Scaling Down Application on iPad > > is the only one that has no workaround, and is a regression. > > My question was also on the JIRA process: is it the way it should work to > mark issues as fixed for the next major version ? > How was it managed eg. for 4.9.1 ? > > Thanks, > > Maurice > > -----Message d'origine----- > De : Alex Harui [mailto:[email protected]] Envoyé : vendredi 8 novembre > 2013 02:32 À : [email protected] Objet : Re: SDK 4.11 service pack ? > > What is in the fixed list that we need to get out so quickly (because there > is no workaround or is a serious regression)? > > On 11/7/13 5:11 PM, "Maurice Amsellem" <[email protected]> wrote: > >> Hi Team, >> >> There have been many issues fixed for 4.12. >> >> Is it intended to deliver a 4.11.1 soon ? >> >> In which case, maybe we should create 4.11.1 version in JIRA, and use >> it in the FixVersion, instead of 4.12? >> >> WDYT ? >> >> Maurice >> >
