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
Skin engine enhancements (themes, guide colors, skin functions, weather settings...)
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="tourettes" data-source="post: 825461" data-attributes="member: 10858"><p><strong>Re: AW: Skin engine enhancements (themes, guide colors, skin functions, weather setti</strong></p><p></p><p></p><p></p><p>Once 1.2.2 content (==fixes) have been merged to master (if they haven't already) then it is possible to have almost 1.2.2 + skin engine enchaments build after Andy merges the master to his feature branch - some ohter feature could be completed and merged to master. Code will always flow from the master to the feature or bug fix branhes, there wont be exceptions to that as it will just create much more complex repository workflows (it could easialy double the branch amount).</p><p></p><p>In short We aren't going to have feature branches based on some real releases (1.2.2, 1.2.3, 1.3.0 etc.). If such is wanted then what would need to be done is to create a fork from MediaPortal 1 GitHub repository and then to create the non-standard branch in there.</p></blockquote><p></p>
[QUOTE="tourettes, post: 825461, member: 10858"] [b]Re: AW: Skin engine enhancements (themes, guide colors, skin functions, weather setti[/b] Once 1.2.2 content (==fixes) have been merged to master (if they haven't already) then it is possible to have almost 1.2.2 + skin engine enchaments build after Andy merges the master to his feature branch - some ohter feature could be completed and merged to master. Code will always flow from the master to the feature or bug fix branhes, there wont be exceptions to that as it will just create much more complex repository workflows (it could easialy double the branch amount). In short We aren't going to have feature branches based on some real releases (1.2.2, 1.2.3, 1.3.0 etc.). If such is wanted then what would need to be done is to create a fork from MediaPortal 1 GitHub repository and then to create the non-standard branch in there. [/QUOTE]
Insert quotes…
Verification
Post reply
Forums
MediaPortal 1
Area 51 - Testing Area
Skin engine enhancements (themes, guide colors, skin functions, weather settings...)
Contact us
RSS
Top
Bottom