From: Neal Caidin <ncaidin@linuxfoundation.org>
To: cip-members@lists.cip-project.org,
cip-board@lists.cip-project.org,
cip-security@lists.cip-project.org,
cip-dev@lists.cip-project.org
Subject: [cip-dev] Update - Re: April 6 cutover from Mailman2 to Group.io
Date: Wed, 25 Mar 2020 12:33:56 -0400 [thread overview]
Message-ID: <CAODMxsJ3UzAghVfLpHQ1eiizowpWUi0q5WvYxtSOYbKi36TdEw@mail.gmail.com> (raw)
In-Reply-To: <CAODMxsLOOk7EZwoUgd5fNpXpOoR16ZunzZe0W6nL5NrLN2JWSw@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 1394 bytes --]
Dear CIP community,
I have learned more information about the cutover plans. The migration is
planned to start at 2 pm Pacific time on April 6, which is :
5 pm Eastern / 11 pm CET / and Tuesday, April 7 , 6 am JST
The migration will probably take just a few hours, but the migration team
would like to reserve 24 hours in case they run into any issues with
transferring the archives into the new system.
I'll send more information about the migration as I learn more and as we
get closer to the conversion date.
Thanks for your patience and understanding.
Best regards,
Neal
*Neal Caidin*
Program Manager, Program Management & Operations
The Linux Foundation
+1 (919) 238-9104 (w/h)
+1 (919) 949-1861 (m)
ncaidin@linuxfoundation.org
On Thu, Mar 12, 2020 at 3:50 PM Neal Caidin <ncaidin@linuxfoundation.org>
wrote:
> [x-posted]
> Dear CIP community,
>
> These Mailman2 email lists will be converted starting on Monday, April 6
> and may take up to 24 hours to complete.
>
> There is no action required on your part.
>
> Any emails that are sent during the downtime will be queued up and come
> through when the system is up and running.
>
> Please let me know if you have any questions.
>
> Best regards,
> Neal
>
> *Neal Caidin*
> Program Manager, Program Management & Operations
> The Linux Foundation
> +1 (919) 238-9104 (w/h)
> +1 (919) 949-1861 (m)
> ncaidin@linuxfoundation.org
>
[-- Attachment #1.2: Type: text/html, Size: 3576 bytes --]
[-- Attachment #2: Type: text/plain, Size: 154 bytes --]
_______________________________________________
cip-dev mailing list
cip-dev@lists.cip-project.org
https://lists.cip-project.org/mailman/listinfo/cip-dev
prev parent reply other threads:[~2020-03-25 16:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-12 19:50 [cip-dev] April 6 cutover from Mailman2 to Group.io Neal Caidin
2020-03-25 16:33 ` Neal Caidin [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAODMxsJ3UzAghVfLpHQ1eiizowpWUi0q5WvYxtSOYbKi36TdEw@mail.gmail.com \
--to=ncaidin@linuxfoundation.org \
--cc=cip-board@lists.cip-project.org \
--cc=cip-dev@lists.cip-project.org \
--cc=cip-members@lists.cip-project.org \
--cc=cip-security@lists.cip-project.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).