I’m definitely open to improving the process such that we can have version-specific documentation, and finding a way to automate updating the asf-site branch during the release process. I’m also okay if that process is somewhat manual.
I’ve thought about it a little but haven’t really come with a process. Ideally we’d do something that would do a snapshot of the docs at release time and create a subdirectory in the asf-site website (e.g. “1.0.0-docs”). I’m open to suggestions. -Taylor > On Jan 22, 2016, at 4:25 PM, Kyle Nusbaum <[email protected]> > wrote: > > The new website is awesome. > > Tt would be great to keep tabs on documentation for different versions of > Storm and host those different versions on the site. > > I don't care too much for having all the documentation in its own branch. I > would suggest that each version branch of Storm keeps its own version of the > docs -- or keeps any modifications to the docs, if not the entire collection, > in order to keep the common parts in sync -- and that these docs get merged > into the asf-site branch in their own version directory as part of the > release process. > Please let me know what you think and I'll file Jira issues as necessary.-- > Kyle
signature.asc
Description: Message signed with OpenPGP using GPGMail
