If you think a bug might affect users in the 57 release, please set the correct tracking and status flags for Release Management.

Followup to consolidation of relengapi blueprints

RESOLVED FIXED

Status

Release Engineering
General
RESOLVED FIXED
2 years ago
2 years ago

People

(Reporter: dustin, Assigned: dustin)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Assignee)

Description

2 years ago
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
(Assignee)

Comment 1

2 years ago
neato! https://github-issue-mover.appspot.com/
(Assignee)

Comment 2

2 years ago
> * 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
(Assignee)

Comment 3

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

> * add a review checklist
  DONE

> * update docs for creating new blueprints
  DONE
(Assignee)

Comment 4

2 years ago
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
(Assignee)

Updated

2 years ago
Flags: needinfo?(bugspam.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....
(Assignee)

Comment 6

2 years ago
I made blueprint-specific labels.  Is that enough?
we're done here.
Status: NEW → RESOLVED
Last Resolved: 2 years ago
Flags: needinfo?(bugspam.Callek)
Resolution: --- → FIXED
(Assignee)

Comment 8

2 years ago
I pushed the "gone fishin'" commit to slaveloan.  I doubt there's anything pointing to the slaveloan repo, though -- should we just remove it?
You need to log in before you can comment on or make changes to this bug.