And might as well use 3.16-beta2 since it was just released. There were a couple new minor bugs in this beta, but we decided to release it anyways. Had it been a final release, we would have fixed the bug found from our regression testing, built another RC, gone through the testing process again, and released the build two weeks later. It wasn't worth that effort for a beta, so that's the danger of using a beta.
As Andi said, if you don't experience any bugs using the beta, use it if you can. On Feb 9, 2017 02:25, "kiwiwings" <[email protected]> wrote: > Hi, > > we have this policies here too [in my $dayjob], about not using those evil > beta releases. > In my point of view there's not so much difference between a beta and a > final release. > Before releasing we crunch through a big corpus of office files and do some > validations/verifications with our own test projects. > I guess the difference is more in validating that we haven't introduced > undocumented api breaks > and that it works nicely with Tika. > > So if a beta works ok for your tests, then use the beta ... if not, please > open a bugzilla entry! > > Best wishes, > Andi > > > > -- > View this message in context: http://apache-poi.1045710.n5. > nabble.com/3-16-Beta1-vs-3-15-FINAL-tp5726521p5726527.html > Sent from the POI - Dev mailing list archive at Nabble.com. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
