Closed johnd0e closed 4 years ago
Also I would like to solve Scripts versioning #99, as it will become more painful to do it later, when IITC-CE get more and more user adoption.
Just rebuilt fresh test-builds from scratch. Added #205 here, please check.
no news?
What news are you waiting for? Our development process is transparent, you can see issues, PRs's, etc. There is no hidden development behind the scenes.
news = ETA for new release!!
ahhahaha sorry
May I ask you why new release is better that test-builds for you?
it works generally though, i have had crashes, it can't get my location, it is to be expected for an unstable app, so i am looking forward to a new bug fix and stable update.
i have had crashes, it can't get my location [...] so i am looking forward to a new bug fix
Are there open issues describing these problems? If not - it means that we are unaware of them.
FYI
test-build
is draft of upcoming release, in some point (which is pretty close now) we just announce it as 0.30
.
So if you're not satisfied with test-build
- it's unlikely that you will see anything new in release
.
And if you wait for something particular fix - you better say about it. I do not know what is you meaning of 'eyes' emoji, but it is not enough.
test-builds
updated
Visible changes:
shielding
tooltip: round mitigation excess
to cope with lack of js float precision #279
window.makePermalink
(utils_misc.js) #198watch
mode to auto-rebuild on source changes.*.user.js
-> *.js
, rearrange source directories.version
of Release scripts (closes #99).web_meta_gen.py
, web_server_local.py
, tampermonkey_stubs_gen.py
.
We have a lot of new features already, so I propose to think about preparing new release.
Stoppers:
Also, after we get all merged, do not release immediately, as I would like to make some final changes. Among them:
P.S. As usual, I track all planned/tested/done features in Project 1 board. Please check if you'd like to include some more PR's there.