> On Jul 11, 2018, at 1:03 PM, Wm via gnucash-devel
> wrote:
>
> On 11/07/2018 03:49, John Ralls wrote:
>>> On Jul 10, 2018, at 6:45 PM, Wm wrote:
>
>>> Aside: is there a reason why version changes aren't on (or easily found
>>> from) the front page of gnucash.org? they used to be there.
>
On July 11, 2018, at 4:04 PM, Wm via gnucash-devel
wrote:
>On 11/07/2018 03:49, John Ralls wrote:
>>
>>
>>> On Jul 10, 2018, at 6:45 PM, Wm wrote:
>>> Aside: is there a reason why version changes aren't on (or easily found
>>> from) the front page of gnucash.org? they used to be there.
>>
On 11/07/2018 03:49, John Ralls wrote:
On Jul 10, 2018, at 6:45 PM, Wm wrote:
Aside: is there a reason why version changes aren't on (or easily found from)
the front page of gnucash.org? they used to be there.
David T. thought that it made the front page too busy and moved it to
https
> On Jul 10, 2018, at 6:45 PM, Wm wrote:
>
> On 29/06/2018 08:43, Geert Janssens wrote:
>> Op donderdag 28 juni 2018 22:11:49 CEST schreef Dennis West:
>>> I'm sure you like to get feedback from someone with absolutely no
>>> problems at all.
>>>
>>> I was using 2.6.21 on my primary computer a
On 29/06/2018 08:43, Geert Janssens wrote:
Op donderdag 28 juni 2018 22:11:49 CEST schreef Dennis West:
I'm sure you like to get feedback from someone with absolutely no
problems at all.
I was using 2.6.21 on my primary computer and testing 3.1/3.2 on my
standby testbed (both on Win 10.1803).
Op donderdag 28 juni 2018 22:11:49 CEST schreef Dennis West:
> I'm sure you like to get feedback from someone with absolutely no
> problems at all.
>
> I was using 2.6.21 on my primary computer and testing 3.1/3.2 on my
> standby testbed (both on Win 10.1803). I finally decided to take the
> plun
