In my opinion, a better place for such guidance would be in some “project best practices” wiki. The release train checklist is already so long that many projects routinely ignore many of its items. It would be a more effective checklist, if it was pruned down to absolute “must have or you get kicked off the train” items. Everything else arguable isn’t a release train concern and belongs somewhere else as general guidance.
- Konstantin
From: cross-project-issues-dev-bounces@xxxxxxxxxxx [mailto:cross-project-issues-dev-bounces@xxxxxxxxxxx] On Behalf Of Mickael Istria
Sent: Friday, December 07, 2012 7:38 AM
To: Cross project issues
Subject: [cross-project-issues-dev] Suggested SHOULD HAVE for release train
Hi all,
I'd like to suggest the following SHOULD HAVE for the release train requirements check list:
Explicit Target Platform Definiton
Project should provide a definition of their dependencies as one (or several) target definition file(s). These files should be promoted on the Contribution Guide as a way for contributors to ensure they are using the right dependencies for the project, and this target definition should also be used at build-time to ensure project doesn't have some unexpected dependencies.
These files should contain the strict necessary dependencies for the project to compile and execute. It's recommended setting includeSources attribute to true in .target files to provide to developers access to sources of the dependencies, when available, in their development environment (PDE) without effort; for Tycho builds, this attribute is ignored and does not add sources to the build target-platform.
Project could maintain several target defintions, for example to match several version of Eclipse.
WDYT?
