Skip to content

Branches - developers, read me! #7

@thibautjombart

Description

@thibautjombart

Permanent branches

master: functional devel version, meant to be used by people, so it should be relatively safe. Please do not push changes preventing the package from being installed or breaking backward compatibility unless this has been agreed on, and avoid warnings at all cost - we need travis's green light.
newfeatures: used for pushing changes that still need testing/checking; warnings are fine, but avoid pushing changes preventing the package from installing

Experimental changes

For experimental changes, the best course of action is fork the project and make a pull request when your patch is ready.
Other (unused) branches

roxygen2: was used for migrating the doc of the package to roxygen2 (was manual before); not fully integrated, migration is only partial at this stage. This is an old branch.
gh-pages: would be used for a website on github pages; not used at the mom

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions