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 <[email protected]> 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 <[email protected]> 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 > >
