cleanflight / cleanflight-configurator

Google chrome/chromium based configuration tool for the cleanflight firmware
GNU General Public License v3.0
334 stars 252 forks source link

Prepare for next configurator release 1.3 #382

Closed martinbudden closed 7 years ago

martinbudden commented 8 years ago

TODO

  1. Create release notes
  2. Wait for bug reports and make a list of them here.

    Release Candidate bug reports

  3. Issue https://github.com/cleanflight/cleanflight-configurator/issues/383: PID values should be scaled 0 to 255

    DONE

  4. None yet
hydra commented 8 years ago

Need to investigate why current sensor reads 65536 in latest configurator. i noticed this when testing today. not sure if it's MSP or firmware related yet. Have someone else confirm this would be good.

reedbn commented 8 years ago

Issue #384 needs to be addressed

skaman82 commented 8 years ago

@martinbudden here a list with things to do: https://github.com/cleanflight/cleanflight-configurator/pull/362 Board type detection before flashing (in progress) https://github.com/cleanflight/cleanflight-configurator/pull/397 New LED modes (can be merged) https://github.com/cleanflight/cleanflight-configurator/pull/399 GPS - Clear Signal Strength Data (merged) https://github.com/cleanflight/cleanflight-configurator/pull/373 Show gps home info (in progress) https://github.com/cleanflight/cleanflight-configurator/issues/381 Swapped values in the graphs under sensors + NEW OSD Tab (because of that I would say we jump right to 1.3 instead 1.2.3.

Or maybe it is worth it to release 1.2.3. in the current state (that way users can benefit from advanced LED tab before the OSD stuff is ready (this can take some more weeks I think). @hydra What do you think?

martinbudden commented 8 years ago

Personally, if you are confident in the code, and you think you haven't introduced any bugs, I'd release 1.2.3 now.

skaman82 commented 8 years ago

Yes, I am pretty confident that i didn't break anything :)

skaman82 commented 8 years ago

@hydra I am also for releasing 1.2.3 now and then start to working on 1.3.0