DOCSLIB.ORG

Gestión Del Proyecto Chromium

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Gestión Del Proyecto Chromium Gestión del proyecto Chromium Grupo 7 Evolución y Gestión de la Configuración (EGC) Tabla de control de versiones y cambios Descripción Nº de Autores Revisado Fecha de versión modificación Creación del documento 1.0 Jesús Díaz Sí 21/11/2013 Inserción del mapa de 1.1 Jesús Díaz Sí 28/11/2013 herramientas y creación de índice Integración de partes en el 1.2 Jesús Díaz No 03/12/2013 documento Integración de partes en el 1.3 Jesús Díaz No 03/12/2013 documento Gestión del código y ejercicios 1.4 David Romero, Sí 18/12/2013 Sergio Trigos Algunas correcciones 1.5 Jesús Díaz Sí 19/12/2013 Integración de partes faltantes 1.6 Daniel Platas Sí 22/12/2013 Finalización para versión 1.7 Daniel Platas Sí 23/12/2013 entregable Incluir hoja de cambios 1.8 Jesús Díaz Sí 21/01/2014 Integración de partes 1.9 Daniel Platas Sí 06/02/2014 corregidas y actualización 2.0 Versión Actual: 1.9 Tabla 1: Control de versiones y cambios del documento de memoria 2 ÍNDICE 1 Resumen ......................................................................................................................................................... 5 2 Introducción .................................................................................................................................................... 6 3 Gestión del código fuente ............................................................................................................................. 8 3.1 Ramas ...................................................................................................................................................... 9 3.2 Parches .................................................................................................................................................. 12 3.3 Gestión de los cambios en el código ................................................................................................. 12 3.4 Procesos a seguir para el cambio del código ................................................................................... 14 3.5 Estados por los que pasa el código .................................................................................................... 15 3.6 Políticas para descartar, fomentar o retardar un cambio .............................................................. 15 3.7 Roles en la gestión del código ............................................................................................................ 16 3.8 Políticas de nombres y estilo .............................................................................................................. 17 3.9 Ejercicios ................................................................................................................................................ 19 4 Gestión de la construcción ......................................................................................................................... 23 4.1 Cómo construir Chromium ................................................................................................................. 24 4.1.1 Obtener un el código fuente para la construcción .................................................................. 24 4.1.2 Crear ficheros de construcción .................................................................................................. 25 4.1.3 Construir Chrome ........................................................................................................................ 25 4.1.4 Construir Test ............................................................................................................................... 26 4.2 Resultados obtenidos .......................................................................................................................... 27 4.2.1 Modo Debug ................................................................................................................................. 27 4.2.2 Modo Release ............................................................................................................................... 27 4.3 Ejercicios ................................................................................................................................................ 27 5 Construcción e Integración continua ........................................................................................................ 32 5.1 Definición de BuildBot ......................................................................................................................... 35 5.2 Instalación de BuildBot ........................................................................................................................ 36 3 5.3 Ejercicios ................................................................................................................................................ 39 6 Gestión de entregables ............................................................................................................................... 43 6.1 Cómo se generan ................................................................................................................................. 43 6.2 Cómo se identifican ............................................................................................................................. 43 6.3 Cómo se gestiona la publicación ........................................................................................................ 44 6.4 Dónde se publican los entregables .................................................................................................... 45 6.5 Ejercicios ................................................................................................................................................ 45 7 Gestión del despliegue ................................................................................................................................ 46 7.1 Integración / despliegue continuos ................................................................................................... 46 7.2 Mecanismos y procesos de despliegue ............................................................................................. 48 7.3 Establecer los permisos (policy) ......................................................................................................... 50 8 Gestión de incidencias y depuración ........................................................................................................ 53 8.1 Gestión de incidencias ......................................................................................................................... 53 8.1.1 Estados posibles para una incidencia (bugs) ............................................................................ 54 8.1.2 Creación de una incidencia ......................................................................................................... 55 8.1.3 Resolución de una incidencia ..................................................................................................... 56 8.2 Mecanismos de depuración ................................................................................................................ 57 8.3 Ejercicios ................................................................................................................................................ 58 9 Gestión de la variabilidad ........................................................................................................................... 60 9.1 Modelo de variabilidad ........................................................................................................................ 60 9.2 Modelo de Características ................................................................................................................... 61 9.3 Ejercicio .................................................................................................................................................. 62 10 Mapa de herramientas ............................................................................................................................ 63 11 Conclusiones ............................................................................................................................................. 66 12 Anexos ........................................................................................................................................................ 66 4 1 RESUMEN Este documento refleja el estudio sobre la gestión de la configuración sobre el proyecto de software libre Chromium. En este proyecto podemos destacar diversos campos los cuales son explicados con profundidad a lo largo del texto. En la gestión del código podemos encontrar cual es la herramienta utilizada para el desarrollo del proyecto, concretamente git-svn, que utiliza en general las instrucciones de gestión de código de git, pero se integra con un servidor svn para el control de versiones. Después podemos observar en esta sección las diferentes categorías o papeles que poseen los diferentes responsables del proyecto como pueden ser Sheriff, Trooper o Gardener. También podremos encontrar unos ejercicios sobre la utilización de git-svn. El método seguido para la realización de cambios es una interacción entre el afectado, conocido como code owner y el reviewer que va a revisarlo. Esta interacción estará basada en una estructura pregunta-respuesta entre ambos individuos hasta que el reviewer dé el visto bueno al código. También encontraremos una descripción de cómo el reviewer depurará este código mediante
Load more

