Not so strange. Big software projects means alot of things that need to be coordinated. At my job (not audio software, but still) when a new version is about to come out we recieve new binaries (the basic code) from development (wich has been developed and tested there), maybe some new graphics from graphical design, sounds from the sound department. We then package, encrypte and compile all this into an install executable. This then goes to the test department that has to test everything, even old stuff since that may have been effected by the new additions and is often bounced back and forth between us and test a couple of times until acceptable. Release notes is written. Finally the project leader signs off the project and the system owner tests everything again in an acceptance test. Now the tech guys can upload it to all servers and finally update the web scripts to point to the new version. Every step of this needs to be documented in minute detail.h2ogun99 wrote:pdxindy wrote:It may be that it will be different that it has been. My impression (since I am new to this forum) is that Tracktion was having regular updates and more direct feedback with the developer (Jules). That is common with software developed by one person.
Now it is under the auspices of Mackie and it may be more along the usual lines of software development from larger companies. (There are exceptions so it may stay more like it was) That appears to be the case, so some users may feel frustrated with such changes cause it is nice to feel more directly in contact with development and feel like one has some influence over ones tools of choice.
I agree,
it is funny that the 'one man show' software companies can update their software on a near daily basis if wanted, yet the bigger the company, the longer you wait. You would think it would be the opposite. I don't think T2 is any more complicated than T1, in that a few fixes could be delt with in the same timely fasion as when Jules was solo. He used to have them up within 24 hours. I guess we were spoiled.
Lance
When a lone developer works all theese steps are done by her or him alone. There is no need for communication between different departments, different managers to sign acceptance etc. Smaller organizations is always mor efficient, but of course there is only som much one guy can do in a given time period.
