[GNC-dev] Advice on what to look at next
ripngo at gmail.com
Wed Mar 25 00:30:11 EDT 2020
I have a possibly silly question. If the migration to 4.0 is somewhat
near, what point is there in cleaning up the code in 3.x or removing
hacks etc or even adding new features?
Am I missing something?
On 3/23/20 5:55 PM, Chris Graves wrote:
> For all you devs, it’s understood(or it should be) that what you do for this project is a labor of love. Take your time, relax and just enjoy the fixes/enhancements that you bring to this project. Who cares if a deadline needs to slip, just have fun!!!
> Thank you devs!!!
>> On Mar 23, 2020, at 5:22 PM, John Ralls <jralls at ceridwen.us> wrote:
>> It's up in the air. The major sticking point is that I'm working on a major rewrite of the options system from an ugly mixture of C and Scheme to C++. I'd hoped to have it far enough along by now to start test releases, but it's not. The back end is mostly done and I'm 3/4 through with the GUI. After that is making sure that the Scheme API is compatible. (It's the c++options branch in my GitHub repo if you want to have a look. I haven't committed the GUI stuff yet, it doesn't build.) We'll have to discuss whether to proceed to user testing without it or slip the 4.0 release when Geert gets back from travel.
>> John Ralls
>>> On Mar 23, 2020, at 2:17 PM, Jean Laroche <ripngo at gmail.com> wrote:
>>> How far along are you on 4.0? Is the planned 28 June 2020 release reasonable?
>>> On 3/23/20 2:12 PM, Christopher Lam wrote:
>>>> For a /very/ high level overview, see the design goals at https://wiki.gnucash.org/wiki/Release_Schedule
>>>> Or, write tests and refactor the existing hacks.
>>>> Or, feel free to squash bugs at leisure!
>>>> On Mon, 23 Mar 2020 at 17:16, jeanl <ripngo at gmail.com <mailto:ripngo at gmail.com>> wrote:
>>>> Can you point me to something you think needs to be looked at sooner
>>>> than later in the gnucash code? I find that bugzilla does not give a
>>>> image of bug priority, but I'm sure you guys have a good idea of
>>>> what needs
>>>> to be fixed next. I wouldn't mind helping with that.
>>>> Sent from:
>>>> gnucash-devel mailing list
>>>> gnucash-devel at gnucash.org <mailto:gnucash-devel at gnucash.org>
>>> gnucash-devel mailing list
>>> gnucash-devel at gnucash.org
>> gnucash-devel mailing list
>> gnucash-devel at gnucash.org
More information about the gnucash-devel