Re: 389-ds Migration to GitHub - [2020-09-12 - 2020-09-13]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi team,
so everything is an order and ready.

Today at 3 pm EDT we disable Pagure notifications and I start the migration process.

On Saturday, after I clone all of the issues and PRs and close Pagure issues, I'll put 389-ds-base issue tracker on 'read-only' mode.
And during Saturday-Sunday I'll update all related Bugzillas with new Devel Whiteboard issue numbers and links.

And finally, on Sunday, I'll recheck that everything is in order and I'll open the new repo to the public (and I'll post the update in this mail thread).

P.S. in case, you'll get some unwanted email notifications (you should really not), I apologize for all inconvenience.

Sincerely,
Simon

On Wed, Sep 9, 2020 at 1:48 PM Simon Pichugin <spichugi@xxxxxxxxxx> wrote:
Thanks!
 
So, the final look is ready, please, check:

The migration project that can be used by other teams:

Issues:

Pull requests can be found by filtering labels (I've created them as issues so we can store all of the valuable discussions that were held there):

The pull requests that were open on the moment of migration (you can download the code from the last comment) are here:

Milestones:

Tags and releases:

The updated Bugzillas will look like this (I've changed Devel Whiteboard and added the link to Links table):

Pagure issues and PRs will be closed and each of them will have the message similar to this:
The code:

So. please, check and we can move on this weekend if everything is good.

Sincerely,
Simon

On Tue, Sep 8, 2020 at 8:21 PM Simon Pichugin <spichugi@xxxxxxxxxx> wrote:
Hi team,
for the last couple of weeks, I was working on the migration tool that will allow us to switch 389-ds project to GitHub.

It will be done through the weekend 2020-09-12 - 2020-09-13.

I was testing it on a custom repo for some time but, please, review the code, if you would like to:

I will open the example 389-ds-base [migrated] repo tomorrow when my final run will finish.

I've managed to disable Github notifications but there are two more things that should be taken into the account:

1. Pagure notifications - as Viktor has suggested, probably, we can ask Pierre-Yves Chibon <pingou@pingoured.fr> to do this for us at Friday.

2. Bugzilla notifications. It may be that it's not possible to disable it for everyone involved. In that case, it will be one time thing that will spam you with 3000 emails. :) But I hope not.

Regards,
Simon


_______________________________________________
389-devel mailing list -- 389-devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to 389-devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/389-devel@xxxxxxxxxxxxxxxxxxxxxxx

[Index of Archives]     [Fedora Directory Announce]     [Fedora Users]     [Older Fedora Users Mail]     [Fedora Advisory Board]     [Fedora Security]     [Fedora Devel Java]     [Fedora Desktop]     [ATA RAID]     [Fedora Marketing]     [Fedora Mentors]     [Fedora Package Review]     [Fedora Art]     [Fedora Music]     [Fedora Packaging]     [CentOS]     [Fedora SELinux]     [Big List of Linux Books]     [KDE Users]     [Fedora Art]     [Fedora Docs]

  Powered by Linux