Closed Bug 355295 Opened 13 years ago Closed 13 years ago

Upload Lightning 0.3 release notes

Categories

(Calendar :: Website, defect)

defect
Not set

Tracking

(Not tracked)

RESOLVED FIXED
Lightning 0.3

People

(Reporter: mattwillis, Assigned: mattwillis)

Details

Attachments

(2 files)

Sister bug to bug 355294.

Create and upload Lightning's release notes.
Assignee: nobody → lilmatt
Flags: blocking0.3+
Status: NEW → ASSIGNED
Same deal as the Sunbird ones.
We'll need to change the URL in Lightning's install.rdf
Attachment #241116 - Flags: first-review?(bugzilla)
Comment on attachment 241116 [details]
Lightning release notes HTML

Um... just ignore the 5 absolute-URLed css lines at the top. Those were just for testing and shouldn't have made it into the file.
Since we're using separate relnotes now, here's the fix to install.rdf for inclusion in 0.3rc2.

Note to self: HAND MERGE THIS when committing. Don't use cross-commit.
Attachment #241146 - Flags: first-review?(dmose)
Comment on attachment 241146 [details] [diff] [review]
patch to install.rdf to change relnotes url (checked in)

r=dmose
Attachment #241146 - Flags: first-review?(dmose) → first-review+
Comment on attachment 241146 [details] [diff] [review]
patch to install.rdf to change relnotes url (checked in)

Patch checked in on MOZILLA_1_8_BRANCH, SUNBIRD_0_3_BRANCH, and trunk
Attachment #241146 - Attachment description: patch to install.rdf to change relnotes url → patch to install.rdf to change relnotes url (checked in)
Comment on attachment 241116 [details]
Lightning release notes HTML

General note:
Please use a consistent indenting style. I mostly used 1-space-indenting and 
sometimes 2-space indenting. Please try to match that throughout the file.

><link rel="stylesheet" type="text/css" href="http://www.mozilla.org/css/print.css"  media="print">
><link rel="stylesheet" type="text/css" href="http://www.mozilla.org/css/base/content.css"  media="all">
><link rel="stylesheet" type="text/css" href="http://www.mozilla.org/css/cavendish/content.css" title="Cavendish" media="screen">
><link rel="stylesheet" type="text/css" href="http://www.mozilla.org/css/base/template.css"  media="screen">
><link rel="stylesheet" type="text/css" href="http://www.mozilla.org/css/cavendish/template.css" title="Cavendish" media="screen">

As you already said, these lines should not be committed.

>        <style type="text/css">
>        <!--
>            .lightning-releasenotes {
>                background: url("../images/releasenotes-lightning.png") no-repeat;
>                padding-top: 70px !important;
>                width: 100% !important;
>            }
>        -->
>        </style>

Please add these local styles to calendar.css so that we can reuse it for later 
Lightning release notes.

>        <div id="product-desc" class="sunbird-releasenotes">
>          <!-- Introduction -->

We don't need this comment.

>      </div>
>      <!-- What's New -->
>      <h2><a name="new">What's New in Lightning 0.3</a></h2>

Same here.

>      <h2 id="links">Other Resources and Links</h2>
>      <p>The following resources contain useful information about Sunbird:</p>
>      
>      <ul>
>        <li><a href="http://wiki.mozilla.org/Calendar:FAQ">Sunbird Help</a></li>
>        <li><a href="http://wiki.mozilla.org/Calendar:Hacking">Developer Information</a></li>
>      </ul>

s/Sunbird/Lightning

>    </div><!-- close #mainContent -->
>    
>    <div id="side" class="right">
>      <ul id="nav">
>        <li><a href="../">Back to Sunbird Page</a></li>
>      </ul>

s/Sunbird/Lightning

If we put the release notes into the releases directory as we did for 0.1 and 
the Sunbird alpha releases that link will go to the main Calendar Project 
page and not to the Lightning page. Please fix that.

r=sipaq with all review comments fixed.
Attachment #241116 - Flags: first-review?(bugzilla) → first-review+
HTML uploaded to www with nits addressed.

We'll need to fix the date once we release.

-> FIXED
Status: ASSIGNED → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.