dev releases - forum thread and changelog

For those of us running Volumio in ‘test’ mode and checking the latest changes is there a thread here that announces/discusses these changes? I can’t find a tread but maybe I’m not looking in the right place?

Also, there are frequently new ‘test’ releases with no change log so we have no idea what it is we are 'test’ing. Can we have a thread for test releases that gives us information on the changes and a platform to discuss the changes? Otherwise, what is the point of ‘test’ releases? Following the Git doesn’t help because it seems to operate disparately from the forum…

Well, I’m still blindly downloading updates without any idea of what has changed… Latest V2.138. Guess I’ll just have to test everything and try to work it out myself. This seems crazy to me.

i agree with you. i do these updates but do not know what matters…

No feedback from the devs?

we don’t always read all topics, but we took notice. Doing something about it is not quite that easy for a small team

Please let me know if I can help.

Hi Liberator, yours is definetely a good idea.
First, let me explain how updates work: dev updates are in reality nightly-builds that we build every time a new thing is added, and test internally. That’s why there’s no changelog.
So basically there are 2 kind of releases: dev and stable.

What we could do is we could crete 3 levels of release: the dev build that we have now, an “almost-ready” and stable. So we could pre-publish almost ready images for people on the forum to test. What do you think?

So the current ‘dev’ updates that are downloaded if in test mode are nightly builds? I think that is all that is needed, but with some indication of which new commits are included so that the people testing will know which features have changed and can test those changes extensively. The more people we can get testing the more confident we can be when a new stable release is done.

I would like to see a thread ‘Latest test releases’ which includes this information (with links to the changes) and enables people to give feedback on the changes. This is important because, as I have seen, you can’t test every possible scenario when you make changes. I came across an issue with my Search Function commit that probably would have been found by someone testing much earlier.

Only minimal info needs to be posted each time - something like this:

