Skip to content

Conversation

@pietro909
Copy link

Several things have changed in the last 10 months:

  • we use Jira rather than Redmine
  • GitLab is used for reviewing and merging
  • the main branch is now next

Copy link

@pmodin pmodin left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Also, s/jira/JIRA/gi

Good thing you went through this document, let's discuss further.

**Title and Description guidelines** section.
Set no label, this will be done by someone else.
Set no assignee, unless you've been asked to.
9. Set label "Ready for review".
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is on a per project basis. The projects I mostly work in, for example, we consider all MRs as ready for review unless labeled as WIP.

Set no label, this will be done by someone else.
Set no assignee, unless you've been asked to.
9. Set label "Ready for review".
10. Assign it to another developer.
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is also on a per project basis

### Closing a merge request
When the reviewer considers the code ready to merge, he'll say so, and a label
with the name `ready-to-merge` will be applied, indicating that the branch is
with the name `Ready for release` will be applied, indicating that the branch is
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is also a per-project convention, nowadays. Good find.

@pietro909
Copy link
Author

pietro909 commented Mar 12, 2017

I think that at this point we need to split the documentation per project, keeping the common procedures in these documents.

@pmodin
Copy link

pmodin commented Mar 12, 2017

Agreed, let's have a workshop 😃

@miono
Copy link

miono commented Mar 31, 2017

why am i still able to comment here??? remove me.

@jeltz
Copy link

jeltz commented Mar 31, 2017

While removing Markus, you could also remove me as well.

@pmodin
Copy link

pmodin commented Apr 4, 2017

@miono @jeltz It's a public repository, if you don't want to be notified you can unfollow it 😸


## Branches
1. Branch `master` contains the latest stable release
1. Branch `next` contains the latest stable release
Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

still master branch for deployment

Master is no longer the main branch and branches are never deleted
Pietro Grandi added 2 commits April 4, 2017 15:42
References to Jira, new labels, and new branch to be used.
@pietro909
Copy link
Author

pietro909 commented Apr 21, 2017

@pmodin it would be nice to close this PR at the latest by May 1st since later I might not have access to this repo anymore 😸

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants