On 04/23/2010 07:38 PM, John Plevyak wrote:
Regarding the copyright change. Since the code
didn't change if we need the copyright changes then
we should just be able to rebuild the package and release
if we get the vote.
A new set of files are on
http://people.apache.org/~zwoop/
-rw-r--r-- 1 zwoop zwoop 70 Apr 24 02:53
trafficserver-2.0.0.tar.bz2.sha1
-rw-r--r-- 1 zwoop zwoop 62 Apr 24 02:53
trafficserver-2.0.0.tar.bz2.md5
-rw-r--r-- 1 zwoop zwoop 2852645 Apr 24 02:53 trafficserver-2.0.0.tar.bz2
-rw-r--r-- 1 zwoop zwoop 836 Apr 24 02:53
trafficserver-2.0.0.tar.bz2.asc
Checksums:
MD5: 4c000131b19bdda05f1f21c6ae0547af trafficserver-2.0.0.tar.bz2
SHA1: 45b4a0b1e8f2917a1b0ee972ed214daf4d946309
trafficserver-2.0.0.tar.bz2
These packages should include John's changes (please verify), and I also
added a link to the "Build" on the CWiki to the INSTALL file.
Consider this the new candidate, there should be no other changes than
those mentioned.
-- leif
P.s
These are the two merged changesets from 2.0.x that are in this new
release candidate:
http://svn.apache.org/viewvc?rev=937578&view=rev
http://svn.apache.org/viewvc?rev=937581&view=rev
Note: the 2.0.0 release candidate is built off tags/2.0.0 in SVN, which
is why I had to merge these two changes on to that tag. I know it might
be frowned upon to merge onto a tag, but until we have the candidate
frozen, it's easier to just merge any 2.0.x branch changes onto the
2.0.0 tag (this is actually a feature I like in SVN). If someone feels
strongly about that, and suggest we make another tag in a situation like
this, just suggest such a "rule".
Of course, once 2.0.0 is released, the 2.0.0 tag should be considered
untouchable. Is there a way to make it read-only? :)
