What´s next?

Monday, July 09, 2007 3 Comments


We’ve just released Plastic SCM 1.5 a few days ago, our first big release since the initial 1.0 launch date back in November. We’ve tried to include customers’ requests on the latest release, making Plastic what users expect it to be, or at least that’s what we tried.


Ok, but, what’s next? What are the things you can expect in the coming releases of Plastic SCM?Well, here is a short list of things we’re about to release really, really soon (some of the features are already under testing, I mean, totally finished and just waiting for approval to be published)



  • Jira integration: one of the “already ready” features. Plastic will be fully integrated with the popular Jira defect tracking system. Both a “server side” (on Jira) and a “client side” (being able to get the associated task from Plastic) will be available.

  • CVS and SourceSafe enhanced importers: now a new import wizard will be available, helping users to migrate away from CVS or SourceSafe into Plastic. The current one is command line based, and the new one will provide a GUI too.

  • User/password security based system: most of our users integrate Plastic with a LDAP directory (both ActiveDirectory and OpenLDAP). But, on “popular demand” a new authentication system will be available: a user/password based one. It will help companies not using ActiveDirectory or OpenLDAP and who don’t want to rely on native operating system users, setting up Plastic in their environment. It will be also useful to set up internet-available servers.

  • Enhanced Eclipse integration: we’re working hard to get Plastic fully integrated with Eclipse to help Java developers in their move to Plastic. A new “check out view”, a revisited refactor support and a new toolbar will be published really soon.

  • Independent workspace and repository servers: you'll be able to set up as many rep servers as you need, which is very good for heavy load, and also as many wk servers as required.Performance: yes, performance is always an ongoing work for us...
We've made great improvements to our "solve path" system, which is the one responsible of mapping between revisions and their current locations according to the selector. Well, now detecting changes (downloading data was also quite fast) will be much, much, much faster than before...

Well, the previous ones are the features we already have finished and almost ready to be shipped, but, what are we currently working on for the coming months?



  • Trac integration

  • Subversion importer

  • Smart branching support

  • Distributed development support

  • The workflow system

  • MySQL backend

  • New GUI supporting multiple views and enhacing visualization

Feel free to post comments. :-)

3 comments:

  1. gallifantes to:

    - trac integration
    - subversion importer
    - faster checks

    ReplyDelete
  2. Yes, we'll be implementing the SVN importer in the coming sprints, basically due to popular demand...

    SVN is a huge player in the version control field, but many developers contact us to migrate away from subversion.

    So, yes, we will be hopefuly implementing the importer in the coming weeks

    ReplyDelete