I plan to spend some time on fixing bugs too. We really should pay attention to contributions.
A year back, when I released POI 3.9, we had about 200 open Bugzilla issues and now we have 350 tickets ; https://issues.apache.org/bugzilla/buglist.cgi?bug_file_loc=&bug_file_loc_type=allwordssubstr&bug_id=&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bugidtype=include&chfieldfrom=&chfieldto=Now&chfieldvalue=&email1=&email2=&emailassigned_to1=1&emailassigned_to2=1&emailcc2=1&emailreporter2=1&emailtype1=substring&emailtype2=substring&field0-0-0=noop&keywords=&keywords_type=allwords&long_desc=&long_desc_type=substring&product=POI&query_format=advanced&short_desc=&short_desc_type=allwordssubstr&type0-0-0=noop&value0-0-0=&votes=&order=bug_id%20DESC&query_based_on= At minimum we should review and apply pending patches, we have quite a few of them. Yegor On Mon, Sep 30, 2013 at 12:27 AM, Dominik Stadler <[email protected]>wrote: > Ok, agreed, I started to look at some of the reported patches, however the > OLE patches are quite large, at least I cannot verify what side-effects > they might have on other parts of the code with my still limited knowledge > of some parts of the code... > > Dominik. > > > On Tue, Sep 24, 2013 at 12:52 AM, Dave Fisher <[email protected]> > wrote: > > > OLE Embedding looks like a hot patch to check out. It is certainly very > > useful. > > > > Regards, > > Dave > > > > On Sep 22, 2013, at 2:28 PM, Nick Burch wrote: > > > > > On Fri, 20 Sep 2013, Dominik Stadler wrote: > > >> what are the next steps on POI? Do we stabilize a bit more and release > > 3.10 before doing more risky stuff? Or do some more bugfixes before > > starting the 3.10 release process again? > > > > > > Given we've had 2 betas so far, it would probably confuse users if we > > started doing major and/or breaking changes before 3.10 final is out. > > Afterwards we're fine to, compatibility rules withstanding! Hopefully > that > > won't be that long, if you want to make some big changes it's not too > long > > to hold off... > > > > > > What we do have is quite a lot of user contributed patches/fixes that > > haven't been applied. If we're not very good at reviewing/applying them, > > then it has two bad effects. Firstly, we're less likely to get more > > contributions in future if we're not seen to appreciate them. Secondly, > > people who have their patches ignored tend not to stick about, so we > loose > > out on potential new committers going forward. Neither good! > > > > > > Everyone here is a volunteer, so no-one can demand anyone else do > > anything! But, if I did have more spare time than I currently seem to, > I'd > > personally be focusing on trying to review + apply as many recent user > > contributed fixes/enhancements as possible. > > > > > > Either way, we probably want to set a rough deadline on the next > > release. A few days before, we can do a straw poll on beta 3 vs final. If > > Tim decides it's leaning towards another beta, then he can pretty much > roll > > it then. If final is the consensus, then probably best allow a week or so > > extra for last minute fixes / tweaks, then roll 3.10 final! > > > > > > In the mean time, if anyone wants to play with some major changes, best > > bet is to take a branch in SVN to work on, then merge it back to trunk > once > > 3.10 is out. > > > > > > Nick > > > > > > --------------------------------------------------------------------- > > > To unsubscribe, e-mail: [email protected] > > > For additional commands, e-mail: [email protected] > > > > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [email protected] > > For additional commands, e-mail: [email protected] > > > > >
