I have kept myself busy studying the information in HACKING [1], in
Mark's SVN Release Management repo [2], in tools/dist/release.py, etc.

A quick test run with release.py seems to work (mostly) correctly. It
successfully installs the needed Autoconf, Libtool, and SWIG. It is
able to generate tarballs and Windows zips (though I haven't tested
these at all; they're just throwaways right now).

There were a few warnings while rolling these throwaways:

* Copyright year is stale; I committed r1914220 and r1914221 to address
  that.

* CHANGES has unmerged revisions; that's expected because I haven't
  updated CHANGES yet. That's the next task on my list.

* It complained that COMMITTERS file is not found, therefore
  make-keys.sh failed. I remember seeing something about this in Mark's
  svnrm repo notes. Need to revisit that...

Also a couple of questions:

Do we notify translators before a patch release? (i.e., should I send
out an email as described in #notify-translators [3]?)

I need to guesstimate the release date. If I can get to the point of
rolling tarballs within the next few days, how much time will be needed
by those who plan to test?

Thanks,
Nathan

[1] 
https://subversion.apache.org/docs/community-guide/community-guide.html#release-creating

[2] https://github.com/markphip/svnrm

[3] 
https://subversion.apache.org/docs/community-guide/community-guide.html#notify-translators

Reply via email to