So we don't fix bugs just because it's old code, this is pretty nonsense to me. How can the project expect to get people committing fixes if they get turned down because it fixes "legacy" components? It's already hard to get people involved and this clearly doesn't make it easier, just my 2 cents.
BTW, some issues solved in "legacy" code https://issues.apache.org/jira/browse/FLEX-33814 https://issues.apache.org/jira/browse/FLEX-34016 On 7 January 2014 16:04, Tom Chiverton <t...@extravision.com> wrote: > On 07/01/2014 15:49, João Fernandes wrote: > >> 2) switching from halo to spark forms is not a simple task of find & >> replace. >> > I understand that, but it seems to me it's a known, almost expected, bug > in a set of components we don't recommend people use. > > As you say, no new projects will hit the bug, and any old projects will > already have workarounds in place for it. > > Tom > -- João Fernandes
