gregsohl Posted April 27, 2012 Report Share Posted April 27, 2012 I have a question and some concerns about how users are to learn of new PlasticSCM releases. Clearly you and your user base are excited about the 4.1 release. It is huge and very nice. Yet as far as I can see, there is yet to be a blog post, an announcements forum entry or a tweet about its release earlier this week. Today, there is a release in the downloads area (Version 4.1.10.268) which is one newer than I downloaded earlier in the week. There are no release notes for this release. The latest release notes are for Version 4.1.10.267. Was 268 not important enough to tell users about? So here's the question (I said I had one). What am I missing? How are we to learn of your great work? Whoops, that was two questions. It's not enough to just write great software folks. Don't forget the other stuff too. (I'm not just talking to Codice about that everyone. This goes for all our industry!) BTW, my evaluation of SCCM systems is now complete. Plastic is my recommendation. That is an almost certainty of adoption. My interest in the type of thing I'm asking about above (along with many of the details I've previously written about) is now heightened. As I've said, I'm a fan and pulling for your success. Thanks. Greg Link to comment Share on other sites More sharing options...
gregsohl Posted April 30, 2012 Author Report Share Posted April 30, 2012 Ahhh. Finally a tweet today and the web site is updated. The What's New page looks great. Link to comment Share on other sites More sharing options...
manu Posted May 2, 2012 Report Share Posted May 2, 2012 It's not enough to just write great software folks. Don't forget the other stuff too. (I'm not just talking to Codice about that everyone. This goes for all our industry!) We are starting about taking care of this stuff too :S We are a really small (but strong!!!) team and sometimes is hard to manage the resources... Link to comment Share on other sites More sharing options...
carpediemevive Posted May 2, 2012 Report Share Posted May 2, 2012 We are starting about taking care of this stuff too :S We are a really small (but strong!!!) team and sometimes is hard to manage the resources... I feel your pain Manu! I've found that not only software development can be iterative but so can these more business type things. Link to comment Share on other sites More sharing options...
psantosl Posted May 11, 2012 Report Share Posted May 11, 2012 Yes guys, you're right. We should do a better job promoting the new releases. What happened with 4.1 was sort of interesting, anyway: we were waiting for the 4.1 landing page to be ready like 3 weeks or so... which, you know, is not very normal because normally is the software itself the one which is not ready... We wanted to get it properly launched with landing and everything, then we didn't do the tweet, although our PR firm sent the press release to the media, but maybe it didn't arrive to you... :'( We're trying to keep people informed using twitter @plasticscm and there now I'm even telling about the features we're implementing on each SPRINT. We'll try to be more active from now on. We need help from you retweeting and making noise when we release new stuff, of course! Link to comment Share on other sites More sharing options...
gregsohl Posted May 14, 2012 Author Report Share Posted May 14, 2012 Thanks for the response! I'm glad you'll be putting some emphasis on communication. I didn't really get a clear answer to my base question though: What is/are the way(s) for users to learn of the posting of a new build? Twitter is good but tweets scroll off before they get read sometimes. Link to comment Share on other sites More sharing options...
manu Posted May 15, 2012 Report Share Posted May 15, 2012 I'm afraid that now we only publish it on Twitter, and not always.... We can discuss about the best way to do it: 1) Mailing Sometimes users are upset about this because they feel they are getting SPAM. 2) Forum post This is my favorite, but sometimes you don't realize about the new topic created... 3) Webinars This is great but we need also get known to have more attenders. 4) Twitter We have to do it always and we need retweeting. 5) Facebook The same as Twitter but with "Shares". Link to comment Share on other sites More sharing options...
gregsohl Posted May 15, 2012 Author Report Share Posted May 15, 2012 My thoughts: 1. Mailing - As long as it is Opt-In with easy Opt-out you should not have any worries 2. Forum Post - A user can "Follow" the announcements forum, which will provide them with notifications. This makes it a great replacement for #1 too. This would be the best option to me. 3. Webinars - Not as a release announcement mechanism. 4. Twitter - Yes, yes, yes. If you use @PlasticSCM you probably should be following @PlasticSCM. 5. Facebook - Not in the office. Link to comment Share on other sites More sharing options...
Soho Posted May 16, 2012 Report Share Posted May 16, 2012 Please make a forum announcement when a new release is available for download. Link to comment Share on other sites More sharing options...
Olaf Kober Posted May 16, 2012 Report Share Posted May 16, 2012 +1 for forum announcement Link to comment Share on other sites More sharing options...
manu Posted May 17, 2012 Report Share Posted May 17, 2012 As I said it's my favorite one. I'll start posting the release announcements from today. I'll be also posting the release notes. Link to comment Share on other sites More sharing options...
gregsohl Posted June 6, 2012 Author Report Share Posted June 6, 2012 Doesn't look like this process is in place yet. There have been 3 external releases since the 17th and no posts in Announcements for them yet. Link to comment Share on other sites More sharing options...
manu Posted June 7, 2012 Report Share Posted June 7, 2012 Sorry, extremely hard work weeks... I'll try to be more active publishing the new releases in the forum. Link to comment Share on other sites More sharing options...
gregsohl Posted June 18, 2012 Author Report Share Posted June 18, 2012 We are very excited about the new release Version 4.1.10.296 (2012.06.13). Or we would be, if 1. We knew about it through a release announcement, and 2. There were some release notes for it. Please, please tell us about all your great work! Greg Link to comment Share on other sites More sharing options...
psantosl Posted June 18, 2012 Report Share Posted June 18, 2012 Hi Greg, Sorry for the inconveniences. Please, find here a copy of the notes from the latest releases</p> External Release 4.1.10.296 (Jun 14th 2012) ==================================================== New New log added to replica; it is now able to dump trees on source and destination. In order to enable it: <logger name="ReplicationTree"> <level value="INFO" /> </logger> External Release 4.1.10.295 (Jun 14th 2012) ==================================================== New Branch layout in the Branch Explorer has been optimized for cases with many small and contiguous branches. New GUI: During checkin, if non-conflicting changes are present on the workspace branch, the user can now automatically update before checking changes in. Before, the Platic SCM GUI required the user to manually merge the head of the branch to the workspace and then check in the changes. Bug Code review: Null fixed when closing the Code Review dialog just after being opened, if the controls have been disposed when they are not loaded yet. Bug Fast-export: It has been modified to support special characters in branches, labels and owner names (author/commiter). Fast-import command has been also modified to use only UTF8 to avoid encoding problems. External Release 4.1.10.290 (Jun 03th 2012) ==================================================== New cm ls is now able to list GUIDs and also list changeset trees by GUID. External Release 4.1.10.283 (May 26th 2012) ==================================================== Performance Fixed memory leak in the GUI under some circumstances with items-based views (like browse branch or changeset content). Performance Save the last used changesets when shutting down the Plastic server. This way they are loaded faster in the next startup. Bug The replica could assign wrong GUID's to some revisions if some of them could not been calcutated. Fixed. Bug Update operation stopped when a file pointed by a controlled symlink that was deleted in the old selector already existed on disk and the "Set repository dates on update" option was set in the client configuration. Fixed. Bug Clients were hanging randomly due to an incorrectly released buffer on the channel layer. This was noticeable when browsing repositories. Fixed. Bug When the client was configured in User Password authentication mode and was trying to connect to a server running in LDAP authentication mode, in Windows asked for credentials, which is right, but in Linux was retrieving an "authentication methods are different" error. Fixed: The problem was that Mono deserializes the method response of the server in a different way than .NET does. Now both types of messages are correctly managed. Bug GUI: Labels view was not sorting labels by changeset number. The list was sorted by label name instead. Fixed. Bug Replica: Creating a replication package failed with the error: "Trying to use a previously finished transaction. Invalid transaction found. Aborting operation", when the branch to be replicated was very big. Fixed. Bug Replica: Added more log to the server to check the inner exception when executing database commands. Bug Fast export: Initial export from Plastic to Git failed, because the initial mark was not declared. Fixed. Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.