Bug #16401

release_process: insufficient git fetch?

Added by CyrilBrulebois 2019-01-29 10:13:14 . Updated 2019-02-13 08:28:53 .

Status:
Resolved
Priority:
Normal
Assignee:
Category:
Target version:
Start date:
2019-01-29
Due date:
% Done:

100%

Feature Branch:
Type of work:
Contributors documentation
Blueprint:

Starter:
Affected tool:
Deliverable for:

Description

Spotted during the 3.12 release process, in the Prepare upgrade-description files section: we have two such constructs (non-final vs. final) →

cd ${MASTER_CHECKOUT:?} && \
git fetch && \
[…]
git push origin master:master

The git fetch doesn’t help much, as any remote changes aren’t taken into account. We should probably add git rebase origin/master?

(I had spotted it during previous releases, but that wasn’t a practical issue; with the delays during 3.12, that became an issue.)


Subtasks


History

#1 Updated by anonym 2019-01-29 18:15:39

  • Status changed from Confirmed to In Progress

Applied in changeset commit:tails|c1c2a95596563e47ff54f9bf6b5816a3a8422504.

#2 Updated by anonym 2019-02-13 08:28:53

  • Status changed from In Progress to Resolved
  • Assignee deleted (anonym)
  • Target version set to Tails_3.12.1
  • % Done changed from 0 to 100
  • QA Check set to Pass