ox.releasator.1.0.1.source-code.changes.xsd Maven / Gradle / Ivy
Go to download
Show more of this group Show more artifacts with this name
Show all versions of releasator Show documentation
Show all versions of releasator Show documentation
Commandline utility for creating reproducible releases. Minimal parametrization, isolated sandbox for releases. Currently built on top of maven-release-plugin.
The newest version!
developer's notes about work on a software
configuration properties providing high level of customization for release components, while still keeping track of these options
lists known issues of the project; in effect, can serve as a poor man's issue-tracking system
changes that were implemented and will appear in the next release. This part is intended
for manual edits. Please do always add changes to the top.
unreleased changes in distribution - created from "unreleased" by the build tool
describes released version. Usually created by a script from "unreleased" element during
release
this information is typically filled automatically
timestamp of the release
free formated name of the person who initiated the release
information about storage in source code repository
identification of source code reposirory
path in the code repository at the time of development, starting with slash; for CVS, should be prefixed using
cvs2svn-like convention ("/trunk/...", "/branches/BRANCHNAME/...")
path in the code repository at the time of release, starting with slash; for CVS, should be prefixed using
cvs2svn-like convention ("/tags/TAGNAME/[path]")
type of version control, abbreviated; examples: "svn" (the implied default), "cvs", "git", "bzr", "hg", ...
the revision from which the release is initiated, i.e. before any commit to vcs
individual change items
change type. If not specified, indicates either incompatible change or a change
undetermined by migration heuristic
introduces a new feature in a way that does not hurt compatibility (note that
adding an interface method hurts!)
describes a bugfix, which either does not impact compatibility or brings the
behavior closer to what was requested/expected.
minor improvements and optimizations - something what keeps functionality
but gives it better quality
informs about something important - project abandoned, codebase moved,
identification changed etc.
corresponding JIRA issue id if any
name of the component or part relevant to this change
time of committing the change; should be entered by a tool, perhaps as part of a postcommit hook.
email of the person who found and reported the issue
email of the person who is either assigned to resolve the issue (in issues), or who really did it (in version)
How fast should this be done. Having a todo with priority "blocker" should
prevent the release tool from releasing production version.
The processing details of other levels should yet be specified; they may end up as configurable.
upgrade procedure for a specific (usually previous) version
steps that form a complete upgrade sequence
step type; good values are for instance: sql-script, shell-script, program
currently supported properties are: cmdline.maven.arguments (goes to cmdline), maven.* (goes to release.properties)
© 2015 - 2024 Weber Informatics LLC | Privacy Policy