Opened 4 years ago

Closed 4 years ago

#49 closed task (fixed)

Solve the different DVCS mess

Reported by: borja Owned by: borja
Priority: critical Milestone: OpenWorkouts 0.2
Component: infraestructure Keywords:
Cc:

Description

So, we started working on the project using darcs as the DVCS for the repos. Then we created a git so some people could work on the project and personally I even considered a third option (mercurial as I do prefer that over the other 2).

This lead to a big mess when trying to keep the repos in sync, plus a big headache to me and a not-very-productive discussion about what to do.

So, BDFL style, I decided to go on with:

  • use git as the DVCS tool (for now)
  • keep the repos in our openworkouts server
  • keep using trac for web access to the repos + tickets/tasks/milestones
  • have a mirror in github, with a very big WARNING telling users where the main development and repos goes (trac+git on our server)

I'm not fond of git, but right now this is what we will do.

So, for this ticket, we have to:

  • remove/delete darcs and mercurial repos
  • put the main git repo (under repos/git/OpenWorkouts-current) into repos/OpenWorkouts
  • remove the third-party darcs plugin from trac (as this allows us to update trac to the most recent versions)
  • update docs, scripts, tickets, etc to point to the git repo

Change History (3)

comment:1 Changed 4 years ago by borja

  • Milestone changed from OpenWorkouts 0.1 to OpenWorkouts 0.2

comment:2 Changed 4 years ago by borja

  • Owner set to borja
  • Status changed from new to accepted

comment:3 Changed 4 years ago by borja

  • Resolution set to fixed
  • Status changed from accepted to closed

Done with the changes on trac.

Removed the mercurial repos, I've kept the darcs repos around for history purposes, they are still accessible through darcs get.

The docs have been updated too and I'll keep repos/git/OpenWorkouts-current as the main repo for now.

Note: See TracTickets for help on using tickets.