Page MenuHomePhabricator

Release: start adding changerequests
Changes PlannedPublic

Authored by avivey on Dec 9 2016, 10:16 PM.
Referenced Files
Unknown Object (File)
Mon, Mar 13, 11:16 AM
Unknown Object (File)
Wed, Mar 8, 8:51 PM
Unknown Object (File)
Sun, Feb 26, 11:18 PM
Unknown Object (File)
Feb 22 2023, 11:58 AM
Unknown Object (File)
Feb 22 2023, 9:32 AM
Unknown Object (File)
Feb 16 2023, 6:24 AM
Unknown Object (File)
Feb 13 2023, 10:37 PM
Unknown Object (File)
Feb 9 2023, 11:35 PM


Group Reviewers
Blessed Reviewers
Test Plan


Diff Detail

rP Phabricator
Lint Errors
Errorsrc/applications/release/ReleaseRenderEventListener.php:43XHP5Use of Undeclared Variable
Warningresources/sql/autopatches/20161220.release.changes.sql:CHMOD1Invalid Executable
Warningsrc/applications/release/OPEN_QUESTIONS:11TXT3Line Too Long
Warningsrc/applications/release/controller/ReleaseChangeRequestFromRevisionController.php:60TXT3Line Too Long
Warningsrc/applications/release/controller/ReleaseChangeRequestFromRevisionController.php:63TXT3Line Too Long
Warningsrc/applications/release/controller/ReleaseChangeRequestFromRevisionController.php:66TXT3Line Too Long
Warningsrc/applications/release/controller/ReleaseChangeRequestFromRevisionController.php:67TXT3Line Too Long
Warningsrc/applications/release/controller/ReleaseChangeRequestFromRevisionController.php:69TXT3Line Too Long
Warningsrc/applications/release/controller/ReleaseChangeRequestFromRevisionController.php:72TXT3Line Too Long
Warningsrc/applications/release/controller/ReleaseChangeRequestFromRevisionController.php:84TXT3Line Too Long
Warningsrc/applications/release/phid/ReleaseChangeRequestPHIDType.php:CHMOD1Invalid Executable
Warningsrc/applications/release/phid/ReleaseChangeRequestPHIDType.php:32TXT3Line Too Long
Advicesrc/applications/release/changes/ReleaseChangeRequestImplementation.php:26XHP16TODO Comment
Advicesrc/applications/release/changes/actions/ReleaseChangeRequestAction.php:31XHP16TODO Comment
Advicesrc/applications/release/conduit/ReleaseReleaseEditConduitAPIMethod.php:7XHP16TODO Comment
Advicesrc/applications/release/controller/ReleaseChangeRequestFromRevisionController.php:22XHP16TODO Comment
Advicesrc/applications/release/controller/ReleaseChangeRequestFromRevisionController.php:92XHP16TODO Comment
Advicesrc/applications/release/controller/ReleaseReleaseDetailsController.php:102XHP16TODO Comment
Advicesrc/applications/release/editor/ReleaseChangeRequestEditEngine.php:62XHP16TODO Comment
Advicesrc/applications/release/editor/ReleaseChangeRequestEditor.php:53XHP16TODO Comment
Advicesrc/applications/release/editor/ReleaseChangeRequestEditor.php:69XHP16TODO Comment
Advicesrc/applications/release/query/ReleaseChangeRequestQuery.php:50XHP16TODO Comment
Advicesrc/applications/release/query/ReleaseChangeRequestQuery.php:55XHP16TODO Comment
Advicesrc/applications/release/query/ReleaseChangeRequestQuery.php:106XHP16TODO Comment
Advicesrc/applications/release/query/ReleaseChangeRequestQuery.php:129XHP16TODO Comment
Tests Passed
Build Status
Buildable 15405
Build 20294: Run Core Tests
Build 20293: arc lint + arc unit

Event Timeline

avivey retitled this revision from to Release: start adding changerequests.
avivey updated this object.
avivey edited the test plan for this revision. (Show Details)
avivey edited edge metadata.
  • wip still

Editing, Actions, Controller, List All.

  • $release->canAcceptChangeRequests()
  • conduit .edit, .search methods
  • db migrations
  • custom fields

@epriestley: When you have a chance, I've gathered some mostly-technical questions that I'd like your input on:

  • expandTransaction: Because I decided to implement "custom actions" using transactions (P2009), I ended up having xactions that are shown on the timeline ("avive has frozen this release"), but their actual work is been handled by another xaction ("CloseBranchTransaction"). expandTransaction is how the old transaction code handled this, but it didn't make it to the modular code. Should I just find a new way to do it?
  • What kind of Edges do we need? RepositoryInRelease, ObjectRequestedAsChangeForRelease, ChangeRequestInRelease, ?
  • Should Change Request have their own policy, subscribers, comments, etc.?
  • Transactions Metadata: That one didn't make the cut for modular-transactions either. For the case of "Updates on CR show up on the Release page", they would be very useful. Do we hate it?
  • In Releeph, there's a "want" status, that's corresponds to Differential's Accept, and distinct from "Pull" status. Is that an important enough feature to include as first-class? Is there a way to include something like that (A user->value mapping) as a Custom Field?
  • EditEngine::buildCustomEditFields(): Why don't we move the field definitions into the *TransactionType classes, and then use reflection to implement this method? It looks like there's a 1-1 relation between fields and xaction types.

Check policy when requesting a new change