New URL for NEMO forge!   http://forge.nemo-ocean.eu

Since March 2022 along with NEMO 4.2 release, the code development moved to a self-hosted GitLab.
This present forge is now archived and remained online for history.
#2015 (ENHANCE-06 Repository cleaning (previously 2018WP)) – NEMO

Opened 6 years ago

Last modified 3 years ago

#2015 assigned Task

ENHANCE-06 Repository cleaning (previously 2018WP)

Reported by: nicolasmartin Owned by: ayoung
Priority: low Milestone: Unscheduled
Component: env Version: trunk
Severity: minor Keywords: SVN,
Cc: acc, clevy

Description

Context

The way we use the repository has getting worse over years as we have stopped to follow the best practices.
A repository should constantly evolved and would just reflect the ongoing work, then it should be easy to find inside the official releases without difficulties.
Instead we have one which is full of all developments done since the code has been put under version control, even the official releases are hidden in the middle of the development branches.

In addition to not deleting dev branches after merging, we have lost in particularly a clever organisation of the repository.
Each branch newly created add 1 Go to the repository and the vast majority of the duplicate code will not be modified (outside CONFIG and NEMO).
As a result, the repository has grown to a huge size (~130 Go !) that prevents the developers to be able to work with a entire working copy (~ 1 hour for downloading and endless updates).

Implementation plan

The goal is to recover a proper state of the repository along with a new trunk structure, that tends to minimize the unnecessary copies by taking out the dependencies development.
It will not delete the history of the repository but the tree structure of the repository for further revisions starting from this cleaning.
Each item could be recovered by updating/downloading selected revision.

The first part of the action could be lead quickly, it is mainly a cleaning of '/branches' and '/tags' repository paths with a move of the official releases to '/tags' and several additions of files at the trunk root.

The second part is much more intrusive with a vast reorganisation of the trunk which includes many moves to /vendors path, mergers and renaming of directories.
The best moment for doing this would be between the release of 4.0 and the beginning of the new developments in order to have the same organisation in every development branch.

Commit History (1)

ChangesetAuthorTimeChangeLog
9596nicolasmartin2018-05-15T17:51:07+02:00

Reorganisation plan for NEMO repository: preliminary implementation of the new trunk structure (ref #2015)

  • Deletion of useless 1st level, add new explicit names for folders
  • Extract dev tools (SETTE and Trusting) to /utils/CI
  • Extract figures folder from documentation to /utils/figures
  • Extrac TEST_CASES to /utils/test_cases
  • Move ./TOOLS/COMPILE to ./mk
  • Add few wiki files at the root: README, INSTALL and LICENSE with full text of CeCILL v2.0
  • Style: uppercase for wiki files, lowercase for folder names

Additionally, inclusion of routines renaming in NST: agrif_si3 -> agrif_ice

Change History (13)

comment:1 Changed 6 years ago by nicolasmartin

  • Priority changed from low to high

comment:2 Changed 6 years ago by nicolasmartin

  • Milestone changed from 2018 WP to 2018 release-4.0

comment:3 Changed 6 years ago by nicolasmartin

  • Summary changed from ENHANCE-10 Repository cleaning to ENHANCE-11 Repository cleaning

comment:4 Changed 5 years ago by nicolasmartin

In 9596:

Error: Failed to load processor CommitTicketReference
No macro or processor named 'CommitTicketReference' found

comment:5 Changed 5 years ago by nicolasmartin

  • Milestone changed from 2018 release-4.0 to 2018 WP
  • Priority changed from high to low
  • wp_comment set to British branches remained to be moved to the new repositroy layout (/branches -> /NEMO/branches)

comment:6 Changed 5 years ago by nemo

  • Status changed from new to assigned

comment:7 Changed 5 years ago by nicolasmartin

  • branch_review set to pending
  • wp_comment changed from British branches remained to be moved to the new repositroy layout (/branches -> /NEMO/branches) to British branches remained to be moved to the new repository path (/branches -> /NEMO/branches)

comment:8 Changed 5 years ago by nicolasmartin

  • Component changed from OCE to env
  • Milestone changed from 2018 WP to 2019 WP
  • Summary changed from ENHANCE-11 Repository cleaning to ENHANCE-06(2018WP) Repository cleaning
  • wp_comment changed from British branches remained to be moved to the new repository path (/branches -> /NEMO/branches) to Wait for British fully appropriation of the new repository layout to complete the cleaning (dev. branches transferred from `/branches` to `/NEMO/branches`)

comment:9 Changed 5 years ago by nicolasmartin

  • Summary changed from ENHANCE-06(2018WP) Repository cleaning to ENHANCE-06 Repository cleaning (peviously 2018WP)

comment:10 Changed 5 years ago by nemo

  • Priority changed from low to high

comment:11 Changed 4 years ago by nicolasmartin

  • branch_review changed from pending to passed
  • Milestone changed from 2019 WP to Unscheduled
  • Priority changed from high to low
  • Summary changed from ENHANCE-06 Repository cleaning (peviously 2018WP) to ENHANCE-06 Repository cleaning (previously 2018WP)

Switch to Unscheduled milestone for triage, action completion is still waiting for the final cleaning of branches/.

comment:12 Changed 3 years ago by nicolasmartin

  • Cc acc added
  • Owner changed from nicolasmartin to ayoung

Is there any concrete progress within the Met Office and NERC in order to put an end to this reorganisation of the SVN repo that dates back now to almost 4 years?

At least, could you please resume the removal of unnecessary branches? NERC bchs and UKMO bchs

Last edited 3 years ago by nicolasmartin (previous) (diff)

comment:13 Changed 3 years ago by nicolasmartin

  • Cc clevy added
Note: See TracTickets for help on using tickets.