Closed Bug 498872 Opened 16 years ago Closed 16 years ago

Version notes header not showing next to version notes

Categories

(addons.mozilla.org Graveyard :: Public Pages, defect, P3)

defect

Tracking

(Not tracked)

VERIFIED FIXED

People

(Reporter: davemgarrett, Assigned: jbalogh)

References

()

Details

Attachments

(2 files)

In the newest layout on preview, the version notes header, "Version x.y.z — date — file size", is showing above the developer comments instead of above the version notes. The whole section is labeled "Release Notes", and the developer comments aren't necessarily entirely that. They're a distinctly separate field from the version/release notes. The version/release notes are used for each update's changelog and the developer comments are often used as a more general set of comments about recent versions, or to give any other information that doesn't belong in the descriptions. Seeing as the version/release notes are per version and the developer comments are not, this layout doesn't make sense. The listed version, date, and file size apply to the latest version and should be next to specific info connected to the latest version. With Flagfox, for example, I have a small FAQ in there along with a note about the recent server change and a locale list. The two line changelog is quite hidden at the bottom of this, and there's nothing indicating that it's a separate field. https://preview.addons.mozilla.org/en-US/firefox/addon/5791
We could probably add a Developer Comments section under Support in More about this add-on.
Assignee: nobody → nnguyen
Can this please be considered for 5.0.7? As it is currently, this means the version notes are mixed into the developer comments and essentially hidden. It's quite messed up like this.
Target Milestone: --- → 5.0.7
(In reply to comment #2) > Can this please be considered for 5.0.7? As it is currently, this means the > version notes are mixed into the developer comments and essentially hidden. > It's quite messed up like this. 5.0.7 is deep into code freeze. I'll throw it in 5.0.8 though which we are triaging early next week.
Target Milestone: 5.0.7 → 5.0.8
I agree with Jeff- Let's just make a separate Developer Comments section
Assignee: nnguyen → lorchard
Target Milestone: 5.0.8 → 5.0.9
Priority: -- → P3
Just saw this bug landed on my queue, but don't understand the issue. Can I get a screenshot marked up or something? Or might Jeff already have a solution from comment 1?
I would explain if I remembered what I was talking about. It's probably easier for me to take this and recall what I thought we should do.
Assignee: lorchard → jbalogh
Attached image Issue as I understand
(In reply to comment #5) > Just saw this bug landed on my queue, but don't understand the issue. Can I > get a screenshot marked up or something? Or might Jeff already have a solution > from comment 1? The attached screenshot hopefully explains what I understand as an issue from Comment 0.
Thank you fcp. That shows it perfectly. As you can see, my version (release) notes are quite small in comparison to the developer comments and get lost down there. These days most Flagfox releases are just routine monthly IPDB updates to keep things accurate. What I've been doing for both my extensions on production is adding "=== Changes In Latest Update ===" to the end of the developer comments to hack a header into existence for the version notes. It works, but I'd like the section to just be properly labeled again in some way like it was previously.
Attachment #393064 - Flags: review?(clouserw)
Attachment #393064 - Flags: review?(clouserw) → review+
Status: NEW → RESOLVED
Closed: 16 years ago
Keywords: push-needed
Resolution: --- → FIXED
I'll let Dave verify this on preview, but it looks good to me; fcp, thanks also for comment 7.
Looks good to me too. The release notes are now sorta buried down there, though that's another issue. Bug 495525 might be good to go along with this. Regardless, this one's verified.
Status: RESOLVED → VERIFIED
Product: addons.mozilla.org → addons.mozilla.org Graveyard
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: