Closed
Bug 1449884
Opened 7 years ago
Closed 7 years ago
Add a RSS feed on the list of releases
Categories
(www.mozilla.org :: Release notes, enhancement)
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 1366651
People
(Reporter: Sylvestre, Unassigned)
Details
Would be great to have an rss feed to list the new versions:
https://www.mozilla.org/en-US/firefox/releases/
Reporter | ||
Comment 1•7 years ago
|
||
Kohei, is that something you would help with? Thanks
Flags: needinfo?(kohei.yoshino)
Reporter | ||
Comment 3•7 years ago
|
||
ESR are on this page too. Maybe we should have them in a separate feed.
For Thunderbird, maybe it will benefit of the change easily:
https://www.mozilla.org/en-US/thunderbird/releases/
Comment 5•7 years ago
|
||
Do we need a feed just for a version list? I think the product-details data is enough for most use cases. I've filed Bug 1366651 for per-channel release note feeds, which might be more useful.
Flags: needinfo?(kohei.yoshino)
Yest just number version (52.x.1, 52.x2, 52.x.3) to be warned when new version (subversion) was release
Reporter | ||
Comment 7•7 years ago
|
||
Using product-details requires creating some tooling to be notified with new versions when RSS is designed for this.
We could also generate a RSS on p-d. Pascal, what do you think?
Flags: needinfo?(pascalc)
Comment 8•7 years ago
|
||
(In reply to Sylvestre Ledru [:sylvestre] from comment #7)
> Using product-details requires creating some tooling to be notified with new
> versions when RSS is designed for this.
> We could also generate a RSS on p-d. Pascal, what do you think?
I would be in favor of having it on product-details so as to not add unnecessary complexity to mozilla.org which is more consumer focused. maybe a firefox_versions.xml alongside firefox_versions.json
Flags: needinfo?(pascalc)
Comment 9•7 years ago
|
||
I thought Mozilla basically didn't want end users to be aware of minor releases in favour of the auto update functionality. This kind of detailed information may be against the strategy.
On the other hand, transparency is also important as an open source community. That's why every single release comes with the release notes as well as security advisories, if applicable, published in a timely manner.
I still think it's reasonable to provide release notes feeds as described in Bug 1366651. It will actually contain version numbers so this bug's request can also be fulfilled.
Comment 10•7 years ago
|
||
... so I'd suggest marking this bug as a dup of Bug 1366651.
Reporter | ||
Comment 11•7 years ago
|
||
(In reply to Kohei Yoshino [:kohei] from comment #9)
> I thought Mozilla basically didn't want end users to be aware of minor
> releases in favour of the auto update functionality. This kind of detailed
> information may be against the strategy.
I am not sure where you get this information but we have been doing release for dot releases for quite sometimes.
Product details also contains this information.
> I still think it's reasonable to provide release notes feeds as described in
> Bug 1366651. It will actually contain version numbers so this bug's request
> can also be fulfilled.
This is different issue.
Here, it is just about getting a RSS feed to be informed about new versions.
Bug 1366651 is about release notes.
Or am I missing a point?
Reporter | ||
Comment 12•7 years ago
|
||
OK, I did miss a point, pascal explained me with this example:
{
'59.0.2': {blablareleasenotes},
'59.0.1': {blablareleasenotes},
'59.0': {blablareleasenotes}
}
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•