Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Report new NVDA versions via rss or other formats #172

Closed
nvaccessAuto opened this issue Jan 1, 2010 · 15 comments

Comments

Projects
None yet
1 participant
@nvaccessAuto
Copy link

commented Jan 1, 2010

Reported by ragb on 2008-09-11 15:27
There are some sites providing links for downloading NVDA snapshots and stable versions, however, mainly in the case of snapshots links become obsulet very quickly.
My suggestion is to implement some kind of RSS/RDF feed, or other similar way, to report new versions to automatic systems. This can also be used to NVDA itself report new versions available to users.

@nvaccessAuto

This comment has been minimized.

Copy link
Author

commented Jan 1, 2010

Comment 1 by jteh on 2008-09-11 22:31
While I agree that we probably do need this for official releases, I'm not so certain we really need it for snapshots. If you're using snapshots, they are basically uploaded daily anyway, so there is little point in a feed. Also, users should be encouraged to be careful when using snapshots. Including changelogs and the like in the feed is also a bit tricky technically speaking.

I'm open to discussion on this one, but I'm going to need some serious convincing.

@nvaccessAuto

This comment has been minimized.

Copy link
Author

commented Jan 1, 2010

Comment 2 by ragb (in reply to comment 1) on 2008-09-12 13:26
Replying to jteh:

While I agree that we probably do need this for official releases, I'm not so certain we really need it for snapshots. If you're using snapshots, they are basically uploaded daily anyway, so there is little point in a feed. Also, users should be encouraged to be careful when using snapshots. Including changelogs and the like in the feed is also a bit tricky technically speaking.

For oficial releases I do think it will be really useful. Regarding snapshots... The fact is that most users that report information and participate in lists about NVDA are using snapshots, even 0.6p2 beeing a stable and recomended release, it seems they preffer new features from stability and our recomendations... I don't know how you are generating the snapshots page so can't expeculate about the technical dificulties of implementing something like a feed for these...

I'm open to discussion on this one, but I'm going to need some serious convincing.

Ok... For oficial releases I think it will be really useful something that notifies the users about new versions. I can help if you want, I'll btry to be on IRC these days so we can talk about this. Regarding snapshots, I'll try to convince you, but I do know that is not a real priority...:)

@nvaccessAuto

This comment has been minimized.

Copy link
Author

commented Jan 1, 2010

Comment 3 by aleksey_s on 2008-09-12 18:22
Uhm, isn't there rss translation for the nvda blog? The announces for the new nvda releases will be posted here.

@nvaccessAuto

This comment has been minimized.

Copy link
Author

commented Jan 1, 2010

Comment 4 by ragb (in reply to comment 3) on 2008-09-12 18:48
Replying to aleksey_s:

Uhm, isn't there rss translation for the nvda blog? The announces for the new nvda releases will be posted here.

Yes there is an RSS feed, but my idea is to get some kind of more automatic notification, so nVDA itself or possibly other sites or applications can notify the user and provide automaticly links to upgrade. Maby I was not clear explaining the idea... I thought about RSS but any other format (possibly simpler) would work.

@nvaccessAuto

This comment has been minimized.

Copy link
Author

commented Jan 1, 2010

Comment 5 by tbd on 2008-09-12 19:11
Could it be usefull if NVDA could update itself or the user could choose to search for updates such as the latest snapshots or the latest officialy release?

@nvaccessAuto

This comment has been minimized.

Copy link
Author

commented Jan 1, 2010

Comment 6 by aleksey_s (in reply to comment 4) on 2008-09-13 07:00
Replying to ragb:
becouse nvda official releases aren't so often, as well as many users who have interest in nvda are subscribed to the nvda users list or rss, i thing yet another system isn't needed. right now all who want this can receive info about nvda news quickly.

@nvaccessAuto

This comment has been minimized.

Copy link
Author

commented Jan 1, 2010

Comment 7 by aleksey_s (in reply to comment 5) on 2008-09-13 07:08
Replying to tbd:
hovewer, it is separate ticket. and thus ticket already exists, and developers already expressed their opinion on this (nvda automatic updates feature).
As initial request was about rss translation of new nvda releases, and such possibility is alive, i thing ticket can be closed as wantfix.

@nvaccessAuto

This comment has been minimized.

Copy link
Author

commented Jan 1, 2010

Comment 8 by ragb (in reply to comment 6) on 2008-09-13 12:24
Replying to aleksey_s:

Replying to ragb:

becouse nvda official releases aren't so often, as well as many users who have interest in nvda are subscribed to the nvda users list or rss, i thing yet another system isn't needed. right now all who want this can receive info about nvda news quickly.

You're right, but for users that don't speak english the information is not so accessible. I'm saying this because in NVDA's portuguese list I and Diogo (the other portuguese translator) are constantly translating information to and from users... My suggestion was not really the automatic upgrade thing, but the automatic notification. If we provide notifications in an neutral language format it will be really easier at least for news translators! I'm not saying that we most provide translations of changelogs for exampple, that would be rather useless for most users (unhappyly most users that use snapshots don't even read them) but for links it could be done. That was just an idea, nothing NVDA must provide to keep it alive :).

@nvaccessAuto

This comment has been minimized.

Copy link
Author

commented Jan 1, 2010

Comment 9 by ragb on 2008-09-13 12:32
I didn't remeber ticket #73, my initial idea (at least for snapshots) was just the notificaitions part.. Sorry for any dupplication.

@nvaccessAuto

This comment has been minimized.

Copy link
Author

commented Mar 4, 2010

Comment 10 by jteh on 2010-03-04 11:53

  • Trac already provides rss feeds for changelogs. For example, see log:main?format=rss.
  • Commit notifications are also sent to the nvda-dev list.
  • You can query the latest snapshot for the main branch using http://www.nvda-project.org/snapshots/main/.last_snapshot
    Does this satisfy this ticket?
@nvaccessAuto

This comment has been minimized.

Copy link
Author

commented Mar 5, 2010

Comment 11 by ragb (in reply to comment 10) on 2010-03-05 01:23
Replying to jteh:

Does this satisfy this ticket?

I think so... you could provide a file like .last_snapshot for oficial releases with release name (like 2009.1 or something) but because there are fiew releases, for what I use, I can update it manually.

@nvaccessAuto

This comment has been minimized.

Copy link
Author

commented May 10, 2010

Comment 12 by mdcurran on 2010-05-10 07:29
Can this ticket be closed? or were we interested in a .last-release file?

@nvaccessAuto

This comment has been minimized.

Copy link
Author

commented May 10, 2010

Comment 13 by jteh on 2010-05-10 10:30
The rss feed for the !NewReleases blog category can be used for releases. The data will only need to be parsed very slightly. See http://www.nvda-project.org/blog/category/NewReleases?format=rss
If we get an auto update system, we probably want a quicker way even so, so leaving open for now.
Changes:
State: closed

@nvaccessAuto

This comment has been minimized.

Copy link
Author

commented May 10, 2010

Comment 14 by jteh on 2010-05-10 10:30
Err, leaving open really...
Changes:
State: reopened

@nvaccessAuto

This comment has been minimized.

Copy link
Author

commented May 23, 2012

Comment 15 by Q on 2012-05-23 07:14
Closing this ticket as the functionality has been superseded by NVDA's automatic update mechanism coupled with release announcements on the Blog, Twitter, and mailing lists.
Changes:
State: closed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.