1171004 - Followup to consolidation of relengapi blueprints

Status: RESOLVED FIXED

(Release Engineering :: General, defect)

Description

[Dustin J. Mitchell [:dustin] (he/him)]

I just merged
  https://github.com/mozilla/build-relengapi/pull/235
and now it's time for some followup:

* copy all issues from the other repos into relengapi, with backlinks
* add mapper docs (from https://wiki.mozilla.org/ReleaseEngineering/Applications/Mapper)
* add a review checklist
  * documentation for any changes
    * for the correct audience -- usage (API users), deployment (ops), development (contributors)
  * good test coverage
  * no imports between blueprints
  * "core" (relengapi.lib) should be generic and broadly useful
* wind down the tooltool, clobberer, mapper, and slaveloan repos
  * delete contents, replace with a README
  * disable Travis
  * close all issues
  * for tooltool, leave tooltool.py et al.
  * wait for callek to merge his latest patch to slaveloan first
* delete relengapi-skeleton repo
* update docs for creating new blueprints
  * don't use skeleton
  * add to blueprints list in relengapi.app

Comment 1

[Dustin J. Mitchell [:dustin] (he/him)]

neato! https://github-issue-mover.appspot.com/

Comment 2

[Dustin J. Mitchell [:dustin] (he/him)]

> * copy all issues from the other repos into relengapi, with backlinks
  DONE

> * add mapper docs (from https://wiki.mozilla.org/ReleaseEngineering/Applications/Mapper)
> * add a review checklist
>   * documentation for any changes
>     * for the correct audience -- usage (API users), deployment (ops), development (contributors)
>   * good test coverage
>   * no imports between blueprints
>   * "core" (relengapi.lib) should be generic and broadly useful
> * wind down the tooltool, clobberer, mapper, and slaveloan repos
>   * delete contents, replace with a README
      DONE for everything but slaveloan

>   * disable Travis
      DONE for everything but slaveloan

>   * close all issues
      DONE and copied to relengapi, with labels

>   * wait for callek to merge his latest patch to slaveloan first
      waiting :)

> * delete relengapi-skeleton repo
  DONE (I just replaced it with a README)

> * update docs for creating new blueprints
>   * don't use skeleton
>   * add to blueprints list in relengapi.app

Comment 3

[Dustin J. Mitchell [:dustin] (he/him)]

https://github.com/mozilla/build-relengapi/pull/277

> * add a review checklist
  DONE

> * update docs for creating new blueprints
  DONE

Comment 4

[Dustin J. Mitchell [:dustin] (he/him)]

https://github.com/mozilla/build-relengapi/pull/278

> * add mapper docs (from https://wiki.mozilla.org/ReleaseEngineering/Applications/Mapper)
  DONE

So all that remains is

>   * wait for callek to merge his latest patch to slaveloan first

Comment 5

[Justin Wood (:Callek)]

(In reply to Dustin J. Mitchell [:dustin] from comment #4)
> https://github.com/mozilla/build-relengapi/pull/278
> 
> > * add mapper docs (from https://wiki.mozilla.org/ReleaseEngineering/Applications/Mapper)
>   DONE
> 
> So all that remains is
> 

Actually there is one more minor item I forgot to put here (in time for your "I'm done" feeling)

* Labeling all relengapi "core" issues as "core", to differentiate between "slaveloan" and related blueprints.


> >   * wait for callek to merge his latest patch to slaveloan first

I'm still working on this, since I want to finish it out....

Comment 6

[Dustin J. Mitchell [:dustin] (he/him)]

I made blueprint-specific labels.  Is that enough?

Comment 7

[Justin Wood (:Callek)]

we're done here.

Comment 8

[Dustin J. Mitchell [:dustin] (he/him)]

I pushed the "gone fishin'" commit to slaveloan.  I doubt there's anything pointing to the slaveloan repo, though -- should we just remove it?