Hi all, What's the next step to be done here, i.e., where are we with the process to put together and publish NetBeans API javadoc?
What are the open questions, what are the blockers? Thanks, Gj On Tue, Sep 18, 2018 at 10:40 AM, Neil C Smith <[email protected]> wrote: > On Mon, 17 Sep 2018 at 20:40, Antonio <[email protected]> wrote: > > So shall we remove the bits.netbeans.org subdirectory at [1]? > > Let's keep it until we're certain what we're doing here. That might > still form the basis of a Jenkins script for doing docs for dev > snapshots? > > On Mon, 17 Sep 2018 at 20:51, Antonio <[email protected]> wrote: > > Just talked to infra. They indeed prefer to commit all the javadoc files > > to git and then use the "asf-site" branch and gitpubsub. I'll keep you > > posted on my findings and update Neil's confluence page with my findings. > > That doesn't really surprise me, although I should have asked that > earlier - finally found out where infra chat is! :-) > > Thanks for adding notes on the wiki page. Sounds like self-serve for > getting the repo up is a good first step? > > I'm not sure on automating the Javadoc for releases, at least more > than updating the main releases Jenkins task to build the docs > alongside the binaries and source bundles. They need manually > signing, checking and uploading post-vote don't they? In which case > maybe adding Javadoc commit to step 5 at > https://cwiki.apache.org/confluence/display/NETBEANS/ > Apache+NetBeans+Release+README > makes sense? > > Best wishes, > > Neil > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > For further information about the NetBeans mailing lists, visit: > https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists > > > >
