The current mechanism for publishing the website is quite convoluted. As you point out, the software and the website are only loosely coupled. I see only good outcomes for allowing the repos to reflect that reality.
On Thu, Feb 16, 2017 at 4:10 PM, Karen Miller <kmil...@apache.org> wrote: > I think that the website content that is currently in geode/geode-site > ought to be moved to its own repository. The driving reason for this is > that changes to the website occur on a different schedule than code > releases. We often want to add a new committer's name or a new > event, and these items are not associated with sw releases. A new website > release that comes from the develop branch may have commits that > should not yet be made public. > > Are there downsides to separating the website content into its own repo? >
