Re: [VOTE] Release Apache Traffic Control (incubating) 2.2.0-RC2
Ah, sorry, I'd removed them form dist/dev but not dist/release. They have been removed from https://dist.apache.org/repos/dist/release/incubator/ trafficcontrol/2.0.0-incubating/ now. On Fri, Mar 23, 2018 at 7:18 AM, sebb wrote: > On 22 March 2018 at 17:36, Robert Butts wrote: > > Ah, thanks for the clarification. > > > > Ok, the 2.0.0 RPMs have been removed from dist > > Huh? I still see files here: > > https://dist.apache.org/repos/dist/release/incubator/trafficcontrol/2.0.0- > incubating/ > > Please remove the folder and its contents. > > > , and the webpage links updated to archive.apache.org. > > Agreed; thanks. > > > > On Mon, Mar 19, 2018 at 5:48 PM, sebb wrote: > > > >> On 19 March 2018 at 19:01, Robert Butts > wrote: > >> > MD5s have been removed. > >> > > >> > Henk, I'm not sure what you mean about a 2.x branch. We don't have a > >> branch > >> > named 2.x. We do our primary development in master, then create > branches > >> > for each release, e.g. 2.0.x, 2.1.x, 2.2.x. Those branches are only > ever > >> > updated with backported fixes. There's no separate branch for version > 2 > >> > development, just master. > >> > > >> > Is that ok? Or do we still need to move 2.0.0? > >> > >> I think Henk meant that the mirrors should only hold the current > release. > >> At present that is 2.1.0, so 2.0.0 should be removed, and the download > >> page updated to refer to the archive server at: > >> http://archive.apache.org/dist/incubator/trafficcontrol/ > 2.0.0-incubating/ > >> > >> When 2.2.0 is released, the same should be done for 2.1.0. > >> i.e. update the download page to add 2.2.0; change 2.1.0 and any > >> earlier links to use the archive server. > >> Once the new release has been announced, remove the older releases from > >> > >> https://dist.apache.org/repos/dist/release/incubator/trafficcontrol/ > >> > >> which will remove them from the ASF mirror system. > >> > >> > > >> > On Mon, Mar 19, 2018 at 11:57 AM, Henk P. Penning > wrote: > >> > > >> >> On Mon, 19 Mar 2018, Robert Butts wrote: > >> >> > >> >> Date: Mon, 19 Mar 2018 18:34:22 +0100 > >> >>> From: Robert Butts > >> >>> To: gene...@incubator.apache.org > >> >>> Cc: dev@trafficcontrol.incubator.apache.org > >> >>> Subject: [VOTE] Release Apache Traffic Control (incubating) > 2.2.0-RC2 > >> >>> > >> >>> Hello Incubator PMC, > >> >>> > >> >>> The Apache Traffic Control community has voted on and approved a > >> >>> proposal to release Apache Traffic Control 2.2-incubating. We now > >> >>> kindly request that the Incubator PMC members review and vote on > this > >> >>> incubator release. > >> >>> > >> >> > >> >> The previous approved releases and release notes (along with links to > >> >>> artifacts, signatures/checksums, and updated documentation) can be > >> >>> found here: > >> >>> http://trafficcontrol.incubator.apache.org/downloads/ > >> >>> > >> >> > >> >> Regarding you download page : > >> >> > >> >> -- It appears you have only one development branch (2.x) going ; > >> >> If so, 2.0.0 should not be in /dist/ (and on the mirrors) > anymore. > >> >> Please refer to 2.0.0 files as : > >> >> > >> >> http://archive.apache.org/dist/incubator/trafficcontrol/2. > >> >> 0.0-incubating/ > >> >> > >> >> The source distribution is here: > >> >>> https://dist.apache.org/repos/dist/dev/incubator/trafficcont > >> >>> rol/2.2.0/RC2/ > >> >>> > >> >> > >> >> Please don't publish .md5's anymore ; remove before moving 2.2.0 > >> >> from dist/dev/ to dist/release/. > >> >> > >> >> Thanks ; regards, > >> >> > >> >> Henk Penning > >> >> > >> >> _ > >> >> Henk P. Penning, ICT-beta R Uithof MG-403_/ \_ > >> >> Faculty of Science, Utrecht UniversityT +31 30 253 4106 / \_/ \ > >> >> Leuvenlaan 4, 3584CE Utrecht, NL F +31 30 253 4553 \_/ \_/ > >> >> http://www.staff.science.uu.nl/~penni101/ M penn...@uu.nl \_/ > >> >> > >> >
Re: [VOTE] Release Apache Traffic Control (incubating) 2.2.0-RC2
On 22 March 2018 at 17:36, Robert Butts wrote: > Ah, thanks for the clarification. > > Ok, the 2.0.0 RPMs have been removed from dist Huh? I still see files here: https://dist.apache.org/repos/dist/release/incubator/trafficcontrol/2.0.0-incubating/ Please remove the folder and its contents. > , and the webpage links updated to archive.apache.org. Agreed; thanks. > On Mon, Mar 19, 2018 at 5:48 PM, sebb wrote: > >> On 19 March 2018 at 19:01, Robert Butts wrote: >> > MD5s have been removed. >> > >> > Henk, I'm not sure what you mean about a 2.x branch. We don't have a >> branch >> > named 2.x. We do our primary development in master, then create branches >> > for each release, e.g. 2.0.x, 2.1.x, 2.2.x. Those branches are only ever >> > updated with backported fixes. There's no separate branch for version 2 >> > development, just master. >> > >> > Is that ok? Or do we still need to move 2.0.0? >> >> I think Henk meant that the mirrors should only hold the current release. >> At present that is 2.1.0, so 2.0.0 should be removed, and the download >> page updated to refer to the archive server at: >> http://archive.apache.org/dist/incubator/trafficcontrol/2.0.0-incubating/ >> >> When 2.2.0 is released, the same should be done for 2.1.0. >> i.e. update the download page to add 2.2.0; change 2.1.0 and any >> earlier links to use the archive server. >> Once the new release has been announced, remove the older releases from >> >> https://dist.apache.org/repos/dist/release/incubator/trafficcontrol/ >> >> which will remove them from the ASF mirror system. >> >> > >> > On Mon, Mar 19, 2018 at 11:57 AM, Henk P. Penning wrote: >> > >> >> On Mon, 19 Mar 2018, Robert Butts wrote: >> >> >> >> Date: Mon, 19 Mar 2018 18:34:22 +0100 >> >>> From: Robert Butts >> >>> To: gene...@incubator.apache.org >> >>> Cc: dev@trafficcontrol.incubator.apache.org >> >>> Subject: [VOTE] Release Apache Traffic Control (incubating) 2.2.0-RC2 >> >>> >> >>> Hello Incubator PMC, >> >>> >> >>> The Apache Traffic Control community has voted on and approved a >> >>> proposal to release Apache Traffic Control 2.2-incubating. We now >> >>> kindly request that the Incubator PMC members review and vote on this >> >>> incubator release. >> >>> >> >> >> >> The previous approved releases and release notes (along with links to >> >>> artifacts, signatures/checksums, and updated documentation) can be >> >>> found here: >> >>> http://trafficcontrol.incubator.apache.org/downloads/ >> >>> >> >> >> >> Regarding you download page : >> >> >> >> -- It appears you have only one development branch (2.x) going ; >> >> If so, 2.0.0 should not be in /dist/ (and on the mirrors) anymore. >> >> Please refer to 2.0.0 files as : >> >> >> >> http://archive.apache.org/dist/incubator/trafficcontrol/2. >> >> 0.0-incubating/ >> >> >> >> The source distribution is here: >> >>> https://dist.apache.org/repos/dist/dev/incubator/trafficcont >> >>> rol/2.2.0/RC2/ >> >>> >> >> >> >> Please don't publish .md5's anymore ; remove before moving 2.2.0 >> >> from dist/dev/ to dist/release/. >> >> >> >> Thanks ; regards, >> >> >> >> Henk Penning >> >> >> >> _ >> >> Henk P. Penning, ICT-beta R Uithof MG-403_/ \_ >> >> Faculty of Science, Utrecht UniversityT +31 30 253 4106 / \_/ \ >> >> Leuvenlaan 4, 3584CE Utrecht, NL F +31 30 253 4553 \_/ \_/ >> >> http://www.staff.science.uu.nl/~penni101/ M penn...@uu.nl \_/ >> >> >>
Re: [VOTE] Release Apache Traffic Control (incubating) 2.2.0-RC2
Ah, thanks for the clarification. Ok, the 2.0.0 RPMs have been removed from dist, and the webpage links updated to archive.apache.org. On Mon, Mar 19, 2018 at 5:48 PM, sebb wrote: > On 19 March 2018 at 19:01, Robert Butts wrote: > > MD5s have been removed. > > > > Henk, I'm not sure what you mean about a 2.x branch. We don't have a > branch > > named 2.x. We do our primary development in master, then create branches > > for each release, e.g. 2.0.x, 2.1.x, 2.2.x. Those branches are only ever > > updated with backported fixes. There's no separate branch for version 2 > > development, just master. > > > > Is that ok? Or do we still need to move 2.0.0? > > I think Henk meant that the mirrors should only hold the current release. > At present that is 2.1.0, so 2.0.0 should be removed, and the download > page updated to refer to the archive server at: > http://archive.apache.org/dist/incubator/trafficcontrol/2.0.0-incubating/ > > When 2.2.0 is released, the same should be done for 2.1.0. > i.e. update the download page to add 2.2.0; change 2.1.0 and any > earlier links to use the archive server. > Once the new release has been announced, remove the older releases from > > https://dist.apache.org/repos/dist/release/incubator/trafficcontrol/ > > which will remove them from the ASF mirror system. > > > > > On Mon, Mar 19, 2018 at 11:57 AM, Henk P. Penning wrote: > > > >> On Mon, 19 Mar 2018, Robert Butts wrote: > >> > >> Date: Mon, 19 Mar 2018 18:34:22 +0100 > >>> From: Robert Butts > >>> To: gene...@incubator.apache.org > >>> Cc: dev@trafficcontrol.incubator.apache.org > >>> Subject: [VOTE] Release Apache Traffic Control (incubating) 2.2.0-RC2 > >>> > >>> Hello Incubator PMC, > >>> > >>> The Apache Traffic Control community has voted on and approved a > >>> proposal to release Apache Traffic Control 2.2-incubating. We now > >>> kindly request that the Incubator PMC members review and vote on this > >>> incubator release. > >>> > >> > >> The previous approved releases and release notes (along with links to > >>> artifacts, signatures/checksums, and updated documentation) can be > >>> found here: > >>> http://trafficcontrol.incubator.apache.org/downloads/ > >>> > >> > >> Regarding you download page : > >> > >> -- It appears you have only one development branch (2.x) going ; > >> If so, 2.0.0 should not be in /dist/ (and on the mirrors) anymore. > >> Please refer to 2.0.0 files as : > >> > >> http://archive.apache.org/dist/incubator/trafficcontrol/2. > >> 0.0-incubating/ > >> > >> The source distribution is here: > >>> https://dist.apache.org/repos/dist/dev/incubator/trafficcont > >>> rol/2.2.0/RC2/ > >>> > >> > >> Please don't publish .md5's anymore ; remove before moving 2.2.0 > >> from dist/dev/ to dist/release/. > >> > >> Thanks ; regards, > >> > >> Henk Penning > >> > >> _ > >> Henk P. Penning, ICT-beta R Uithof MG-403_/ \_ > >> Faculty of Science, Utrecht UniversityT +31 30 253 4106 / \_/ \ > >> Leuvenlaan 4, 3584CE Utrecht, NL F +31 30 253 4553 \_/ \_/ > >> http://www.staff.science.uu.nl/~penni101/ M penn...@uu.nl \_/ > >> >
Re: [VOTE] Release Apache Traffic Control (incubating) 2.2.0-RC2
On 19 March 2018 at 19:01, Robert Butts wrote: > MD5s have been removed. > > Henk, I'm not sure what you mean about a 2.x branch. We don't have a branch > named 2.x. We do our primary development in master, then create branches > for each release, e.g. 2.0.x, 2.1.x, 2.2.x. Those branches are only ever > updated with backported fixes. There's no separate branch for version 2 > development, just master. > > Is that ok? Or do we still need to move 2.0.0? I think Henk meant that the mirrors should only hold the current release. At present that is 2.1.0, so 2.0.0 should be removed, and the download page updated to refer to the archive server at: http://archive.apache.org/dist/incubator/trafficcontrol/2.0.0-incubating/ When 2.2.0 is released, the same should be done for 2.1.0. i.e. update the download page to add 2.2.0; change 2.1.0 and any earlier links to use the archive server. Once the new release has been announced, remove the older releases from https://dist.apache.org/repos/dist/release/incubator/trafficcontrol/ which will remove them from the ASF mirror system. > > On Mon, Mar 19, 2018 at 11:57 AM, Henk P. Penning wrote: > >> On Mon, 19 Mar 2018, Robert Butts wrote: >> >> Date: Mon, 19 Mar 2018 18:34:22 +0100 >>> From: Robert Butts >>> To: gene...@incubator.apache.org >>> Cc: dev@trafficcontrol.incubator.apache.org >>> Subject: [VOTE] Release Apache Traffic Control (incubating) 2.2.0-RC2 >>> >>> Hello Incubator PMC, >>> >>> The Apache Traffic Control community has voted on and approved a >>> proposal to release Apache Traffic Control 2.2-incubating. We now >>> kindly request that the Incubator PMC members review and vote on this >>> incubator release. >>> >> >> The previous approved releases and release notes (along with links to >>> artifacts, signatures/checksums, and updated documentation) can be >>> found here: >>> http://trafficcontrol.incubator.apache.org/downloads/ >>> >> >> Regarding you download page : >> >> -- It appears you have only one development branch (2.x) going ; >> If so, 2.0.0 should not be in /dist/ (and on the mirrors) anymore. >> Please refer to 2.0.0 files as : >> >> http://archive.apache.org/dist/incubator/trafficcontrol/2. >> 0.0-incubating/ >> >> The source distribution is here: >>> https://dist.apache.org/repos/dist/dev/incubator/trafficcont >>> rol/2.2.0/RC2/ >>> >> >> Please don't publish .md5's anymore ; remove before moving 2.2.0 >> from dist/dev/ to dist/release/. >> >> Thanks ; regards, >> >> Henk Penning >> >> _ >> Henk P. Penning, ICT-beta R Uithof MG-403_/ \_ >> Faculty of Science, Utrecht UniversityT +31 30 253 4106 / \_/ \ >> Leuvenlaan 4, 3584CE Utrecht, NL F +31 30 253 4553 \_/ \_/ >> http://www.staff.science.uu.nl/~penni101/ M penn...@uu.nl \_/ >>
Re: [VOTE] Release Apache Traffic Control (incubating) 2.2.0-RC2
MD5s have been removed. Henk, I'm not sure what you mean about a 2.x branch. We don't have a branch named 2.x. We do our primary development in master, then create branches for each release, e.g. 2.0.x, 2.1.x, 2.2.x. Those branches are only ever updated with backported fixes. There's no separate branch for version 2 development, just master. Is that ok? Or do we still need to move 2.0.0? On Mon, Mar 19, 2018 at 11:57 AM, Henk P. Penning wrote: > On Mon, 19 Mar 2018, Robert Butts wrote: > > Date: Mon, 19 Mar 2018 18:34:22 +0100 >> From: Robert Butts >> To: gene...@incubator.apache.org >> Cc: dev@trafficcontrol.incubator.apache.org >> Subject: [VOTE] Release Apache Traffic Control (incubating) 2.2.0-RC2 >> >> Hello Incubator PMC, >> >> The Apache Traffic Control community has voted on and approved a >> proposal to release Apache Traffic Control 2.2-incubating. We now >> kindly request that the Incubator PMC members review and vote on this >> incubator release. >> > > The previous approved releases and release notes (along with links to >> artifacts, signatures/checksums, and updated documentation) can be >> found here: >> http://trafficcontrol.incubator.apache.org/downloads/ >> > > Regarding you download page : > > -- It appears you have only one development branch (2.x) going ; > If so, 2.0.0 should not be in /dist/ (and on the mirrors) anymore. > Please refer to 2.0.0 files as : > > http://archive.apache.org/dist/incubator/trafficcontrol/2. > 0.0-incubating/ > > The source distribution is here: >> https://dist.apache.org/repos/dist/dev/incubator/trafficcont >> rol/2.2.0/RC2/ >> > > Please don't publish .md5's anymore ; remove before moving 2.2.0 > from dist/dev/ to dist/release/. > > Thanks ; regards, > > Henk Penning > > _ > Henk P. Penning, ICT-beta R Uithof MG-403_/ \_ > Faculty of Science, Utrecht UniversityT +31 30 253 4106 / \_/ \ > Leuvenlaan 4, 3584CE Utrecht, NL F +31 30 253 4553 \_/ \_/ > http://www.staff.science.uu.nl/~penni101/ M penn...@uu.nl \_/ >
Re: [VOTE] Release Apache Traffic Control (incubating) 2.2.0-RC2
Dangit, I already started this email so I am going to finish it: +1 I tested the following: - Signatures and hashes are good - Created builds via PKG on a brand new Centos 7.x server - Tested install of TM, TR, and TS. On Thu, Mar 8, 2018 at 9:28 AM, Dan Kirkwood wrote: > Hank, fyi -- from the top level of trafficcontrol, `./pkg -v` will build > all components. > > -dan > > On Thu, Mar 8, 2018 at 6:34 AM, Hank Beatty wrote: > > > +1 > > > > Lab Testing: > > > > - Docker build - Could not figure out how to get all components to build > > at once > > - build/build.sh on CentOS 6 - all components built successfully > > - Upgraded Traffic Monitor (2.2.0.d7e588 -> 2.2.0.6ea850) > > - Could pull up UI and it connects to all cache servers > > - Upgraded Traffic Router (2.2.0.d7e588 -> 2.2.0.6ea850) > > - Could connect to : and crs/stats looked correct > > - Upgraded Traffic Stats (2.2.0.d7e588 -> 2.2.0.6ea850) CentOS 6 > > - Upgraded Traffic Ops ORT > > - mid cache "report" and "badass" mode seem to work correctly > > - edge cache "report" and "badass" mode seem to work correctly > > - Tested DNS DS and works correctly > > > > On 03/05/2018 01:25 PM, Robert Butts wrote: > > > >> Hello All, > >> > >> I've prepared a release for v2.2.0-RC2 > >> > >> The vote is open for at least 72 hours and passes if a majority of at > >> least > >> 3 +1 PPMC votes are cast. > >> > >> [ ] +1 Approve the release > >> > >> [ ] -1 Do not release this package because ... > >> > >> Changes since 2.1.0: > >> https://github.com/apache/incubator-trafficcontrol/compare/ > >> RELEASE-2.1.0...RELEASE-2.2.0-RC2 > >> > >> This corresponds to git: > >> Hash: 6ea85056a1a69973be4a74b82d602df29f21f42d > >> Tag: RELEASE-2.2.0-RC2 > >> > >> Which can be verified with the following: git tag -v RELEASE-2.2.0-RC2 > >> > >> My code signing key is available here: > >> http://keys.gnupg.net/pks/lookup?search=0xFDD04F7F&op=vindex > >> > >> Make sure you refresh from a key server to get all relevant signatures. > >> > >> The source .tar.gz file, pgp signature (.asc signed with my key from > >> above), md5 and sha1 checksums are provided here: > >> > >> https://dist.apache.org/repos/dist/dev/incubator/ > trafficcontrol/2.2.0/RC2 > >> > >> > >> Thanks! > >> > >> >
Re: [VOTE] Release Apache Traffic Control (incubating) 2.2.0-RC2
On Mon, 19 Mar 2018, Robert Butts wrote: Date: Mon, 19 Mar 2018 18:34:22 +0100 From: Robert Butts To: gene...@incubator.apache.org Cc: dev@trafficcontrol.incubator.apache.org Subject: [VOTE] Release Apache Traffic Control (incubating) 2.2.0-RC2 Hello Incubator PMC, The Apache Traffic Control community has voted on and approved a proposal to release Apache Traffic Control 2.2-incubating. We now kindly request that the Incubator PMC members review and vote on this incubator release. The previous approved releases and release notes (along with links to artifacts, signatures/checksums, and updated documentation) can be found here: http://trafficcontrol.incubator.apache.org/downloads/ Regarding you download page : -- It appears you have only one development branch (2.x) going ; If so, 2.0.0 should not be in /dist/ (and on the mirrors) anymore. Please refer to 2.0.0 files as : http://archive.apache.org/dist/incubator/trafficcontrol/2.0.0-incubating/ The source distribution is here: https://dist.apache.org/repos/dist/dev/incubator/trafficcontrol/2.2.0/RC2/ Please don't publish .md5's anymore ; remove before moving 2.2.0 from dist/dev/ to dist/release/. Thanks ; regards, Henk Penning _ Henk P. Penning, ICT-beta R Uithof MG-403_/ \_ Faculty of Science, Utrecht UniversityT +31 30 253 4106 / \_/ \ Leuvenlaan 4, 3584CE Utrecht, NL F +31 30 253 4553 \_/ \_/ http://www.staff.science.uu.nl/~penni101/ M penn...@uu.nl \_/
Re: [VOTE] Release Apache Traffic Control (incubating) 2.2.0-RC2
Hello, This vote has passed with +3. Putting together the IPMC email now. Thanks everyone. On Thu, Mar 8, 2018 at 9:28 AM, Dan Kirkwood wrote: > Hank, fyi -- from the top level of trafficcontrol, `./pkg -v` will build > all components. > > -dan > > On Thu, Mar 8, 2018 at 6:34 AM, Hank Beatty wrote: > > > +1 > > > > Lab Testing: > > > > - Docker build - Could not figure out how to get all components to build > > at once > > - build/build.sh on CentOS 6 - all components built successfully > > - Upgraded Traffic Monitor (2.2.0.d7e588 -> 2.2.0.6ea850) > > - Could pull up UI and it connects to all cache servers > > - Upgraded Traffic Router (2.2.0.d7e588 -> 2.2.0.6ea850) > > - Could connect to : and crs/stats looked correct > > - Upgraded Traffic Stats (2.2.0.d7e588 -> 2.2.0.6ea850) CentOS 6 > > - Upgraded Traffic Ops ORT > > - mid cache "report" and "badass" mode seem to work correctly > > - edge cache "report" and "badass" mode seem to work correctly > > - Tested DNS DS and works correctly > > > > On 03/05/2018 01:25 PM, Robert Butts wrote: > > > >> Hello All, > >> > >> I've prepared a release for v2.2.0-RC2 > >> > >> The vote is open for at least 72 hours and passes if a majority of at > >> least > >> 3 +1 PPMC votes are cast. > >> > >> [ ] +1 Approve the release > >> > >> [ ] -1 Do not release this package because ... > >> > >> Changes since 2.1.0: > >> https://github.com/apache/incubator-trafficcontrol/compare/ > >> RELEASE-2.1.0...RELEASE-2.2.0-RC2 > >> > >> This corresponds to git: > >> Hash: 6ea85056a1a69973be4a74b82d602df29f21f42d > >> Tag: RELEASE-2.2.0-RC2 > >> > >> Which can be verified with the following: git tag -v RELEASE-2.2.0-RC2 > >> > >> My code signing key is available here: > >> http://keys.gnupg.net/pks/lookup?search=0xFDD04F7F&op=vindex > >> > >> Make sure you refresh from a key server to get all relevant signatures. > >> > >> The source .tar.gz file, pgp signature (.asc signed with my key from > >> above), md5 and sha1 checksums are provided here: > >> > >> https://dist.apache.org/repos/dist/dev/incubator/ > trafficcontrol/2.2.0/RC2 > >> > >> > >> Thanks! > >> > >> >
Re: [VOTE] Release Apache Traffic Control (incubating) 2.2.0-RC2
Hank, fyi -- from the top level of trafficcontrol, `./pkg -v` will build all components. -dan On Thu, Mar 8, 2018 at 6:34 AM, Hank Beatty wrote: > +1 > > Lab Testing: > > - Docker build - Could not figure out how to get all components to build > at once > - build/build.sh on CentOS 6 - all components built successfully > - Upgraded Traffic Monitor (2.2.0.d7e588 -> 2.2.0.6ea850) > - Could pull up UI and it connects to all cache servers > - Upgraded Traffic Router (2.2.0.d7e588 -> 2.2.0.6ea850) > - Could connect to : and crs/stats looked correct > - Upgraded Traffic Stats (2.2.0.d7e588 -> 2.2.0.6ea850) CentOS 6 > - Upgraded Traffic Ops ORT > - mid cache "report" and "badass" mode seem to work correctly > - edge cache "report" and "badass" mode seem to work correctly > - Tested DNS DS and works correctly > > On 03/05/2018 01:25 PM, Robert Butts wrote: > >> Hello All, >> >> I've prepared a release for v2.2.0-RC2 >> >> The vote is open for at least 72 hours and passes if a majority of at >> least >> 3 +1 PPMC votes are cast. >> >> [ ] +1 Approve the release >> >> [ ] -1 Do not release this package because ... >> >> Changes since 2.1.0: >> https://github.com/apache/incubator-trafficcontrol/compare/ >> RELEASE-2.1.0...RELEASE-2.2.0-RC2 >> >> This corresponds to git: >> Hash: 6ea85056a1a69973be4a74b82d602df29f21f42d >> Tag: RELEASE-2.2.0-RC2 >> >> Which can be verified with the following: git tag -v RELEASE-2.2.0-RC2 >> >> My code signing key is available here: >> http://keys.gnupg.net/pks/lookup?search=0xFDD04F7F&op=vindex >> >> Make sure you refresh from a key server to get all relevant signatures. >> >> The source .tar.gz file, pgp signature (.asc signed with my key from >> above), md5 and sha1 checksums are provided here: >> >> https://dist.apache.org/repos/dist/dev/incubator/trafficcontrol/2.2.0/RC2 >> >> >> Thanks! >> >>
Re: [VOTE] Release Apache Traffic Control (incubating) 2.2.0-RC2
+1 Lab Testing: - Docker build - Could not figure out how to get all components to build at once - build/build.sh on CentOS 6 - all components built successfully - Upgraded Traffic Monitor (2.2.0.d7e588 -> 2.2.0.6ea850) - Could pull up UI and it connects to all cache servers - Upgraded Traffic Router (2.2.0.d7e588 -> 2.2.0.6ea850) - Could connect to : and crs/stats looked correct - Upgraded Traffic Stats (2.2.0.d7e588 -> 2.2.0.6ea850) CentOS 6 - Upgraded Traffic Ops ORT - mid cache "report" and "badass" mode seem to work correctly - edge cache "report" and "badass" mode seem to work correctly - Tested DNS DS and works correctly On 03/05/2018 01:25 PM, Robert Butts wrote: Hello All, I've prepared a release for v2.2.0-RC2 The vote is open for at least 72 hours and passes if a majority of at least 3 +1 PPMC votes are cast. [ ] +1 Approve the release [ ] -1 Do not release this package because ... Changes since 2.1.0: https://github.com/apache/incubator-trafficcontrol/compare/RELEASE-2.1.0...RELEASE-2.2.0-RC2 This corresponds to git: Hash: 6ea85056a1a69973be4a74b82d602df29f21f42d Tag: RELEASE-2.2.0-RC2 Which can be verified with the following: git tag -v RELEASE-2.2.0-RC2 My code signing key is available here: http://keys.gnupg.net/pks/lookup?search=0xFDD04F7F&op=vindex Make sure you refresh from a key server to get all relevant signatures. The source .tar.gz file, pgp signature (.asc signed with my key from above), md5 and sha1 checksums are provided here: https://dist.apache.org/repos/dist/dev/incubator/trafficcontrol/2.2.0/RC2 Thanks!
Re: [VOTE] Release Apache Traffic Control (incubating) 2.2.0-RC2
+1 -- I checked: - hashes and signature good - builds all from `./pkg -v` - TO rpm installs cleanly on a fresh VM - TO basic functionality works (no extensive testing..) On Wed, Mar 7, 2018 at 7:00 AM, Eric Friedrich (efriedri) < efrie...@cisco.com> wrote: > +1 > > I checked the following: > - Release hashes and signatures good > - Release builds via pkg > - TO, TR, TM fresh install and start/retrieve config > - Looked through RAT > > Nitpick in the below email: the SHA checksum is a SHA-512 not a SHA-1 > > —Eric > > > > > On Mar 5, 2018, at 1:25 PM, Robert Butts wrote: > > > > Hello All, > > > > I've prepared a release for v2.2.0-RC2 > > > > The vote is open for at least 72 hours and passes if a majority of at > least > > 3 +1 PPMC votes are cast. > > > > [ ] +1 Approve the release > > > > [ ] -1 Do not release this package because ... > > > > Changes since 2.1.0: > > https://github.com/apache/incubator-trafficcontrol/ > compare/RELEASE-2.1.0...RELEASE-2.2.0-RC2 > > > > This corresponds to git: > > Hash: 6ea85056a1a69973be4a74b82d602df29f21f42d > > Tag: RELEASE-2.2.0-RC2 > > > > Which can be verified with the following: git tag -v RELEASE-2.2.0-RC2 > > > > My code signing key is available here: > > http://keys.gnupg.net/pks/lookup?search=0xFDD04F7F&op=vindex > > > > Make sure you refresh from a key server to get all relevant signatures. > > > > The source .tar.gz file, pgp signature (.asc signed with my key from > > above), md5 and sha1 checksums are provided here: > > > > https://dist.apache.org/repos/dist/dev/incubator/ > trafficcontrol/2.2.0/RC2 > > > > > > Thanks! > >
Re: [VOTE] Release Apache Traffic Control (incubating) 2.2.0-RC2
+1 I checked the following: - Release hashes and signatures good - Release builds via pkg - TO, TR, TM fresh install and start/retrieve config - Looked through RAT Nitpick in the below email: the SHA checksum is a SHA-512 not a SHA-1 —Eric > On Mar 5, 2018, at 1:25 PM, Robert Butts wrote: > > Hello All, > > I've prepared a release for v2.2.0-RC2 > > The vote is open for at least 72 hours and passes if a majority of at least > 3 +1 PPMC votes are cast. > > [ ] +1 Approve the release > > [ ] -1 Do not release this package because ... > > Changes since 2.1.0: > https://github.com/apache/incubator-trafficcontrol/compare/RELEASE-2.1.0...RELEASE-2.2.0-RC2 > > This corresponds to git: > Hash: 6ea85056a1a69973be4a74b82d602df29f21f42d > Tag: RELEASE-2.2.0-RC2 > > Which can be verified with the following: git tag -v RELEASE-2.2.0-RC2 > > My code signing key is available here: > http://keys.gnupg.net/pks/lookup?search=0xFDD04F7F&op=vindex > > Make sure you refresh from a key server to get all relevant signatures. > > The source .tar.gz file, pgp signature (.asc signed with my key from > above), md5 and sha1 checksums are provided here: > > https://dist.apache.org/repos/dist/dev/incubator/trafficcontrol/2.2.0/RC2 > > > Thanks!
Re: [VOTE] Release Apache Traffic Control (incubating) 2.2.0-RC2
The 2.1 profiles should work for 2.2 On Tue, Mar 6, 2018 at 9:19 AM, Eric Friedrich (efriedri) < efrie...@cisco.com> wrote: > Can you please post default profiles for 2.2 on the website? > > For now, I’m using 2.1 default profiles to test the release > > —Eric > > > On Mar 5, 2018, at 1:25 PM, Robert Butts wrote: > > > > Hello All, > > > > I've prepared a release for v2.2.0-RC2 > > > > The vote is open for at least 72 hours and passes if a majority of at > least > > 3 +1 PPMC votes are cast. > > > > [ ] +1 Approve the release > > > > [ ] -1 Do not release this package because ... > > > > Changes since 2.1.0: > > https://github.com/apache/incubator-trafficcontrol/ > compare/RELEASE-2.1.0...RELEASE-2.2.0-RC2 > > > > This corresponds to git: > > Hash: 6ea85056a1a69973be4a74b82d602df29f21f42d > > Tag: RELEASE-2.2.0-RC2 > > > > Which can be verified with the following: git tag -v RELEASE-2.2.0-RC2 > > > > My code signing key is available here: > > http://keys.gnupg.net/pks/lookup?search=0xFDD04F7F&op=vindex > > > > Make sure you refresh from a key server to get all relevant signatures. > > > > The source .tar.gz file, pgp signature (.asc signed with my key from > > above), md5 and sha1 checksums are provided here: > > > > https://dist.apache.org/repos/dist/dev/incubator/ > trafficcontrol/2.2.0/RC2 > > > > > > Thanks! > >
Re: [VOTE] Release Apache Traffic Control (incubating) 2.2.0-RC2
Can you please post default profiles for 2.2 on the website? For now, I’m using 2.1 default profiles to test the release —Eric > On Mar 5, 2018, at 1:25 PM, Robert Butts wrote: > > Hello All, > > I've prepared a release for v2.2.0-RC2 > > The vote is open for at least 72 hours and passes if a majority of at least > 3 +1 PPMC votes are cast. > > [ ] +1 Approve the release > > [ ] -1 Do not release this package because ... > > Changes since 2.1.0: > https://github.com/apache/incubator-trafficcontrol/compare/RELEASE-2.1.0...RELEASE-2.2.0-RC2 > > This corresponds to git: > Hash: 6ea85056a1a69973be4a74b82d602df29f21f42d > Tag: RELEASE-2.2.0-RC2 > > Which can be verified with the following: git tag -v RELEASE-2.2.0-RC2 > > My code signing key is available here: > http://keys.gnupg.net/pks/lookup?search=0xFDD04F7F&op=vindex > > Make sure you refresh from a key server to get all relevant signatures. > > The source .tar.gz file, pgp signature (.asc signed with my key from > above), md5 and sha1 checksums are provided here: > > https://dist.apache.org/repos/dist/dev/incubator/trafficcontrol/2.2.0/RC2 > > > Thanks!