20/04/17 - New dev release V 2.777
Includes new commits:
Fix Artist artwork (#1108)<Link
Fix Search Function (#1134)<Link

I don’t think a 3rd level is needed…

Would it be possible to display the commit messages from Git since the last build? This way the change log doesn’t need any additional curation and it would encourage developers to write proper commit messages, which is also not a bad thing :slight_smile:

That’s exactly what I would like to see: A list of the new commits included with a description and a link to the change. Nothing else needed really. We then know what has changed and can test extensively.

Interesting, but indeed very complicated to achieve.
We know the hash of: UI, BE , Build, both of the previous dev and released version and the new dev version.
Any suggestion on how to achieve this?

Keep in mind that a manual approach is not viable

When you find a discover a program that will find problems, analyse the code, talk with the users and then fix the code let me know :slight_smile:.

Having spent many hours working with and re-writing code I don’t think a few minutes writing a post with the change details is too much trouble. Otherwise I might as well just stick to my own fork and then spend more hours testing the changes. Maybe I will never try to do something that another use tries and never see a problem…

As I see it we need to introduce potential changes and then let users test it. If all is OK then push it to the main repository. The effort needed to post the change details is minuscule compared to the the effort needed to make the changes.

New dev release out. This is Release candidate.
You can test it and if everything is ok I will release it

I’ve added proper changelog :wink:

Thanks for the changelog :slight_smile: - I have put it in a separate thread because it disappears quickly!

Problem loading djmount on my Raspberry Pi 3 (don’t have my other boards here to try) :

Apr 23 04:08:32 volumio systemd[1]: Starting DJMmount... Apr 23 04:08:32 volumio volumio[804]: info: CoreCommandRouter::executeOnPlugin: mpd , getConfigParam Apr 23 04:08:32 volumio volumio[804]: info: CoreCommandRouter::executeOnPlugin: alsa_controller , getConfigParam Apr 23 04:08:32 volumio volumio[804]: info: CoreCommandRouter::executeOnPlugin: alsa_controller , getAlsaCards Apr 23 04:08:32 volumio volumio[804]: info: CoreCommandRouter::executeOnPlugin: alsa_controller , getConfigParam Apr 23 04:08:32 volumio volumio[804]: info: CoreCommandRouter::executeOnPlugin: alsa_controller , getConfigParam Apr 23 04:08:32 volumio volumio[804]: info: CoreCommandRouter::executeOnPlugin: alsa_controller , getConfigParam Apr 23 04:08:32 volumio volumio[804]: info: CoreCommandRouter::executeOnPlugin: alsa_controller , getConfigParam Apr 23 04:08:32 volumio volumio[804]: info: CoreCommandRouter::executeOnPlugin: alsa_controller , getConfigParam Apr 23 04:08:32 volumio systemd[1]: Started DJMmount. Apr 23 04:08:32 volumio sudo[895]: pam_unix(sudo:session): session closed for user root Apr 23 04:08:32 volumio volumio[804]: info: BOOT COMPLETED Apr 23 04:08:32 volumio volumio[804]: Express server listening on port 3000 Apr 23 04:08:32 volumio volumio[804]: Volumio Calling Home Apr 23 04:08:32 volumio volumio[804]: info: [1492920512298] CoreStateMachine::resetVolumioState Apr 23 04:08:32 volumio volumio[804]: info: [1492920512301] CoreStateMachine::getcurrentVolume Apr 23 04:08:32 volumio volumio[804]: info: CoreCommandRouter::volumioRetrievevolume Apr 23 04:08:32 volumio volumio[804]: info: [1492920512341] CoreStateMachine::updateTrackBlock Apr 23 04:08:32 volumio volumio[804]: info: [1492920512345] CorePlayQueue::getTrackBlock Apr 23 04:08:32 volumio ifup[441]: dhcpcd[464]: timed out Apr 23 04:08:32 volumio ifup[441]: dhcpcd[464]: allowing 8 seconds for IPv4LL timeout Apr 23 04:08:32 volumio dhcpcd[464]: timed out Apr 23 04:08:32 volumio dhcpcd[464]: allowing 8 seconds for IPv4LL timeout Apr 23 04:08:32 volumio volumio[804]: info: Cannot read play queue form file Apr 23 04:08:32 volumio systemd[1]: djmount.service: main process exited, code=exited, status=1/FAILURE Apr 23 04:08:32 volumio systemd[1]: Unit djmount.service entered failed state. Apr 23 04:08:32 volumio volumio[804]: info: DJMOUNT Started Apr 23 04:08:32 volumio volumio[804]: info: MPD running with PID556 ,establishing connection Apr 23 04:08:32 volumio mpd[556]: client: [1] opened from local Apr 23 04:08:32 volumio volumio[804]: info: Setting Device type: Raspberry PI Apr 23 04:08:32 volumio sudo[943]: volumio : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/usr/sbin/i2cdetect -y 1 Apr 23 04:08:32 volumio sudo[943]: pam_unix(sudo:session): session opened for user root by (uid=0) Apr 23 04:08:32 volumio sudo[943]: pam_unix(sudo:session): session closed for user root Apr 23 04:08:32 volumio systemd[1]: djmount.service holdoff time over, scheduling restart. Apr 23 04:08:32 volumio systemd[1]: Stopping DJMmount... Apr 23 04:08:32 volumio systemd[1]: Starting DJMmount... Apr 23 04:08:32 volumio volumio[804]: info: [1492920512922] VolumeController:: Volume=40 Mute =false Apr 23 04:08:32 volumio volumio[804]: info: [1492920512935] CoreStateMachine::pushState Apr 23 04:08:32 volumio systemd[1]: Started DJMmount. Apr 23 04:08:32 volumio volumio[804]: info: [1492920512942] CoreStateMachine::getState Apr 23 04:08:32 volumio volumio[804]: info: [1492920512945] CorePlayQueue::getTrack 0 Apr 23 04:08:32 volumio volumio[804]: info: CoreCommandRouter::volumioPushState Apr 23 04:08:32 volumio volumio[804]: info: CoreCommandRouter::executeOnPlugin: volumiodiscovery , saveDeviceInfo Apr 23 04:08:32 volumio volumio[804]: info: [1492920512957] interfaceApi::pushState Apr 23 04:08:32 volumio volumio[804]: info: [1492920512960] InterfaceWebUI::pushState Apr 23 04:08:33 volumio volumio[804]: info: Pushing Favourites {"service":"mpd","uri":"","favourite":false} Apr 23 04:08:33 volumio volumio[804]: info: Apr 23 04:08:33 volumio systemd[1]: djmount.service: main process exited, code=exited, status=1/FAILURE Apr 23 04:08:33 volumio systemd[1]: Unit djmount.service entered failed state.

Tried manual loading later but also fails.

Otherwise functionality is fine.