c172p-team / c172p

A high detailed version of the Cessna 172P aircraft for FlightGear
GNU General Public License v2.0
80 stars 43 forks source link

Gather a list of features and bugs we fixed in 2019.1 #1196

Closed onox closed 5 years ago

onox commented 6 years ago

We should gather a list of all the new features, major changes, and bugs we fixed. Please create a list (use * to create bullet points) here.

Features:

Fixes:

Do not forget to update NEWS.md before creating the release. See https://github.com/c172p-team/c172p-detailed/wiki/Release-process-and-versioning

legoboyvdlp commented 5 years ago

I think we should close this issue and make a new one for 2019.1 unless @onox can edit the title?

gilbertohasnofb commented 5 years ago

@legoboyvdlp No need for @onox, super @gilbertohasnofb can change titles at will too! :rofl:

wlbragg commented 5 years ago

@gilbertohasnofb I think I have everything. Feel free to edit!

gilbertohasnofb commented 5 years ago

@wlbragg Looks good. @legoboyvdlp @dany93 can you confirm you all new features included here? If so, I will make the new release later tonight.

dany93 commented 5 years ago

Confirmed, all new features(just a few for me).

Thank you, @onox and @gilbertohasnofb, And thank you, @wlbragg for the huge and difficult work you did.

gilbertohasnofb commented 5 years ago

All right, I will start preparing the release now.

gilbertohasnofb commented 5 years ago

@wlbragg @dany93 @legoboyvdlp @onox Done! We have a new release :smile: Congratulations to you all for the hard work, this aircraft gets more and more impressive as time goes by. We have no standing PRs and we seem to have fixed all major bugs, as well as added a bunch of new exciting features.

@onox It was really fun preparing the release, and I hope I did this right. You might want to double check it since this is the first time I did this, but I am 99.999...% sure it all worked as it should.

@everyone Once again, my apologies for been a bit absent recently. In the near future I might not be able to contribute as much as I did in the past, but I will definitely be around and willing to do at least some work from time to time. @wlbragg ping me when you decide what to tackle next, perhaps the glass effect could be a good place to start? I would love to have a scratched windshield that gets annoying when the sun is in the pulot's face :smile:

Thanks to you all once again. :tada:

wlbragg commented 5 years ago

@gilbertohasnofb thank you for cutting the release, I was dreading that part, but you seemed to have no issues with it, I'm thankful for that and it was a hug relief for me to have that done. Thank you! I'll ping them on the dev list and see if they will take it from here. Ah, you beat me to it, too cool, you made this easy, thanks again!

@everyone Ditto from me, thank you to all that help get this to this stage. I've got so many projects I am wanting to put time in, it's getting overwhelming. Time to work smarter and not harder! Thanks everyone!

gilbertohasnofb commented 5 years ago

I was dreading that part, but you seemed to have no issues with it

Well, thanks to @onox 's wonderfully detailed instructions, making a release is actually quite easy. One just needs to make sure that all 2019.1 and 2019.2-git tags and commit comments are correct, there were many that needed to be changed.

gilbertohasnofb commented 5 years ago

And I am happy to make the next releases as well, even if I am busy. It took me just a handful of minutes.

onox commented 5 years ago

@onox It was really fun preparing the release, and I hope I did this right. You might want to double check it since this is the first time I did this, but I am 99.999...% sure it all worked as it should.

@gilbertohasnofb Thanks for doing this release! :smile: Everything looks alright from the Github web interface. I only deleted the extraneous * in front of Fixes: in the release notes (but this was a typo in the instructions on the wiki - fixed it there as well).

onox commented 5 years ago

@gilbertohasnofb One more thing: I've moved any open issues with a 2019.1 features/release milestone to the future features/release milestone, and closed the 2019.1 milestones.

gilbertohasnofb commented 5 years ago

@onox Yeah, I forgot about moving the opened issues to a new milestone. I will remember to do that next time. Thanks for taking a look at this!