> > > > On Apr 11, 2013, at 10:33 PM, "Marcus Sorensen" <shadow...@gmail.com> > wrote: > > > One thing I'd like to point out, and perhaps its merely subjective, > > but it seemed like from initial 4.1 feature freeze to a week or two > > before the rc was supposed to be cut there wasn't much action on bug > > fixing. It wasn't until the deadlines started becoming imminent that > > people came back to work on 4.1. Just something to keep in mind when > discussing extending deadlines. > > Certainly the urgency does set in closer to deadlines. > [Animesh>] Marcus I did further analysis and it points out that there was constant activity in defect fixing since the code freeze date and matches up closely with defect creation. Please see attached graph.
- [ASFCS42] Proposed schedule for our next release Animesh Chaturvedi
- Re: [ASFCS42] Proposed schedule for our next relea... David Nalley
- RE: [ASFCS42] Proposed schedule for our next r... Animesh Chaturvedi
- Re: [ASFCS42] Proposed schedule for our next r... Marcus Sorensen
- Re: [ASFCS42] Proposed schedule for our ne... Animesh Chaturvedi
- RE: [ASFCS42] Proposed schedule for ou... Animesh Chaturvedi
- Re: [ASFCS42] Proposed schedule f... David Nalley
- RE: [ASFCS42] Proposed schedu... Animesh Chaturvedi
- RE: [ASFCS42] Proposed schedule f... Animesh Chaturvedi
- Re: [ASFCS42] Proposed schedule for our next relea... Chip Childers
- RE: [ASFCS42] Proposed schedule for our next r... Animesh Chaturvedi
- RE: [ASFCS42] Proposed schedule for our next r... Will Chan
- Re: [ASFCS42] Proposed schedule for our ne... David Nalley
- Re: [ASFCS42] Proposed schedule for ou... Chiradeep Vittal
- Re: [ASFCS42] Proposed schedule f... David Nalley
- Re: [ASFCS42] Proposed schedu... Chip Childers