SageTV Open Source Download Area

[jusjoken]

Originally Posted by Fuzzy

I'm not positive, but I think that later runs of open source the v9 installer would still keep the same location as previous

Unfortunately on an upgrade the user will also need to select a location if its other than the default. This should not be hard to resolve as the installer does write the selected location to the registry so it just need to read it back.

Also unfortunately I have no time to change this for a while but its on the list to review.

k

[gary201]

On a whim, I thought I would check to see if a newer version of Sage had been released since the version I'm running (9.2.1), and it looks like 9.2.2 was released last month. However, I have no idea if it's worth the time to update to it since there are no release notes indicating what may have been changed.

It would be nice if there was at least a one-line bulleted list of fixes/changes made.

Just a suggestion..

[KeithAbbott]

Originally Posted by gary201

On a whim, I thought I would check to see if a newer version of Sage had been released since the version I'm running (9.2.1), and it looks like 9.2.2 was released last month. However, I have no idea if it's worth the time to update to it since there are no release notes indicating what may have been changed.

It would be nice if there was at least a one-line bulleted list of fixes/changes made.

Just a suggestion..

https://github.com/google/sagetv/blo...r/CHANGELOG.md

[wayner]

If you are using the unRAID docker version of SageTV it will upgrade every time you restart the docker container. My system backs up all containers weekly so the container gets restarted and updated once a week.

[gary201]

Originally Posted by KeithAbbott

https://github.com/google/sagetv/blo...r/CHANGELOG.md

Perhaps someone can post this link on the site where the downloads are located (https://bintray.com/opensagetv/sagetv/SageTV#) so people can more easily find out what's changed since the download site doesn't contain any info on the release notes tab.

[ASegredo]

https://github.com/google/sagetv/tags Has the 9.1 source downloads
https://bintray.com/opensagetv/sagetv/SageTV# Has the excellent 9.2 binary downloads

But I have a problem with one machine possibly due to needing old libraries/ffmpeg
Is the 9.2 source available?

[jpwegas]

Originally Posted by ASegredo

https://github.com/google/sagetv/tags Has the 9.1 source downloads
https://bintray.com/opensagetv/sagetv/SageTV# Has the excellent 9.2 binary downloads

But I have a problem with one machine possibly due to needing old libraries/ffmpeg
Is the 9.2 source available?

The deploy.sh script says it tags releases in github but it doesn't appear that has been happening as there are no tags since 9.1.6.

The current TravisCI build process builds and releases to Bintray anything that has "[ci release]" in the commit message.

From this, it appears that the last commits to match the Bintray releases are:

9.2.2     https://github.com/google/sagetv/commit/a3f8ef929d46f46aec863f8d88150bf5a6afe31c
9.2.1     https://github.com/google/sagetv/commit/f948f49ef3c670da40a53e16d1a5e9537c301086
9.1.10    https://github.com/google/sagetv/commit/7912487d42f7db28abe1a2bbad409db87338cc15
9.1.9     https://github.com/google/sagetv/commit/0e22903acd823d6f99cf582be717edd3f793a67e

If you want to download the source for those versions, use the link to go to the commit, click on "Browse Files" in the upper right, then select "Code -> Download ZIP".

Or you are using git, just clone the repo and checkout the commit ID you want to review.

--John

[ASegredo]

I did as you suggested. Is there anything in that zip that identifies it as say v9.2.1.485 ?

I gather that if I download the tip I will be getting unreleased code.

[jpwegas]

Originally Posted by ASegredo

I did as you suggested. Is there anything in that zip that identifies it as say v9.2.1.485 ?

Not that I could see unfortunately. That would probably be a nice addition.

Originally Posted by ASegredo

I gather that if I download the tip I will be getting unreleased code.

Correct.

But, the nice thing about git is if you clone the repo, you aren't cloning just a specific commit point - you get everything. All commits, all history, all versions. You can move around to whatever point you like.

After cloning, if you want to view the source as it was for a specific point, you can do "git checkout COMMIT_ID" and git will check out things as it was at that point.

So for example, this would change the local repo to what was in the 9.2.1 release:

git checkout f948f49ef3c670da40a53e16d1a5e9537c301086

Ideally you could just use the tag:

git checkout V9.2.1

But the recent releases haven't been tagged.


--John

[wnjj]

Originally Posted by ASegredo

I did as you suggested. Is there anything in that zip that identifies it as say v9.2.1.485 ?

I gather that if I download the tip I will be getting unreleased code.

The java/sage/Version.java file contains the 9.2.1. I don’t know where the build number at the end comes from.

[stuckless]

FYI, the build number at the end comes the commit number, such that if you have multiple commits between version releases, it'll always be unique.

That being said, I don't think we are automatically publishing releases anymore.

Travis (via the .travis.yml file in the repo) calls the build/deploy.sh on commits to master. This looks for the commit message to have the static text [ci release] in the commit message and if sees it, then it will tag and release the build.

https://github.com/google/sagetv/blo...uild/deploy.sh

This can't be triggered by a Pull Request and it needs to be done with someone that has direct commit access to master. You guys might want to change how the deploy.sh works and just publish with every commit to master. The deploy.sh is in the repo itself, so anyone can change the behaviour here and submit a PR.

[jpwegas]

Originally Posted by stuckless

Travis (via the .travis.yml file in the repo) calls the build/deploy.sh on commits to master. This looks for the commit message to have the static text [ci release] in the commit message and if sees it, then it will tag and release the build.

Sean,
Does the Travis server have permissions to tag the release in github? Or did you mean it tags the Travis build or the Bintray release?

--John

[stuckless]

Originally Posted by jpwegas

Sean,
Does the Travis server have permissions to tag the release in github? Or did you mean it tags the Travis build or the Bintray release?

--John

Travis should be configured with permissions to tag releases and upload to bintray via the configuration of API keys in the travis config (in the travis UI). All this was there when I managed this, and I doubt it has changed. But that's why only a person with direct commit access to the master repo could trigger this.