Skip to content

Releases: How the update process should look like? #17

@coditive-przemek-h

Description

@coditive-przemek-h

One of the key questions here is what the update process should look like when using this starter? We always had a problem implementing the starter updates in the projects in the old version. We've started the project, and after few months a new fix/release/enhancement has been released to the starter. The existing projects were mostly not updated with the latest changes.

It was hard because it required reviewing all the changes and copying/pasting them manually to the project because the starter files already included project-specific code.

We should focus on this, how we can prevent such problems with updating, or research how such cases are solved in other open-source projects.

Metadata

Metadata

Assignees

No one assigned

    Labels

    questionFurther information is requested

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions