Friends,
Where did the Maniphest Tasks go when the move to github was made?

I ask because the release notes for 2.5.X say:

   Make sure to read the Upgrading to Cyrus IMAP 2.5.0
   
<https://cyrusimap.org/imap/release-notes/2.5/x/2.5.0.html#imap-relnotes-2-5-0-upgrading>
   notes (all of them).

and those notes contain this:


         Cyrus IMAP Murder Topologies

   Environments that run a Cyrus IMAP Murder topology will want to
   upgrade their backends before they upgrade their frontends. See Task
   #16 <https://git.cyrus.foundation/T16> for details.

But the link for Task #16 is dead, still pointing to git.cyrus.foundation:

   glop:master$ grep -iR foundation cyrus-imapd/docsrc/
   cyrus-imapd/docsrc/imap/download/release-notes/2.5/x/2.5.0.rst:Please
   see https://git.cyrus.foundation/.
   cyrus-imapd/docsrc/conf.py:
   'task':('https://git.cyrus.foundation/T%s', 'Task #'),

I'd be happy to fix that, but am unclear as to where this information now lives.

Cheers,
    -nic

On 06/23/2016 06:37 PM, Bron Gondwana via Cyrus-devel wrote:
Hi all,

Phabricator is being deprecated.  The project is moving to github at:

https://github.com/cyrusimap/

I'm working on migrating all the bugs from bugzilla and phabricator to be 
github issues.  For now the website is still hosted at CMU.

One thing I'm doing is applying a "kill commit" to the top of the git 
repositories at the other locations.  This doesn't lose any history, you can just reset 
--hard HEAD^ to get back to the latest master commit - but it does discourage any further 
pushes of commits that get lost, because they won't merge or rebase very happily on top 
of the kill commit!

The kill commit contains a small README.txt which tells you how to update your 
git repository to point to the new location.

Cheers,

Bron.


--
Nic Bernstein                             n...@onlight.com
Onlight, Inc.                             www.onlight.com
6525 W Bluemound Road, Suite 24           v. 414.272.4477
Milwaukee, Wisconsin  53213-4073

<<attachment: nic.vcf>>

Reply via email to