--On December 9, 2010 10:24:51 AM -0800 John Ralls
wrote:
Anyway, if we're going to introduce the gnucash-version row, we
should do it now, before 2.4 is released.
It seems like this is a good idea, even if it is never used for
automatic upgrades or fixups. At the very least it would help
experimenting with new features or new storage
modes, that they may have to go back to a stable-version-generated database and
start over.
I guess it's OK for an older version to load a newer-versioned database if it's
read-only, though it might misinterpret the stored data and do somethi
On Thu, December 9, 2010 12:01 pm, John Ralls wrote:
>
> On Dec 9, 2010, at 7:05 AM, Derek Atkins wrote:
>
>> John Ralls writes:
>>
>>
>>> Oh, and there isn't enough sql yet to have "bugs in the sql".
>>
>> The fact that we're having this discussion would prove this incorrect.
>> There already has
On Dec 9, 2010, at 7:05 AM, Derek Atkins wrote:
>
> Let's get 2.4 out the door first, and then we can talk about how we can
> fix this in a piecemeal fashion. It would be nice if we could get
> releases out approximately yearly. Can we come up with a
> feature-set/timeline that would allow for
On Dec 9, 2010, at 7:05 AM, Derek Atkins wrote:
> John Ralls writes:
>
>
>> Oh, and there isn't enough sql yet to have "bugs in the sql".
>
> The fact that we're having this discussion would prove this incorrect.
> There already has been a bug in the SQL causing the slots to not get
> delete
John Ralls writes:
>> Maybe this is a silly question, but why couldn't we use the versions
>> table to notice this, too? It's still a bug in the SQL, and we should
>> get used to fixing SQL bugs internally.
>>
>> I understand it might take a few tries to get right, but that's what
>> "mysqldump
On Dec 8, 2010, at 12:42 PM, Derek Atkins wrote:
> John Ralls writes:
>
>> On Dec 8, 2010, at 6:36 AM, Phil Longstaff wrote:
>>
>>> Support for this already exists. There's a "versions" table which has
>>> table-name/table-version pairs. This is loaded automatically when the file
>>> is
>
John Ralls writes:
> On Dec 8, 2010, at 6:36 AM, Phil Longstaff wrote:
>
>> Support for this already exists. There's a "versions" table which has
>> table-name/table-version pairs. This is loaded automatically when the file
>> is
>> opened. The backend code for each object type contains a "
On Dec 8, 2010, at 6:36 AM, Phil Longstaff wrote:
> Support for this already exists. There's a "versions" table which has
> table-name/table-version pairs. This is loaded automatically when the file
> is
> opened. The backend code for each object type contains a "create tables"
> routine w
On Dec 8, 2010, at 5:23 AM, Derek Atkins wrote:
> John,
>
> John Ralls writes:
>
>> Everyone using a SQL backend who started with data saved from XML with a
>> Gnucash version before 2.3.16 should re-save from XML with 2.3.17 and
>> re-enter any intervening tra
o I took something for it.
From: Derek Atkins
To: John Ralls
Cc: devel gnucash
Sent: Wed, December 8, 2010 8:23:46 AM
Subject: Re: SQL Databases from before 2.3.16
John,
John Ralls writes:
> Everyone using a SQL backend who started with data saved from XML with a
&g
John,
John Ralls writes:
> Everyone using a SQL backend who started with data saved from XML with a
> Gnucash version before 2.3.16 should re-save from XML with 2.3.17 and
> re-enter any intervening transactions.
>
> I just fixed 635967 [1], which complained that scheduled tran
Everyone using a SQL backend who started with data saved from XML with a
Gnucash version before 2.3.16 should re-save from XML with 2.3.17 and re-enter
any intervening transactions.
I just fixed 635967 [1], which complained that scheduled transactions didn't
work in 2.3.17 from a dat
On Dec 1, 2010, at 5:09 PM, David T. wrote:
> I am again hankering for some of the features in the development version of
> Gnucash (currently at 2.3.17), and wanted to ask a few Mac-specific
> questions...
>
> 1) The disk image includes a couple of introductory apps to help the
> transition
I am again hankering for some of the features in the development version of
Gnucash (currently at 2.3.17), and wanted to ask a few Mac-specific questions...
1) The disk image includes a couple of introductory apps to help the transition
(UpdateDirs.app and FinanceQuote Update.app). I read the re
Am Freitag, 12. November 2010 schrieb David Reiser:
> src/doc/design/gnucash-design.info has been included in the tarballs
> through 2.3.15, but is not present in 2.3.16. The whole 'design' folder is
> gone. Was that intentional? There are some messages during install that
&g
src/doc/design/gnucash-design.info has been included in the tarballs through
2.3.15, but is not present in 2.3.16. The whole 'design' folder is gone. Was
that intentional? There are some messages during install that suggest the file
is still expected to be present.
Dave
--
David Re
On Saturday 6 November 2010, Yawar Amin wrote:
> Hi Geert,
>
> On 2010-11-06, at 05:47, Geert Janssens wrote:
> >> […]
> >
> > The other part the is not documented at all is the business functionality
> > in GnuCash. But this has never been documented before, so there is no
> > loss compared with
g freeze for a while, but there have been
several small string changes. When can we expect to see 2.3.16 at the
Translation Project to dot the remaining i's and cross the final t's?
--
Mark Haanen
___
gnucash-devel mailing list
gnucash
Hi Geert,
On 2010-11-06, at 05:47, Geert Janssens wrote:
>> […]
> The other part the is not documented at all is the business functionality in
> GnuCash. But this has never been documented before, so there is no loss
> compared with the previous versions if it remains undocumented. Personally,
On Saturday November 6 2010 09:47:59 Geert Janssens wrote:
> On Saturday 6 November 2010, Yawar Amin wrote:
> > Hi John & List,
> >
> > On 2010-11-05, at 14:33, John Ralls wrote:
> > > […]
> > > I think it should be a release candidate for 2.4, with a code freeze
> > > for anything but critical bu
On Saturday 6 November 2010, Yawar Amin wrote:
> Hi John & List,
>
> On 2010-11-05, at 14:33, John Ralls wrote:
> > […]
> > I think it should be a release candidate for 2.4, with a code freeze for
> > anything but critical bugs. If it works as well as I think it will, then
> > we can release 2.4 a
Commited to rev. 19759
Thanks!
Cristian
Il 05/11/2010 22:28, Valdis Vītoliņš ha scritto:
Hello!
Please commit updated lv.po file before build.
Thanks!
Valdis
Am Freitag, 5. November 2010 schrieb Phil Longstaff:
I think I can do 2.3.16 this weekend.
That sounds very good
--On November 6, 2010 12:25:12 AM -0400 Yawar Amin
wrote:
Hi John & List,
On 2010-11-05, at 14:33, John Ralls wrote:
[…]
I think it should be a release candidate for 2.4, with a code freeze
for anything but critical bugs. If it works as well as I think it
will, then we can release 2.4 as so
Hi John & List,
On 2010-11-05, at 14:33, John Ralls wrote:
> […]
> I think it should be a release candidate for 2.4, with a code freeze for
> anything but critical bugs. If it works as well as I think it will, then we
> can release 2.4 as soon as the documentation is ready.
Are there any user-
Am Freitag, 5. November 2010 schrieb Phil Longstaff:
> I think I can do 2.3.16 this weekend.
That sounds very good. Indeed a 2.3.16 is necessary. Thanks a lot!
Christian
___
gnucash-devel mailing list
gnucash-devel@gnucash.org
https://lists.gnucash.
I think I can do 2.3.16 this weekend.
Phil
-
I used to be a hypochondriac AND a kleptomaniac. So I took something for it.
From: John Ralls
To: Gnucash Devel
Sent: Fri, November 5, 2010 2:33:28 PM
Subject: 2.3.16
It's been 2 months since 2.3.1
It's been 2 months since 2.3.15 and we've made some pretty major improvements.
I think it's time to do a release.
I think it should be a release candidate for 2.4, with a code freeze for
anything but critical bugs. If it works as well as I think it will, then we can
release 2.4 as soon as the d
28 matches
Mail list logo