home
products
contribute
download
documentation
forum
Home
Forums
New posts
Search forums
What's new
New posts
All posts
Latest activity
Members
Registered members
Current visitors
Donate
Log in
Register
What's new
Search
Search
Search titles only
By:
New posts
Search forums
Search titles only
By:
Menu
Log in
Register
Navigation
Install the app
Install
More options
Contact us
Close Menu
Forums
MediaPortal 1
Area 51 - Testing Area
CableCARD tuner support for MediaPortal 1
Contact us
RSS
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Reply to thread
Message
<blockquote data-quote="chefkoch" data-source="post: 1015171" data-attributes="member: 10438"><p>sure, but we need kind of a concept how to deploy test versions. Packages for the releases is not a problem, but what if mm created a new branch with some fixes and would like to include this into it's own repo as nuget packages?</p><p> </p><p>Creating "pre-release" / "unstable" packages from latest dev state and uploading them to our official nuget feed is possible and no problem of course, but releases of packages which are in their own branches should not go to this feed, as versioning is difficult / more complex this way. (maybe hosting a separated NuGet-feed at myget could be a solution for such branch releases)</p><p> </p><p>I will prepare the nuget package specifications for the MP2 core files first so that we are able to upload packages for releases and "pre-release" versions from dev-branch to the official nuget feed. Everything else can be sorted out later.</p><p> </p><p>The implementation of this package in the TVE or MP1 build process needs to be done by someone else, especially the NSIS code won't be touched by me. I don't understand how the dev workflow for TVE35 is working. Who is reviewing and merging branches etc...</p></blockquote><p></p>
[QUOTE="chefkoch, post: 1015171, member: 10438"] sure, but we need kind of a concept how to deploy test versions. Packages for the releases is not a problem, but what if mm created a new branch with some fixes and would like to include this into it's own repo as nuget packages? Creating "pre-release" / "unstable" packages from latest dev state and uploading them to our official nuget feed is possible and no problem of course, but releases of packages which are in their own branches should not go to this feed, as versioning is difficult / more complex this way. (maybe hosting a separated NuGet-feed at myget could be a solution for such branch releases) I will prepare the nuget package specifications for the MP2 core files first so that we are able to upload packages for releases and "pre-release" versions from dev-branch to the official nuget feed. Everything else can be sorted out later. The implementation of this package in the TVE or MP1 build process needs to be done by someone else, especially the NSIS code won't be touched by me. I don't understand how the dev workflow for TVE35 is working. Who is reviewing and merging branches etc... [/QUOTE]
Insert quotes…
Verification
Post reply
Forums
MediaPortal 1
Area 51 - Testing Area
CableCARD tuner support for MediaPortal 1
Contact us
RSS
Top
Bottom