Code Review / releng / global-jjb.git / commit
? search:
summary | shortlog | log | commit | commitdiff | review | tree
(parent: 59ef2e7) | patch
Standardize "release" wording 38/16038/5
authorJessica Wagantall <jwagantall@linuxfoundation.org>
Fri, 28 Jun 2019 22:14:52 +0000 (15:14 -0700)
committerJessica Wagantall <jwagantall@linuxfoundation.org>
Tue, 9 Jul 2019 23:02:56 +0000 (16:02 -0700)
commite5e453e0f83977caaedf121ba9c0456d0702acdb
tree95d809886813ee5756e38f60d1521019ff8e14a2tree | snapshot
parent59ef2e78b9af7977117c06f154ed5faf92adff6fcommit | diff
Standardize "release" wording

Using "releases" and "release" in different places
is becoming a little confusing. Standardize to "release"
to match lftools command and the majority of the exisiting
wording.
Using "releases" for the list of tech team releases does
makes sense to be kept that way, for example:
releases/1.1.1.yaml

Issue: RELENG-2131
Change-Id: I9a9a548947cc1acbe3e61bb8fa6532a89fb17e16
Signed-off-by: Jessica Wagantall <jwagantall@linuxfoundation.org>
.jjb-test/lf-release-jobs.yaml diff | blob | history
docs/jjb/lf-macros.rst diff | blob | history
docs/jjb/lf-release-jobs.rst diff | blob | history
jjb/lf-macros.yaml diff | blob | history
jjb/lf-release-job-groups.yaml diff | blob | history
jjb/lf-release-jobs.yaml diff | blob | history
releasenotes/notes/standardize_release_version_job-81eb03ef2c798827.yaml [new file with mode: 0644] blob
Global Jenkins Job Builder templates