Change Details

//This task was created with the Sprint app as the main use case, but the solution must be equally applicable to any local patches.// Sprint is an experimental stage application with issues that is undergoing rapid development and attempting to accommodate the needs of a variety of uses. A regular testing, review and deployment plan should be implemented to facilitate the continuous integration of Sprint with Phabricator main. There is an important bug fix that has been sitting in Gerrit since 11 December with no action. (https://gerrit.wikimedia.org/r/#/c/179155/). A hotfix like this could and should have been handled promptly. If it is a question of concern about "making a bad situation worse", this is absolutely not the case with T78208. This is a very simple problem with an easy solution. Any reluctance to merge this change is not warranted. However, thorough code review is always appropriate. Furthermore, Sprint is now at 0.6.1.9, and the additional patches will absolutely improve the user experience and address some of the key problems noted in the first go. When or if these changes will be merged is clearly not at the discretion of the developer, but with the maintainers of the production instance. I encourage those responsible to take this task to task. Adding more details. We should develop a Zuul like interface and system for phabricator. The reasons are it made it easy to add mutiple jobs to one project. Also made it easy to view what tests are running for what project. It also supported spreading it across the nodes. It also allowed us to have a repo where users could submit patches for the tests they wanted and someone from releng reviewed them which made everything easy and open sourced. In phabricator none of this is possible. Zuul also had an easy view in the web browser whereas phabricators builds did not.

//This task was created with the Sprint app as the main use case, but the solution must be equally applicable to any local patches.// Sprint is an experimental stage application with issues that is undergoing rapid development and attempting to accommodate the needs of a variety of uses. A regular testing, review and deployment plan should be implemented to facilitate the continuous integration of Sprint with Phabricator main. There is an important bug fix that has been sitting in Gerrit since 11 December with no action. (https://gerrit.wikimedia.org/r/#/c/179155/). A hotfix like this could and should have been handled promptly. If it is a question of concern about "making a bad situation worse", this is absolutely not the case with T78208. This is a very simple problem with an easy solution. Any reluctance to merge this change is not warranted. However, thorough code review is always appropriate. Furthermore, Sprint is now at 0.6.1.9, and the additional patches will absolutely improve the user experience and address some of the key problems noted in the first go. When or if these changes will be merged is clearly not at the discretion of the developer, but with the maintainers of the production instance. I encourage those responsible to take this task to task.

//This task was created with the Sprint app as the main use case, but the solution must be equally applicable to any local patches.// Sprint is an experimental stage application with issues that is undergoing rapid development and attempting to accommodate the needs of a variety of uses. A regular testing, review and deployment plan should be implemented to facilitate the continuous integration of Sprint with Phabricator main. There is an important bug fix that has been sitting in Gerrit since 11 December with no action. (https://gerrit.wikimedia.org/r/#/c/179155/). A hotfix like this could and should have been handled promptly. If it is a question of concern about "making a bad situation worse", this is absolutely not the case with T78208. This is a very simple problem with an easy solution. Any reluctance to merge this change is not warranted. However, thorough code review is always appropriate. Furthermore, Sprint is now at 0.6.1.9, and the additional patches will absolutely improve the user experience and address some of the key problems noted in the first go. When or if these changes will be merged is clearly not at the discretion of the developer, but with the maintainers of the production instance. I encourage those responsible to take this task to task. Adding more details. We should develop a Zuul like interface and system for phabricator. The reasons are it made it easy to add mutiple jobs to one project. Also made it easy to view what tests are running for what project. It also supported spreading it across the nodes. It also allowed us to have a repo where users could submit patches for the tests they wanted and someone from releng reviewed them which made everything easy and open sourced. In phabricator none of this is possible. Zuul also had an easy view in the web browser whereas phabricators builds did not.