On Fri, 2004-12-24 at 07:00 -0500, Chris Shoemaker wrote: > On Thu, Dec 23, 2004 at 06:16:50PM -0500, Josh Sled wrote: > > > > I believe the current desires are best captured by: "get thing working > > under gnome2 first, then later get things working right." > > Ok, is there a list of MUSTFIXes for a g2 release? I checked the > bugzilla: not much about g2. And GNOME2_STATUS mostly says where g2 > is at now, but says little about where it has to get to. Is there an > archived email I didn't find? >
We probably ought to just start filing bug reports against the G2 port. This will help prevent any duplicate work--if you wanted to work on something, you could add to the bug comments that you are working on it. I'm not well versed in Gnome-2 widgets and GUI programming (more of a Java guy), and probably won't take the time to be, but I can certainly fill out a Web page bug report! I think any G2-port developer could take the time to file specific bug reports on changes required and work- in-progress, or on things that simply don't work and an immediate solution cannot be thought of. This would allow the team to review current/past work-in-progress on G2, and avoid trying to do something that someone else is already working on. The disadvantage is that the bug system may get a lot of bugs entered, but if you use the branch tag (gnucash-gnome2-dev) in other-version- info, then you ought to be able to filter on that. Just my thoughts, -- Matthew Vanecek perl -e 'print $i=pack(c5,(41*2),sqrt(7056),(unpack(c,H)-2),oct(115),10);' ******************************************************************************** For 93 million miles, there is nothing between the sun and my shadow except me. I'm always getting in the way of something...
signature.asc
Description: This is a digitally signed message part
_______________________________________________ gnucash-devel mailing list [email protected] https://lists.gnucash.org/mailman/listinfo/gnucash-devel
