hawq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Radar Lei <r...@pivotal.io>
Subject Re: Transferring HAWQ Resources out of the Incubator
Date Thu, 30 Aug 2018 02:59:08 GMT
Thanks Roman's follow up. I drafted an unfinished checklist, please help to


   - 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.’.
   - 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
   - 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
      - 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.
      - Double-check that all of your lists have sufficient active
   - 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.


On Thu, Aug 30, 2018 at 8:06 AM, Roman Shaposhnik <roman@shaposhnik.org>

> Sorry for coming to this late (was on vacation) but what's left? I can
> definitely help cleaning up the incubator records, is there anything
> else?
> Thanks,
> Roman.
> On Tue, Aug 28, 2018 at 7:24 PM, Radar Lei <rlei@pivotal.io> wrote:
> > Hi HAWQ community,
> >
> > We have been graduated from incubator for a while, it's time to follow
> the
> > guide to clean all the graduation transfer processes. So it won't block
> our
> > routine works, e.g. release, vote new committers.
> >
> > We already made some progress to update related websites, but more
> actions
> > required to update other infrastructures, e.g. Chair register, code
> > repositories, links, mail lists, LDAP etc.
> >
> > Below guide can be a reference, please check:
> > https://incubator.apache.org/guides/transferring.html
> >
> > BTW, we would appreciate incubator mentors's comments if anything is not
> > covered here. Thanks.
> >
> > Regards,
> > Radar

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message