Yeah was planning on casually doing that. My gripe with release notes is that they take time to write and review, delaying an RC by days if we were to wait for them to be written before releasing it.
On Thu, Mar 3, 2016 at 1:22 PM, Todd Lipcon <[email protected]> wrote: > Should we edit docs/release_notes.adoc to include release notes for 0.7.1 > before releasing? It seems odd that the release wouldn't mention the latest > version in the included release notes. > > -Todd > > On Wed, Mar 2, 2016 at 4:41 PM, Jean-Daniel Cryans <[email protected]> > wrote: > > > Hi, > > > > We're happy to announce the first release candidate for Apache Kudu > > (incubating) 0.7.1. > > > > This release fixes a few important bugs found during the process of > > releasing 0.7.0 that didn't warrant sinking the vote for. It also takes > > care of fixing some licenses. > > > > The is a source-only release. The artifacts were staged here: > > https://dist.apache.org/repos/dist/dev/incubator/kudu/0.7.1-RC1/ > > > > It was built from this tag: > > > > > https://git1-us-west.apache.org/repos/asf?p=incubator-kudu.git;a=commit;h=bd191ec7366e13c3a11c6144f3b5af03d6496b38 > > > > The list of all issues fixed can be found here: > > > > > https://issues.apache.org/jira/issues/?jql=project%20%3D%20KUDU%20AND%20fixVersion%20%3D%200.7.1 > > > > KEYS file: > > http://www.apache.org/dist/incubator/kudu/KEYS > > > > I'd suggest going through the README, building Kudu, and running the unit > > tests. > > > > Please try the release and vote; vote will be open for at least 72 hours. > > > > Thanks, > > > > J-D > > > > > > -- > Todd Lipcon > Software Engineer, Cloudera >
