Quoting Chris Shoemaker <[EMAIL PROTECTED]>:
On Fri, Oct 07, 2005 at 10:36:59AM -0400, David Hampton wrote:
On Sat, 2005-10-01 at 16:59 -0400, Chris Shoemaker wrote:
> Nevertheless, I've been sitting on a stable, complete implementation
> of budgeting since the spring, (I actually use it for my own
> budgeting.) along with lots of other general improvements to
> e.g. tracing, testing, debugging, etc. As soon as G2 is released and
> a "dev" branch opens I was planning on pushing for inclusion(^).
> ...
>
> (^) I know there's an incomplete budget in G2, I was expecting it to
> be removed for G2.
If what's in the tree is broken and needs to be pulled, and you're
sitting on a "stable complete implementation", then IMHO we clearly
should commit your code.
Even though budgeting wasn't a 1.8 feature?
OFX Direct Connect wasn't a 1.8 feature, either. ;)
If what you have is complete and working, solves both your needs and
those of Darrin, and doesn't replicate existing APIs, then I think it's
reasonable to put into G2 now. E.g., if you haven't combined FreqSpec and
Recurrence into a single API then no, it's not ready to be committed.
OTOH, I wouldn't mind comitting the code and then just leaving the
menu item off if we decide to release G2 without it. But, it would be
nice to get some more people using it, even if just in alpha.
If it's working, why hide the feature?
-chris
-derek
--
Derek Atkins, SB '93 MIT EE, SM '95 MIT Media Laboratory
Member, MIT Student Information Processing Board (SIPB)
URL: http://web.mit.edu/warlord/ PP-ASEL-IA N1NWH
[EMAIL PROTECTED] PGP key available
_______________________________________________
gnucash-devel mailing list
[email protected]
https://lists.gnucash.org/mailman/listinfo/gnucash-devel
