All,
The eventual release of R14 will mark a turning point in Trinity history. The R14 release is significant because of the many class and branding renaming changes. While we have drafted a README document to explain such changes, we have no mechanism for users to read the document.
I would like to see us patch the sources such that a Release Notes document is always placed on the user's desktop when updating to a new release. That practice would continue with maintenance releases too.
While the drafted README for R14.0.0 lists many changes, subsequent copies would only list bug and security fixes in that release and will not be large documents.
Of course, the user is free to delete the document from the desktop at any time. The document reappears on the desktop only with new releases.
We would need to update the document before officially releasing each subsequent release, but this simple mechanism would ensure users are updated with changes.
Thoughts?
Darrell
On 01/17/2014 12:26 PM, Darrell Anderson wrote:
All,
The eventual release of R14 will mark a turning point in Trinity history. The R14 release is significant because of the many class and branding renaming changes. While we have drafted a README document to explain such changes, we have no mechanism for users to read the document.
I would like to see us patch the sources such that a Release Notes document is always placed on the user's desktop when updating to a new release. That practice would continue with maintenance releases too.
Darrell,
I usually always agree with you, but here I don't. It absolutely burns me up when an install places things on my desktop that I haven't told it to put there and I don't want. I just think of windows and all the worthless links you had to delete off the desktop just to see a clean desktop.
I agree it would be good to give that information to users on install, but can't we find a better place for it? Why not do it in:
a small systray app that is run on first use after install; or a button in the about:tde dialog access from every help menu; or as an entry in tmenu -> README - R14 Release (opening in kwrite)
Anything, I mean anything, except a whopping big icon planted on the desktop
Thoughts?
You asked ;-)
Where else do you think we could put it that would accomplish what you are trying to do?
On Fri, 17 Jan 2014 17:40:20 -0600 "David C. Rankin" drankinatty@suddenlinkmail.com wrote:
On 01/17/2014 12:26 PM, Darrell Anderson wrote:
All,
The eventual release of R14 will mark a turning point in Trinity history. The R14 release is significant because of the many class and branding renaming changes. While we have drafted a README document to explain such changes, we have no mechanism for users to read the document.
I would like to see us patch the sources such that a Release Notes document is always placed on the user's desktop when updating to a new release. That practice would continue with maintenance releases too.
Darrell,
I usually always agree with you, but here I don't. It absolutely burns me up when an install places things on my desktop that I haven't told it to put there and I don't want. I just think of windows and all the worthless links you had to delete off the desktop just to see a clean desktop.
I agree it would be good to give that information to users on install, but can't we find a better place for it? Why not do it in:
a small systray app that is run on first use after install; or a button in the about:tde dialog access from every help menu; or as an entry in tmenu -> README - R14 Release (opening in kwrite)
Anything, I mean anything, except a whopping big icon planted on the desktop
Thoughts?
You asked ;-)
Where else do you think we could put it that would accomplish what you are trying to do?
A handbook entry or plain webpage, optionally force-opening it in Konqueror the first time a user logs into a new version of TDE? I know that the handbook is the first place I would probably look for the release notes if I wanted them and had no access to the website.
I agree with David on not liking random things placed on my desktop--it disrupts my icon grouping and I would probably junk an involuntarily installed icon without checking to see what it did.
E. Liddell
-
Darrell Anderson -
David C. Rankin -
E. Liddell