Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

New release and defined baseline #251

Open
linuxianer99 opened this issue Feb 4, 2022 · 15 comments
Open

New release and defined baseline #251

linuxianer99 opened this issue Feb 4, 2022 · 15 comments

Comments

@linuxianer99
Copy link
Member

linuxianer99 commented Feb 4, 2022

Hey all!

As we integrated lots of improvements the last week, i suggest to declare a Release Candidate ....

I my mind it makes sense to get a status, what is working now and where are some issues, which have to be fixed.

@August2111 @lordfolken @mihu-ov Can you please make some basic tests, if the image can be used by "normal" users in flight, or if there are still some bugs to fix ??

@MaxKellermann @kedder @lordfolken @August2111 Do you agree in general with my point ??

If so, i would tag the current source as V3.0-RC1.
Side note: We have still to check, if the new version numbering breaks anything ...

@kedder
Copy link
Member

kedder commented Feb 4, 2022

Good idea, let's do that!

@kedder
Copy link
Member

kedder commented Feb 4, 2022

I think we'd need a new XCSoar release for #207 though, in order for users to do any testing.

@linuxianer99
Copy link
Member Author

@lordfolken
Copy link
Contributor

I would agree.

We could open a milestone in github, and start triaging stuff we see necessary for that release?
Also if we could use labels in issues... So we can separate with enhancement and bugs.

The current prs i would see:
#245
#220
Some bugs:
#230
#225
#224
#207 as @kedder mentioned.
and probably some others.

@lordfolken
Copy link
Contributor

We would also need to do some testing, with usb stick upgrades. So far i only imaged with dd, but didn't do a "field" upgrade.

@August2111
Copy link
Contributor

August2111 commented Feb 4, 2022

So far i only imaged with dd, but didn't do a "field" upgrade.

@lordfolken What do you exactly mean with "field upgrade"?

@lordfolken
Copy link
Contributor

pilot copying the new image to the usb stick and upgrade via recovery. Not removing the sdcard.

@linuxianer99
Copy link
Member Author

I would agree.

We could open a milestone in github, and start triaging stuff we see necessary for that release? Also if we could use labels in issues... So we can separate with enhancement and bugs.

The current prs i would see: #245 #220 Some bugs: #230 #225 #224 #207 as @kedder mentioned. and probably some others.

Added this issues to the project!

We would also need to do some testing, with usb stick upgrades. So far i only imaged with dd, but didn't do a "field" upgrade.

I fully agree.

How has which hardware for testing ??
I have just 4,3 RGB and CH070

@lordfolken
Copy link
Contributor

lordfolken commented Feb 4, 2022

57-lvds

@August2111
Copy link
Contributor

What I really like is version information at XCSoar with NEWS.txt and VERSION.txt.

  • With a living NEWS.txt you have a good overview what happens since the last release - otherwise it is very difficult to remember...
  • With Version.txt you can link every time your version number to the image

@lordfolken
Copy link
Contributor

lordfolken commented Feb 4, 2022

A prominent version number that is being displayed from a single source of truth.
(For example in menu title bar, or mentioned in the splash screen)

What we could do better in xcsoar: is display those changes when you startup with a new version.

@August2111
Copy link
Contributor

August2111 commented Feb 4, 2022

How has which hardware for testing ??

57-lvds without vario board
AM070-DS2 without vario board

From time to time I have access to both types of device with vario in our club...

@lordfolken
Copy link
Contributor

Maybe we should device a testing plan?

@MaxKellermann
Copy link
Collaborator

I think we'd need a new XCSoar release for #207 though, in order for users to do any testing.

Unfortunately, there was not enough time this week - but I promise 7.23 will be ready next week!

@linuxianer99
Copy link
Member Author

I think we'd need a new XCSoar release for #207 though, in order for users to do any testing.

Unfortunately, there was not enough time this week - but I promise 7.23 will be ready next week!

No problem :-) We are all doing this in our spare time :-)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants