Feature #6276
Migrate the website to its own Git repository
Status:
Rejected
Priority:
Normal
Assignee:
intrigeri
Category:
Infrastructure
Target version:
Start date:
2013-09-11
Due date:
% Done:
0%
Description
Subtasks
History
#1 Updated by intrigeri 2013-09-11 13:27:34
- Type of work changed from Sysadmin to Code
#2 Updated by intrigeri 2014-04-07 08:42:13
- Category set to Infrastructure
- Assignee set to intrigeri
- Target version set to Sustainability_M1
#3 Updated by intrigeri 2014-07-10 14:30:02
- Type of work changed from Code to Discuss
#4 Updated by sajolida 2014-08-02 15:44:54
- Status changed from Confirmed to Rejected
We discussed this informally during the summit again several times, and there were main arguments against, so I think that this is not open for discussion anymore unless something big changes our minds.
#5 Updated by intrigeri 2014-08-02 16:57:10
For the record, my main arguments were:
- It is entirely wrong that, as given as a reason to do this work on the parent ticket, “We’ve never taken advantage of mixing website with sources, so we only experience the disadvantages of it”. We do take advantage of this by writing and adjusting end-user and design documentation in topic branches, which allow everything to be merged at the same time without any need for manual synchronization.
- We have found no good solution (see Feature #7036) to keep in sync’ the main repo with other repositories whose content is needed at ISO build time. We’ll need to find such a solution at some point, but in the meantime, splitting the website Git repo would make things worse in this area.
#6 Updated by intrigeri 2014-08-02 16:57:25
- blocked by deleted (
Feature #6277: Rewrite the tails-live.git history