Help people be aware of the release notes about betaflight-configurator

[mikeller]

+1 from me. Could probably even be auto-generated from GitHub release notes.

[borisbstyle]

The release notes are shown when you load the online hex in the
configurator actually. Maybe some additional big font is needed in the
flash window as extra warning to make sure they read it.

Also flashing standard repos is always safe. There is a special checkbox
for unstable releases.
Op 26 jun. 2016 22:08 schreef "Michael Keller" [email protected]:

+1 from me. Could probably even be auto-generated from GitHub release
notes.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
#51 (comment),
or mute the thread
https://github.com/notifications/unsubscribe/AKQlhBRdzlgm_qX0GBq33KbTe_KzQ_Kcks5qPtwygaJpZM4I-j_9
.

[mikeller]

Also flashing standard repos is always safe. There is a special checkbox
for unstable releases.

I think this is not only about stability, it's more about features and config settings that get renamed and defaults that get changed.

There is a lot of

Q: 'feature X doesn't work as expected any more after update'

A: 'this is because the config for feature X has changed, you need to modify your config, see release notes'

going on in here. If we can reduce this by getting people to read the release notes when updating it would free up devs to do more productive work instead of answering this kind of question.

[skaman82]

I don't think that would realy help. Some people just don't want to read the notes. Even if you show the release notes in 30px bold.

Von meinem iPhone gesendet

Am 26.06.2016 um 23:28 schrieb Michael Keller [email protected]:

Also flashing standard repos is always safe. There is a special checkbox
for unstable releases.

I think this is not only about stability, it's more about features and config settings that get renamed and defaults that get changed.

There is a lot of

Q: 'feature X doesn't work as expected any more after update'

A: 'this is because the config for feature X has changed, you need to modify your config, see release notes'

going on in here. If we can reduce this by getting people to read the release notes when updating it would free up devs to do more productive work instead of answering this kind of question.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

[borisbstyle]

they dont read anyway. I actually sometimes get same quastion every day and
sometimes multiple times per day :)
Op 26 jun. 2016 23:53 schreef "Albert Kravcov" [email protected]:

I don't think that would realy help. Some people just don't want to read
the notes. Even if you show the release notes in 30px bold.

Von meinem iPhone gesendet

Am 26.06.2016 um 23:28 schrieb Michael Keller <[email protected]
:

Also flashing standard repos is always safe. There is a special checkbox
for unstable releases.

I think this is not only about stability, it's more about features and
config settings that get renamed and defaults that get changed.

There is a lot of

Q: 'feature X doesn't work as expected any more after update'

A: 'this is because the config for feature X has changed, you need to
modify your config, see release notes'

going on in here. If we can reduce this by getting people to read the
release notes when updating it would free up devs to do more productive
work instead of answering this kind of question.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
#51 (comment),
or mute the thread
https://github.com/notifications/unsubscribe/AKQlhHgjohD-1H1AkMNaw7iZy6y82gpxks5qPvTegaJpZM4I-j_9
.

[mikeller]

@borisbstyle:

they dont read anyway. I actually sometimes get same quastion every day and
sometimes multiple times per day :)

You got a point there.

I hope that, once my CLI 'diff' code is in the firmware, and we've got diff / restore as buttons in the configurator, this will at least remove the problem of changing default values across updates...

[cmavr8]

I don't think that would realy help. Some people just don't want to read the notes. Even if you show the release notes in 30px bold.

Absolutely true, but wouldn't it help some people in the middle? The ones that may forget (or not yet know) about release notes, but would still read them if they popped up in front of them.

It could be that these people are too few to be worth saving. Your guys' call. You'll pay the price (dev time) so you decide.

Cheers :)
And thanks for all the great work to all.

[skaman82]

I think that the notes are clearly shown already

Von meinem iPhone gesendet

Am 27.06.2016 um 21:29 schrieb Chris Mavrakis [email protected]:

I don't think that would realy help. Some people just don't want to read the notes. Even if you show the release notes in 30px bold.

Absolutely true, but wouldn't it help some people in the middle? The ones that may forget (or not yet know) about release notes, but would still read them if they popped up in front of them.

It could be that these people are too few to be worth saving. Your guys' call. You'll pay the price (dev time) so you decide.

Cheers :)
And thanks for all the great work to all.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.

[blckmn]

Should the firmware flasher front page have a release notes that changes when you select the firmware?

[mikeller]

I would be in favour of that. Anything that can help to get people to read the information available before they create issues on GitHub is a good thing - for the devs and for the users.

[KiteAnton]

The firmware flasher page already displays the release notes when you load fw online.

[stale]

This issue / pull request has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs within a week.

[stale]

Automatically closing as inactive.