|
|
This page lists all necessary steps needed to migrate ISC DHCP to gitlab.
|
|
|
|
|
|
* [X] Create repository on gitlab, set access as internal
|
|
|
* [ ] Upload code to gitlab
|
|
|
* [ ] Review code in gitlab, make sure there is nothing confidential (such as branches or tags having customer names)
|
|
|
* [X] Create repository on gitlab, set access as internal.
|
|
|
* [X] Upload code to gitlab.
|
|
|
* [ ] Review code in gitlab, make sure there is nothing confidential (such as branches or tags having customer names).
|
|
|
* [ ] Decide whether we want to have gitlab issues. Most likely the answer will be yes, because with the intention to engage community more in the project, we need to have a process going. Having issues would be essential part of it.
|
|
|
* [ ] Decide if we want to migrate issues from RT. As of Jan 28, 2019, there are 637 open issues in RT. Many of them are confidential. We absolutely can't and shouldn't migrate all of them. We can consider migrating selected few, maybe dhcp-public (91 tickets) and/or dhcp-suggest (261 tickets)? Tomek's take on this would to be migrate only those few that are really useful.
|
|
|
* [ ] Create milestones representing upcoming releases.
|
|
|
* [ ] Create labels that reflect our process (Doing, Review) and components (client, server, relay, build, doc, omapi, failover, ddns, etc)
|
|
|
* [ ] Create labels that reflect our process (Doing, Review) and components (client, server, relay, build, doc, omapi, failover, ddns, etc).
|
|
|
* [ ] Set more appropriate logo for the project.
|
|
|
* [ ] Announce internally that we're moving to gitlab.
|
|
|
* [ ] Write README.md file.
|
|
|
* [ ] Switch the repo to public
|
|
|
* [ ] Enable github synchronization (we want mirror on github)
|
|
|
* [ ] send announcements to dhcp-users
|
|
|
* [ ] Switch the repo to public.
|
|
|
* [ ] Enable github synchronization (we want mirror on github).
|
|
|
* [ ] send announcements to dhcp-users.
|
|
|
|
|
|
|