- December 6, 2004
- 2,055
- 318
All of us working on MP-TVSeries were very frustrated with SourceForge (very slow, svn commit problems, login problems, overloaded site....) over the past few months, and we finally decided to try an alternative host. Seeing that and how John is hosting the great new moving pictures plugin at google code, and after discussions we decided to move there.
The new URL: mptvseries - Google Code
From now on new commits will only go there...the SF page will continue to exist, but is abandoned.
Binaries ("SVN builds") will not be posted for now. This is for two reasons,
1) we don't want to commit them to svn anymore and we don't have any easy other way to host them, and
2) people don't seem to understand what svn builds are (intended for) and blindly recommend to any new-comer to install them to get a "cool new feature", causing them to experience other issues.
If you want the lastest you will have to build yourself or wait. If we need to community to test something, we will either host a binary build elsewhere and link to it directly, or create a milestone download on code.google.com.
Now, as you may have noticed we have a tendancy to confirm bugs and then forget about them
. This is bad, and mainly because we didn't use any issue trackers at all so far, so if a dev. didn't immediatly fix it it slipped to the back of our heads before they eventually get entirely forgotten. We want to take the opportunity of the switch to change this.
We'll play copy-cat with John once again here and try to let anyone enter new issues into the tracker, at least at first. If that doesn't work (a bad bug report is worse than no bug-report at all) we'll go closed and ask a few experience community members if they would like to help us make these entries. Regardless, always make a forum post first and wait for other people to confirm you're bug. Don't go posting them to the tracker left and right because something doesn't work on your box.
All you need to post issues is a google account (if you have gmail you have one).
So I'd like to ask the community to step in here, and post any bugs, or feature enhancements you have already reported in the past, that were confirmed and have not been resolved yet. If possible add a link to the original thread. Don't post bugs that weren't confirmed by either a team member or at least two community members. Remember, quality, not quantity. The better the report, the easier it is for us to work on it.
Questions, comments, crits?
Greetz
Inker
The new URL: mptvseries - Google Code
From now on new commits will only go there...the SF page will continue to exist, but is abandoned.
Binaries ("SVN builds") will not be posted for now. This is for two reasons,
1) we don't want to commit them to svn anymore and we don't have any easy other way to host them, and
2) people don't seem to understand what svn builds are (intended for) and blindly recommend to any new-comer to install them to get a "cool new feature", causing them to experience other issues.
If you want the lastest you will have to build yourself or wait. If we need to community to test something, we will either host a binary build elsewhere and link to it directly, or create a milestone download on code.google.com.
Now, as you may have noticed we have a tendancy to confirm bugs and then forget about them
We'll play copy-cat with John once again here and try to let anyone enter new issues into the tracker, at least at first. If that doesn't work (a bad bug report is worse than no bug-report at all) we'll go closed and ask a few experience community members if they would like to help us make these entries. Regardless, always make a forum post first and wait for other people to confirm you're bug. Don't go posting them to the tracker left and right because something doesn't work on your box.
All you need to post issues is a google account (if you have gmail you have one).
So I'd like to ask the community to step in here, and post any bugs, or feature enhancements you have already reported in the past, that were confirmed and have not been resolved yet. If possible add a link to the original thread. Don't post bugs that weren't confirmed by either a team member or at least two community members. Remember, quality, not quantity. The better the report, the easier it is for us to work on it.
Questions, comments, crits?
Greetz
Inker
United States of America