Hi William, Thanks a lot for working on the release!
How about we include all the non-zero copy JIRAs? All of them are bug fixes, minor code improvements or build improvements. The only conflicts are RATIS-2186 and RATIS-2235, which you already have resolved. The attached a.sh file can cherry-pick all the JIRAs over the release-3.1.2 branch. The release-3.1.3_review branch is the result after cherry-picks. Tsz-Wo On Thu, Jan 9, 2025 at 5:23 AM Attila Doroszlai <[email protected]> wrote: > Hi William, > > > https://github.com/apache/ratis/tree/ratis-3.1.3-rc1 > > Thanks for working on the release. I would like to ask for the > following commits to be included, all related to the build and release > process, and the artifacts it creates. > > * e9755a63 RATIS-2204. Avoid downloads from repository.apache.org (#1187) > => This helps avoid getting banned from apache.org servers (which is > useful for both local and CI builds) > > * 703189ed RATIS-2206. Jars in Maven repo and binary tarball are not > the same (#1188) > * a0eada8b RATIS-2211. publish-mvn fails with: ... did not assign a > file to the build artifact (#1190) > => These fix a mismatch in the release artifacts between tarballs and > Maven repo. Note that steps in make_rc.sh are renamed. > > * 318c8970 RATIS-2216. Bump maven-shade-plugin to 3.6.0 (#1191) > * 17c96529 RATIS-2215. Bump maven-remote-resources-plugin to 3.3.0 (#1208) > => Upgrade plugins because old versions may produce non-reproducible > artifacts. This was discovered after the 3.1.2 release. > > Can be cleanly cherry-picked: > $ git cherry-pick -x e9755a63 703189ed a0eada8b 318c8970 17c96529 > > Thanks for considering it. > > -Attila >
a.sh
Description: Bourne shell script
