Closed Bug 410140 Opened 16 years ago Closed 16 years ago

Update calendar copyright dates to 2008

Categories

(Calendar :: General, defect)

Product:
Calendar
Component:
General
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
VERIFIED FIXED

People

(Reporter: philor, Assigned: mschroeder)

Details

Attachments

(3 files, 1 obsolete file)

[checked in] Patch v1 (Trunk)
5.14 KB, patch
dbo
: review+
Details | Diff | Splinter Review
[checked in] Patch v1 (Branch)
6.01 KB, patch
dbo
: review+
Details | Diff | Splinter Review
Updated patch (Branch-l10n)
32.56 KB, patch
mschroeder
: review+
Details | Diff | Splinter Review 
+++ This bug was initially created as a clone of Bug #365765 +++

After all, think how badly people would fail to be funny in the bugs they will file on 2008-01-01 if the nightly "of a _Calendar_ application!!1!" doesn't have the new year in the various and sundry copyright statements.
Flags: blocking-calendar0.8?
Assignee: nobody → mschroeder
Update copyright dates to 2008.
Attachment #294824 - Flags: review?(daniel.boelzle)
Status: NEW → ASSIGNED
Version: Trunk → unspecified
Update copyright dates to 2008.
Attachment #294825 - Flags: review?(daniel.boelzle)
It would be good if someone with the corresponding access rights could update all aboutDialog.dtd l10n files too. This would be easier than contacting each l10n team separately.
Comment on attachment 294824 [details] [diff] [review]
[checked in] Patch v1 (Trunk)

r=dbo
Attachment #294824 - Flags: review?(daniel.boelzle) → review+
Comment on attachment 294825 [details] [diff] [review]
[checked in] Patch v1 (Branch)

r=dbo
Attachment #294825 - Flags: review?(daniel.boelzle) → review+
(In reply to comment #3)
Yes, makes sense. Martin, would you mind to create a patch? If your cvs access doesn't cover l10n, I could check it in.
Attachment #294824 - Attachment description: Patch v1 (Trunk) → [checked in] Patch v1 (Trunk)
Attachment #294825 - Attachment description: Patch v1 (Branch) → [checked in] Patch v1 (Branch)
(In reply to comment #6)
> (In reply to comment #3)
> Yes, makes sense. Martin, would you mind to create a patch?

I'll create a patch.

Simon, can you commit it to /l10n? Maybe we should inform the localizers about this change.
Target Milestone: --- → 0.8
Attached patch Patch v1 (Branch-l10n) (obsolete) — — Splinter Review 

        Attachment #295224 -
        Flags: review?(bugzilla)

    
    

    
  
Simon, do I need to create an additional Trunk-l10n patch, or can you apply my Branch-l10n patch where possible to Trunk-l10n?
Flags: blocking-calendar0.8? → blocking-calendar0.8+

    
    

    
  
Simon, please review the patch, so ause could check it in.

    
    

    
  
Comment on attachment 295224 [details] [diff] [review]
Patch v1 (Branch-l10n)

r=sipaq

Martin, I would appreciate it however, if you could put up a new patch for checkin as s few locales have already made that change on their own.

So we don't want to risk messing around with their locale.

        Attachment #295224 -
        Flags: review?(bugzilla) → review+

    
    

    
  


  
carrying over review from "Patch v1 (Branch-l10n)"

        Attachment #295224 -
        Attachment is obsolete: true

        Attachment #297345 -
        Flags: review+

    
    

    
  
commit done for 1.8 branch and trunk

    
    

    
  
Comment on attachment 297345 [details] [diff] [review]
Updated patch (Branch-l10n)

Checked in on HEAD and MOZILLA_1_8_BRANCH

-> FIXED

    
  
Status: ASSIGNED → RESOLVED
Closed: 16 years ago
Resolution: --- → FIXED

    
  
Status: RESOLVED → VERIFIED

          You need to log in
          before you can comment on or make changes to this bug.