Any objection to declaring a 1.3 partial feature freeze?

[Chris Travers <..hidden..>]

Hi all;

Since 1.2 was released we have overhauled much more of the software than we expected to do for 1.3.  1.3  to date has new logic for check payment and printing, cash reconciliation, drafts and vouchers, user management and security, and database setup in addition to the areas we expected to get into.  If we don't stop shortly, there won't be a 1.3, and we will go eventually to 2.0.  Such an approach wouldn't be good for the project as it would greatly complicate our testing and QA requirements.

At this point, I am going to suggest that all non-essential (for 1.3) development stop and we start rolling towards a public beta perhaps as early as the end of the month.  The following areas would be exempt from the feature freeze:
1)  CSS tweaks and stylesheets
2)  Installation and setup
3)  Year-end procedures (hopefully to be committed tonight)
4)  Overpayment functionality (last feature should be in place tomorrow)
5)  1099 reports.
6)  Functionality present in 1.2 but missing in 1.3

I will also be breaking off the fixed asset handling into an add-on module.  MRP functions under development will also broken off.

What do people think?

Best Wishes,
Chris Travers