Skip to content

Create branch for latest release #25

@ChemicalXandco

Description

@ChemicalXandco

I highly recommend that documentation be managed properly regarding how to update the documentation if the changes do not apply to the release version of meshroom. I suggest that here should be 2 versions of the documentation: release and develop. This way the documentation can be updated with the new features and changes before they are in the release version while also having the correct documentation for the current release. Corrections and improvements should target the release branch and then it will also be merged into the develop branch, possibly by using Nightly Merge github action for example. Documentation of new features/changes should target only the develop branch.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions