developer help: provide binary patches only for test usages [not relevant]
asked 2015-11-04 10:25:48 +0300
Hello Jolla-men and especially managers,
you have a great developer team, who are really active. And make a good job. And are right pleasing. And sometime they make some fix of problem, and test by themselves. And i have the feeling that they are alone on their problems.
I'm not a developer, but want/is motivated to help on testing their works, for going faster on a successful resolution.
would it be possible to organize a kind of binary patch, when the dev is satisfied or need further testing help from extern side. A patch dedicated only on the issue that he solved and just for testing usage. That we could de-install when we upgrade the OS (for example).
That's not a kind of impatience. But if a bug is fixed, then it comes not necessary on next release, and even if it is tested, sometimes it is not enough tested, and other issues appears.
By this suggestion is to be sure, that if an issue is fixed, not just jolla test it internally, but all interested person could bring their part. And the fix which goes in forge has more chance to be the last and the only good one.
Wish you have a good time, and a good sail.
Isnt that what Early Access is for? Of course, this type of approach would make single fixes faster available, but might be not so feasible for all fixes..
tortoisedoc ( 2015-11-04 10:36:14 +0300 )editno early acces if for the whole os. Here i speak about an issue to be fixed. just one. furthermore, the early access of the system where you want to see your fix, could be in the second next release. and never accessible at bug fixation.
cemoi71 ( 2015-11-04 10:51:29 +0300 )editthe purpose is for a direct test as soon as the developer is able to provide his patch. and for security has no garantee. responsibility would be on the extern test/user side.
cemoi71 ( 2015-11-04 10:53:16 +0300 )edit