Probably before 3.14b1, we'll want to update * http://poi.apache.org/overview.html#components * Bugzilla component for product=POI for Common SL support On Nov 30, 2015 12:13 AM, "Andreas Beeker" <[email protected]> wrote:
> Hi Javen, > I had a similar problems [1] and even after trying to use openjdk on > Windows, there were still a lot of differences.So currently, I leave > updating the javadocs to Nick and Dominik, i.e. someone with a linux > installation. > Andi > [1] > http://apache-poi.1045710.n5.nabble.com/update-website-javadocs-td5719468.html > > -------- Original message -------- > From: Javen O'Neal <[email protected]> > Date: 30/11/2015 08:44 (GMT+01:00) > To: POI Developers List <[email protected]> > Subject: Re: Ready for 3.14-Beta1? > > I've got most of the commits I wanted to get in for 3.14beta1. The > online javadocs need to be updated prior to release. > > For some reason when I generate javadocs on my computer, nearly every > file changes. The last time I changed the javadocs [1], the section > links changed, javascript code was written to standalone files rather > than in the .html file, and the page formatting got borked. I think my > ant/forrest are consistent with > https://poi.apache.org/howtobuild.html#Install+Apache+Forrest > I feel bad for not committing my javadoc html changes, so thanks to > the folks who have been updating those for me. > Using Ant 1.9.3 (2015-04-08), but I also have Ant 1.6alpha > (2003-05-26) installed > Forrest 0.5 (2003-09-13) > > What versions are people using to generate "ant javadocs" and "ant site"? > > Time to take a break from subversion for some pie! > > [1] https://svn.apache.org/viewvc?view=revision&revision=1715754, I > only committed the added files to minimize the damage to other files > Nick fixed it in r1715845 > > https://svn.apache.org/viewvc/poi/site/publish/apidocs/org/apache/poi/ss/util/class-use/CellAddress.html?view=log > > On Sun, Nov 29, 2015 at 6:47 AM, Andreas Beeker <[email protected]> > wrote: > > Hi David, > > > > in case you'll start with the beta preparation soon, please leave an > one-liner here, > > with the time you begin, so we stop committing stuff by then. > > > > Apart of that, feel free to begin with the releasing. > > > >> I'm still happy to do so if that's acceptable to everyone? > > One thing, which took me a while to realize is ... silence is > acceptance! [1] ;) > > > > Andi > > > > [1] https://en.wikipedia.org/wiki/Wikipedia:Silence_and_consensus > > > > On 20.11.2015 12:36, David North wrote: > >> Yes, it's definitely time. As previously discussed there was a > >> suggestion that I'd manage this one (as a one-off) to confirm that the > >> process is well-documented enough for someone new to follow. I'm still > >> happy to do so if that's acceptable to everyone? > >> > >> Thanks, > >> David > >> > >> On 20/11/15 00:47, Javen O'Neal wrote: > >>> Keeping with the 2 month release cycle, I'd say it's a good time for > >>> another release. My vote would be to include the ooxml-schema fix in > the > >>> beta to maximize time for people to report issues before 3.14 final. > >>> > >>> π!!! > >>> Hi, > >>> > >>> the changes since 3.13 don't fit anymore on my browser window *), I > guess > >>> it's time for 3.14-Beta1, > >>> what do you think? > >>> > >>> Should we do the beta before or after the ooxml-schema patch? (#58617) > >>> > >>> Andi > >>> > >>> *) yes, I know, press <ctrl>+<-> ... > >>> > >>> --------------------------------------------------------------------- > >>> 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] > >> > >> > > > > > > > > --------------------------------------------------------------------- > > 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] > >
