+1, ineffective planning + lots of slipped issues = extra unnecessary
paperwork every 3 weeks.
On Wed, Jun 28, 2017 at 3:04 AM, Aurélien Pupier <apupier(a)redhat.com> wrote:
I take the opportunity of this mail just to raise my concern from an
external point of view.
For the AM1, there are 232 issues that were "planned" (with the fix
version to AM1) and 220 were fixed, so it means that only half of what was
planned has been done. it makes it a bit hard, at least for me, to know
when i can expect to have some issues fixed. I don't know when and if I can
expect issues that are impacting Fuse Tooling in my case will be fixed.
It would be nice to provide a more precise scope (I know this is not
completely easy but I'm sure that being more accurate than 50% is possible)
On Tue, Jun 27, 2017 at 9:18 PM, Nick Boldt <nboldt(a)redhat.com> wrote:
> Yeah, it's that time again -- where I beg you guys to triage your issues
> so I can release AM1.
> I could move them all to AM2, but maybe some of them are done and you
> plan to resolve them for AM1? So I once again need your help.
> Anyway, here's the list of 232 unresolved JIRAs:
> Thanks in advance,
> Nick Boldt
> Senior Software Engineer, RHCSA
> Productization Lead :: JBoss Tools & Dev Studio
> IM: @nickboldt / @nboldt / http://nick.divbyzero.com
> TRIED. TESTED. TRUSTED. <https://redhat.com/trusted>
> @ @redhatnews <https://twitter.com/redhatnews>
> jbosstools-dev mailing list
SENIOR SOFTWARE ENGINEER, FUSE TOOLING
Red Hat France <https://www.redhat.com/>
apupier(a)redhat.com IM: apupier
Senior Software Engineer, RHCSA
Productization Lead :: JBoss Tools & Dev Studio
IM: @nickboldt / @nboldt /
TRIED. TESTED. TRUSTED. <