Re: [fluid-dev] About the trac tickets

2010-10-21 Thread Pedro Lopez-Cabanillas
On Thursday 21 October 2010, David Henningsson wrote: > So about the trac tickets, and whether things get picked up or ignored More comments about the tickets. * Our Trac reports are currently broken. The report "{1} Active Tickets" omits all the tickets having the state "None", migrated from t

Re: [fluid-dev] About the trac tickets

2010-10-21 Thread James Le Cuirot
On Thu, 21 Oct 2010 17:39:49 +1100 Matt Giuca wrote: > Thanks for that good clarification. I've been confused as to whether > we were supposed to be using trac or not. > > Perhaps we can create some kind of "virtual" sf.net user, that owns > all new > > tickets, and has the fluid-dev list regist

Re: [fluid-dev] About the trac tickets

2010-10-21 Thread Bernd Casper
Hi David, as a side question: here, when hitting "Reply" to a list posting, I get the personal e-mail address of the poster in the address field. Would it be a good idea, to get the fluid-dev@nongnu.org in that field, instead (I think which default address shall be used for "Reply to:", can be

Re: [fluid-dev] About the trac tickets

2010-10-20 Thread Graham Goode
Hi David, As mainly a 'tester' I think that having the bugs go to the Dev list would be a great idea, we'd also know when our 'testing' experience will be needed ;) GrahamG ___ fluid-dev mailing list fluid-dev@nongnu.org http://lists.nongnu.org/mailman

Re: [fluid-dev] About the trac tickets

2010-10-20 Thread Matt Giuca
Hi David, Thanks for that good clarification. I've been confused as to whether we were supposed to be using trac or not. Perhaps we can create some kind of "virtual" sf.net user, that owns all new > tickets, and has the fluid-dev list registered as his "home email" so that > all ticket notificati

[fluid-dev] About the trac tickets

2010-10-20 Thread David Henningsson
So about the trac tickets, and whether things get picked up or ignored when put there: First: Up to a week ago, all tickets were assigned to jgreen by default, and he is currently not active in this project, at least not much. So one problem was that nobody got a notification when a new ticket