• If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below.

Announcement

Collapse
No announcement yet.

Source Code only

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Source Code only

    We're looking to have Valence become an integral part of our new development. Towards that end, we need to develop and implement the Valence programs as we do our ERP programs, by using source management and QC testing methodologies. It would be great if we could get only the source code changes that go along with the bug fixes instead of simply releasing a whole new package.

    I can't speak for others, but migrating to new versions and/or applying bug fixes is difficult to implement and even more difficult to track/test the changes. In fact, because versions upgrades are so problematic, it's hard to justify a maintenance agreement with management.

    And files with no DBCS would be greatly appreciated. At least duplicate fields in the files that are not DBCS.

    All that said, Valence is still a good thing because it is so cost effective :-)

  • #2
    Just to follow up from our phone conversation and for the benefit of others who may read this thread, you can indeed get source code only from CNX if you are on a maintenance. The best way to implement change management is to have a "base" Valence instance where all your updates from CNX are applied and then use the Instance Manager to propagate changes to your Dev, QA and Live instances. You can use your own change management anywhere along the way if you like.

    Comment

    Working...
    X