answered
2015-05-06 10:46:43 +0200
simo 
29079 ●345 ●466 ●481
Announcements or changelogs are not questions looking for answers, and each issue should be posted as a new question instead of adding any answers to the announcement.
I think it's our own action which is causing the confusion.
The area under update tagged questions can be used for discussion of the update, but it shouldn't be used for reporting any problems (or at least these problems should also have their dedicated question).
Separating posts
There's a clear border between versions set by the version numbering. There's nothing actually done between Early Adopter 1.1.4.29 and the public 1.1.4.29, so a new announcement of the public release wasn't needed. However, there were minor changes between .28 and .29, which might have caused some confusion on this:
Timeline of the latest upgrade:
- 1.1.4.28 was released to Early Adopters on April 16th. The changelog is huge. TJC got two new posts under "1.1.4" topic: one for announcing the Early Adopter release and one for the full changelog
- 1.1.4.29 was released to Early Adopters on April 28th. The update only includes two fixes. Earlier announcement post was edited under "Upgrade version history" instead of adding these to the changelog (which was left untouched!)
- 1.1.4.29 was released to all customers May 4th. There's no changes to the latter Early Adopter version, so only the announcement of the release was updated.
The only problem I see above is that the .29 fixes were not edited into the changelog, or posted as a separate (short) changelog.
