See my pr.  We can disable autopush, but when we do release doc generation
would still work.  I.e. second part of your todo.

Regarding whether we always push javadocs I see your point and xanelive
with that.

Maybe we need a "upcoming" javadoc list too.
On Jun 2, 2014 3:49 PM, "eugene yokota" <notifications@github.com> wrote:

> In project/Docs.scala:
>
> > @@ -27,27 +26,18 @@ object Docs
> >  	val HomeHtml = "home.html"
> >  	val VersionPattern = """(\d+)\.(\d+)\.(\d+)(-.+)?""".r.pattern
> >
> > -	def settings: Seq[Setting[_]] =
> > -		site.settings ++
> > -		site.sphinxSupport(DocsPath) ++
> > -		site.includeScaladoc("api") ++
>
> I'm still thinking about this, but more leaning towards treating Scaladoc
> comment as part of code. We should just cut a release and let it go. Any
> improvement should just wait till 0.13.6. There are several benefits for
> this:
>
>    - Documentation maintenance of 0.13.5 doesn't cut into the development
>    time of 0.13.6.
>    - Having the clear deadline should force us to review API docs as part
>    of milestone process.
>    - When we ship zipped version of the API, what we shipped on the
>    release date is the same thing we show on the website.
>
> I only deleted the Sphnix related code. site.settings is just commented
> out.
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/sbt/sbt/pull/1385/files#r13303415>.
>