Not logged in. · Lost password · Register

chronark
Member since Nov 2019
4 posts
Subject: git branches and release-candidates
Hello again,

1. Are we allowed to close merged branches or should be keep them around for grading purposes?
2. Can we delete the release-candidate tag after the real release?

Cheers,
Andreas
Maximilian Capraro
Member since Oct 2015
21 posts
Hi Chronark,

Thanks for you question and double-thanks for using the FSI forum!

In theory, you are allowed to use the git conventions that suit you best.

In practice, your coach will look at your git repo to grade you. So ideally you communicate your branching model etc. with the coach.

1. Are we allowed to close merged branches or should be keep them around for grading purposes?

You should never "squash" when merging branches and you should keep all the branches until the end of the project (because we want the individual contribution of every team member to always be visible). A good naming convention for branches can help you to keep an overview.


2. Can we delete the release-candidate tag after the real release?

Please leave it in so that the coach can see (and grade) that everything was properly tagged by the review and release manager.
chronark
Member since Nov 2019
4 posts
Alright thanks for clearing that up.

I'll talk to our coach and let him know as well.
Close Smaller – Larger + Reply to this post:
Verification code: VeriCode Please enter the word from the image into the text field below. (Type the letters only, lower case is okay.)
Smileys: :-) ;-) :-D :-p :blush: :cool: :rolleyes: :huh: :-/ <_< :-( :'( :#: :scared: 8-( :nuts: :-O
Special characters:
Go to forum
Datenschutz | Kontakt
Powered by the Unclassified NewsBoard software, 20150713-dev, © 2003-2011 by Yves Goergen