[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
[emfcp-dev] Design Decisions
|
Hi,
during the last months, there has been a lot of communication among the
active committers via Skype, Mail or in person. While I am very happy
with the amount of communication, we did not do a very good job in
making this communication transparent for everybody. This is crucial for
mainly two reasons:
- Not everybody had the possibility to be informed about decisions and
things we work on.
- Decisions made are not well documented
I therefore propose the following rules effectively from today:
- Every Commit on the develop or a hotfix need to be related to a
Bugzilla and contain the number and title of the BugReport
- For feature branches, squash the commits and add the BR information to
the merge commit
- If you want to change the API or the architecture, create a BR
beforehand to give others the possibility to comment on this
- For all changes affecting the API or the architecture, capture the
reason for the change
- If you discuss changes online, capture the result and the reason for
the decision in a BR
If you have any comments about this, please use:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=411986
Regards
Jonas
