[Ledger-smb-devel] Tentative Schedule for 1.4
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. 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. 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? Best Wishes, Chris Travers -- Virtualization Cloud Management Using Capacity Planning Cloud computing makes use of virtualization - but cloud computing also focuses on allowing computing to be delivered as a service. http://www.accelacomm.com/jaw/sfnl/114/51521223/___ Ledger-smb-devel mailing list Ledger-smb-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/ledger-smb-devel
Re: [Ledger-smb-devel] Tentative Schedule for 1.4
Chris, On 2012-02-23 19:00, 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. 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. 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 presume we could be testing from the beginning and if we are not using the newly worked on features or the ones waiting to be worked on, we should be good? - in terms of the data being maintained up to a proper release? My immediate demand is for just minimal, basic accounting . . a few large incomings and regular small outgoings, bank charges etc Thanks, Phil. -- Philip Rhoades GPO Box 3411 Sydney NSW 2001 Australia E-mail: p...@pricom.com.au -- Virtualization Cloud Management Using Capacity Planning Cloud computing makes use of virtualization - but cloud computing also focuses on allowing computing to be delivered as a service. http://www.accelacomm.com/jaw/sfnl/114/51521223/ ___ Ledger-smb-devel mailing list Ledger-smb-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/ledger-smb-devel
Re: [Ledger-smb-devel] Tentative Schedule for 1.4
Chris, On 2012-02-23 21:54, Chris Travers wrote: On Thu, Feb 23, 2012 at 2:12 AM, Philip Rhoades p...@pricom.com.au [1] wrote: I presume we could be testing from the beginning and if we are not using the newly worked on features or the ones waiting to be worked on, we should be good? - in terms of the data being maintained up to a proper release? My immediate demand is for just minimal, basic accounting . . a few large incomings and regular small outgoings, bank charges etc Thats correct. Once the business unit code is all in and breakage corrected, and the customer/vendor db redesign complete (nothing major here, just a few tweakstweaks!), then transactional testing can begin. I would note a couple things: Financial storage and financial information storage routines are not changing in 1.4. So bugs should be more on the this is broken and doesnt wtweakstweaksork line rather than the this is saving incorrect data. I dont anticipate very many of these actually. As we get into reporting though, you will want to be double checking the reports as you upgrade. Check the changelogs for details before you do and compare old/new reports, flagging differences. Also truly new features like transaction import of things like timecards and chart of accounts entries may have a greater likelihood of bugs/incorrect entry. Also I believe we will probably clear the Fixes.sql so it goes back no more than one beta, so if you are doing this youd need to stay up to date. Now worries - if I can get done what I need to and also help with testing, I'll be happy. I have a few years of back accounts to deal with (same organisation) but I will consult with you privately about the best approach etc. While this (non-profit) still does not have a high transaction rate - we hope it will in the future, so I would like to have a complete set of accounts by the time that starts happening. Thanks, Phil. -- Philip Rhoades GPO Box 3411 Sydney NSW 2001 Australia E-mail: p...@pricom.com.au -- Virtualization Cloud Management Using Capacity Planning Cloud computing makes use of virtualization - but cloud computing also focuses on allowing computing to be delivered as a service. http://www.accelacomm.com/jaw/sfnl/114/51521223/ ___ Ledger-smb-devel mailing list Ledger-smb-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/ledger-smb-devel
Re: [Ledger-smb-devel] Tentative Schedule for 1.4
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 -- Virtualization Cloud Management Using Capacity Planning Cloud computing makes use of virtualization - but cloud computing also focuses on allowing computing to be delivered as a service. http://www.accelacomm.com/jaw/sfnl/114/51521223/ ___ Ledger-smb-devel mailing list Ledger-smb-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/ledger-smb-devel
Re: [Ledger-smb-devel] Tentative Schedule for 1.4
Hi John; On Thu, Feb 23, 2012 at 10:41 AM, John Locke m...@freelock.com wrote: 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 am thinking about reviving Jason's work on the old code here. I don't know of anyone doing active work on the new code. 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. Not yet. My suggestion would be this: 1) Wait about another month for the customer/vendor stuff to get solidified. 2) Run in parallel for a month just to make sure that core things work for you Also a note on payroll. Payroll varies a tremendous amount from state to state and from country to country. What we will have will be a framework for building systems which provide payroll functionality. It isn't clear yet which locations will be supported. Because of the fact that rules tend to change frequently, I think this is likely to be a framework which allows local or regional businesses (working with me or on their own) to create payroll systems. 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. Web services are on the road map. I guess my main question to everyone on the list is what I can do to facilitate contributions in this area? Right now I am thinking of reviving Jason Rodrigues's work on this area.and setting it up so that we can get more involvement in actually hooking it into old or new code. Ideally web services, like reporting, would happen after the main transactional functionality is stable enough for early beta testing. 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. Thanks! Best Wishes, Chris Travers Cheers, John Locke http://www.freelock.com -- Virtualization Cloud Management Using Capacity Planning Cloud computing makes use of virtualization - but cloud computing also focuses on allowing computing to be delivered as a service. http://www.accelacomm.com/jaw/sfnl/114/51521223/ ___ Ledger-smb-devel mailing list Ledger-smb-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/ledger-smb-devel -- Virtualization Cloud Management Using Capacity Planning Cloud computing makes use of virtualization - but cloud computing also focuses on allowing computing to be delivered as a service. http://www.accelacomm.com/jaw/sfnl/114/51521223/___ Ledger-smb-devel mailing list Ledger-smb-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/ledger-smb-devel
