+1 on the fix and reverting. Thank you Alex for figuring those out. I think we should actively prevent the 'New Project' issue from occurring. All we need to do is change the version number to something with only single digits. That really couldn't be simpler, could it? 5.0 has my vote.
This is not something people will be able to overlook. It is not an obscure RTE in a feature few use, will happen each time they create a new project. Doing nothing but adding a note in the docs will leave a bad impression and will taint this release and - more importantly - the still fragile image of the project. People, especially the press and bloggers, tend to look at the negatives, no matter how awesome the rest is. EdB On Mon, Jul 29, 2013 at 7:07 AM, Alex Harui <aha...@adobe.com> wrote: > > > On 7/28/13 9:44 PM, "Justin Mclean" <jus...@classsoftware.com> wrote: > >>Hi, >> >>> What day do you get in the airplane? >>Thursday your time. > OK, do we have consensus on taking both the resource module fix and > reverting Ilist? > If so, I will check them into the release4.10 branch sometime tomorrow > after Europe has had a chance to weigh in on this thread. > > Then we have to work out wording for whatever to say about the "New > Project" issue and put that in the release notes. I'm thinking we should > should put in something generic that points to our wiki for the "latest > news". That way if we get a patch from Adobe we can update just the wiki. > > Thoughts? > -Alex > -- Ix Multimedia Software Jan Luykenstraat 27 3521 VB Utrecht T. 06-51952295 I. www.ixsoftware.nl
