-
Notifications
You must be signed in to change notification settings - Fork 142
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
cli: release 3.14 #1845
Comments
I did a mistake and pushed |
As mentioned in ooni/probe#1845 (comment), I did a mistake and published an `-alpha` debian package, so I need to bump master's version to 3.14 and create a 3.13 release train. やれやれだぜ
As mentioned in ooni/probe#1845 (comment), I did a mistake and published an `-alpha` debian package, so I need to bump master's version to 3.14 and create a 3.13 release train. やれやれだぜ
We're starting to prepare a new release. The first step is to use go1.17.6 in the following places: 1. everywhere we define the version of Go in this tree; 2. when we're building for Android (using ooni/go); 3. in our ooni/oohttp fork of Go net/http standard library. Reference issue: ooni/probe#1845
We're starting to prepare a new release. The first step is to use go1.17.6 in the following places: 1. everywhere we define the version of Go in this tree; 2. when we're building for Android (using ooni/go); 3. in our ooni/oohttp fork of Go net/http standard library. Reference issue: ooni/probe#1845
This release uses January 2022 databases. See ooni/probe#1845.
This release uses January 2022 databases. Since this commit, we're now always using db-ip.com for the ASN database. See ooni/probe#1845 as well as ooni/probe#1959.
This release uses January 2022 databases. Since this commit, we're now always using db-ip.com for the ASN database. See ooni/probe#1845 as well as ooni/probe#1959.
This diff contains the following changes and enhancements: 1. upgrade snowflake to v2 2. observe that we were not changing defaults from outside of snowflake.go, so remove code allowing to do that; 3. bump the timeout to 600 seconds (it seems 300 was not always enough based on my testing); 4. add useful knob to disable `torsf` progress (it's really annoying on console, we should do something about this); 5. ptx.go: avoid printing an error when the connection has just been closed; 6. snowflake: test AMP cache, see that it's not working currently, so leave it disabled. Related issues: ooni/probe#1845, ooni/probe#1894, and ooni/probe#1917.
This diff includes some final changes to be ready for blessing a cli release. These changes are: 1. run `go generate ./...` to update the bundled CA 2. update the header we use for measuring 3. ensure `mk` uses the latest version of several tools Reference issue: ooni/probe#1845
This diff includes some final changes to be ready for blessing a cli release. These changes are: 1. run `go generate ./...` to update the bundled CA 2. update the header we use for measuring 3. ensure `mk` uses the latest version of several tools Reference issue: ooni/probe#1845
We're mostly done with releasing. What remains to be done is some extra smoke testing on Android and Desktop using the |
While doing QA in ooni/probe#1845, I noticed we're not using the correct directory. Results are written in the current directory inside of the OONI_HOME, which is quite not what we want to happen. This diff WILL require forward porting to master.
This commit forward ports 59c63ee, whose original log message follows: - - - While doing QA in ooni/probe#1845, I noticed we're not using the correct directory. Results are written in the current directory inside of the OONI_HOME, which is quite not what we want to happen. This diff WILL require forward porting to master.
This commit forward ports 59c63ee, whose original log message follows: - - - While doing QA in ooni/probe#1845, I noticed we're not using the correct directory. Results are written in the current directory inside of the OONI_HOME, which is quite not what we want to happen. This diff WILL require forward porting to master.
Where applicable, also re-enable torsf. See ooni/probe#1845.
Where applicable, also re-enable torsf. See ooni/probe#1845.
Where applicable, also re-enable torsf. See ooni/probe#1845.
Where applicable, also re-enable torsf. See ooni/probe#1845.
Where applicable, also re-enable torsf. See ooni/probe#1845.
See ooni/probe#1845. Co-authored-by: Norbel Ambanumben <aanorbel@gmail.com>
It seems I forgot about bumping the version number 😩. See ooni/probe#1845.
Adding 8 points to this issue since I needed to work a bit more when finalizing the release. |
We can now close this issue. We have 3.14.1 with all the bugs found during the beta cycle fixed. |
(The only still open issue in this Epic is one that we should continue working on in the release/3.15 cycle.) |
As mentioned in ooni/probe#1845 (comment), I did a mistake and published an `-alpha` debian package, so I need to bump master's version to 3.14 and create a 3.13 release train. やれやれだぜ
We're starting to prepare a new release. The first step is to use go1.17.6 in the following places: 1. everywhere we define the version of Go in this tree; 2. when we're building for Android (using ooni/go); 3. in our ooni/oohttp fork of Go net/http standard library. Reference issue: ooni/probe#1845
This release uses January 2022 databases. Since this commit, we're now always using db-ip.com for the ASN database. See ooni/probe#1845 as well as ooni/probe#1959.
This diff contains the following changes and enhancements: 1. upgrade snowflake to v2 2. observe that we were not changing defaults from outside of snowflake.go, so remove code allowing to do that; 3. bump the timeout to 600 seconds (it seems 300 was not always enough based on my testing); 4. add useful knob to disable `torsf` progress (it's really annoying on console, we should do something about this); 5. ptx.go: avoid printing an error when the connection has just been closed; 6. snowflake: test AMP cache, see that it's not working currently, so leave it disabled. Related issues: ooni/probe#1845, ooni/probe#1894, and ooni/probe#1917.
This diff includes some final changes to be ready for blessing a cli release. These changes are: 1. run `go generate ./...` to update the bundled CA 2. update the header we use for measuring 3. ensure `mk` uses the latest version of several tools Reference issue: ooni/probe#1845
…#694) This commit forward ports 59c63ee, whose original log message follows: - - - While doing QA in ooni/probe#1845, I noticed we're not using the correct directory. Results are written in the current directory inside of the OONI_HOME, which is quite not what we want to happen. This diff WILL require forward porting to master.
This issue is about performing a bunch of release related tasks and cleanups that I could not perform during the 3.13 release cycle. Such a release cycle has been pretty chaotic and I think it's proper to sit down and adjust the process. We will consider this epic issue done when all the related issues have been solved.
This issue derives from #1506. We have figured out that the routine releases model does not serve us well when we have longer release cycles (which we have now). Hence I am spawning off this issue of #1506.
We will put into this Epic all the tasks that we could not perform as part of #1506 that are not related to 3.11.0 (#1843).
The text was updated successfully, but these errors were encountered: