You may have misunderstood my intent.
I can understand a test release not being supported until it's official, but I don't see how it can become official until it's tested.
#Amahi does not typically update Greyhole until it's an official release by the Greyhole author. Currently it's like a release candidate in my opinion and possibly have bugs. We will obviously need to test it with #Amahi once it's been released by him, but don't have the bandwidth to work pre-releases.
I have the time -- and more importantly -- the motivation to test it because I'm one of the users who asked the Greyhole Team to make the changes.
That's great you are willing to assist. We welcome your assistance when we are ready to test it with #Amahi.
Uninstalling the Greyhole UI App makes no sense to me when the goal is to integrate the new Greyhole features into Amahi's Greyhole version.
I meant if you were doing a manual install. If there were bugs with
greyhole-ui App, we would address that when testing the new Greyhole update.
In the past when new Greyhole releases have become available, what is the process someone in the Amahi community goes through to incorporate it into the latest Amahi code?
Typically we take care of testing Greyhole updates internally. The community rarely assists. We have a checklist in we use which can be found in the
#Amahi Wiki
If you mean submitting a bug report is the way I would get that info, then that is important for me to know.
No I mean to
submit a bug report requesting that Greyhole be upgraded.
I have the impression the Amahi Team is overwhelmed as it is, which is why I hope you can accept that I'm trying to help.
The #Amahi team consists of 3 folks. With the exception of the developer, we are volunteers and do this in our spare time.
Please understand that we have a task list that is prioritized by the developer. We are currently working on #Amahi 10 for Fedora 25, so that takes up most of our time. Greyhole is treated like any other app that needs updated, it's prioritized with all other tasks.