Recommended publications
  • ** OPEN SOURCE LIBRARIES USED in Tv.Verizon.Com/Watch
    ** OPEN SOURCE LIBRARIES USED IN tv.verizon.com/watch ------------------------------------------------------------ 02/27/2019 tv.verizon.com/watch uses Node.js 6.4 on the server side and React.js on the client- side. Both are Javascript frameworks. Below are the licenses and a list of the JS libraries being used. ** NODE.JS 6.4 ------------------------------------------------------------ https://github.com/nodejs/node/blob/master/LICENSE Node.js is licensed for use as follows: """ Copyright Node.js contributors. All rights reserved. Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE. """ This license applies to parts of Node.js originating from the https://github.com/joyent/node repository: """ Copyright Joyent, Inc. and other Node contributors.
    [Show full text]
  • Linux from Scratch 版本 R11.0-36-中⽂翻译版 发布于 2021 年 9 ⽉ 21 ⽇
    Linux From Scratch 版本 r11.0-36-中⽂翻译版 发布于 2021 年 9 ⽉ 21 ⽇ 由 Gerard Beekmans 原著 总编辑：Bruce Dubbs Linux From Scratch: 版本 r11.0-36-中⽂翻译版 : 发布于 2021 年 9 ⽉ 21 ⽇ 由 由 Gerard Beekmans 原著和总编辑：Bruce Dubbs 版权所有 © 1999-2021 Gerard Beekmans 版权所有 © 1999-2021, Gerard Beekmans 保留所有权利。 本书依照 Creative Commons License 许可证发布。 从本书中提取的计算机命令依照 MIT License 许可证发布。 Linux® 是Linus Torvalds 的注册商标。 Linux From Scratch - 版本 r11.0-36-中⽂翻译版 ⽬录 序⾔ .................................................................................................................................... viii i. 前⾔ ............................................................................................................................ viii ii. 本书⾯向的读者 ............................................................................................................ viii iii. LFS 的⽬标架构 ............................................................................................................ ix iv. 阅读本书需要的背景知识 ................................................................................................. ix v. LFS 和标准 ..................................................................................................................... x vi. 本书选择软件包的逻辑 .................................................................................................... xi vii. 排版约定 .................................................................................................................... xvi viii. 本书结构 .................................................................................................................
    [Show full text]
  • Project Skeleton for Scientific Software
    Computational Photonics Group Department of Electrical and Computer Engineering Technical University of Munich bertha: Project Skeleton for Scientific Software Michael Riesch , Tien Dat Nguyen , and Christian Jirauschek Department of Electrical and Computer Engineering, Technical University of Munich, Arcisstr. 21, 80333 Munich, Germany [email protected] Received: 10 December 2019 / Accepted: 04 March 2020 / Published: 23 March 2020 * Abstract — Science depends heavily on reliable and easy-to-use software packages, such as mathematical libraries or data analysis tools. Developing such packages requires a lot of effort, which is too often avoided due to the lack of funding or recognition. In order to reduce the efforts required to create sustainable software packages, we present a project skeleton that ensures the best software engineering practices from the start of a project, or serves as reference for existing projects. 1 Introduction In a recent essay in Nature [1], a familiar dilemma in science was addressed. On the one hand, science relies heavily on open-source software packages, such as libraries for mathematical operations, implementations of numerical methods, or data analysis tools. As a consequence, those software packages need to work reliably and should be easy to use. On the other hand, scientific software is notoriously underfunded and the required efforts are achieved as side projects or by the scientists working in their spare time. Indeed, a lot of effort has to be invested beyond the work on the actual implementation – which is typically a formidable challenge on its own. This becomes apparent from literature on software engineering in general (such as the influential “Pragmatic Programmer” [2]), and in scientific contexts in particular (e.g., [3–6]).
    [Show full text]
  • Node.Js Et Leap Drone
    UFR DES SCIENCES Node.js et Leap Drone Procédure d’installation et d’utilisation Jaleed RIAZ 12/13/2013 Ce document a pour but de vous pré senter la dé marche per mettant d’installer et utiliser le paquet Node Package Manager (NPM) et Node.js pour pouvoir interagir avec l’AR drone à l’aide du Leap motion. Sommaire Introdution .......................................................................................................................................... 2 Moteur V8 ....................................................................................................................................... 2 Le modèle non bloquant ................................................................................................................. 2 Procédure d’installation et d’utilisation du paquet ............................................................................ 3 Sous Windows ................................................................................................................................. 3 Sous Linux ........................................................................................................................................ 3 Sous Mac ......................................................................................................................................... 3 Leapdrone-master ............................................................................................................................... 4 Connexion en mode sécurisé WPA2 ..................................................................................................
    [Show full text]
  • Builder Documentation Release 3.26.0
    Builder Documentation Release 3.26.0 Christian Hergert, et al. Sep 13, 2017 Contents 1 Contents 3 1.1 Installation................................................3 1.1.1 via Flatpak...........................................3 1.1.1.1 Command Line....................................3 1.1.2 Local Flatpak Builds......................................4 1.1.3 via JHBuild...........................................4 1.1.3.1 Command Line....................................4 1.1.4 via Release Tarball.......................................5 1.1.5 Troubleshooting.........................................5 1.2 Exploring the Interface..........................................5 1.2.1 Project Greeter.........................................6 1.2.2 Workbench Window......................................6 1.2.3 Header Bar...........................................7 1.2.4 Switching Perspectives.....................................7 1.2.5 Showing and Hiding Panels...................................7 1.2.6 Build your Project........................................7 1.2.7 Editor..............................................9 1.2.8 Autocompletion......................................... 11 1.2.9 Documentation......................................... 11 1.2.10 Splitting Windows....................................... 12 1.2.11 Searching............................................ 14 1.2.12 Preferences........................................... 15 1.2.13 Command Bar.......................................... 16 1.2.14 Transfers...........................................
    [Show full text]
  • Oracle Communications Policy Management Licensing Information User Manual Release 12.5 Copyright © 2011, 2019, Oracle And/Or Its Affiliates
    Oracle® Communications Policy Management Licensing Information User Manual Release 12.5.1 F16918-02 October 2019 Oracle Communications Policy Management Licensing Information User Manual Release 12.5 Copyright © 2011, 2019, Oracle and/or its affiliates. All rights reserved. This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited. The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing. If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, then the following notice is applicable: U.S. GOVERNMENT END USERS: Oracle programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, delivered to U.S. Government end users are “commercial computer software” pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, shall be subject to license terms and license restrictions applicable to the programs.
    [Show full text]
  • (NASACFZ-1S2/Ot
    (NASACFZ-1s2/ot (1'AS-C-121~fPRELIMAINARY STUDY FOR A NUMERICAL AERODYNAMIC SIMULATION FACILITy. N78-19052 PHASE 1: EXTENSION Control Data Corp., St. Paul, Minn.) 434 p HC A19/MF A01 CSCL 01A Unclas G3/02 08630 PRELIMINARY STUDY FOR A NUMERICAL AERODYNAMIC SIMULATION FACILITY SUMMARY REPORT - PHASE 1 EXTENSION By: N. R. Lincoln FEBRUARY, 1978 Distribution of this report is provided in the interest of information exchang'e. Responsibility for the contents resides in the authors or organization that prepared it. Prepared under Contract No. NAS2-9457 by: CONTROL DATA CORPORATION Research and Advanced Design Laboratory 4290 Fernwood Street St. Paul, Minnesota 55112 for AMES RESEARCH CENTER NATIONAL AERONAUTICS AND SPACE ADMINISTRATION R EPVED ItA SI FACULWM SUMMARY REPORT - PHASE I EXTENSION Phase I of the NASF study which was completed in October 1977 produced several conclusions about the feasibility of construction of a flow model simulation facility. A computer structure was proposed for the Navier-Stokes Solver (NSS), now called the Flow Model Processor (FMP), along with technological and system approaches. Before such a system can enter an intensive design investigation phase several tasks must be accomplished to establish uniformity and control over the remaining design steps, as well as clarifying and amplifying certain portions of the conclusions drawn in Phase 1. In order of priority these were seen as: 1. Establishing a structure and format for documenting the design and implementation of the FMP facility. 2. Developing 'a complete, practically engineered design that would perform as claimed in the Phase 1 report. 3. Creating a design verification tool for NASA analysts, using a computerized simulation system.
    [Show full text]
  • Autotools: an Overview
    Autotools: An Overview Autotools: An Overview Danny Robson 2014-09-24 2014-09-24 Autotools: An Overview Danny Robson Overview Autotools autoconf Autotools: An Overview automake pkg-config Final Words Danny Robson 2014-09-24 Autotools: An Overview About Me Performance systems programming About Me C, C++ Linux GNU autotools Self-taught. Slowly. caveat emptor About Me Ask lots of questions 2014-09-24 Autotools: An Overview Danny Robson Overview Performance systems programming Autotools C, C++ autoconf Linux automake GNU pkg-config autotools Final Words Self-taught. Slowly. caveat emptor Ask lots of questions Autotools: An Overview About Me Performance systems programming About Me C, C++ Linux GNU autotools Self-taught. Slowly. caveat emptor About Me Ask lots of questions 2014-09-24 Autotools: An Overview Danny Robson Overview Performance systems programming Autotools C, C++ autoconf Linux automake GNU pkg-config autotools Final Words Self-taught. Slowly. caveat emptor Ask lots of questions Autotools: An Overview About Me Performance systems programming About Me C, C++ Linux GNU autotools Self-taught. Slowly. caveat emptor About Me Ask lots of questions 2014-09-24 Autotools: An Overview Danny Robson Overview Performance systems programming Autotools C, C++ autoconf Linux automake GNU pkg-config autotools Final Words Self-taught. Slowly. caveat emptor Ask lots of questions Autotools: An Overview What You're In For 1 Overview What You're In For 2 Autotools 3 autoconf What You're In For 4 automake 5 pkg-config 2014-09-24 6 Final Words Autotools:
    [Show full text]
  • Conan Documentation Release 1.3.3
    conan Documentation Release 1.3.3 conan Sep 24, 2021 CONTENTS 1 Upgrading to conan 1.0 3 1.1 Command line changes..........................................3 1.2 Deprecations/removals..........................................3 1.3 Settings and profiles. Gcc/CLang versioning..............................4 1.4 New features...............................................4 2 Introduction 5 2.1 Open Source...............................................5 2.2 Decentralized package manager.....................................5 2.3 Binary management...........................................6 2.4 Cross platform, build system agnostic..................................6 2.5 Stable...................................................7 3 Install 9 3.1 Install with pip (recommended).....................................9 3.2 Install from brew (OSX)......................................... 10 3.3 Install from AUR (Arch Linux)..................................... 10 3.4 Install the binaries............................................ 10 3.5 Initial configuration........................................... 10 3.6 Install from source............................................ 11 4 Getting started 13 4.1 A Timer using POCO libraries...................................... 13 4.2 Installing dependencies......................................... 14 4.3 Building the timer example....................................... 16 4.4 Inspecting dependencies......................................... 16 4.5 Searching packages........................................... 17 4.6 Building
    [Show full text]
  • EPICS How-Tos
    EPICS How-Tos Sep 10, 2021 Contents 1 Installation on Linux/UNIX/DARWIN (Mac)1 1.1 What is EPICS about?..........................................1 1.2 Prepare your system...........................................1 1.3 Install EPICS...............................................1 1.4 Test EPICS................................................2 1.5 Create a demo/test ioc to test ca and pva.................................3 1.6 Add the asyn package..........................................4 1.7 Install StreamDevice (by Dirk Zimoch, PSI)..............................5 2 Packages required for EPICS on Centos 87 2.1 Overview.................................................7 2.2 Packages required to build EPICS base.................................8 2.3 Packages required by the sequencer...................................8 2.4 Packages required by epics-modules/asyn................................8 2.5 Packages required by the Canberra and Amptek support in epics-modules/mca............8 2.6 Packages required by the Linux drivers in epics-modules/measComp.................8 2.7 Packages required by areaDetector/ADSupport/GraphicsMagick....................8 2.8 Packages required by areaDetector/ADEiger..............................9 2.9 Packages required to build aravis 7.0.2 for areaDetector/ADAravis...................9 2.10 Packages required to build areaDetector/ADVimba...........................9 2.11 Packages required to build EDM.....................................9 2.12 Packages required to build MEDM...................................9
    [Show full text]
  • Porting Guide
    Kunpeng BoostKit for Database Porting Guide Issue 05 Date 2021-06-30 HUAWEI TECHNOLOGIES CO., LTD. Copyright © Huawei Technologies Co., Ltd. 2021. All rights reserved. No part of this document may be reproduced or transmitted in any form or by any means without prior written consent of Huawei Technologies Co., Ltd. Trademarks and Permissions and other Huawei trademarks are trademarks of Huawei Technologies Co., Ltd. All other trademarks and trade names mentioned in this document are the property of their respective holders. Notice The purchased products, services and features are stipulated by the contract made between Huawei and the customer. All or part of the products, services and features described in this document may not be within the purchase scope or the usage scope. Unless otherwise specified in the contract, all statements, information, and recommendations in this document are provided "AS IS" without warranties, guarantees or representations of any kind, either express or implied. The information in this document is subject to change without notice. Every effort has been made in the preparation of this document to ensure accuracy of the contents, but all statements, information, and recommendations in this document do not constitute a warranty of any kind, express or implied. Issue 05 (2021-06-30) Copyright © Huawei Technologies Co., Ltd. i Kunpeng BoostKit for Database Porting Guide Contents Contents 1 MySQL 5.7.27 Porting Guide................................................................................................
    [Show full text]
  • Techniques and Challenges in Speech Synthesis Final Report for ELEC4840B
    Techniques and Challenges in Speech Synthesis Final Report for ELEC4840B David Ferris - 3109837 04/11/2016 A thesis submitted in partial fulfilment of the requirements for the degree of Bachelor of Engineering in Electrical Engineering at The University of Newcastle, Australia. Abstract The aim of this project was to develop and implement an English language Text-to-Speech synthesis system. This first involved an extensive study of the mechanisms of human speech production, a review of modern techniques in speech synthesis, and analysis of tests used to evaluate the effectiveness of synthesized speech. It was determined that a diphone synthesis system was the most effective choice for the scope of this project. A diphone synthesis system operates by concatenating sections of recorded human speech, with each section containing exactly one phonetic transition. By using a database that contains recordings of all possible phonetic transitions within a language, or diphones, a diphone synthesis system can produce any word by concatenating the correct diphone sequence. A method of automatically identifying and extracting diphones from prompted speech was designed, allowing for the creation of a diphone database by a speaker in less than 40 minutes. The Carnegie Mellon University Pronouncing Dictionary, or CMUdict, was used to determine the pronunciation of known words. A system for smoothing the transitions between diphone recordings was designed and implemented. CMUdict was then used to train a maximum-likelihood prediction system to determine the correct pronunciation of unknown English language alphabetic words. Using this, the system was able to find an identical or reasonably similar pronunciation for over 76% of the training set.
    [Show full text]