I think all the renewed activity is great. Next week, I will update JIRA to reflect these comments, and perhaps close out some items that are not mentioned here.
We seem to make a release after about 6 months or 150 JIRA issues. There's no hard rules about that, but seems like a fine pace to date. That would put us to a new release around January next year by default. Hey, if there's a surge of activity, let's make it sooner. On Thu, Aug 18, 2011 at 2:44 PM, Grant Ingersoll <[email protected]>wrote: > I intend to get through M-688 and M-627 soon. I'd appreciate some other > eyeballs on M-627. I think M-399 warrants more interest, but I also seem > to recall Jake saying he has a pretty significant overhaul of LDA coming > anyway, so it may not be worth the time. > > Seems like with this push, we could get to 0.6 sometime in late Sept or > Oct.? > > > On Aug 17, 2011, at 4:48 AM, Sean Owen wrote: > > > Hi all, I'm again seeing the issue count tend to pile up. I try to run > > through regularly to resolve anything addressed to me, and even things > that > > aren't but that I am confident enough to fix. It would be great if > everyone > > could do the same in a spare 1-2 hours this week, if only to say "yes, go > > ahead on that patch" or "no I don't think this is a good idea". > Especially > > the committers who have not been active in a while. > > > > To me, this is the most essential work we can do, because without > responses > > from those with power to commit, new community members get the message > that > > their contributions are ignored, or that nobody's home. That's no good. > > Understanding that individuals may not have time to actively write their > own > > new changes and improvements, it seems that the least we can all do is > > involve and respond to external input, to bring in those who want to make > > changes. > > > > I'd also like to sweep through the issues that have not been touched in > 6+ > > months and close some that just do not seem to be getting any traction or > > attention. The theory is that closing stuff that by all accounts won't > get > > looked at better communicates what's coming in the project, and focuses > > attention on issues that might get looked at. > > > > Before I start that though, would welcome anyone to peek at everything > > that's open and assign, comment, ping, etc. anything that needs to be > kept > > alive. > > -------------------------------------------- > Grant Ingersoll > http://www.lucidimagination.com > >
