SlickEdit Community
Archived Beta Discussions => SlickEdit 201x Beta Discussions => SlickEdit 2013 v18 beta => Topic started by: mjdl on June 06, 2013, 06:00:40 PM
-
I'm old school and don't see the point about reviewing my lunch on Twitter ::) but one thing I really do appreciate about Twitter is as a news/announcement/current awareness service. So, can @SlickEdit put a little notice of new betas when they are ready for download at the customer portal?
Another idea would be a separate @SlickEdit-Beta Twitter account which would do the above messages, as well as messages in the format VSDIFF fixed in beta 7 http://bit.ly/122SdVm (http://bit.ly/122SdVm), i.e. maintain a an easily accessible public overview of when beta problems discussed in the forum are ostensibly fixed in a beta.
-
I'll second that. Useful stuff like news, releases, betas, etc. are terribly interesting to this follower, and probably 'most anyone that would follow @SlickEdit.
-
We probably wouldn't use Twitter for 'I just fixed this, see it in the next beta' type announcements, since we already do that on this forum. But we could start tweeting each beta release. (Next of which will be early next week)
-
Well, the fix announcements are scattered all over the forum threads.
But actually I tend agree with you--why complicate communications with customers, announcing the beta releases in the Twitter feed is enough, and the existing forum threads do provide an opportunity to point out when a fix hasn't actually solved a problem. (Perhaps the beta release readme files could provide links to relevant forum threads about the major fixes in each beta, just in order to organize and de-duplicate any further follow-ups from testers.)