Author Topic: Versioning out to CVS  (Read 984 times)

heffalump

  • EA Novice
  • *
  • Posts: 6
  • Karma: +0/-0
  • I love YaBB 1 Gold!
    • View Profile
Versioning out to CVS
« on: November 11, 2003, 03:53:42 am »
We are running the Corporate edition into a MySQL database, with SCCS provided using Jalindi Igloo into pserver CVS (not just for EA, works fine elsewhere).

I am trying to use version control to save releases. I can create packages into version control and see the XML files turn up in the correct place for CVS. But the Project/Version Control submenu grays out the Set Version Control Options and Start Version Control Explorer once they are set up so they can never be changed or stopped. Further, the browser right-click Package Control submenu has virtually all the options (except Configure, Update Package Status and Set Namespace Root) grayed out. Little seems to work fully.

Am I missing some crucial concept here? Should this work as I expect?

heffalump

  • EA Novice
  • *
  • Posts: 6
  • Karma: +0/-0
  • I love YaBB 1 Gold!
    • View Profile
Addendum: Versioning out to CVS
« Reply #1 on: November 11, 2003, 05:13:49 am »
Would I be better off just Data-Transfering the project from RDBMS to file, then using WinCVS to load into CVS? It looks a lot simpler.