Page MenuHomekolab.org

How would you like to work with Cyrus IMAP Source Code Management repositories and Process Tooling?
Closed, ResolvedPublic1 Story Points

Description

Please see the parent T1 for a description of the problem space.

Two separate considerations;

  • With cloning the Cyrus IMAP repositories from their original locations over to our environment, pushes are not possible.

    Without cloning the Cyrus IMAP repositories from their original locations over to our environment, the branching policy is arbitrary and our copy would be incomplete (this is what we currently do).
  • Cyrus IMAP upstream also uses Phabricator, which would void auto-closing on branches that are upstream (i.e. a commit message with "Closes T4" cannot close T4).

Details

Ticket Type
Task

Event Timeline

vanmeeuwen updated the task description. (Show Details)
vanmeeuwen raised the priority of this task from to 60.
vanmeeuwen claimed this task.
vanmeeuwen added a subscriber: petersen.
vanmeeuwen set Ticket Type to Epic.Apr 13 2015, 10:55 PM
vanmeeuwen edited a custom field.
vanmeeuwen closed this task as Resolved.

We cooperate so closely with the upstream project (host Phabricator, host the email environment, release management), and therefore we need no separate GIT repository.

Tasks set against Cyrus IMAP here should just be worked on at the remote tracker, and be tracked here purely to remain on the radar.

vanmeeuwen changed Ticket Type from Epic to Task.Apr 13 2015, 10:58 PM
vanmeeuwen moved this task from Review to Done on the Sprint Process 201516 board.Apr 20 2015, 3:22 PM