Skip to main content
text improvements
Source Link
  1. Usually, it is the same as any other software projects and their code base (outside Drupal).

  2. One by one issue - merge the first, a Major change or important Bug, then ask the other issues' resolvers to update their fixes / patches / code changes.

  3. Merge the next change, solve the next issue, if there is code conflicts again repeat point 2. and then 3. again.

  4. Publish the official new Drupal project (module) release version.

  1. Usually it is the same as any other projects and their code base.

  2. One by one - merge the first, a Major change or important Bug, then ask the other issues' resolvers to update their fixes / patches / code changes.

  3. Merge the next change, solve the next issue, if there is code conflicts again repeat point 2. and then 3. again.

  1. Usually, it is the same as any other software projects and their code base (outside Drupal).

  2. One by one issue - merge the first, a Major change or important Bug, then ask the other issues' resolvers to update their fixes / patches / code changes.

  3. Merge the next change, solve the next issue, if there is code conflicts again repeat point 2. and 3. again.

  4. Publish the official new Drupal project (module) release version.

Source Link

  1. Usually it is the same as any other projects and their code base.

  2. One by one - merge the first, a Major change or important Bug, then ask the other issues' resolvers to update their fixes / patches / code changes.

  3. Merge the next change, solve the next issue, if there is code conflicts again repeat point 2. and then 3. again.