Getting Started with Changelogic

• Changelogic
• Getting Started

Getting started The intention of this page is to give you a fast glimpse to development process promoted and supported by Changelogic. This page is an overview, but you can also get to the details by following the links provided in each section.

When setting up Changelogic you probably want to check installation, development environment setup, administration and project setup guides before this one.

If you are looking for an answer to some specific question you might want to see our FAQ.

Think it's too complex?
It's not simple for sure, but you can try this: start with task management – enter all your tasks to Changelogic. When you need more, bring in the change management – bind your tasks to changes. And if you have a project big enough, everything else comes quite naturally – release management, environment adjustments managament, modules and so forth.

• Enter tasks. Enter the tasks to your project.
• Analyze. Approve tasks, comment on, negotiate and set the production release cycle, prioritize, give estimates, try reproducing bugs etc.
• Create change. Create change from task, assign the change, estimate risk and value.
• Begin development. Having the development environment set up, begin development.
• Develop.
  • Write code using you favourite IDE,
  • implement bound tasks,
  • update base version,
  • commit to change,
  • proofread your diffs and
  • describe the environment adjustments your change requires.
• End development. End development – run the preconditions (compile, deploy, test, run code analyzer and/or beautifier), commit your code, upload diffs and test reports in one step.
• Verify.
  • Do the code review,
  • look at changed code,
  • define checklists for review,
  • pass or fail the review,
  • analyze impact and
  • replan or
  • abandon the change if needed.
• Integrate. Set up integration environment and integrate the change to one or multiple branches resolving conflicts on the way.
• Update test. Deploy a version into test environment to check the status of your application.
• Accept.
  • Do the acceptance test,
  • define checklist,
  • enter testcases for acceptance,
  • look at version differences to
  • verify tasks and
  • analyze the impact of whole release.
• Update production. Deploy a version into production environment.
• Feedback. Collect feedback from your users.
• Support production. Act according to feedback – plan and do maintenance releases to support production.