Closed johnd0e closed 5 years ago
I think now there are all the changes I planned. I need to start making a list for merge
That list is in the Project 1 already, try it.
P.S. And I'd like to finish #110 before release
Ok. Indeed, it is better to make such changes before the auto-update works.
@modos189 Some of issues require your feedback: https://github.com/IITC-CE/ingress-intel-total-conversion/issues?utf8=%E2%9C%93&q=label%3Aattention
I've finished planned changes for this release. Next: we should resolve a couple of issues that needs your attention.
Edit: we need to solve scripts versioning issue.
I suggest to test again and release (for example) tomorrow
Sure, but I still want to resolve versioning issues before release: https://github.com/IITC-CE/ingress-intel-total-conversion/issues/99#issuecomment-468583737
https://github.com/IITC-CE/iitc.modos189.ru/issues/1 is also important for release
IITC-CE/iitc.modos189.ru#1 is also important for release
This is a useful change, but not a blocking release. This can be implemented soon.
Well, download page looks not ok (after renames), and it's bad for new release. We should at least make temporary category correction now. I could do it tomorrow.
There 2 PRs left unmerged. Why?
I thought they weren't ready. Then, in the next release.
Renames should be applied as soon as possible
I suppose we should release 0.29.1
If do this only for desktop version, nothing will break?
I suppose all will be ok, but why not release mobile too?
P.S. Actually I need updated mobile release, because I am unable to use test-builds apk due of #12.
In release notes there should be some warning:
Desktop users: additional one-time action required when updating to current release!
Some plugins are renamed, and do not replace old versions automatically.
So it's necessary to delete old versions manually.
Sorry for the inconvenience.
Added to description of github release
What about to add this to news stream on site (and tg channel)?
I don’t want to write there, because then news about release 0.29 will not be displayed on the site :( This is not so important; not so many people were updated in a day.
I don’t want to write there, because then news about release 0.29 will not be displayed on the site :(
Isn't possible to add this warning to existent description of 0.29?
@modos189 So what features do you want to include in nearest release? Would you like to use Project#1 to track the progress?