Ask / Submit

[feature request] Two different TJC posts for pre-release and release

asked 2015-05-06 10:07:57 +0200 gravatar image

updated 2015-05-06 10:09:26 +0200

Hi, I see that Jolla sailors have the habit of creating one TJC post for a pre-release version and then when the release is pushed to the public they just edit the post adding that the release is now public.

I believe this is confusing: this way in the release thread there is already a discussion about topics already fixed and not relevant any more for the released version.

Please create a new TJC post for release version, maybe you can just link the pre-release post.

Thank you

edit retag flag offensive close delete

1 Answer

Sort by » oldest newest most voted

answered 2015-05-06 10:46:43 +0200

simo gravatar image

updated 2015-05-06 10:47:29 +0200

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 and the public, 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:

  • 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
  • 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!)
  • 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.

edit flag offensive delete publish link more
Login/Signup to Answer

Question tools

1 follower


Asked: 2015-05-06 10:07:57 +0200

Seen: 96 times

Last updated: May 06 '15