On Thu, Mar 14, 2013 at 4:50 PM, Paul Burba wrote:
> Whenever we approach a release we always face the question: Which of
> our open issues are blockers for the upcoming release? Obviously as
> we approach 1.8, anything with a target milestone of 1.8.0 is
> (supposedly) a blocker. But what about
On 03/14/2013 04:50 PM, Paul Burba wrote:
> In the interests of sanity I propose we bulk assign all issues filed
> before some arbitrary point in time to the 'unscheduled' milestone. I
> suggest using the date 1.7.0 was tagged as that point, under the
> assumption that any issues filed prior were
Paul Burba wrote:
> Whenever we approach a release we always face the question: Which of
> our open issues are blockers for the upcoming release? Obviously as
> we approach 1.8, anything with a target milestone of 1.8.0 is
> (supposedly) a blocker. But what about all the issues with the '---'
> t
Whenever we approach a release we always face the question: Which of
our open issues are blockers for the upcoming release? Obviously as
we approach 1.8, anything with a target milestone of 1.8.0 is
(supposedly) a blocker. But what about all the issues with the '---'
target milestone? Very old i
4 matches
Mail list logo
