mirror of
https://github.com/ciur/papermerge.git
synced 2026-04-25 12:05:58 +03:00
[GH-ISSUE #113] Missing: How to update #85
Labels
No labels
2.1
3.0
3.0.1
3.0.2
3.0.3
3.0.3
3.1
3.2
3.2
3.3
3.5
3.x
Fixed. Waiting for feedback.
Fixed. Waiting for feedback.
UX
Version 2.1 - alpha
XSS
announcement
beta
blocker
bug
cannot reproduce
confirmed
confirmed
critical
demo
dependencies
deployment
detchnical debt
discussion
docker
documentation
donations
duplicate
enhancement
feature request
frontend
fundraising
good first issue
good issue
help wanted
high
implemented
important
improvement
incomplete
invalid
investigation
kubernetes
low
low impact
medium
medium
medium impact
migration from 2.0
migration from 2.1
missing-language
missing-ocr-language
no-activity
note
ocr
outofscope
packaging
performance
popular request
pull-request
pypi
question
raspberry pi
roadmap
search
security
setup
status
task
technical debt
updates
user xp
version 1.4.0 - demo
will be implemented
will not be implemented
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/papermerge#85
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @Pyromane on GitHub (Sep 6, 2020).
Original GitHub issue: https://github.com/ciur/papermerge/issues/113
Similar to the extremely detailed bare metal installation instructions, I miss instructions on how to perform an update.
@ciur commented on GitHub (Sep 7, 2020):
@Pyromane, good point!
I will update that part of documentation.
Thank you for opening the issue!
@ciur commented on GitHub (Sep 14, 2020):
Hi @Pyromane ,
Here is documentation on how to perform an update.
On 16th of September 2020 I will release v1.4.3. By upgrading to 1.4.3 you can try/check if update related documentation is complete or needs adjustments.
@Pyromane commented on GitHub (Sep 19, 2020):
Thanks for the instructions!
Should after that
git checkoutnot a
git pullconsequences? Because the changelog.md has not changed for me.
(Sry, I'm still a git newbie)
@ciur commented on GitHub (Sep 29, 2020):
Hi @Pyromane,
git checkoutwill "checkout" application source code for exact point your are asking for. E.g.checkout -b v1.4.5will checkout source code to be exact for version 1.4.5. Thegit pullcommand on the hand will retrieve the latest source code from current branch.Usually the workflow is:
I added this points to the documentation.
@Pyromane in case you are happy with resolution of this ticket - you may close it.