Conversation
There was a problem hiding this comment.
I have a serious concern about our current versioning approach, which takes all Git commits between 0.9.0 and 0.10.0 as 0.9.0. This is not realistic.
Consider that when errors occur with an experiment, users should report and upload the log so could we help. The printed log should contain the real version/commit id, so could we reproduce the error and locate the bug.
The correct logic should be
if paddle.version.tagged:
print paddle.version # 0.10.0, 0.10.0rc1 or something
print paddle.version.major # 0
print paddle.version.minor # 10
print paddle.version.release # 0
print paddle.version.rc # 1, or 0 if not a release candidate
else:
print paddle.version # 1232131abdd3
print paddle.version.commit # 1232131abdd3What do you think?
|
Thanks for @wangkuiyi , to distinguish
So how about the following logic? if paddle.version.tagged:
print paddle.version.full_version # 0.10.0, 0.10.0rc1 or something
print paddle.version.major # 0
print paddle.version.minor # 10
print paddle.version.patch # 0
print paddle.version.rc # 1, or 0 if not a release candidate
else:
print paddle.version.commit # 1232131abdd3 |
|
@Yancey1989 Completely agree! Thanks! |
|
Done with @wangkuiyi 's comments. |
typhoonzero
left a comment
There was a problem hiding this comment.
@Yancey1989 Can you please update this PR and merge the latest changes, so we can merge this.
| * 在`release/版本号`分支存在的时候,如果有bugfix的行为,需要将bugfix的分支同时merge到`master`, `develop`和`release/版本号`这三个分支。 | ||
|
|
||
| # PaddlePaddle 分支规范 | ||
| ## PaddlePaddle 分支规范 |
There was a problem hiding this comment.
With markdownlint MD025, there is only one top-level header.
|
Seem CI failed at: |
|
@typhoonzero , I'm debugging with this failed and will update this PR later. |
typhoonzero
left a comment
There was a problem hiding this comment.
LGTM! This is a awesome feature.
Fixed #2924
We can use the version API as: