Closed
Bug 1153351
Opened 10 years ago
Closed 10 years ago
Move Firefox for Android release notes to /firefox/android/
Categories
(www.mozilla.org :: Information Architecture & UX, enhancement)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: kohei, Assigned: kohei)
References
(Blocks 1 open bug, )
Details
(Whiteboard: [kb=1717464] )
Attachments
(1 file)
Currently those notes are still under /mobile/. Given Firefox OS and upcoming Firefox for iOS, I think it might better to have them under /firefox/android/. Also, the "View notes for" switcher on the relnotes should say Android instead of Mobile.
Assignee | ||
Updated•10 years ago
|
Summary: Move Firefox for Android release notes to /firefox/android/ → Move Firefox for Android release notes from /mobile/ to /firefox/android/
Assignee | ||
Updated•10 years ago
|
Whiteboard: [kb=1717464]
Comment 1•10 years ago
|
||
+Holly and Josh for any thoughts.
Flags: needinfo?(jmize)
Flags: needinfo?(hhabstritt.bugzilla)
Comment 2•10 years ago
|
||
I think that the URL recommendation from Kohei will work well. However, we may want the "View notes for:" picker to be able to contain more than 2 products. (Android, iOS, Desktop... and OS too?) So that would move us away from the toggle/switcher to a dropdown menu for now.
For a broader, consistent solution for all release notes, it would be great to have a similar URL structure for all release notes.
/firefox/[product]/[version #]/releasenotes/
(i.e.,https://www.mozilla.org/firefox/29.0/releasenotes/)
In the near future I'd like do discuss if it makes sense to have the version number at this level in the URI or at least have /[product]/releasenotes/ redirect to the latest version.
Just an FYI for those cc'd on this bug that we plan to work on a new design for the release notes pages which can address a better "switcher" UI and navigation at that time.
Flags: needinfo?(hhabstritt.bugzilla)
Comment 3•10 years ago
|
||
(In reply to Holly Habstritt Gaal [:Habber] from comment #2)
> I think that the URL recommendation from Kohei will work well. However, we
> may want the "View notes for:" picker to be able to contain more than 2
> products. (Android, iOS, Desktop... and OS too?) So that would move us away
> from the toggle/switcher to a dropdown menu for now.
>
I completely agree with getting rid of the "toggle" design we have now, and look forward to seeing the redesign that eliminates it :)
> For a broader, consistent solution for all release notes, it would be great
> to have a similar URL structure for all release notes.
>
> /firefox/[product]/[version #]/releasenotes/
> (i.e.,https://www.mozilla.org/firefox/29.0/releasenotes/)
>
I also dislike our current URL structure, and agree that it needs more consistency across products. What do you think about moving the version to the end, and hyphenating release-notes? For example:
/firefox/release-notes/38.1
/firefox/android/release-notes/38.1
/firefox/ios/release-notes/38.1
/firefox/os/release-notes/2.0
/thunderbird/release-notes/31.6
> In the near future I'd like do discuss if it makes sense to have the version
> number at this level in the URI or at least have /[product]/releasenotes/
> redirect to the latest version.
If we go with my suggestion above of moving the version to the end, I think leaving the version number off should 302 redirect you to the latest version:
/firefox/release-notes -> /firefox/release-notes/38.1
/firefox/android/release-notes -> /firefox/android/release-notes/38.1
/firefox/ios/release-notes -> /firefox/ios/release-notes/38.1
/firefox/os/release-notes -> /firefox/os/release-notes/2.0
/thunderbird/release-notes -> /thunderbird/release-notes/31.6
This is, however, a much larger change than originally suggested, and I'm perfectly fine with restricting ourselves to the more modest changes proposed in comment #0.
Flags: needinfo?(jmize)
Comment 4•10 years ago
|
||
(In reply to Josh Mize [:jgmize] from comment #3)
> (In reply to Holly Habstritt Gaal [:Habber] from comment #2)
> > I think that the URL recommendation from Kohei will work well. However, we
> > may want the "View notes for:" picker to be able to contain more than 2
> > products. (Android, iOS, Desktop... and OS too?) So that would move us away
> > from the toggle/switcher to a dropdown menu for now.
> >
> I completely agree with getting rid of the "toggle" design we have now, and
> look forward to seeing the redesign that eliminates it :)
>
> > For a broader, consistent solution for all release notes, it would be great
> > to have a similar URL structure for all release notes.
> >
> > /firefox/[product]/[version #]/releasenotes/
> > (i.e.,https://www.mozilla.org/firefox/29.0/releasenotes/)
> >
>
> I also dislike our current URL structure, and agree that it needs more
> consistency across products. What do you think about moving the version to
> the end, and hyphenating release-notes? For example:
>
> /firefox/release-notes/38.1
> /firefox/android/release-notes/38.1
> /firefox/ios/release-notes/38.1
> /firefox/os/release-notes/2.0
> /thunderbird/release-notes/31.6
>
> > In the near future I'd like do discuss if it makes sense to have the version
> > number at this level in the URI or at least have /[product]/releasenotes/
> > redirect to the latest version.
>
> If we go with my suggestion above of moving the version to the end, I think
> leaving the version number off should 302 redirect you to the latest version:
>
> /firefox/release-notes -> /firefox/release-notes/38.1
> /firefox/android/release-notes -> /firefox/android/release-notes/38.1
> /firefox/ios/release-notes -> /firefox/ios/release-notes/38.1
> /firefox/os/release-notes -> /firefox/os/release-notes/2.0
> /thunderbird/release-notes -> /thunderbird/release-notes/31.6
>
>
> This is, however, a much larger change than originally suggested, and I'm
> perfectly fine with restricting ourselves to the more modest changes
> proposed in comment #0.
Let's stick with the changes suggested in comment #0 that are mandatory for the 38.1 launch since they are a quicker fix. We can discuss the URL structure updates with :lmandel on May 4th in the larger redesign conversation. Regardless, +1 to your URL suggestions.
Assignee | ||
Comment 5•10 years ago
|
||
How about following the current Firefox OS release notes saying just "notes" in the URLs? And desktop release notes can be moved as well, like this:
/firefox/desktop/notes/[version]/ (no longer say releasenotes nor auroranotes)
/firefox/android/notes/[version]/
/firefox/os/notes/[version]/
/firefox/ios/notes/[version]/
/thunderbird/notes/[version]/
Summary: Move Firefox for Android release notes from /mobile/ to /firefox/android/ → Redesign release notes URL structure
Comment 6•10 years ago
|
||
(In reply to Holly Habstritt Gaal [:Habber] from comment #4)
> (In reply to Josh Mize [:jgmize] from comment #3)
> > (In reply to Holly Habstritt Gaal [:Habber] from comment #2)
> > > I think that the URL recommendation from Kohei will work well. However, we
> > > may want the "View notes for:" picker to be able to contain more than 2
> > > products. (Android, iOS, Desktop... and OS too?) So that would move us away
> > > from the toggle/switcher to a dropdown menu for now.
> > >
> > I completely agree with getting rid of the "toggle" design we have now, and
> > look forward to seeing the redesign that eliminates it :)
> >
> > > For a broader, consistent solution for all release notes, it would be great
> > > to have a similar URL structure for all release notes.
> > >
> > > /firefox/[product]/[version #]/releasenotes/
> > > (i.e.,https://www.mozilla.org/firefox/29.0/releasenotes/)
> > >
> >
> > I also dislike our current URL structure, and agree that it needs more
> > consistency across products. What do you think about moving the version to
> > the end, and hyphenating release-notes? For example:
> >
> > /firefox/release-notes/38.1
> > /firefox/android/release-notes/38.1
> > /firefox/ios/release-notes/38.1
> > /firefox/os/release-notes/2.0
> > /thunderbird/release-notes/31.6
> >
> > > In the near future I'd like do discuss if it makes sense to have the version
> > > number at this level in the URI or at least have /[product]/releasenotes/
> > > redirect to the latest version.
> >
> > If we go with my suggestion above of moving the version to the end, I think
> > leaving the version number off should 302 redirect you to the latest version:
> >
> > /firefox/release-notes -> /firefox/release-notes/38.1
> > /firefox/android/release-notes -> /firefox/android/release-notes/38.1
> > /firefox/ios/release-notes -> /firefox/ios/release-notes/38.1
> > /firefox/os/release-notes -> /firefox/os/release-notes/2.0
> > /thunderbird/release-notes -> /thunderbird/release-notes/31.6
> >
> >
> > This is, however, a much larger change than originally suggested, and I'm
> > perfectly fine with restricting ourselves to the more modest changes
> > proposed in comment #0.
>
> Let's stick with the changes suggested in comment #0 that are mandatory for
> the 38.1 launch since they are a quicker fix. We can discuss the URL
> structure updates with :lmandel on May 4th in the larger redesign
> conversation. Regardless, +1 to your URL suggestions.
+1 to all of this! Let's move forward with the suggestion in comment 0 for the iOS release and combine the larger changes to the URL structure with any redesign work.
Thanks for the good discussion everyone!
Assignee | ||
Comment 7•10 years ago
|
||
Looks like I pushed the button first ;-) Then I'll change just the URL of the Android version relnotes for now. PR coming.
Assignee: nobody → kohei.yoshino
Status: NEW → ASSIGNED
Summary: Redesign release notes URL structure → Move Firefox for Android release notes from /mobile/ to /firefox/android/
Assignee | ||
Comment 8•10 years ago
|
||
Is that okay to move desktop release notes to /firefox/desktop/ as well to make my PR simpler?
/firefox/ -> /firefox/desktop/
/mobile/ -> /firefox/android/
No other changes for now.
Comment 9•10 years ago
|
||
Not sure if this was very clear, but there is one amendment to the suggestion in comment #0. We need to change the "View notes for:" picker. Since the toggle only allows for 2 options, we'll need to make it a dropdown for now. Can we put all products in this picker or stick to Desktop, Android, iOS? (it doesn't solve for the other channel release notes, but we can solve for that at another time)
Assignee | ||
Comment 10•10 years ago
|
||
That switcher assumes that each version is released at (almost) the same time. Will the Firefox for iOS release cycle and versioning be the same as other platforms?
Assignee | ||
Comment 11•10 years ago
|
||
I think the switcher can be modified as part of Bug 1152909.
Component: General → Information Architecture & UX
Summary: Move Firefox for Android release notes from /mobile/ to /firefox/android/ → Move Firefox release notes to /firefox/desktop/ and /firefox/android/
Assignee | ||
Comment 12•10 years ago
|
||
Assignee | ||
Comment 13•10 years ago
|
||
From today's triage meeting: we'll change the Android relnotes only as I initially suggested.
Summary: Move Firefox release notes to /firefox/desktop/ and /firefox/android/ → Move Firefox for Android release notes to /firefox/android/
Comment 14•10 years ago
|
||
Commits pushed to master at https://github.com/mozilla/bedrock
https://github.com/mozilla/bedrock/commit/1b1a295c08fb6bc39fe72e33001cb03f5ed0ab09
Fix Bug 1153351 - Move Firefox for Android release notes to /firefox/android/
https://github.com/mozilla/bedrock/commit/b93bf4dca63fa34472272b04d99882a5f83625f6
Merge pull request #2906 from kyoshino/bug-1153351-move-relnotes
Fix Bug 1153351 - Move Firefox for Android release notes to /firefox/android/
Updated•10 years ago
|
Status: ASSIGNED → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•