#8428 closed defect (wontfix)
Need to autoupdate dojo.version in release script
Reported by: | Adam Peller | Owned by: | dante |
---|---|---|---|
Priority: | high | Milestone: | 1.4 |
Component: | BuildTools | Version: | 1.2.3 |
Keywords: | Cc: | ||
Blocked By: | Blocking: |
Description (last modified by )
dojo.version major, minor and patch should be updated by the release script.
Change History (9)
comment:1 Changed 12 years ago by
Description: | modified (diff) |
---|
comment:2 Changed 12 years ago by
comment:3 Changed 12 years ago by
comment:4 Changed 12 years ago by
comment:5 Changed 12 years ago by
Milestone: | tbd → 1.4 |
---|
so this is actually not straightforward. We use build_release (iirc) for branch as well, and the current changeVersion function works to change all the revision info about dojo.version ... but it is applied to the tag (and committed). If it were applied to "whatever the next version would be" we'd have to differentiate between branch and trunk, and otherwise complicate the operation.
know what needs to happen, just no simple solution comes to mind. will update manually for 1.3 -> 1.4 while solution found.
comment:6 Changed 12 years ago by
Resolution: | → wontfix |
---|---|
Status: | new → closed |
i'm happy manually updating the tag after a major. for 1.3->1.4 it acted as a sort of indication trunk was open again after release. please reopen if you feel inclined to fix this to be automated.
comment:7 Changed 12 years ago by
I can't believe anyone else noticed. I think it should be automated. Trunk should be open right away, since we can always create a branch off any revision. If you wish to shut down development, there should probably be a way to lock the trunk.
comment:8 Changed 12 years ago by
I'm just saying I don't want to spend any cycles on making this automated, as it is a very low priority for me. we don't release that often.
It hasn't been updated since 1.1.0 :-O