I think we should rm trunk/track/contrib so that the tag matches the archive.
We keep a vendor branch, so the removal of contrib in trunk is "just another local change". (I really dislike tags that differ from the archive; it means the tag is not a true copy of the release) (sounds like we need to toss 0.5, update the change log, and go to 0.6 anyways) Cheers, -g On Mar 11, 2013 5:50 AM, "Ryan Ollos" <[email protected]> wrote: > Hi everyone, > > I would like to initiate the vote for releasing Apache Bloodhound 0.5 > (incubating). > > Please find the change log for this proposed release below: > > * Implemented Bootstrap templates for the repository browser, log viewer > and attachment pages. > * Upgraded Bootstrap to version 2.3.1. > * Upgraded Trac to version 1.0.1. > * Various bug fixes and enhancements. > > * Not fixed for this release: > * No major outstanding issues > > For this release, the archive differs from the tag in that the Trac > "contrib" directory has been removed from the archive. The files > in that directory currently lack license headers. We are working > with the Trac team to clarify the licenses under which the contrib files > are released: > https://issues.apache.org/bloodhound/ticket/273 > > The release candidate artifacts consist of source release as a tar.gz > archive along with the associated MD5 and GPG signature. > These can be found at: > https://dist.apache.org/repos/dist/dev/incubator/bloodhound/ > > The archive is based on the tag: > http://svn.apache.org/viewvc/incubator/bloodhound/tags/0.5-incubating > > Please vote: > [ ] +1 Release this package as Apache Bloodhound 0.5 > [ ] +0 Don't care > [ ] -1 Do not release this package (please explain) > > The vote is open for 72 hours and, if successful, will be followed by a > vote on general@incubator for a further 72 hours. >
