i can not understand all the members not wanting to wait until its done it seems like they don't care about the quailty?
or maybe they don't understand the times needed to make the updates?
1 program version is relased as stable
2 users of programs on different systems find same errors on all systems and errors are not all caused by the same thing.
3 users report bugs to the developers with as much info about their system as they know, the developers start working on them to get the bugs fixed.
4 each developer does the bugs they are most able to fix, they attempt to fix the bug by either hunt and search for other program developers forums for most likely error, or they do trial and error code fixes which could take up to a week to fix it some times longer depending on how hard the bug is to locate.
5 the developers get together and hash out the errors when they can and then send the updated code to the main developers for adding it in to the main program.
6 the main developer has to then check the program one update at a time to see if the update caused any other errors.
and if it is being messed with by any other of the updated codes, if so then they have to fix that new error or make the new updates play nice with each other. and that might take up a couple of months to get all that worked out.
7 then they release the update patch.
8 users find more errors now in the updated version and they start the process over again to fix them.
9 making a new version of the program throughs a hammer in the routine and now they have to add more time to fix
the errors found in the new version along with the patches for the old version they were updating.
10 now the OP system companys through in their hammers which is to change things in the op's for the desktops, laptops, or other hand held devices, which makes more errors in the program and causes about 3 more months to find all those they can and fix them before they release the new stable version of the program.
so it is as you can see NOT a FAST or easy fix. the developers would love to have it all fixed in one night. but that is not possible with all the above hammers being tossed in to play.
now mediamonkey with the developers in different countrys has the most ideal situation for they can cover tons of code errors all day with each of them being up at different times. so that makes mediamonkey the fastest updated and upgraded program i've seen as in a world wide used program. but it still takes some time, also because the developers are not machines they have lives they have to live too going to work or college or other personel issues they have to deal with.
they can not sit in the chair and do coding 24 hours a day. some also like to take vacations and go someplace where they can not think about coding in order to clear their head. tin foil only works for so long. and under the desk vacations arnt really that fun.
i can not understand all the members not wanting to wait until its done it seems like they don't care about the quailty?
or maybe they don't understand the times needed to make the updates?
1 program version is relased as stable
2 users of programs on different systems find same errors on all systems and errors are not all caused by the same thing.
3 users report bugs to the developers with as much info about their system as they know, the developers start working on them to get the bugs fixed.
4 each developer does the bugs they are most able to fix, they attempt to fix the bug by either hunt and search for other program developers forums for most likely error, or they do trial and error code fixes which could take up to a week to fix it some times longer depending on how hard the bug is to locate.
5 the developers get together and hash out the errors when they can and then send the updated code to the main developers for adding it in to the main program.
6 the main developer has to then check the program one update at a time to see if the update caused any other errors.
and if it is being messed with by any other of the updated codes, if so then they have to fix that new error or make the new updates play nice with each other. and that might take up a couple of months to get all that worked out.
7 then they release the update patch.
8 users find more errors now in the updated version and they start the process over again to fix them.
9 making a new version of the program throughs a hammer in the routine and now they have to add more time to fix
the errors found in the new version along with the patches for the old version they were updating.
10 now the OP system companys through in their hammers which is to change things in the op's for the desktops, laptops, or other hand held devices, which makes more errors in the program and causes about 3 more months to find all those they can and fix them before they release the new stable version of the program.
so it is as you can see NOT a FAST or easy fix. the developers would love to have it all fixed in one night. but that is not possible with all the above hammers being tossed in to play. :(
now mediamonkey with the developers in different countrys has the most ideal situation for they can cover tons of code errors all day with each of them being up at different times. so that makes mediamonkey the fastest updated and upgraded program i've seen as in a world wide used program. but it still takes some time, also because the developers are not machines they have lives they have to live too going to work or college or other personel issues they have to deal with.
they can not sit in the chair and do coding 24 hours a day. some also like to take vacations and go someplace where they can not think about coding in order to clear their head. tin foil only works for so long. and under the desk vacations arnt really that fun.
8)
