|
23 August 2011
After the release of MediaPortal 1.2.0, we will make major changes to the development model we use.
Lead Developers
To reduce the workload of our MP1 Development Managers arion_p and chemelli, we have started to implement Lead Developers for the various sections of MP1. These lead developers are in charge of their areas. So if you have a question, or a patch for a specific section of MP, they are the experts to contact.
Currently we have Lead Developers for the following 2 sections:
- Deda - Lead Dev Videos
- jameson_uk - Lead Dev Music
Switch to GitHub
As you may know, we successfully migrated MediaPortal 2's source code from our private svn server to GitHub a few months ago. After the release of MP 1.2.0, the trunk from MP1 will be migrated to GitHub as well.
During the migration process we will not be able to commit new code. So the development of MP 1.3.0 will be on hold. We expect this won't take longer than a few days.
We will publish a separate news with the details of the switch, such as dates and technical information about the migration.
Extensive Use of Branches
One of the great benefits of GIT is the speed when working with branches. MediaPortal 1.3.0 will be the first release where we will make extensive use of them. All big features, reworks and bug fixes will be done in their own branch. This ensures that the code of a change is only added to the 1.3.0 code base once it is finished and fully tested.
An unfinished change will no longer delay the release of a new MediaPortal version. It will simply be postponed to the next release. So you can expect more frequent releases of MP.
Public Builds for the Community
With MP 1.3.0 we will re-introduce public builds for you to test - but in a bit different form than you might remember from the past.
- MediaPortal 1.3.0 will have its own section in the MP1 development forums
- inside this forum, every branch will have its own thread, featuring:
- download links of public builds for testing
- change logs about what changed between those builds
- documentation regarding the change
- These threads will also be the place for your to post your feedback and bug reports
- There will also be builds from the 1.3.0 code base, which includes the already merged changes
- All builds are done manually - there won't be automated nightly builds.
This allows the developer to obtain focused testing as soon as he feels his code is ready to be tested.
{jfusion_discuss 99641}
News & Blogs