You are obviously free to implement this as you wish, however one of the things we realised is that the hosted API docs on the web site are also very out of date, and by doing it this way would mean they stay out of date. Doing it this way means you would really have to update on every commit, or at least once a day.
When we were discussing this with Dave at MesosCon Europe we thought the better option was to have a CI server (or something similar) perform this work by deploying it directly without going via subversion. There are many other Apache projects with API docs on their web sites so they are likely not going via subversion for this. On Wed, Nov 11, 2015 at 4:30 AM, Vinod Kone <vinodk...@gmail.com> wrote: > That said, this can be automated as a step in apply-reviews script. For > example, the script can check if something in site/ (or docs/ ?) is being > committed and if yes, also do an svn update. @artem do you want to take > this on as you revamp the apply-reviews script? > > On Tue, Nov 10, 2015 at 1:23 AM, Adam Bordelon <a...@mesosphere.io> wrote: > > > Since it's still a manual process, the website is usually only updated a) > > when we have a new release to announce, or b) when some other blog-worthy > > content arises (e.g. MesosCon). > > > > On Tue, Nov 10, 2015 at 1:06 AM, Jonathon Rossi <j...@jonorossi.com> > > wrote: > > > > > It is currently a manual process performed by a committer, however > there > > > are plans to make it automated. See this thread for the recent > > discussion: > > > > > > http://www.mail-archive.com/dev@mesos.apache.org/msg33541.html > > > > > > On Tue, Nov 10, 2015 at 6:56 PM, Neil Conway <neil.con...@gmail.com> > > > wrote: > > > > > > > Does anyone know how frequently the docs at mesos.apache.org are > > > > updated? I notice that some docs changes from > 1 week ago aren't > > > > reflected on the current site. > > > > > > > > Neil > > > > > > > > > > -- > > > Jono > > > > > > -- Jono
