You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@poi.apache.org by Jeevan Chamarthi <ch...@gmail.com> on 2017/02/09 06:21:54 UTC
3.16 Beta1 vs 3.15 FINAL
Hi Guys,
I am working on a production application which uses Apache POI PPT, during which I encountered a bug with poi ppt table row height which is resolved in 3.16 beta1.
Wanted to know if it is fine to switch to beta releases without risk. Please suggest.
Thanks,
Jeevan
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@poi.apache.org
For additional commands, e-mail: dev-help@poi.apache.org
Re: 3.16 Beta1 vs 3.15 FINAL
Posted by kiwiwings <ki...@apache.org>.
jeevan86 wrote
> By the way, any probable date decided on 3.16 FINAL release ?
We will usually have 2 betas before a final and try to release often, which
is currently every 2-3 month. I would expect the final to be announced by
end of April.
--
View this message in context: http://apache-poi.1045710.n5.nabble.com/3-16-Beta1-vs-3-15-FINAL-tp5726521p5726541.html
Sent from the POI - Dev mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@poi.apache.org
For additional commands, e-mail: dev-help@poi.apache.org
Re: 3.16 Beta1 vs 3.15 FINAL
Posted by Jeevan Chamarthi <ch...@gmail.com>.
Thanks Andi and Javen. That helps a lot. I will go ahead and use 3.16 beta 1.
By the way, any probable date decided on 3.16 FINAL release ?
Regards,
Jeevan
On 2017-02-09 22:29 (+0530), "Javen O'Neal" <on...@apache.org> wrote:
> 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" <ki...@apache.org> 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: dev-unsubscribe@poi.apache.org
> > For additional commands, e-mail: dev-help@poi.apache.org
> >
> >
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@poi.apache.org
For additional commands, e-mail: dev-help@poi.apache.org
Re: 3.16 Beta1 vs 3.15 FINAL
Posted by Javen O'Neal <on...@apache.org>.
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" <ki...@apache.org> 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: dev-unsubscribe@poi.apache.org
> For additional commands, e-mail: dev-help@poi.apache.org
>
>
Re: 3.16 Beta1 vs 3.15 FINAL
Posted by kiwiwings <ki...@apache.org>.
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: dev-unsubscribe@poi.apache.org
For additional commands, e-mail: dev-help@poi.apache.org
Re: 3.16 Beta1 vs 3.15 FINAL
Posted by Marco Amador <ma...@gmail.com>.
Hi all,
Following this thread, out of curiosity. :)
I'm actually in a similar situation to the one Jeevan described
(application receives files with CryptoAPI encryption, which was added in
the 3.16 beta 1), though I'm inclined to wait for the 3.16 final before
switching versions.
Regards,
Marco
On 9 February 2017 at 07:21, Jeevan Chamarthi <ch...@gmail.com>
wrote:
> Hi Guys,
> I am working on a production application which uses Apache POI PPT, during
> which I encountered a bug with poi ppt table row height which is resolved
> in 3.16 beta1.
>
> Wanted to know if it is fine to switch to beta releases without risk.
> Please suggest.
>
> Thanks,
> Jeevan
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@poi.apache.org
> For additional commands, e-mail: dev-help@poi.apache.org
>
>