Re: [Ledger-smb-users] Development progress [2011-06-26]

2011-06-27 Thread Chris Travers
On Sun, Jun 26, 2011 at 2:37 PM, Erik Huelsmann wrote: > And with success: Even though new bugs were found and logged, we're > currently down to 0 (zero!) bugs registered in the bug-tracker (and > none located elsewhere). The pending patches queue contains only 2 > patches and all pending patches

[Ledger-smb-users] Development progress [2011-06-26]

2011-06-26 Thread Erik Huelsmann
Another (two?) week(s) have gone by and it's time for another progress report. We've been working hard to further drive LedgerSMB 1.3 (trunk) to stabilization. And with success: Even though new bugs were found and logged, we're currently down to 0 (zero!) bugs registered in the bug-tracker (and no

Re: [Ledger-smb-users] Development progress

2011-06-17 Thread Chris Travers
On Fri, Jun 17, 2011 at 12:43 PM, Erik Huelsmann wrote: > Hi all, > > On Thu, Jun 16, 2011 at 6:54 PM, Chris Travers > wrote: >> On Thu, Jun 16, 2011 at 8:13 AM, John Locke wrote: >>> Hi, all, >>> >>> It's really great to see rapid progress these days. Way to go! >>> >>> I had written up a bit

Re: [Ledger-smb-users] Development progress

2011-06-17 Thread Erik Huelsmann
Hi all, On Thu, Jun 16, 2011 at 6:54 PM, Chris Travers wrote: > On Thu, Jun 16, 2011 at 8:13 AM, John Locke wrote: >> Hi, all, >> >> It's really great to see rapid progress these days. Way to go! >> >> I had written up a bit of a response several weeks ago when Erik was >> getting involved, and

Re: [Ledger-smb-users] Development progress

2011-06-16 Thread Chris Travers
On Thu, Jun 16, 2011 at 8:13 AM, John Locke wrote: > Hi, all, > > It's really great to see rapid progress these days. Way to go! > > I had written up a bit of a response several weeks ago when Erik was > getting involved, and I guess I never sent it. The one bit that's still > relevant is a sugges

Re: [Ledger-smb-users] Development progress

2011-06-16 Thread John Locke
Hi, all, It's really great to see rapid progress these days. Way to go! I had written up a bit of a response several weeks ago when Erik was getting involved, and I guess I never sent it. The one bit that's still relevant is a suggestion for a CLI tool... In Drupal, there's a sub-project called

Re: [Ledger-smb-users] Development progress

2011-06-16 Thread Chris Travers
As further progress, we've closed out large numbers of 1.3 bugs and this is continuing. I expect to make a few changes to the db loading routines to make them easier to maintain. Commits are continuing apace. Perhaps another beta of 1.3 can be released soon. What I'dlike to accomplish for the n

Re: [Ledger-smb-users] Development progress

2011-06-14 Thread Chris Travers
On Tue, Jun 14, 2011 at 1:04 PM, Luke wrote: > On Tue, 14 Jun 2011, Chris Travers wrote: > >> Development snapshots are under Development Snapshots in the >> Sourceforge file system. >> >> Biweekly snapshots will be named [branch]-[mmdd] >> >> First snapshot is in place. > > Chris > > Personal

Re: [Ledger-smb-users] Development progress

2011-06-14 Thread Erik Huelsmann
Hi Luke, On Tue, Jun 14, 2011 at 10:04 PM, Luke wrote: > On Tue, 14 Jun 2011, Chris Travers wrote: > >> Development snapshots are under Development Snapshots in the >> Sourceforge file system. >> >> Biweekly snapshots will be named [branch]-[mmdd] >> >> First snapshot is in place. > > Chris >

Re: [Ledger-smb-users] Development progress

2011-06-14 Thread Luke
On Tue, 14 Jun 2011, Chris Travers wrote: > Development snapshots are under Development Snapshots in the > Sourceforge file system. > > Biweekly snapshots will be named [branch]-[mmdd] > > First snapshot is in place. Chris Personally, I'm fine with SVN, and stay away from SF sites as much as

Re: [Ledger-smb-users] Development progress

2011-06-14 Thread Erik Huelsmann
Hi Chris, On Tue, Jun 14, 2011 at 5:08 PM, Chris Travers wrote: > Development snapshots are under Development Snapshots in the > Sourceforge file system. > > Biweekly snapshots will be named [branch]-[mmdd] > > First snapshot is in place. My solution would be to completely automate the proce

Re: [Ledger-smb-users] Development progress

2011-06-14 Thread Chris Travers
Development snapshots are under Development Snapshots in the Sourceforge file system. Biweekly snapshots will be named [branch]-[mmdd] First snapshot is in place. Best Wishes, Chris Travers -- EditLive Enterprise is

Re: [Ledger-smb-users] Development progress

2011-06-14 Thread Chris Travers
On Tue, Jun 14, 2011 at 7:09 AM, ehu...@gmail.com wrote: > Hi Philip, > > Thanks for your positive response! It made me realize not everybody simply > checks out the sources from version control. > > Would it be alright if I created a tarball to be downloadable from a > non-official location (my

Re: [Ledger-smb-users] Development progress

2011-06-14 Thread ehu...@gmail.com
, if that helps people with their evaluations. Bye, Erik. Sent from my Nokia phone -Original Message- From: Philip Rhoades Sent: 14/06/2011, 13:33 To: ledger-smb-users@lists.sourceforge.net Subject: Re: [Ledger-smb-users] Development progress Erik, On Sat, 11 Jun 2011 19:26:49 +0200

Re: [Ledger-smb-users] Development progress

2011-06-14 Thread Philip Rhoades
Erik, On Sat, 11 Jun 2011 19:26:49 +0200, Erik Huelsmann wrote: > Since most of you probably don't follow the commits or development > list very closely, I thought I'd send an update to the users list > summarizing recent activity. > > Over the past 4 weeks there have been almost 100 commits to t

Re: [Ledger-smb-users] Development progress

2011-06-11 Thread Chris Travers
On Sat, Jun 11, 2011 at 10:26 AM, Erik Huelsmann wrote: > Since most of you probably don't follow the commits or development > list very closely, I thought I'd send an update to the users list > summarizing recent activity. > > Over the past 4 weeks there have been almost 100 commits to the > repo

[Ledger-smb-users] Development progress

2011-06-11 Thread Erik Huelsmann
Since most of you probably don't follow the commits or development list very closely, I thought I'd send an update to the users list summarizing recent activity. Over the past 4 weeks there have been almost 100 commits to the repository. As a result, many of the patches pending in SourceForge's pa