Project

General

Profile

Bug #4681

Check all file properties before release

Added by Derik Barseghian almost 10 years ago. Updated over 9 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
general
Target version:
Start date:
01/20/2010
Due date:
% Done:

0%

Estimated time:
Bugzilla-Id:
4681

Description

See bug#4056 for background.

I think we need to go through all our files before release to make sure the appropriate properties are set, e.g. svn:keywords (do we want to agree to a standard set?) and svn:eol-style.


Related issues

Blocked by Kepler - Bug #4684: Release tracking bugResolved01/21/2010

History

#1 Updated by Chad Berkley over 9 years ago

Which properties should we set? I propose keywords and eol-style as Derik said. Are there any others? I can write a build task to do this.

#2 Updated by Christopher Brooks over 9 years ago

Yep, svn:keywords and svn:style for all files:
bash-3.2$ svn proplist README.txt
Properties on 'README.txt':
svn:keywords
svn:eol-style
bash-3.2$ svn propget svn:keywords README.txt
Author Date Id Revision
bash-3.2$ svn propget svn:eol-style README.txt
native

Executables should probably have svn:executable set

ptII/adm/bin/svnpropcheck might help.
See
http://ptolemy.eecs.berkeley.edu/ptolemyII/ptII8.0/ptII8.0.beta/doc/coding/releasemgt.htm
and

http://chess.eecs.berkeley.edu/ptexternal/wiki/Main/Subversion#KeywordSubstitution

#3 Updated by Chad Berkley over 9 years ago

updated file props for trunk and 2.0. if this is done in the future, do not update keywords for any jar files. this breaks some of them.

#4 Updated by Redmine Admin over 6 years ago

Original Bugzilla ID was 4681

Also available in: Atom PDF