Does there exist a functional definition for recurring transactions? For example, being in the habit of pre-filling Gnucash with the whole month's recurring transactions on pay-day up to the next pay-day (15th in my case), in order to project budgets/disposable income, it would be nice to know that I will be able to do this automatically.
Thanks, /Dave. > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] > Sent: 25 September 2002 09:57 > To: [EMAIL PROTECTED] > Subject: Re: Gnucash 1.8 proposed schedule (and HBCI status) > > > > I know that this has been asked for before, but does anyone > know when recurring transactions will be ready? I believe > that someone is already working on that feature? > > thanks, > andy. > > > > > > Christian Stimming > > <[EMAIL PROTECTED]> To: > [EMAIL PROTECTED] > Sent by: cc: > > [EMAIL PROTECTED] > Subject: Gnucash 1.8 proposed schedule (and HBCI status) > nucash.org > > > > > > 25/09/02 10:01 > > > > > > > > > Here's an updated HBCI planned-feature list, since I managed > to get quite some stuff working. Note that I still can't > recommend the HBCI subsystem for widespread testing, since it > is quite likely to contains heaps of bugs, and it also > requires frequent updates of your openhbci installation. > Interested users should still wait until the official > announcement of the feature freeze. > > - finish Setup druid (2h) > - finish Balance retrieval with account reconcile (2h) > - finish transaction invocation at bank (2h) > - add hbci job queueing, so that several transactions can be > sent in one connection (8h) > - add transaction retrieval, and sync that with generic > transaction import > (12h) > > Given my current spare time, I think I'll finish these > features until Oct 6. What do other people think about their > planned features and how long it will take to complete them? > Of course we could always come up with more features :-) , > but for a new stable release we need to decide what goes in > now and what goes in later. > > How about the following schedule for a stable release *now*: > > Oct 13 Feature freeze, release 1.7.1-alpha > > Oct 27 Total feature freeze, initial string freeze + initial > translation work, release 1.7.2-alpha > > Nov 10 Deep freeze = only bugfixes, String freeze, call for > translations, release 1.7.3-beta > > Nov 24 still Deep+string freeze, only reviewed bugfixes, > release 1.7.4-beta > > Dec 8 Release 1.8.0, or if needed another 1.7.5 release and > 1.8.0 on Dec 22 > > Of course the alpha/beta release numbering scheme is up for > discussion, as is the whole schedule. What do people think? > > Christian > ______________________________________________ > > > -- > "NOTICE: The information contained in this electronic mail > transmission is intended by Convergys Corporation for the use > of the named individual or entity to which it is directed and > may contain information that is privileged or otherwise > confidential. If you have received this electronic mail > transmission in error, please delete it from your system > without copying or forwarding it, and notify the sender of > the error by reply email or by telephone (collect), so that > the sender's address records can be corrected." > > _______________________________________________ > gnucash-devel mailing list > [EMAIL PROTECTED] > http://www.gnucash.org/cgi-> bin/mailman/listinfo/gnucash-devel > ------------------------------------------------------------- --- Visit our Internet site at http://www.reuters.com Any views expressed in this message are those of the individual sender, except where the sender specifically states them to be the views of Reuters Ltd. _______________________________________________ gnucash-devel mailing list [EMAIL PROTECTED] http://www.gnucash.org/cgi-bin/mailman/listinfo/gnucash-devel
