Re: Are we ready for the 2.0.0 release in mid-May?

2006-05-02 Thread Josh Sled
On Tue, 2006-05-02 at 00:36 -0400, Derek Atkins wrote: Quoting Chris Shoemaker [EMAIL PROTECTED]: I'm still waiting for the merge of FreqSpec and Recurrence... You promised that you'd merge them into a single API. I'm still waiting. This isn't a 2.0 blocker. In fact, we probably don't want

Re: Are we ready for the 2.0.0 release in mid-May?

2006-05-01 Thread Derek Atkins
Mike Alexander [EMAIL PROTECTED] writes: --On April 30, 2006 10:48:09 AM -0400 Derek Atkins [EMAIL PROTECTED] wrote: Does the existing Lot Editor not work? Do you mean the one you get to from Actions-Lot Viewer? Or is there another one I haven't found? That one doesn't seem to provide

Re: Re: Are we ready for the 2.0.0 release in mid-May?

2006-05-01 Thread Beth Leonard
On Sun, Apr 30, 2006 at 11:06:21AM -0400, Josh Sled wrote: Should we do a seperate RC in about a week (May 7th)? Should we bother with RCs at all? All that really matters is that we stop making commits at some point ... when should that point be? I'd say 5/7 ... Wed 5/10 at the latest. As

Re: Are we ready for the 2.0.0 release in mid-May?

2006-05-01 Thread Mike Alexander
--On May 1, 2006 11:24:43 AM -0400 Derek Atkins [EMAIL PROTECTED] wrote: Do you mean the one you get to from Actions-Lot Viewer? Or is there another one I haven't found? That one doesn't seem to provide a way to change the assignment of splits to lots. You can see what splits are in a

Re: Are we ready for the 2.0.0 release in mid-May?

2006-05-01 Thread Chris Shoemaker
On Fri, Apr 28, 2006 at 11:16:39AM +0200, Christian Stimming wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Dear developers, I'd like to have a short discussion about the planned 2.0.0 release date, and which prerequisites have to be fulfilled so that we can actually make that

Re: Are we ready for the 2.0.0 release in mid-May?

2006-05-01 Thread Derek Atkins
Quoting Chris Shoemaker [EMAIL PROTECTED]: Regarding budgets, I think they're working well enough to leave enabled. I don't know of any budget misbehavior. Since budgets are new, there's not much user-expectation to live up to so I don't think we have to worry about impressions. Right now,

Re: Are we ready for the 2.0.0 release in mid-May?

2006-04-30 Thread Mike Alexander
--On April 30, 2006 12:11:27 AM -0400 David Hampton [EMAIL PROTECTED] wrote: I've applied this patch too. I don't think anyone else is working on this code, so I'm willing to take whatever changes you have. Thanks, this looks fine. I'm not sure how soon I'll get back to working on this.

Re: Are we ready for the 2.0.0 release in mid-May?

2006-04-30 Thread Derek Atkins
Quoting Mike Alexander [EMAIL PROTECTED]: --On April 30, 2006 12:11:27 AM -0400 David Hampton [EMAIL PROTECTED] wrote: I've applied this patch too. I don't think anyone else is working on this code, so I'm willing to take whatever changes you have. Thanks, this looks fine. I'm not sure

Re: Are we ready for the 2.0.0 release in mid-May?

2006-04-30 Thread Josh Sled
On Fri, 2006-04-28 at 11:16 +0200, Christian Stimming wrote: only one blocker. I'd like to ask everyone to go through the other (critical, major, normal) bugs and look for ones that *must* be resolved before 2.0.0. Then mark those as a blocker -- if others think those are not a blocker for

Re: Are we ready for the 2.0.0 release in mid-May?

2006-04-30 Thread David Hampton
On Sun, 2006-04-30 at 03:36 -0400, Mike Alexander wrote: Another thing that I've thought of doing is to change the stock split druid to distribute the new shares over all open lots in proportion to the size of each lot. This is the main thing that isn't handled properly automatically

Re: Are we ready for the 2.0.0 release in mid-May?

2006-04-30 Thread David Hampton
On Sun, 2006-04-30 at 17:47 -0400, Mike Alexander wrote: In this sort of situation you would likely have separate GnuCash accounts for the two portfolios. Both the stock split druid and the lots manager are specific to a particular GnuCash account I totally misread your previous message.

Re: Are we ready for the 2.0.0 release in mid-May?

2006-04-29 Thread Mike Alexander
--On April 28, 2006 5:12:18 PM -0400 David Hampton [EMAIL PROTECTED] wrote: What about lots? I've been playing around with them a bit and they don't really seem ready for use. They are effectively disabled right now because of the bug I mentioned in

Re: Are we ready for the 2.0.0 release in mid-May?

2006-04-29 Thread David Hampton
On Sat, 2006-04-29 at 18:22 -0400, Mike Alexander wrote: Thanks for committing this. Sorry about not putting it in bugzilla. I'll transfer this there if you think it would be useful. I probably would have found it and committed it earlier, but this is fine for me. I see that you changed

Are we ready for the 2.0.0 release in mid-May?

2006-04-28 Thread Christian Stimming
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Dear developers, I'd like to have a short discussion about the planned 2.0.0 release date, and which prerequisites have to be fulfilled so that we can actually make that release. The Goal of 2.0.0 as written on

Re: Are we ready for the 2.0.0 release in mid-May?

2006-04-28 Thread Mike Alexander
--On April 28, 2006 11:16:39 AM +0200 Christian Stimming [EMAIL PROTECTED] wrote: Additionally, we should think a little bit about the newly introduced features and whether they are ready for showtime already. Specifically, are the budgeting-related features really working good enough? If they

Re: Are we ready for the 2.0.0 release in mid-May?

2006-04-28 Thread Derek Atkins
Quoting Mike Alexander [EMAIL PROTECTED]: What about lots? I've been playing around with them a bit and they don't really seem ready for use. They are effectively disabled right now because of the bug I mentioned in https://lists.gnucash.org/pipermail/gnucash-devel/2006-April/017154.html.

Re: Are we ready for the 2.0.0 release in mid-May?

2006-04-28 Thread David Hampton
On Fri, 2006-04-28 at 13:29 -0400, Mike Alexander wrote: What about lots? I've been playing around with them a bit and they don't really seem ready for use. They are effectively disabled right now because of the bug I mentioned in