Opened 10 years ago

Closed 10 years ago

#7933 closed defect (fixed)

update copyright years to span 2005--2010

Reported by: mvngu Owned by: mvngu
Priority: major Milestone: sage-4.3.2
Component: documentation Keywords:
Cc: Merged in: sage-4.3.2.rc0
Authors: Minh Van Nguyen Reviewers: Mitesh Patel
Report Upstream: N/A Work issues:
Branch: Commit:
Dependencies: Stopgaps:

Description (last modified by mvngu)

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.

Attachments (4)

README.txt (10.9 KB) - added by mvngu 10 years ago.
README.txt with updated copyright years; based on Sage 4.3.1.alpha2
README.patch (505 bytes) - added by mvngu 10 years ago.
differences between the above updated README.txt and the current one in Sage 4.3.1.alpha2
trac_7933-mac-app.patch (1.8 KB) - added by mvngu 10 years ago.
updated copyright years for the Mac app
trac_7933-doc-builder.patch (698 bytes) - added by mvngu 10 years ago.
apply to sage-main; based on Sage 4.3.1.alpha2

Download all attachments as: .zip

Change History (9)

Changed 10 years ago by mvngu

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

Changed 10 years ago by mvngu

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

comment:1 Changed 10 years ago by mvngu

  • Summary changed from update copyright years to span 2006--2010 to update copyright years to span 2005--2010

Changed 10 years ago by mvngu

updated copyright years for the Mac app

comment:2 Changed 10 years ago by mvngu

  • Description modified (diff)

Changed 10 years ago by mvngu

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

comment:3 Changed 10 years ago by mvngu

  • Authors set to Minh Van Nguyen
  • Status changed from new to needs_review

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.
  3. 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".

comment:4 Changed 10 years ago by mpatel

  • Reviewers set to Mitesh Patel
  • Status changed from needs_review to positive_review

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.

comment:5 Changed 10 years ago by mvngu

  • Merged in set to sage-4.3.2.rc0
  • Resolution set to fixed
  • Status changed from positive_review to closed

Merged as per the above instructions.

Note: See TracTickets for help on using tickets.