You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
😃 I would appreciate a screen like that, the question is do we want an "Introduction screen" or a "What's new"?
I would vote for a intro screen which only gets shown the very first time and never again, not even for updates. What's new would be nice too but would lead to extra work for every feature release since the core team developing new this right now is just the three of us I would argue that we should rather spend our time on features than maintaining the what's new screen for every release plus the feature images we would need for every release. So what'#s new will most likely slow down our dev speed 🚀
Well, the code is ready and should work just fine it. Last time I tested it, it was working on first run and on update. owncloud/android#1375
Now with other beta version scheme it will be easier to add this to beta release as well.
Version theme?
We still have 2 themes one for the play store with proper versioning scheme and the f-droid beta which uses the release date. So it would work for the Play Store beta programm
No worries :)
Our Goal is to not need the hardcore beta anymore but to merge fast, test, feature freeze, release to Play beta programm for 2 week, release it as stable
I think it is a good idea to show the biggest changes (if any) on every new release.
Mostly it is just a short text and an image, so it is not that much time and hopefully the PR author supports us.
»What’s new« is only necessary on really big changes as you already said. A generic »changelog« screen is annoying and people generally don’t care as long as everything works. ;)
Didn’t we have a nice intro slideshow at some point, or was that only iOS?
Okay, that then mean that we would use it for "What's new" only and not for "Introduction to the app", which is fine with me. Only issue I can thing of is that nice graphics for new features could block releases if they don't get done on time, same issue if we add text for the features that is only translated by 50% for a language. :(
I thought it is both for introduction and for new features (and we were just talking about the scope for the features).
Regarding the graphics/languages this is indeed a problem.
How is this currently solved? Do we wait until the major languages are fully translated before releasing?
At the moment we just release after the RCs have proven to be stable. This will probably always be the case. Most widely used languages are fully translated at the final release date.
We should then still have a differentiating between whats new and introduction. So at first start we should only show the intro, at update we should only show the what's new.
Activity
AndyScherzinger commentedon Jun 21, 2016
😃 I would appreciate a screen like that, the question is do we want an "Introduction screen" or a "What's new"?
I would vote for a intro screen which only gets shown the very first time and never again, not even for updates. What's new would be nice too but would lead to extra work for every feature release since the core team developing new this right now is just the three of us I would argue that we should rather spend our time on features than maintaining the what's new screen for every release plus the feature images we would need for every release. So what'#s new will most likely slow down our dev speed 🚀
przybylski commentedon Jun 21, 2016
Well, the code is ready and should work just fine it. Last time I tested it, it was working on first run and on update.
owncloud/android#1375
Now with other beta version scheme it will be easier to add this to beta release as well.
AndyScherzinger commentedon Jun 21, 2016
Version theme?
We still have 2 themes one for the play store with proper versioning scheme and the f-droid beta which uses the release date. So it would work for the Play Store beta programm
przybylski commentedon Jun 21, 2016
version number scheme: https://github.com/nextcloud/android/wiki/Development-Guide#version-name-and-number
AndyScherzinger commentedon Jun 21, 2016
...for stabe and release candidate (as in play store beta), else for the Tobias' beta: https://github.com/nextcloud/android/wiki/Development-Guide#development-beta-release
przybylski commentedon Jun 21, 2016
damn, sorry for confusion.
AndyScherzinger commentedon Jun 21, 2016
No worries :)
Our Goal is to not need the hardcore beta anymore but to merge fast, test, feature freeze, release to Play beta programm for 2 week, release it as stable
tobiasKaminsky commentedon Jun 22, 2016
I think it is a good idea to show the biggest changes (if any) on every new release.
Mostly it is just a short text and an image, so it is not that much time and hopefully the PR author supports us.
tobiasKaminsky commentedon Jun 22, 2016
Otherwise e.g. multiselect is not immediately known to users
jancborchardt commentedon Jun 23, 2016
»What’s new« is only necessary on really big changes as you already said. A generic »changelog« screen is annoying and people generally don’t care as long as everything works. ;)
Didn’t we have a nice intro slideshow at some point, or was that only iOS?
AndyScherzinger commentedon Jun 23, 2016
@jancborchardt The what's new screen is actually implemented as a Intro slideshow 💃
przybylski commentedon Jun 23, 2016
In that case on the weekend I will import that PR here
2 remaining items
AndyScherzinger commentedon Aug 16, 2016
Okay, that then mean that we would use it for "What's new" only and not for "Introduction to the app", which is fine with me. Only issue I can thing of is that nice graphics for new features could block releases if they don't get done on time, same issue if we add text for the features that is only translated by 50% for a language. :(
tobiasKaminsky commentedon Aug 16, 2016
I thought it is both for introduction and for new features (and we were just talking about the scope for the features).
Regarding the graphics/languages this is indeed a problem.
How is this currently solved? Do we wait until the major languages are fully translated before releasing?
AndyScherzinger commentedon Aug 16, 2016
At the moment we just release after the RCs have proven to be stable. This will probably always be the case. Most widely used languages are fully translated at the final release date.
We should then still have a differentiating between whats new and introduction. So at first start we should only show the intro, at update we should only show the what's new.
Bugsbane commentedon Aug 16, 2016
I can't promise to always be available depending on my workload, but let me know if I can help out here.
Agreed, although I'm sure the same classes could be used, just feeding in two different content streams.
AndyScherzinger commentedon Aug 16, 2016
That would be great! At least the "Intro graphics" are stable so if you have time you could already help us out with these 😃
Exactly, yes that is the case. 👍
Fix a typo in SQL db upgrade nextcloud#50 logs