Chris,
On 2011-05-18 06:53, Chris Travers wrote:
> Hi all;
>
> Many of you may be frustrated at the pace of development of LedgerSMB
> and the fact that 1.3 has not yet been released. Development may
> appear to have slowed. Public discussions become less frequent...
>
> For the last few years,
Has LedgerSMB a way to deal with the good ole COGS error with reversing
sales invoice? I imagine this fundamental error is something important to
users who offer tangible goods. One suggestion in the past was to restock
items under AP, but that's not as easy as it seems. For a small business
doing
On Thu, 19 May 2011, Chris Travers wrote:
> For the others, what is needed is to go through the manual and review
> everything, adding new sections where appropriate and editing old
> ones. In general, most of the manual applies consistently between 1.2
> and 1.3, so this is less of a huge job th
On Thu, May 19, 2011 at 11:49 AM, Luke wrote:
> I don't know if it would. I haven't seen it in action, so don't know what
> its capabilities are, nor how far it goes to replacing what's running.
>
> It doesn't sound like it would be able to make database changes any more
> likely, and I think at
On Thu, 19 May 2011, Chris Travers wrote:
> On Thu, May 19, 2011 at 11:06 AM, Luke wrote:
>> On Thu, 19 May 2011, Chris Travers wrote:
>>
>>> So let me suggest a priority list at present:
>>
>> Where does a snapshot or beta release fit into that priority list?
>
> I would like to start regular sn
On Thu, 19 May 2011, Chris Travers wrote:
> Ok, so how about a different approach:
>
> 1) Stable branches of addons and main programs are bug-fix only.
> 2) Addons (official patches, additional modules, etc) have their own
> sub-repositories, and can have multiple stable releases against a
> sta
On Thu, May 19, 2011 at 11:06 AM, Luke wrote:
> On Thu, 19 May 2011, Chris Travers wrote:
>
>> So let me suggest a priority list at present:
>
> Where does a snapshot or beta release fit into that priority list?
I would like to start regular snapshots, every two weeks (or other
schedule if others
Hi Luke;
First, thanks for your thoughts here. They are valued.
>
> 3 and 4 should probably be flipped in priority.
First, documentation is a fairly wide field. I think we can break it
down into three areas:
1) User documentation
2) Technical documentation
3) Code documentation
Code docume
On Thu, 19 May 2011, Chris Travers wrote:
> So let me suggest a priority list at present:
Where does a snapshot or beta release fit into that priority list?
--
What Every C/C++ and Fortran developer Should Know!
Read thi
On Thu, 19 May 2011, Erik Huelsmann wrote:
I think the major priorities at this point need to be:
1) Getting 1.3 out the door.
To me, this means being able to develop using the customers model,
differentiating between companies and people. To John Locke this seems
to mean the a stable Reconci
On Thu, May 19, 2011 at 10:03 AM, Luke wrote:
> On Thu, 19 May 2011, Chris Bennett wrote:
>
>> Installation is too difficult
>> Since 1.3 is really just a development phase, I think this issue can be
>> put at a lower priority
>> than documentation, but not too low.
>
> I think I disagree with tha
On Thu, 19 May 2011, Chris Bennett wrote:
> Installation is too difficult
> Since 1.3 is really just a development phase, I think this issue can be
> put at a lower priority
> than documentation, but not too low.
I think I disagree with that, at least somewhat, from two prospectives:
First, whi
Hi Chris,
Thanks for stepping up!
> >From reading this thread, and not having looked at 1.3, it seems that some
> >very particular issues
> are desperately needing to be fixed. These issues seem to be fairly unrelated
> as far as what skills
> are needed.
>
> Documentation - both for usage, ins
I was lightly involved a good while back, but I had to basically close down my
business for a while
to care for my handicapped mother.
>From reading this thread, and not having looked at 1.3, it seems that some
>very particular issues
are desperately needing to be fixed. These issues seem to be
Hi All,
I think the major priorities at this point need to be:
1) Getting 1.3 out the door.
>>>
>>> To me, this means being able to develop using the customers model,
>>> differentiating between companies and people. To John Locke this seems
>>> to mean the a stable Reconciliation inter
On Wed, 18 May 2011, Chris Travers wrote:
On Wed, May 18, 2011 at 10:19 PM, Luke wrote:
On Wed, 18 May 2011, Chris Travers wrote:
probably a good idea to find a mode where releases get only big enough
to address a small number of specific issues (and the regular bug
fixes) on the point relea
16 matches
Mail list logo
