You are not logged in. Your edit will be placed in a queue until it is peer reviewed.
We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.
Required fields*
-
Creating a rc version of a bug-fix release seems like the bad practice. But since you are there, I think your only option is to go for your rename and publish approach.David Arno– David Arno2017-11-29 13:49:20 +00:00Commented Nov 29, 2017 at 13:49
-
1I suspect English may not be your first language. I have edited your question to hopefully make it easier to read. If this is incorrect, please edit your question and roll back the changes (or make your own).Dan Pichelman– Dan Pichelman2017-11-29 14:04:27 +00:00Commented Nov 29, 2017 at 14:04
-
The real problem is that when you start working on "the version after" 1.1.0, you don't yet know that it's going to be 1.1.1. It could end up being 1.1.2 or even 1.2.0.Reinstate Monica– Reinstate Monica2017-11-30 15:22:42 +00:00Commented Nov 30, 2017 at 15:22
-
Thanks @DanPichelman, as you suspect, English is not my mother tongue, so any improvements are appreciated :)Miguel Ángel García Gómez– Miguel Ángel García Gómez2017-11-30 15:40:11 +00:00Commented Nov 30, 2017 at 15:40
-
Thanks for your answer @DavidArno, so what is the recommendation when you have to create a bug-fix release?Miguel Ángel García Gómez– Miguel Ángel García Gómez2017-11-30 15:42:13 +00:00Commented Nov 30, 2017 at 15:42
Add a comment
|
How to Edit
- Correct minor typos or mistakes
- Clarify meaning without changing it
- Add related resources or links
- Always respect the author’s intent
- Don’t use edits to reply to the author
How to Format
-
create code fences with backticks ` or tildes ~
```
like so
``` -
add language identifier to highlight code
```python
def function(foo):
print(foo)
``` - put returns between paragraphs
- for linebreak add 2 spaces at end
- _italic_ or **bold**
- indent code by 4 spaces
- backtick escapes
`like _so_` - quote by placing > at start of line
- to make links (use https whenever possible)
<https://example.com>[example](https://example.com)<a href="https://example.com">example</a>
How to Tag
A tag is a keyword or label that categorizes your question with other, similar questions. Choose one or more (up to 5) tags that will help answerers to find and interpret your question.
- complete the sentence: my question is about...
- use tags that describe things or concepts that are essential, not incidental to your question
- favor using existing popular tags
- read the descriptions that appear below the tag
If your question is primarily about a topic for which you can't find a tag:
- combine multiple words into single-words with hyphens (e.g. design-patterns), up to a maximum of 35 characters
- creating new tags is a privilege; if you can't yet create a tag you need, then post this question without it, then ask the community to create it for you