Changelog for testers versions

[GoogleCodeExporter]

I'm using a testers version and I get notified on new testers version with rss 
but I don't have a changelog so I don't know what I should actually test.

Some changes relate to an issue I've starred. Of those I'm aware through the 
issue update.

Some updates relate to issues I'm not interested in (ie. Keyboard languages I 
don't use).

In between there must be changes related to issues I haven't starred or 
maybe even I'm not even aware of but if I'm aware of an implemented 
change for them I'll be able to test.

Original issue reported on code.google.com by zohars...@gmail.com on 25 Mar 2010 at 6:05

[GoogleCodeExporter]

It is a very good point.
From now on, I'll add testers information to the "Next Release" issue (for the 
next
release it is Issue 257).
After I'll upload a new testers release, I'll also update the issue with all the
relevant information about it.

Thanks for the idea, and the support.

Original comment by menn...@gmail.com on 25 Mar 2010 at 7:56

• Changed state: Done

[GoogleCodeExporter]

First of all,   I should be thanking you, not vice 
verse. But enough of this mushy stuff.

I think it's better on the changelog page since it's 
more accessible. It's linked on the links page on 
the app. Maybe a different testers-changelog with 
a link in links page in app.

Off topic:
Sorry for not searching what issue it relates to but 
swiping up for shift/caps is screwed up. First it 
insert a dot and the the next keypress is ignored 
and lastly it keeps displaying capital layout while 
writing is noncapital.
G1 cm4.2.15.1 20100324

Original comment by zohars...@gmail.com on 25 Mar 2010 at 9:22

[GoogleCodeExporter]

I'll think of a way to maintain a testers changlog, 
but for the meantime, i'll use the method i've 
suggested. 

Please open an issue about the shift bug, i 
reproduced it.

Original comment by menn...@gmail.com on 26 Mar 2010 at 8:45

[GoogleCodeExporter]

Sorry for bumping this issue but the current situation is still no good from my 
POV.

I regularly install/update to the beta version (I follow the RSS feed on my g1) 
but
nothing good comes out of me doing so.

In the past I had some issues that I created/starred/commented-upon and with 
each new
testers version I checked to see if they're dealt so I could give feedback.

Now I don't have any "hot" issues but I still want to help by beta testing. The 
thing
is that to hunt down the relevant "Next Release" issue on the phone is not that 
easy.
Even after hunting it I need to be able to briefly browse the blocking issues 
subject
to decide to which bugs I can relate and might supply useful feedback. No good 
will
come out from a Hebrew speaker (like myself) looking into Catalan issues. With 
Google
code interface I need to click each blocking issue code just to see what's it 
about.

The addition of the notification messages is good but it gives me no info. I 
have no
use for the final versions changelog.

Again, sorry for bumping/nagging. It's your call, I'm just feeling stupid 
installing
beta versions for nothing.

Original comment by zohars...@gmail.com on 30 May 2010 at 11:29

[GoogleCodeExporter]

First of all, even just using the latest beta is good - this way we can verify 
that 
required functionality is still working :)

Second, I fail to maintain additional pages, actually, I fail to maintain the 
main 
changelog page. I try to add information to the Next Release (currently 
http://code.google.com/p/softkeyboard/issues/detail?id=366) page on every 
testers 
version, but I fail in that too.

I feel that the only way to do it, is if it was automatic. Can you maybe 
suggest a 
way?

Original comment by menn...@gmail.com on 30 May 2010 at 1:14