trafodion-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Steve Varnau <steve.var...@esgyn.com>
Subject RE: [DISCUSS] Documentation Versioning
Date Wed, 06 Jul 2016 22:29:27 GMT
Gunnar,

Yes, that makes sense to me.

Either that, or the docs could use only the major/minor numbers of the
release -- at least for the directory path where to generate the docs.  We
probably want the update number in the docs, but only want one version per
minor release.

docs/${TRAFODION_VER_MAJOR}.${TRAFODION_VER_MINOR}

--Steve


> -----Original Message-----
> From: Gunnar Tapper [mailto:tapper.gunnar@gmail.com]
> Sent: Wednesday, July 6, 2016 3:09 PM
> To: dev@trafodion.incubator.apache.org
> Subject: [DISCUSS] Documentation Versioning
>
> Hi,
>
> I noticed that Steve 2.0.x header for the documentation. I think this is
> preferable.
>
> However, I know that we want to move to a model where the documentation
> update is part of the release rather than done against the master post
> release.
>
> The current scheme is that we place documentation in a latest directory as
> well as a versioned directory. This means that you have to; for example,
> build 2.0.x documents setting $TRAFODION_VER to "2.0.0" to ensure that the
> documents are placed on the correct versioned directory. The result will
> be
> that the version-dependent documents are placed in
> http://trafodion.apache.org/docs/2.0.0/*.
>
> Moving forward, I think it'd be better if we create a $DOCS_VER or
> something like that to allow for dot releases without having to create dot
> releases of the documentation.
>
> Thoughts?
>
> --
> Thanks,
>
> Gunnar
> *If you think you can you can, if you think you can't you're right.*

Mime
View raw message