New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Move FCPs to feature branches and use issues #487

Open
t-sommer opened this Issue Nov 7, 2018 · 2 comments

Comments

Projects
None yet
2 participants
@t-sommer
Collaborator

t-sommer commented Nov 7, 2018

The FCP documents contain a lot of valuable information that is closely related to the development that happens on the feature/* branches.

Can we move them to the respective feature branches once the working group agrees that they're mature enough?

See also #304.

@andreas-junghanns

This comment has been minimized.

Contributor

andreas-junghanns commented Nov 7, 2018

I see no real alternative. Do you?

@t-sommer

This comment has been minimized.

Collaborator

t-sommer commented Nov 7, 2018

We should also use issues (with the label FCP) to track the FCPs. That way we can easily reference them in other issues. The current FCP-XXX numbering (with all the stale FCPs) in the fmi-design repo is confusing.

@t-sommer t-sommer changed the title from Move FCPs to feature branches to Move FCPs to feature branches and use issues Nov 7, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment