| Anonymous | Login | 2024-04-25 05:41 MDT |
| Main | My View | View Issues | Change Log | Roadmap | Repositories |
| View Revisions: Issue #4632 | [ Back to Issue ] | ||
| Summary | 0004632: Move fast-updates repo to Koji/mirror system | ||
| Revision | 2015-08-26 15:09 by user2 | ||
| Description | The clearos-bootstrap repo exists to get around limitations of the build system. The repo will no longer be required once the following limitations have been removed: - Ability to upload upstream tarballs (e.g. dropbox binaries) to the build system. - Ability to update *all* mirrors on demand to deploy emergency fixes. - Improved repo update time. Waiting half a day for a repo change is painful - the SDN/Marketplace repos are fully up-to-date every hour (and on demand). |
||
| Revision | 2015-09-02 16:16 by user2 | ||
| Description | The clearos-bootstrap repo exists to get around limitations of the build and mirror systems. The repo will no longer be required once the following limitations have been removed: - Ability to upload upstream tarballs (e.g. dropbox binaries) to the build system. - Ability to update *all* mirrors on demand to deploy emergency fixes. - Improved repo update time. Waiting half a day for a repo change is painful - the SDN/Marketplace repos are fully up-to-date every hour (and on demand). - At least 2 developers (primary, backup) must be able to understand and fix build/mirror issues. In the past, we have had to wait on a single person for critical path issues. That's not sustainable. |
||
| Revision | 2015-09-02 16:24 by user2 | ||
| Description | The clearos-bootstrap repo exists to get around limitations of the build and mirror systems. The repo will no longer be required once the following limitations have been removed: - Ability to upload upstream tarballs (e.g. dropbox binaries) to the build system. - Ability to update *all* mirrors on demand to deploy emergency fixes. - Improved repo update time. Waiting half a day for a repo change is painful - the SDN/Marketplace repos are fully up-to-date every hour (and on demand). - At least 2 developers (primary, backup) must be able to understand and fix build/mirror issues. In the past, we have had to wait on a single person for critical path issues. That's not sustainable. Note: a speedy update repo was also discussed in the CentOS project. Details here: https://lists.centos.org/pipermail/centos-devel/2015-February/012718.html [^] |
||