Skip to content

Commit

Permalink
VERSION: Prepare for v1.1 tagging
Browse files Browse the repository at this point in the history
  • Loading branch information
@mgorges
mgorges committed Dec 2, 2020
1 parent e0ad792 commit 711c27b
Show file tree
Hide file tree
Showing 2 changed files with 7 additions and 0 deletions.
2 changes: 2 additions & 0 deletions .gitignore
View file
Original file line number Diff line number Diff line change
Expand Up @@ -8,6 +8,8 @@ tmp.*
*.core
*.o
*.o2
*.class
#*.jar
*.a
*.old*
*.bak*
Expand Down
5 changes: 5 additions & 0 deletions VERSION
View file
Original file line number Diff line number Diff line change
Expand Up @@ -10,4 +10,9 @@
# 1.0.8: iOS refactoring, new modules, localnotifications, various fixes
# 1.0.9: framework7 web-app support, core module performance improvement
# 1.0.10: iOS refactoring, clipboard support, uiform widget tweaks
# 1.0.11: iOS updates, redcap updates, linux loader updates, bug fixes
# 1.0.12: Gambit 4.9.2 support, library updates, android build improvements
# 1.0.13: arm64 android, macOS codesigning, IPv6, OpenGL bugfixes
# 1.1: android multiple api support, major ln_glgui renderloop timing change
# 1.1.1: Bug fixes, better android support, ln_jScheme module
1.0.10

9 comments on commit 711c27b

@0-8-15
Copy link
Contributor

@0-8-15 0-8-15 commented on 711c27b Dec 2, 2020

Choose a reason for hiding this comment

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

Note: I'm collecting an update to ln_jscheme, webview (both bugs due to the assumption that onCreate was a one-time call) a recreated androidforegroundservice and a few minor things (possibly segfaults and memory leaks in JNI) into PRs right now.

Today or tomorrow I'd guess they will be ready to go.

@0-8-15
Copy link
Contributor

@0-8-15 0-8-15 commented on 711c27b Dec 2, 2020

Choose a reason for hiding this comment

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

OK. Todays PRs are now feature complete.

I will now re-test.

@0-8-15
Copy link
Contributor

@0-8-15 0-8-15 commented on 711c27b Dec 2, 2020

Choose a reason for hiding this comment

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

While I'm testing... iff the conclusions I'm currently drawing from the profile data I'm looking at. Well, if this turns out to be true; let's say I'm surprised! At least, that is.

@mgorges
Copy link
Contributor Author

@mgorges mgorges commented on 711c27b Dec 2, 2020

Choose a reason for hiding this comment

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

I can always release a v1.1.2 quickly as this one is already tagged.

@0-8-15
Copy link
Contributor

@0-8-15 0-8-15 commented on 711c27b Dec 2, 2020

Choose a reason for hiding this comment

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

I can always release a v1.1.2 quickly as this one is already tagged.

Yeah, but why tag a broken version when the fix is in the queue?

@0-8-15
Copy link
Contributor

@0-8-15 0-8-15 commented on 711c27b Dec 2, 2020 •
edited
Loading

Choose a reason for hiding this comment

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

BTW

While I'm testing... iff the conclusions I'm currently drawing from the profile data I'm looking at. Well, if this turns out to be true; let's say I'm surprised! At least, that is.

this we better leave for the next version: 0-8-15@f0e039f

edited: update to link to comments wrt. line 42.

@mgorges
Copy link
Contributor Author

@mgorges mgorges commented on 711c27b Dec 2, 2020

Choose a reason for hiding this comment

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

Sure, happy to consider that for the next release when it comes in a pull request. Thanks.

@mgorges
Copy link
Contributor Author

@mgorges mgorges commented on 711c27b Dec 2, 2020

Choose a reason for hiding this comment

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

Yeah, but why tag a broken version when the fix is in the queue?

Its a limitation of how release management works in GitHub (or git). I don't think I move tags forward to new places?

@0-8-15
Copy link
Contributor

@0-8-15 0-8-15 commented on 711c27b Dec 3, 2020 via email

Choose a reason for hiding this comment

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

Please sign in to comment.