Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Drop milestone creation step #5

Closed

Conversation

greg0ire
Copy link
Member

@greg0ire greg0ire commented Sep 15, 2020

The case when you do not need a milestone (because it is the end of the
branch) is not handled: closing what you intend to be the last milestone of a branch will create another milestone, which you have to close manually which would not create another milestone itself because the closed milestone would be empty.

Pointed out by @morozov in doctrine/dbal#4251 (comment)
Asked about at https://discourse.laminas.dev/t/laminas-automatic-releases-how-do-you-stop-the-milestones/1824
Also discussed in resolved discussion at doctrine/dbal#4251 (comment)

The case when you do not need a milestone (because it is the end of the
branch) is not handled.
Copy link
Member

@morozov morozov left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is how I'd prefer to work with milestones in DBAL. Not sure if this should be dictated to other projects.

Since it's a template, would it make sense to leave it as is and let the project maintainer decide which bits to use?

@greg0ire
Copy link
Member Author

greg0ire commented Sep 16, 2020

Since it's a template, would it make sense to leave it as is and let the project maintainer decide which bits to use?

Would somebody in Doctrine be likely to keep that step in a repo? If nobody does, let's just remove it.

@Ocramius
Copy link
Member

I don't see any damage done in milestones being created automatically: easier to assign issues to them, without having to look at what was released last.

This is more about having the milestones ready for others to start using them after "firing zeh missiles" and logging off.

@greg0ire
Copy link
Member Author

@Ocramius the "damage" at discussion would be the creation of a 2.4.9 milestone when we mean milestone 2.4.8 to be the last of branch 2.4.x . One could argue that the benefit of not having to create them manually outweights the drawback of having to delete that last milestone (or having it around for no reason).

@Ocramius
Copy link
Member

Ocramius commented Sep 16, 2020 via email

@greg0ire
Copy link
Member Author

Okay let's close then :)

@greg0ire greg0ire closed this Sep 16, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants