Release Process and Responsibility
Installations and Configuration Names
| Hostname | Configname | WN | Description |
|---|---|---|---|
| etics.cern.ch | ETICS_R_x_y_z.a locked | >15 | Production Installation (prod): The officially released supported ETICS |
| eticsN.cern.ch | ETICS_R_x_y_z.a locked | (>=6) | Release Candidate Installation (rc): “Next” production, available for final certification & testing by selected users |
| etics-test.cern.ch | ETICS_R_x_y_z_RCn locked | >=6 | Integration Testing Installation (test): All the release candidates of the packages are tagged at project level and installed for integration tests |
| etics-int.cern.ch | ETICS_branch_x_y_z only comp locked/tagged | >=1 | continuous (nightly) integration environment = automated deployment of next RC |
| etics-dev.cern.ch | ETICS_DEV | >=1 | Development Installation (dev): A shared installation where developers can test their packages with the release candidates of other packages |
| etics-??? lxvm??? | ETICS_??? | >=1 | Individual Development (dev-...): Installations: developers or teams can instantiate they infrastructure, often in reduced scale for individual development and testing |
- How about parallel development (JRA1, JRA2, SA2) ?
Release Process
- A new release is decided (at the weekly) and a new org.etics config is created called etics-int- AA
- Withitn 24h - Each subsystem responsible (see table below) updates the configurations in the release attaching them to the project config.
- Passed 24h - the new release is build on the production and give a name for the RC- AA
- Once it builds it is then installed on etics-test - MZ
| Subsystem | Release Mgr |
|---|---|
| org.etics | AA |
| etics-adminsitration | AAR |
| etics-build-system | ADM |
| etics-data-model | LD |
| etics-deployment | MZ |
| etics-myetics | AAR |
| etics-nmi | LD |
| etics-plugins | ADM |
| etics-portal | AAR (+ PF) |
| etics-repository | LD |
| etics-utilities | ADM (+MZ) |
Release Announcements
- Alberto R.: Decides when is a good time for the release and let us know. Do not announce yet. The best would be Thursday lunch time
- A.Di Meglio: Prepares the Release notes and announcement.
- L.DIni:; Announces it at the EMT and ask agreement
- Alberto R.: Announces the down-time if the EMT agrees.
- Alberto R. (and Lorenzo if needed): Executed the release and migrations
- All: Test the new production with the few tests from web app and
- All: Update RSS Feed.
- Alberto R.: Announce that the service is back and sends the Release Notes.
Topic revision: r6 - 2010-02-15 - AlbertoRescoPerez
- ETICS Web
- ETICS Web Home
- Changes
- Index
- Search
- Support Knowledge Base
- ABATBEA
- ACPP
- ADCgroup
- AEGIS
- AfricaMap
- AgileInfrastructure
- ALICE
- AliceEbyE
- AliceSPD
- AliceSSD
- AliceTOF
- AliFemto
- ALPHA
- Altair
- ArdaGrid
- ASACUSA
- AthenaFCalTBAna
- Atlas
- AtlasLBNL
- AXIALPET
- CAE
- CALICE
- CDS
- CENF
- CERNSearch
- CLIC
- Cloud
- CloudServices
- CMS
- Controls
- CTA
- CvmFS
- DB
- DefaultWeb
- DESgroup
- DPHEP
- DM-LHC
- DSSGroup
- EGEE
- EgeePtf
- ELFms
- EMI
- ETICS
- FIOgroup
- FlukaTeam
- Frontier
- Gaudi
- GeneratorServices
- GuidesInfo
- HardwareLabs
- HCC
- HEPIX
- ILCBDSColl
- ILCTPC
- IMWG
- Inspire
- IPv6
- IT
- ItCommTeam
- ITCoord
- ITdeptTechForum
- ITDRP
- ITGT
- ITSDC
- LAr
- LCG
- LCGAAWorkbook
- Leade
- LHCAccess
- LHCAtHome
- LHCb
- LHCgas
- LHCONE
- LHCOPN
- LinuxSupport
- Main
- Medipix
- Messaging
- MPGD
- NA49
- NA61
- NA62
- NTOF
- Openlab
- PDBService
- Persistency
- PESgroup
- Plugins
- PSAccess
- PSBUpgrade
- R2Eproject
- RCTF
- RD42
- RFCond12
- RFLowLevel
- ROXIE
- Sandbox
- SocialActivities
- SPI
- SRMDev
- SSM
- Student
- SuperComputing
- Support
- SwfCatalogue
- TMVA
- TOTEM
- TWiki
- UNOSAT
- Virtualization
- VOBox
- WITCH
- XTCA
 |
|
Copyright &© 2008-2023 by the contributing authors. All material on this collaboration platform is the property of the contributing authors. or Ideas, requests, problems regarding TWiki? use Discourse or Send feedback