Phabricator: All repositories registered - upcoming workflow changes

Ben Cooksley bcooksley at kde.org
Thu Feb 2 09:09:34 UTC 2017


Hi all,

As a starting point: keeping the software itself running is a
non-starting option from my perspective. It's going to be shutdown.
This is purely to reduce the amount of maintenance effort we have to
expend in keeping our systems running.

There is an enormous amount of software and other systems deployed on
our infrastructure, and the value of continuing to maintain software,
including associated security updates, major upgrades to ensure we're
able to continue running it on modern distributions, etc for something
which is no longer in active use is questionable at best. Bitrot and
decay is almost guaranteed to erode the value of it as a historical
archive in the long run in any case.

For those who dismiss decay as an issue - problems with previous
Reviewboard upgrades not taking cleanly have resulted in some reviews
being damaged, causing their diffs to become unavailable. These sorts
of problems do happen.

Whether some kind of read only archive is retained is another topic altogether.

Reviewboard has a WebAPI which should be usable by anyone interested
to extract all the information regarding reviews, including their
comments and the diff itself. This could be used to create a static
snapshot of each review.

Regards,
Ben


More information about the KDevelop-devel mailing list