I vote +1 On Fri, Jul 19, 2019 at 2:28 PM Josh Thompson <[email protected]> wrote:
> -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Well, again, we've had *way* too long between releases. I just cut RC1 > for > 2.5.1. This was the first RC after switching to git. So, it took a bit > of > retooling on my end. > > I created a release branch from develop named release-2.5.1. At this > point, > any new feature development can be committed to the develop branch, but > any > problems with the 2.5.1 release need to be committed to both release-2.5.1 > and > to develop. The only commits to release-2.5.1 should be things to fix > problems discovered in testing the release candidate. > > I created a tag of this release-2.5.1 branch. I exported the code from > the > branch using git archive, added in Dojo Toolkit v1.6.5 with a custom > profile > and Spyc v0.5.1, and created a release candidate artifact from there. > > The artifact, MD5 and SHA512 sums, and my GPG signature of it are > available > from my space on people.a.o: > > https://people.apache.org/~jfthomps/apache-VCL-2.5.1-RC1/ > > The list of resolved JIRA issues associated with this release can be found > under 2.5.1 on the Change Log page in the staging area of the CMS: > > http://vcl.staging.apache.org/docs/changelog.html > > Installation instructions on using the script and doing things manually > are on > the following page in the staging area of the CMS: > > http://vcl.staging.apache.org/docs/VCL251InstallGuide.html > > The INSTALLATION file in the release artifact contains information on > using the script and on installing manually. > > *NOTE* To use the installation script with RC1, you need to give it the > --rc=1 > option (which is not included in the output of --help). > > Test installs and upgrades were successfully performed. > > The directory created by extracting the RC1 artifact is > "apache-VCL-2.5.1-RC1" > (after extracting, you may want to rename it to "apache-VCL-2.5" if you > want > to test the manual installation instructions). > > After we finalize a release vote, the staging part of the CMS will be > published to update the production site. Also, the release-2.5.1 branch > will > be merged in to the master branch. > > Please vote by 5pm (EST) on Wednesday, July 24th to publish this release or > not. Everyone in the community is encouraged to vote if you have at least > done some testing. However, only votes by members of the PMC are binding > votes. > > [ ] +1 yes, release VCL 2.5.1 > [ ] 0 dunno > [ ] -1 no, don't release VCL 2.5.1 (provide reasons if this is your vote) > > Josh > - -- > - ------------------------------- > Josh Thompson > VCL Developer > North Carolina State University > > my GPG/PGP key can be found at pgp.mit.edu > > All electronic mail messages in connection with State business which > are sent to or received by this account are subject to the NC Public > Records Law and may be disclosed to third parties. > -----BEGIN PGP SIGNATURE----- > > iF0EARECAB0WIQRMIdRtWXideTZDK31X8tBw1209AwUCXTILggAKCRBX8tBw1209 > A5t0AJ9bU0re0L48UnCCdgQIlJQMgLcs/gCfVA+8+pCIucS2a4VbKfUcTOPvxfE= > =F6m7 > -----END PGP SIGNATURE----- > > > >
