summaryrefslogtreecommitdiffstats
path: root/releases/fraser
AgeCommit message (Collapse)AuthorFilesLines
2018-06-29Publish Functest 6.2.0 tagsCédric Ollivier1-0/+6
Change-Id: Ieef2d00e57af2c06f588f4f819b9eaf402830a07 Signed-off-by: Cédric Ollivier <cedric.ollivier@orange.com>
2018-06-28tagging compass4nfv Fraser 6.2 releaseHarry Huang1-0/+7
JIRA: - check ip_forward and set to 1 Change-Id: I23f8757339a0433d79d0973366be2db15c6760a3 Signed-off-by: Harry Huang <huangxiangyu5@huawei.com>
2018-06-25Doctor Fraser opnfv-6.2.0Tomi Juvonen1-0/+4
Change-Id: I9f61914d3c07ca52e9b062110a2d0036090b3626 Signed-off-by: Tomi Juvonen <tomi.juvonen@nokia.com>
2018-05-29updated commit for Auto 6.1.1Gerard Damm1-0/+4
Cherry-picked 3 changes from latest master, to stable/fraser merged these 3 changes into stable/fraser new commit ID: 0f43563624832c5908e6fc00eb0a4bbc6cc82c33 will need to be tagged as 6.1.1 patch#2: removed trailing spaces Change-Id: I934dedb6c0b1efde2404f550cbd1a58e618ffc1a Signed-off-by: Gerard Damm <gerard.damm@wipro.com>
2018-05-26Projects did not fill out their releases/fraser/Aric Gardner14-0/+48
This is the patchset of projects that did not fill out their releases fraser file. I have done it for them. some of the projects had no changes on the fraser branch in this case I put the tag in the same place as the 6.0.0 tag some project I am familliar with and I move the tag to the head of fraser for them, Ideally team leads will do this work in the future We will update the tagging instructions accordingly. Change-Id: I1b2c7a8b6e63bc857192757e25f2d103c2629319 Signed-off-by: Aric Gardner <agardner@linuxfoundation.org>
2018-05-26Merge "updated auto.yaml with 6.1.0 commit"Aric Gardner1-0/+4
2018-05-26updated auto.yaml with 6.1.0 commitGerard Damm1-0/+4
master commit to use for 6.1.0: b718a43380376d2b19222c4203c97a95ca849ae8 (note: opnfv-6.1.0 tag: 553ea71b7aa2eb7d9ff46316de367dff0844ce42) (can/should a tag objet ID be used for a point release ?) updated stable/fraser SHA1, to same SHA1 that was used for 6.0.0 (i.e. 3a957a75f99686767d13f45d74b5ca8463559b7b) (I assume stable/fraser SHA1 should be the same as 6.0.0 SHA1 ?) >The stable ref is the ref when the branch was created, it should not >change (cherry-picking for stable/fraser is not possible after 6.0.0 is released) >You can cherry pick as long as you want. Change-Id: I887174801a56b374cae0197b31561673bc0435ea Signed-off-by: Gerard Damm <gerard.damm@wipro.com>
2018-05-26Merge "Doctor Fraser opnfv-6.1.0"Aric Gardner1-0/+4
2018-05-26Merge "Tagging IPv6 stable/fraser branch for Fraser 6.1.0"Aric Gardner1-0/+5
2018-05-26Merge "Tagging SampleVNF stable/fraser branch for Fraser 6.1.0"Aric Gardner1-0/+3
2018-05-26Merge "Publish Functest opnfv-6.1.0 tags"Aric Gardner1-0/+6
2018-05-26Merge "Prepare for 6.1.0"Aric Gardner1-0/+4
2018-05-26Merge "Apex: Ready for Fraser SR1"Aric Gardner1-0/+12
2018-05-26Merge "modified for fraser 6.1.0 release"Aric Gardner1-0/+4
2018-05-26Merge "Prepare for Clover 6.1.0"Aric Gardner1-0/+3
2018-05-26Merge "[yardstick] fraser opnfv-6.1.0 release tag"Aric Gardner1-0/+3
2018-05-26Merge "tagging compass4nfv Fraser 6.1 release"Aric Gardner1-0/+7
2018-05-26[release] Fuel, Armband: Release opnfv-6.1.0Alexandru Avadanii2-0/+6
Change-Id: I7ec0b1d9b40d12500eaf0f82e2e8035c488d1437 Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
2018-05-25Verify and Create Tags from Release FileTrevor Bramwell1-0/+0
Updates the releases verify and merge jobs to check release files for the following: - commits exist - commits are on stable-branch If both of these criteria are met and the patch is merged, the repos will be tagged at the specified commits and pushed. If a repo has already been tagged but not on stable-branch the job will not exit, but will warn that the commit doesn't exist on the correct branch. This is because tags should never be removed. This adds an additional script 'repos.py' that provides an quick interface for pulling out information from release files, along with the script 'release-status.sh' for checking the status of tags. NOTE: The branch creation script has been disabled until it can be reworked. Change-Id: I498bc74f20aa50d2bd321771f20a77905b246399 Signed-off-by: Trevor Bramwell <tbramwell@linuxfoundation.org>
2018-05-26tagging compass4nfv Fraser 6.1 releasechigang1-0/+7
JIRA:- fix 3 neutron trunk testcases failure in functest Change-Id: Ie3cd55c3aac1b6e1104054b3ab666056efa83b5b Signed-off-by: chigang <chigang@huawei.com>
2018-05-25Prepare for Clover 6.1.0Stephen Wong1-0/+3
Change-Id: I885f40ca8ac1c076b8443f03ca99a975d4edc82e Signed-off-by: Stephen Wong <stephen.kf.wong@gmail.com>
2018-05-25modified for fraser 6.1.0 releaseNarinder Gupta1-0/+4
Change-Id: Ibdb9bba605fd7deccf184010085cb14cc2805b59
2018-05-25[yardstick] fraser opnfv-6.1.0 release tagRoss Brattain1-0/+3
Change-Id: Ife8ee87db45381678c44ebd80adf08658bd697f5 Signed-off-by: Ross Brattain <ross.b.brattain@intel.com>
2018-05-25Apex: Ready for Fraser SR1Tim Rozet1-0/+12
Change-Id: Ib59491210da3996fe59885635481b22fd84d1af2 Signed-off-by: Tim Rozet <trozet@redhat.com>
2018-05-25Prepare for 6.1.0Manuel Buil1-0/+4
Change-Id: I1282caa29b6c2a1fe67ec80f090a0acc1d4f24ce Signed-off-by: Manuel Buil <mbuil@suse.com>
2018-05-25Tagging SampleVNF stable/fraser branch for Fraser 6.1.0Deepak S1-0/+3
Change-Id: I6312e57c689519bdf65a562db85acfb343ac7b68 Signed-off-by: Deepak S <deepak.s@linux.intel.com>
2018-05-24Tagging IPv6 stable/fraser branch for Fraser 6.1.0Bin Hu1-0/+5
Change-Id: I5212e57c689519bdf65a562db85acfb343ac7b68 Signed-off-by: Bin Hu <bh526r@att.com>
2018-05-23Publish Functest opnfv-6.1.0 tagsCédric Ollivier1-0/+6
Change-Id: If1f9d8c961d976e21c5fd6354a712027a6591e96 Signed-off-by: Cédric Ollivier <cedric.ollivier@orange.com>
2018-05-23Doctor Fraser opnfv-6.1.0Tomi Juvonen1-0/+4
Change-Id: Ib09b9b919ca046532931fed551d7a6f7aa1857c1 Signed-off-by: Tomi Juvonen <tomi.juvonen@nokia.com>
2018-04-30Add release notes in releases/fraser/functest.yamlCédric Ollivier1-0/+2
Change-Id: I0384563e5e663ea485626562df5ee49815b95817 Signed-off-by: Cédric Ollivier <cedric.ollivier@orange.com>
2018-04-28Merge "Tag SDNVPN for Fraser 6.0"Aric Gardner1-0/+5
2018-04-28Merge "Tag Stor4NFV for Fraser 6.0"Aric Gardner1-0/+7
2018-04-28Merge "Update Clover tags Clover for Fraser 6.0.1"Aric Gardner1-0/+3
2018-04-28Tag OPNFVDocs for Fraser 6.0Trevor Bramwell1-0/+5
This is tagged at the last merged docs patch to stable/fraser Change-Id: I0d976cd947621ceab3a15df8ea98bdc245fe93fc Signed-off-by: Trevor Bramwell <tbramwell@linuxfoundation.org>
2018-04-28Merge "Fraser 6.0.0 tag"Trevor Bramwell1-0/+5
2018-04-28Merge "Fraser 6.0.0 tag"Trevor Bramwell1-0/+5
2018-04-28Merge "Fraser 6.0.0 tag"Trevor Bramwell1-0/+5
2018-04-28Tag Apex for Fraser 6.0agardner1-0/+14
The last commit I had to revert, as the refs were put under branches branch should never change and indicates where the branching happens. I have taken those refs and put them in the releases section Change-Id: I8026b331b18cde18c08ed1bef79d291c3a7ffce8 Signed-off-by: agardner <agardner@linuxfoundation.org>
2018-04-28Revert "Apex: update sha commit hashes for Fraser"Aric Gardner1-4/+4
This reverts commit 583c715b4c5320bdd6e0b09b68af852d8660dc14. Change-Id: I63c99606804c4c02b1e8aff91937c62916137bc9
2018-04-28Update Clover tags Clover for Fraser 6.0.1Trevor Bramwell1-0/+3
Add the opnfv-6.0.1 to the current commit, and lists opnfv-6.0.0 as being tagged on the previous one. Change-Id: I01b3efb6fe04b3dcf32ef2c01315ecb34fb30133 Signed-off-by: Trevor Bramwell <tbramwell@linuxfoundation.org>
2018-04-27Apex: update sha commit hashes for FraserTim Rozet1-4/+4
Change-Id: Ic3cb135911eddc4490a50e57f5165688cec623a0 Signed-off-by: Tim Rozet <trozet@redhat.com>
2018-04-27Update Clover 6.0.0 release SHA1Stephen Wong1-1/+1
Change-Id: I28c584535617afb32801f912adafe5282aa64ed1 Signed-off-by: Stephen Wong <stephen.kf.wong@gmail.com>
2018-04-27Tag SDNVPN for Fraser 6.0Trevor Bramwell1-0/+5
This is tagged at the current tip of stable/fraser branch Change-Id: Ie169aa7e2ef7096155253aeb5c8adeeefc2cf278 Signed-off-by: Trevor Bramwell <tbramwell@linuxfoundation.org>
2018-04-27Tag Stor4NFV for Fraser 6.0Trevor Bramwell1-0/+7
Include link to release notes Change-Id: Ic9b8ed9d08fd54f00bf4afe9539f32fae9339e23 Signed-off-by: Trevor Bramwell <tbramwell@linuxfoundation.org>
2018-04-27Fraser 6.0.0 tagagardner1-0/+5
I have tagged your repo for you at the head of the fraser branch Please let us know if this is correct. If I dont hear back from you I will merge this and tag your repo at this location Change-Id: Ie9ee3b17d5f909b0160cbacd7db99a43385c3d7d Signed-off-by: agardner <agardner@linuxfoundation.org>
2018-04-27Fraser 6.0.0 tagagardner1-0/+5
I have tagged your repo for you at the head of the fraser branch Please let us know if this is correct. If I dont hear back from you I will merge this and tag your repo at this location Change-Id: I66541b703924018ca7d81a736a1af8767c100846 Signed-off-by: agardner <agardner@linuxfoundation.org>
2018-04-27Fraser 6.0.0 tagagardner1-0/+5
I have tagged your repo for you at the head of the fraser branch Please let us know if this is correct. If I dont hear back from you I will merge this and tag your repo at this location Change-Id: I9223da8139ce997e6b7dde9db30a875324c0b94f Signed-off-by: agardner <agardner@linuxfoundation.org>
2018-04-27Merge "Update Parser Fraser 6.0.1 Release Tag"Trevor Bramwell1-0/+3
2018-04-27Functest 6.0.0 release SHA1agardner1-0/+8
Change-Id: Ieaa5b8050da3f502074d7f968c4cf65a108f84c2 Signed-off-by: agardner <agardner@linuxfoundation.org>
2018-04-27Update Parser Fraser 6.0.1 Release TagTrevor Bramwell1-0/+3
opnfv-6.0.0 was previously tagged on the master branch, but the ref to be release is on stable/fraser. So bumping the tag to 6.0.1 and adding the previous tag at the correct ref to the file. Change-Id: Ic57fd2116e8662391748455cfe25c23e9853b65d Signed-off-by: Trevor Bramwell <tbramwell@linuxfoundation.org>