Feature #8616

Decide when, how, and who shall delete obsolete Git branches

Added by intrigeri 2015-01-09 12:55:12 . Updated 2015-05-04 07:37:34 .

Status:
Resolved
Priority:
Normal
Assignee:
Dr_Whax
Category:
Infrastructure
Target version:
Start date:
2015-01-09
Due date:
2015-02-25
% Done:

100%

Feature Branch:
Type of work:
Research
Starter:
Affected tool:
Deliverable for:

Description

e.g. post-release? post-merge? once a year? the release manager? the sysadmin team? What kind of privileges are needed to do that?


Subtasks


History

#1 Updated by intrigeri 2015-01-09 12:55:42

  • Target version set to Sustainability_M1

#2 Updated by intrigeri 2015-01-09 13:49:00

#3 Updated by intrigeri 2015-01-09 14:03:18

  • Target version changed from Sustainability_M1 to Tails_1.3.2

#4 Updated by Dr_Whax 2015-02-21 12:36:51

  • Blueprint set to https://tails.boum.org/blueprint/delete_obsolete_Git_branches/

#5 Updated by intrigeri 2015-02-21 14:11:36

  • Status changed from Confirmed to In Progress

#6 Updated by Dr_Whax 2015-02-23 14:01:54

  • Due date set to 2015-02-25

#7 Updated by intrigeri 2015-02-24 23:14:30

  • % Done changed from 0 to 20

A proposal was sent to -dev@ 4 days ago: <54E88FD2.3080900@useotrproject.org>

#8 Updated by intrigeri 2015-03-17 16:22:42

What’s the status here?

#9 Updated by anonym 2015-04-10 12:22:20

This ticket still has the 1.3.2 milestone. Please postpone it as you see fit.

#10 Updated by intrigeri 2015-04-14 13:03:35

  • Target version changed from Tails_1.3.2 to Tails_1.4.1

#11 Updated by intrigeri 2015-05-04 07:37:34

  • Status changed from In Progress to Resolved
  • Target version changed from Tails_1.4.1 to Tails_1.4
  • % Done changed from 20 to 100

I’ve reviewed the discussion and the blueprint, and I think we’re done.