On Fri, Nov 30, 2012 at 9:08 PM, Branko Čibej wrote:
> It's quite frustrating that people find time to write hundreds of mails
> about points of procedure, but can't take time to review a release
> tarball from a podling.
Reviewing a release when you are not directly involved as a developer is
**
Sorry, seems it was Luciano I agreed with.
Sent from my tablet
On Dec 1, 2012 8:43 AM, "Ross Gardler" wrote:
> I'm with Benson here. But we do need to acknowledge the problem identified
> (again) by Branko.
>
> This is a mentoring problem not an IPMC problem. The IPMC needs to solve
> it for exi
I'm with Benson here. But we do need to acknowledge the problem identified
(again) by Branko.
This is a mentoring problem not an IPMC problem. The IPMC needs to solve it
for existing podlings, and podlings where mentors have gone quiet but we
need to express higher expectations of mentors for new
On Fri, Nov 30, 2012 at 9:08 PM, Branko Čibej wrote:
> It's quite frustrating that people find time to write hundreds of mails
> about points of procedure, but can't take time to review a release
> tarball from a podling.
>
> Activity on Bloodhound is picking up, and the project wants to release
It's quite frustrating that people find time to write hundreds of mails
about points of procedure, but can't take time to review a release
tarball from a podling.
Activity on Bloodhound is picking up, and the project wants to release
every couple weeks; yet the 0.2 vote thread sat in general@ for
