Release 5.3.3

[miguel-a-calles-mba]

Hi,

I created a 5.3.3 milestone.

Whenever you have time, may you please tag the PRs we should include in the next release?

Depending on the level of changes, we might need to consider the release as a minor update (i.e., 5.4.0) instead of a patch (i.e., 5.3.3).

Thanks!

[HyperBrain]

Remember that feature updates which are not backwards compatible must be put into a minor version and breaking changes in a major update. Only bugfixes or completely backwards compatible updates can be put into a patch version. Otherwise you would break automated deployment systems which allow installing patch updates without notice (and a rollback there if e.g. a dependency update is declined in the deployment system).

…

On Mon, May 4, 2020 at 4:16 PM Miguel A. Calles MBA < ***@***.***> wrote: Hi, I created a 5.3.3 milestone. Whenever you have time, may you please tag the PRs we should include in the next release? Depending on the level of changes, we might need to consider the release as a minor update (i.e., 5.4.0) instead of a patch (i.e., 5.3.3). Thanks! — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <https://github.com/orgs/serverless-heaven/teams/serverless-webpack-team/discussions/11>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABKEZXRPIOSRJYL7237YXC3RP3E2RANCNFSM4MYZLHKQ> .

[HyperBrain]

Just to add: In my experience it worked well to have minor and patch milestones in parallel and assign the PRs according to their impact into the milestones. Then you can safely release sequentially.

…

On Tue, May 5, 2020 at 5:44 PM Frank Schmid ***@***.***> wrote: Remember that feature updates which are not backwards compatible must be put into a minor version and breaking changes in a major update. Only bugfixes or completely backwards compatible updates can be put into a patch version. Otherwise you would break automated deployment systems which allow installing patch updates without notice (and a rollback there if e.g. a dependency update is declined in the deployment system). On Mon, May 4, 2020 at 4:16 PM Miguel A. Calles MBA < ***@***.***> wrote: > Hi, > > I created a 5.3.3 milestone. > > Whenever you have time, may you please tag the PRs we should include in > the next release? > > Depending on the level of changes, we might need to consider the release > as a minor update (i.e., 5.4.0) instead of a patch (i.e., 5.3.3). > > Thanks! > > — > You are receiving this because you are subscribed to this thread. > Reply to this email directly, view it on GitHub > <https://github.com/orgs/serverless-heaven/teams/serverless-webpack-team/discussions/11>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/ABKEZXRPIOSRJYL7237YXC3RP3E2RANCNFSM4MYZLHKQ> > . >

[miguel-a-calles-mba]

Thanks for the clarification.

It seems like we need a 5.3.3 milestone for dependency updates and a 5.4.0 milestone for non-breaking PRs.

[miguel-a-calles-mba]

I created release/5.3.3 and release/5.4.0 branches to support parallel releases per @HyperBrain's suggestion. The PRs will merge into their respective branches.