Thanks Roman's comments. Now an INFRA ticket is created: INFRA-16970.
Regards, Radar On Thu, Aug 30, 2018 at 12:10 PM, Roman Shaposhnik <[email protected]> wrote: > On Wed, Aug 29, 2018 at 7:59 PM, Radar Lei <[email protected]> wrote: > > Thanks Roman's follow up. I drafted an unfinished checklist, please help > to > > check. > > > > > > *Checklist:* > > > > - Need Lei to confirm the progress: > > - The secretary will inform the new chair. Once appointed, the new > > Chair needs to finish a checklist which including ‘Work with the > Apache > > Infrastructure team to set up the top level project > infrastructure.’. > > That has happened. > > > - Source > > - Git repositories will be renamed to drop the incubator- prefix, > please > > ensure that developers change their remotes. After you’ve created > the TLP > > request, request the rename. > > - Update site, jenkins, wikis, pom.xml and other resources to point > > to the new repository location. > > > > - Mailing lists > > All of this just needs to be INFRA JIRAs -- anyone from the project > can file them. > > > - Members of the new PMC need to: - Subscribe to the private mailing > > list for the project, if they weren’t already subscribed from > their PPMC > > days > > - Update mail addresses including: > > - confluence commit messages (see adminstration documentation) > > - issue tracking messages (see administration documentation) > > - The chair should have karma to perform these tasks. > > Again -- I don't think this is chair specific. JIRA, for example, has a few > of PMC members with admin karma. > > > - Double-check that all of your lists have sufficient active > > moderators. > > - Issue Tracking > > - Ask infra to move the podling to its own top level category in JIRA. > > - Distribution mirrors: Raise an infra ticket to create your dist area > > and move your Incubator dist area to the new location. > > Again -- INFRA tickets. So just start filing away ;-) > > Thanks, > Roman. >
