Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

update copyright years to span 2005--2010 #7933

Closed
sagetrac-mvngu mannequin opened this issue Jan 15, 2010 · 12 comments
Closed

update copyright years to span 2005--2010 #7933

sagetrac-mvngu mannequin opened this issue Jan 15, 2010 · 12 comments

Comments

@sagetrac-mvngu
Copy link
Mannequin

sagetrac-mvngu mannequin commented Jan 15, 2010

It's that time of the year again when the copyright years for Sage need to be updated to reflect the new year. The copyright years should now span 2005--2010. The Sage wiki contains a page that lists file you need to edit in order to update the copyright years.

Component: documentation

Author: Minh Van Nguyen

Reviewer: Mitesh Patel

Merged: sage-4.3.2.rc0

Issue created by migration from https://trac.sagemath.org/ticket/7933

@sagetrac-mvngu sagetrac-mvngu mannequin added this to the sage-4.3.2 milestone Jan 15, 2010
@sagetrac-mvngu sagetrac-mvngu mannequin self-assigned this Jan 15, 2010
@sagetrac-mvngu
Copy link
Mannequin Author

sagetrac-mvngu mannequin commented Jan 15, 2010

Attachment: README.txt

README.txt with updated copyright years; based on Sage 4.3.1.alpha2

@sagetrac-mvngu
Copy link
Mannequin Author

sagetrac-mvngu mannequin commented Jan 15, 2010

differences between the above updated README.txt and the current one in Sage 4.3.1.alpha2

@sagetrac-mvngu
Copy link
Mannequin Author

sagetrac-mvngu mannequin commented Jan 15, 2010

comment:1

Attachment: README.patch.gz

@sagetrac-mvngu sagetrac-mvngu mannequin changed the title update copyright years to span 2006--2010 update copyright years to span 2005--2010 Jan 15, 2010
@sagetrac-mvngu
Copy link
Mannequin Author

sagetrac-mvngu mannequin commented Jan 15, 2010

Attachment: trac_7933-mac-app.patch.gz

updated copyright years for the Mac app

@sagetrac-mvngu

This comment has been minimized.

@sagetrac-mvngu
Copy link
Mannequin Author

sagetrac-mvngu mannequin commented Jan 16, 2010

Attachment: trac_7933-doc-builder.patch.gz

apply to sage-main; based on Sage 4.3.1.alpha2

@sagetrac-mvngu
Copy link
Mannequin Author

sagetrac-mvngu mannequin commented Jan 16, 2010

Author: Minh Van Nguyen

@sagetrac-mvngu
Copy link
Mannequin Author

sagetrac-mvngu mannequin commented Jan 16, 2010

comment:3

I think the above patches should take care of updating the copyright years. Here's a description of these patches and where to apply them:

  1. The file README.txt should be placed under SAGE_ROOT/. That file is not under revision control, so the release manager needs to replace the current README.txt with the attached updated README.txt. To show the differences between the current README.txt in Sage 4.3.1.alpha2 and the updated README.txt, see the patch file README.patch. Note that this patch is only for showing differences; don't apply it.
  2. The patch trac_7933-mac-app.patch should be applied to the data/ repository under SAGE_ROOT/data/extcode. Before applying that patch, the release manager needs to remove a junk file under that directory:
[mvngu@mod extcode]$ pwd
/dev/shm/mvngu/sage-4.3.1.alpha2/data/extcode
[mvngu@mod extcode]$ hg st
? sage/ext/.DS_Store.rej
[mvngu@mod extcode]$ rm sage/ext/.DS_Store.rej 
[mvngu@mod extcode]$ hg st
<no-output>

After removing the junk file, then apply the patch.

  1. Finally, apply the patch trac_7933-doc-builder.patch to the repository sage-main. This patch affects the configuration file doc/common/conf.py, so the file's corresponding Python byte code file should be removed:
[mvngu@mod common]$ pwd
/dev/shm/mvngu/sage-4.3.1.alpha2/devel/sage-main/doc/common
[mvngu@mod common]$ rm conf.pyc

This ensures that, after the patch is applied, generating the documentation with "./sage -docbuild ..." would first generate a byte code version of the patched doc/common/conf.py file. If the previous byte code file of doc/common/conf.py is not removed, then it's likely that the generated documentation (especially the HTML version) would still use the current copyright years "2005--2009".

@qed777
Copy link
Mannequin

qed777 mannequin commented Jan 31, 2010

Reviewer: Mitesh Patel

@qed777
Copy link
Mannequin

qed777 mannequin commented Jan 31, 2010

comment:4

All three patches apply cleanly.  In particular, they're in line with UpdateCopyright.

Note: I don't have access to a Mac, so I can't test the changes in the extcode patch (if they're testable).

In case someone hasn't already mentioned it: a current copyright year also hints that a project is actively developed.

@sagetrac-mvngu
Copy link
Mannequin Author

sagetrac-mvngu mannequin commented Feb 2, 2010

comment:5

Merged as per the above instructions.

@sagetrac-mvngu
Copy link
Mannequin Author

sagetrac-mvngu mannequin commented Feb 2, 2010

Merged: sage-4.3.2.rc0

@sagetrac-mvngu sagetrac-mvngu mannequin removed the s: positive review label Feb 2, 2010
@sagetrac-mvngu sagetrac-mvngu mannequin closed this as completed Feb 2, 2010
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

0 participants