On Sun, May 5, 2013 at 6:02 AM, Stefan Sperling <[email protected]> wrote: > The CHANGES file in the tarball is incomplete. At the very least, it > lacks some cleanup and a projected release date. Do we really want to > issue the 1.8.0 release with an incomplete CHANGES file?
Of course not, but this file won't be 1.8.0, we have a whole slew of changes that can be made during the soak, including the CHANGES file which is part of the normal work of doing a release. We have a whole month to get that done. No point in holding up the soak time frame just for CHANGES. Any date I would have put in there would probably have been bogus anyway. > Should we update the swig dependency to swig-2.0.9? I noticed that the > release.py script is still using 2.0.4, which was also used for 1.7.0. I did update the release.py script: http://svn.apache.org/r1478948 Remember the release script in the branch isn't used we always use trunk for release.py.
