Difference between revisions of "ESciDoc CoreService Upgrade"
Jump to navigation
Jump to search
(New page: =Core service adoption/upgrade procedure at MPDL= ==Pre-requisites for adoption of new core-service== *latest core-service (decision by dev team if we work with build or RC candidate) d...) |
|||
| Line 8: | Line 8: | ||
**bug/reports should be forwarded to FIZ | **bug/reports should be forwarded to FIZ | ||
**solution/service developments allowed only for interface changes | **solution/service developments allowed only for interface changes | ||
*no green light from MPDL side until solutions (latest releases) are running stable | *no green light from MPDL side until solutions (latest releases) are running stable | ||
*time proposed: focused team max 10 - 15 days | |||
==Pre-requisites for stable core service== | ==Pre-requisites for stable core service== | ||
Revision as of 15:27, 16 March 2010
Core service adoption/upgrade procedure at MPDL[edit]
Pre-requisites for adoption of new core-service[edit]
- latest core-service (decision by dev team if we work with build or RC candidate)
deployed always on latest-coreservice.mpdl.mpg.de (already exists, practice a bit abandoned?)
- latest released solutions/code should be run against the latest core-service
- bug/reports should be forwarded to FIZ
- solution/service developments allowed only for interface changes
- no green light from MPDL side until solutions (latest releases) are running stable
- time proposed: focused team max 10 - 15 days
Pre-requisites for stable core service[edit]
- feedback from solution developments
- agree on "stable"
- already existing features work properly
- bugs reported in previous versions do not appear again
- performance is not affected in negative manner
- agree on "stable"