Wil Sinclair wrote:
Guilty as charged. We have been hogging all the work, and frankly we feel
terrible about it. So, without further ado, Zend Framework's Most Wanted
(issues). . .
http://framework.zend.com/wiki/display/ZFDEV/Zend+Framework%27s+Most+Wanted
At least now you can't say that we
e you what you want. ;)
,Wil
> -Original Message-
> From: Steven Brown [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, January 15, 2008 3:21 PM
> To: 'Zend Framework General'
> Subject: RE: [fw-general] Issue resolving procedure
>
> I totally agree with this, I
I totally agree with this, I have been prepared to get in and help but how do I
know what I can do without interfering with others, and how do I join a team
etc. It's not entirely clear within the issue tracker.
-Original Message-
From: Michał Minicki [mailto:[EMAIL PROTECTED]
Sent: Tue
Greetings
Thomas
I18N Team Leader
- Original Message -
From: "Michał Minicki" <[EMAIL PROTECTED]>
To: "Thomas Weidner" <[EMAIL PROTECTED]>
Cc: "Zend Framework General"
Sent: Tuesday, January 15, 2008 4:05 PM
Subject: Re: [fw-general] Issue resolving proced
Hey.
I'm actually an old-timer, so I know the basics, Thomas. I'm the original
author of Rewrite Router and I have access to svn since 2006 (martel). So
that's not an issue :)
Basically what I'm asking is some way to be sure that unassigned issues (or
issues assigned to team leaders) are sch
Hy Michael,
I can only speak as Team Lead.
Generally when an issue is coming in, the team lead get's an announcement.
He can then decide who get's the issue.
If this is not done, then this issue leaves unassigned.
Anyone who has SVN rights can assign an issue to himself and solve it.
But genera
