[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Tentative Schedule for 1.4
- Subject: Re: Tentative Schedule for 1.4
- From: John Locke <..hidden..>
- Date: Thu, 23 Feb 2012 10:41:23 -0800
Hi, Chris,
Sounds good! Notes/questions below...
On 02/23/2012 12:00 AM, Chris Travers wrote:
Hi all;
I am finishing up what is probably the last of the major
backwards-compatibility-breaking features for 1.4, which is the
rewrite of projects and departments. I expect to have trunk in a
usable (for testing) state within another week.
After that I expect to be working on payroll framework and refactoring
the contact management. I hope to have these fully working on 1.4 by
the end of March. After that point, all manual transaction-entry
parts of the web application should be ready for testing, and my work
will shift to reporting and CSV imports.
Really looking forward to the payroll framework, that's going to be a
huge win for us.
Is anybody working on the web services infrastructure we discussed a
while back? That's the other big thing we're interested in.
I think we can consider 1.4 to be in early beta, but not
feature-complete at the time these areas are complete. Reporting and
import logic can be worked on concurrent to testing of transaction entry.
Are you running any of your production customers on trunk/1.4? We're
definitely tracking the 1.3 branch still, but if the core financial
logic should stay sound, and there's work being done on web services and
payroll in 1.4, I'd be willing to switch us over when you hit that early
beta milestone and be an early tester again.
I would like to make some UI improvements using Dojo Toolkit, but this
will be so much easier to do when there's a web services back end.
I would like to hit feature freeze around the beginning of June, with
betas at that point being released every two weeks. I think that if
things go well, we can shoot for a general release in September.
What do people think?
I think it sounds great! Thanks for all your hard work on this.
Cheers,
John Locke
http://www.freelock.com