Hi all,
With my recent mails sent to this list about sorting out my thoughts, I'll
hereby send an overview of the current development status.
Summarizing, these were the topics under development:
* Account translations
* Account heading trees in the reports
* 1.5.0 release, meaning resolving bl
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
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
On Wed, 15 Jun 2011, David A. Bandel wrote:
> On Wed, Jun 15, 2011 at 20:04, Luke wrote:
>> Using the prepare script from revision 3248, I found some oddities.
>>
>> First, in the usage, the usage line implies that all options are optional
>> (scriptname [option1 .. optionN]).
>> However, the com
While installing 1.3, I'm getting:
ERROR: role "lsmb_testco__ar_voucher_all" does not exist
In relation to sql/modules/Roles.sql.
I don't know why, but these create role statements are commented out. I
have to imagine that there's a reason for this, but it is prompting an
error.
--CREATE RO
During the import of
/usr/share/postgresql/8.3/contrib/pg_trgm.sql
There is this:
NOTICE: type "gtrgm" is not yet defined
DETAIL: Creating a shell type definition.
CREATE FUNCTION
NOTICE: argument type gtrgm is only a shell
Is this something to be concerned about? I'm guessing not, as it's
On Wed, Jun 15, 2011 at 20:04, Luke wrote:
> Using the prepare script from revision 3248, I found some oddities.
>
> First, in the usage, the usage line implies that all options are optional
> (scriptname [option1 .. optionN]).
> However, the company option is required.
Hmm. I saw a * suggesting
Using the prepare script from revision 3248, I found some oddities.
First, in the usage, the usage line implies that all options are optional
(scriptname [option1 .. optionN]).
However, the company option is required.
In addition, the --pgsql-contrib option is supposed to be optional,
apparentl
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
