[ANNOUNCE] wayland 1.7.0
bryce at osg.samsung.com
Mon Feb 23 18:18:40 PST 2015
On Mon, Feb 23, 2015 at 09:30:49AM +0200, Pekka Paalanen wrote:
> On Fri, 20 Feb 2015 14:29:18 -0800
> Bryce Harrington <bryce at osg.samsung.com> wrote:
> > On Tue, Feb 17, 2015 at 11:29:24AM +0200, Pekka Paalanen wrote:
> > > On Mon, 16 Feb 2015 12:52:27 -0800
> > > Bill Spitzak <spitzak at gmail.com> wrote:
> > >
> > > > On 02/14/2015 01:18 AM, Bryce Harrington wrote:
> > > >
> > > > > You can check out this spiffed up documentation at:
> > > > >
> > > > > http://wayland.freedesktop.org/docs/html/
> > > >
> > > > It looks like these pages have not been updated to the newest output,
> > > > in particular apa.html, which does not have the "object" replaced
> > > > with the actual types and the cross-reference links.
> > >
> > > Hi,
> > >
> > > I generated the docs from Wayland 1.7.0 and pushed them to
> > > wayland.fd.o. Is it ok now?
> > If you add this step to the end of the releasing.txt document, I can
> > make sure this gets done at least once a release going forward.
> I wonder... I do a 'make install' to a prefix and then just 'scp -r'
> the right sub-dir. Maybe there's a better way?
> I suppose we could also write a 'make publish-docs' that would do it if
> ssh is set up right.
Cairo has a "make release-publish" step which essentially does
release.sh plus updates the website, and generates and uploads
Their makefile snippet includes a bunch of logic for maintaining old
versions of the docs and linking to the latest via symblinks, but
essentially they're creating a tarball, scping it, and unpacking it on
rm -rf ./$(MANUAL_VERSIONED)
cp -a doc/public/html $(MANUAL_VERSIONED)
tar czf $(MANUAL_TAR_FILE) $(MANUAL_VERSIONED)
scp $(MANUAL_TAR_FILE) $(RELEASE_UPLOAD_HOST):$(MANUAL_UPLOAD_DIR)
ssh $(RELEASE_UPLOAD_HOST) "cd $(MANUAL_UPLOAD_DIR) && tar xzf $(MANUAL_TAR_FILE) && ln -sf $(MANUAL_TAR_FILE) cairo-$(MANUAL_TAR_FILE)"
It'd be nifty if we could fold in similar logic, as well as the
auto-updating of the Downloads page on the website (which is currently
done manually for wayland).
> > Alternatively, maybe we would want the displayed docs to match current
> > git? If so, then maybe a cronjob would be in order?
> Hmm. That'd be almost like a CI service except it also pushes the docs.
> Daniel, suggestions?
 http://cgit.freedesktop.org/cairo/tree/RELEASING - step #6
More information about the wayland-devel