You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cordova.apache.org by Steven Gill <st...@gmail.com> on 2013/02/14 21:52:29 UTC
2.5.0 for end of this month
Hey Guys,
We have been lagging a bit behind on our usual release at the end of the
month cycle. I'd like for us to push to get 2.5.0 out at the end of the
month to get us back on track. How do people feel about aiming to get 2.5.0
released on Feb 28th? We would have to do our first RC early next week
(tuesday) for this to work followed by potential second RC around the 25th.
Thoughts?
-Steve
Re: 2.5.0 for end of this month
Posted by Filip Maj <fi...@adobe.com>.
Reminder that the proposed week Steve is suggesting is ApacheCon, and most
of us will be on the go. I guess remember to grab all your devices?
On 2/14/13 3:34 PM, "Joe Bowser" <bo...@gmail.com> wrote:
>+1 on the release.
>
>Marcel: I actually think that it's healthy to have so many known bugs
>reported in the project, since it shows that we actually know what's
>going on and that the project is actually active. I consider the bug
>count to be relatively low. Also, I'm glad we don't have bugs like
>this: https://code.google.com/p/android/issues/detail?id=7589
>
>As far as bookkeeping, if you have an old bug, please work on it,
>close it or re-assign it somewhere. If we can't fix it, mark it as
>"Won't Fix" with a reason as to why we can't fix this and move on.
>There's bugs that have been sitting in there for a year that we
>haven't touched because we don't have a way of fixing (i.e. Weird
>google contact bug w.r.t. google contact sync). We need those dealt
>with so that they're not inflating our numbers.
>
>
>On Thu, Feb 14, 2013 at 3:09 PM, Brian LeRoux <b...@brian.io> wrote:
>> Marcel: I think the bookkeeping has become a little messy.
>>
>> Joe/Simon: As to why release, in 'release train philosophy' we attempt
>>to
>> follow a version number is a cutoff indiscriminate of features. The
>>reason:
>> we don't want to couple marketing events, and worse, to releases.
>>Sometimes
>> this means we have a light release: oh well. Better than the alternative
>> which I am certain every developer on this list has lived through.
>>
>>
>> On Thu, Feb 14, 2013 at 2:19 PM, Marcel Kinard <cm...@gmail.com>
>>wrote:
>>
>>> Something I've noticed is the default graph on Jira is showing a
>>>widening
>>> gap between open and closed issues, basically wider than it has ever
>>>been.
>>> Looks like there are 140 unresolved bugs (compared to 60 unresolved
>>> improvements, 59 feature requests, and 57 subtasks). Leaving users a
>>>bad
>>> quality taste in their mouth would be bad for everyone. Is the bug
>>>count
>>> creeping beyond what it should be, and should there be a focused
>>>effort on
>>> defect takedown? I could see that kind of content driving a release.
>>>Or is
>>> it simply that our Jira bookkeeping is a bit messy?
>>>
>>> -- Marcel Kinard
>>>
>>> On Feb 14, 2013, at 3:52 PM, Steven Gill <st...@gmail.com>
>>>wrote:
>>>
>>> > Hey Guys,
>>> >
>>> > We have been lagging a bit behind on our usual release at the end of
>>>the
>>> > month cycle. I'd like for us to push to get 2.5.0 out at the end of
>>>the
>>> > month to get us back on track. How do people feel about aiming to get
>>> 2.5.0
>>> > released on Feb 28th? We would have to do our first RC early next
>>>week
>>> > (tuesday) for this to work followed by potential second RC around the
>>> 25th.
>>> >
>>> > Thoughts?
>>> >
>>> > -Steve
>>>
>>>
Re: 2.5.0 for end of this month
Posted by Joe Bowser <bo...@gmail.com>.
+1 on the release.
Marcel: I actually think that it's healthy to have so many known bugs
reported in the project, since it shows that we actually know what's
going on and that the project is actually active. I consider the bug
count to be relatively low. Also, I'm glad we don't have bugs like
this: https://code.google.com/p/android/issues/detail?id=7589
As far as bookkeeping, if you have an old bug, please work on it,
close it or re-assign it somewhere. If we can't fix it, mark it as
"Won't Fix" with a reason as to why we can't fix this and move on.
There's bugs that have been sitting in there for a year that we
haven't touched because we don't have a way of fixing (i.e. Weird
google contact bug w.r.t. google contact sync). We need those dealt
with so that they're not inflating our numbers.
On Thu, Feb 14, 2013 at 3:09 PM, Brian LeRoux <b...@brian.io> wrote:
> Marcel: I think the bookkeeping has become a little messy.
>
> Joe/Simon: As to why release, in 'release train philosophy' we attempt to
> follow a version number is a cutoff indiscriminate of features. The reason:
> we don't want to couple marketing events, and worse, to releases. Sometimes
> this means we have a light release: oh well. Better than the alternative
> which I am certain every developer on this list has lived through.
>
>
> On Thu, Feb 14, 2013 at 2:19 PM, Marcel Kinard <cm...@gmail.com> wrote:
>
>> Something I've noticed is the default graph on Jira is showing a widening
>> gap between open and closed issues, basically wider than it has ever been.
>> Looks like there are 140 unresolved bugs (compared to 60 unresolved
>> improvements, 59 feature requests, and 57 subtasks). Leaving users a bad
>> quality taste in their mouth would be bad for everyone. Is the bug count
>> creeping beyond what it should be, and should there be a focused effort on
>> defect takedown? I could see that kind of content driving a release. Or is
>> it simply that our Jira bookkeeping is a bit messy?
>>
>> -- Marcel Kinard
>>
>> On Feb 14, 2013, at 3:52 PM, Steven Gill <st...@gmail.com> wrote:
>>
>> > Hey Guys,
>> >
>> > We have been lagging a bit behind on our usual release at the end of the
>> > month cycle. I'd like for us to push to get 2.5.0 out at the end of the
>> > month to get us back on track. How do people feel about aiming to get
>> 2.5.0
>> > released on Feb 28th? We would have to do our first RC early next week
>> > (tuesday) for this to work followed by potential second RC around the
>> 25th.
>> >
>> > Thoughts?
>> >
>> > -Steve
>>
>>
Re: 2.5.0 for end of this month
Posted by Brian LeRoux <b...@brian.io>.
Marcel: I think the bookkeeping has become a little messy.
Joe/Simon: As to why release, in 'release train philosophy' we attempt to
follow a version number is a cutoff indiscriminate of features. The reason:
we don't want to couple marketing events, and worse, to releases. Sometimes
this means we have a light release: oh well. Better than the alternative
which I am certain every developer on this list has lived through.
On Thu, Feb 14, 2013 at 2:19 PM, Marcel Kinard <cm...@gmail.com> wrote:
> Something I've noticed is the default graph on Jira is showing a widening
> gap between open and closed issues, basically wider than it has ever been.
> Looks like there are 140 unresolved bugs (compared to 60 unresolved
> improvements, 59 feature requests, and 57 subtasks). Leaving users a bad
> quality taste in their mouth would be bad for everyone. Is the bug count
> creeping beyond what it should be, and should there be a focused effort on
> defect takedown? I could see that kind of content driving a release. Or is
> it simply that our Jira bookkeeping is a bit messy?
>
> -- Marcel Kinard
>
> On Feb 14, 2013, at 3:52 PM, Steven Gill <st...@gmail.com> wrote:
>
> > Hey Guys,
> >
> > We have been lagging a bit behind on our usual release at the end of the
> > month cycle. I'd like for us to push to get 2.5.0 out at the end of the
> > month to get us back on track. How do people feel about aiming to get
> 2.5.0
> > released on Feb 28th? We would have to do our first RC early next week
> > (tuesday) for this to work followed by potential second RC around the
> 25th.
> >
> > Thoughts?
> >
> > -Steve
>
>
Re: 2.5.0 for end of this month
Posted by Marcel Kinard <cm...@gmail.com>.
Something I've noticed is the default graph on Jira is showing a widening gap between open and closed issues, basically wider than it has ever been. Looks like there are 140 unresolved bugs (compared to 60 unresolved improvements, 59 feature requests, and 57 subtasks). Leaving users a bad quality taste in their mouth would be bad for everyone. Is the bug count creeping beyond what it should be, and should there be a focused effort on defect takedown? I could see that kind of content driving a release. Or is it simply that our Jira bookkeeping is a bit messy?
-- Marcel Kinard
On Feb 14, 2013, at 3:52 PM, Steven Gill <st...@gmail.com> wrote:
> Hey Guys,
>
> We have been lagging a bit behind on our usual release at the end of the
> month cycle. I'd like for us to push to get 2.5.0 out at the end of the
> month to get us back on track. How do people feel about aiming to get 2.5.0
> released on Feb 28th? We would have to do our first RC early next week
> (tuesday) for this to work followed by potential second RC around the 25th.
>
> Thoughts?
>
> -Steve
Re: 2.5.0 for end of this month
Posted by Simon MacDonald <si...@gmail.com>.
Yeah, what features or bug fixes are the driving force for 2.5.0 being
out at the end of the month?
Simon Mac Donald
http://hi.im/simonmacdonald
On Thu, Feb 14, 2013 at 4:50 PM, Joe Bowser <bo...@gmail.com> wrote:
> So, are we having a release just to have a release? I'm OK with that,
> but a lot hasn't happened between 2.4.x and this release so far.
>
> On Thu, Feb 14, 2013 at 1:02 PM, Brian LeRoux <b...@brian.io> wrote:
>> +1
>>
>>
>> On Thu, Feb 14, 2013 at 12:52 PM, Steven Gill <st...@gmail.com>wrote:
>>
>>> Hey Guys,
>>>
>>> We have been lagging a bit behind on our usual release at the end of the
>>> month cycle. I'd like for us to push to get 2.5.0 out at the end of the
>>> month to get us back on track. How do people feel about aiming to get 2.5.0
>>> released on Feb 28th? We would have to do our first RC early next week
>>> (tuesday) for this to work followed by potential second RC around the 25th.
>>>
>>> Thoughts?
>>>
>>> -Steve
>>>
Re: 2.5.0 for end of this month
Posted by Joe Bowser <bo...@gmail.com>.
So, are we having a release just to have a release? I'm OK with that,
but a lot hasn't happened between 2.4.x and this release so far.
On Thu, Feb 14, 2013 at 1:02 PM, Brian LeRoux <b...@brian.io> wrote:
> +1
>
>
> On Thu, Feb 14, 2013 at 12:52 PM, Steven Gill <st...@gmail.com>wrote:
>
>> Hey Guys,
>>
>> We have been lagging a bit behind on our usual release at the end of the
>> month cycle. I'd like for us to push to get 2.5.0 out at the end of the
>> month to get us back on track. How do people feel about aiming to get 2.5.0
>> released on Feb 28th? We would have to do our first RC early next week
>> (tuesday) for this to work followed by potential second RC around the 25th.
>>
>> Thoughts?
>>
>> -Steve
>>
Re: 2.5.0 for end of this month
Posted by Brian LeRoux <b...@brian.io>.
+1
On Thu, Feb 14, 2013 at 12:52 PM, Steven Gill <st...@gmail.com>wrote:
> Hey Guys,
>
> We have been lagging a bit behind on our usual release at the end of the
> month cycle. I'd like for us to push to get 2.5.0 out at the end of the
> month to get us back on track. How do people feel about aiming to get 2.5.0
> released on Feb 28th? We would have to do our first RC early next week
> (tuesday) for this to work followed by potential second RC around the 25th.
>
> Thoughts?
>
> -Steve
>