Reply
Thread Tools
ewan's Avatar
Posts: 445 | Thanked: 572 times | Joined on Oct 2009 @ Oxford
#61
Originally Posted by sjgadsby View Post
And that's what made so wonderful Ari Jaaksi's announcement at Maemo Summit 2009 that Nokia will be shifting to use bugs.maemo.org as the sole Maemo bugtracker.
Ah. That is good news.

Originally Posted by bbns View Post
Migration is not gonna happen in short time. It's not just nokia employee using it but some subcontractors, 3rd party companies, etc.
They can all get bugzilla logins too can't they?
 
Posts: 15 | Thanked: 3 times | Joined on Oct 2009
#62
btw i saw the bug for the bluetooth file sharing and voted for it and now some great humanitarian created petrovitch ! i love this place.
 
Posts: 5,335 | Thanked: 8,187 times | Joined on Mar 2007 @ Pennsylvania, USA
#63
Originally Posted by ewan View Post
That is good news.
Yes.

Realistically, do expect Nokia to keep some updates to bugs, and some entire bugs, private within our happy, public bugtracker though. They're still going to want to keep some details of upcoming releases and devices hidden, and there will still be information that cannot be disclosed due to licensing, security, or whatnot.

Still, this will eliminate the excuse of not copying non-sensitive bugs to the public bugtracker one at a time, as they come up, just because it's too much work. Plus, it does away with all that busywork Andre does now playing middleman, freeing his time up for tasks more appropriate to his high skill level.
__________________
maemo.org profile
 

The Following User Says Thank You to sjgadsby For This Useful Post:
ewan's Avatar
Posts: 445 | Thanked: 572 times | Joined on Oct 2009 @ Oxford
#64
Originally Posted by sjgadsby View Post
Yes.

Realistically, do expect Nokia to keep some updates to bugs, and some entire bugs, private within our happy, public bugtracker though. They're still going to want to keep some details of upcoming releases and devices hidden, and there will still be information that cannot be disclosed due to licensing, security, or whatnot.
Well, I'd hope that can be minimised, but certainly there's a legitimate need to have (some) security bugs hidden, and that's pretty common practice in mainstream Linux distribution bug trackers too.

Still, this will eliminate the excuse of not copying non-sensitive bugs to the public bugtracker one at a time, as they come up, just because it's too much work. Plus, it does away with all that busywork Andre does now playing middleman, freeing his time up for tasks more appropriate to his high skill level.
Yup, it'll be a big step forward. It's not enough in itself, Nokia engineers need to have the confidence that they can communicate openly by default without marketing breathing down their necks (as if hiding things from your customers and releasing software that's less well tested than it could be was good marketing anyway), but it should help.
 
Texrat's Avatar
Posts: 11,700 | Thanked: 10,045 times | Joined on Jun 2006 @ North Texas, USA
#65
Understand that this platform started from the direction of closed (ie, commercial world), unlike something like, say, Pandora. If you look back over the history of Maemo you can easily see the steady (but slow) progress toward increased openness.
__________________
Nokia Developer Champion
Different <> Wrong | Listen - Judgment = Progress | People + Trust = Success
My personal site: http://texrat.net
 

The Following 2 Users Say Thank You to Texrat For This Useful Post:
Posts: 5,335 | Thanked: 8,187 times | Joined on Mar 2007 @ Pennsylvania, USA
#66
Originally Posted by Texrat View Post
If you look back over the history of Maemo you can easily see the steady (but slow) progress toward increased openness.
Yes, though a phrase involving "kicking and screaming" does spring to mind at times, movement does appear to be in the correct direction.
__________________
maemo.org profile
 
pelago's Avatar
Posts: 2,121 | Thanked: 1,540 times | Joined on Mar 2008 @ Oxford, UK
#67
Originally Posted by freppas View Post
OK, here's a question: if we do end up OTA fixing bugs automatically on the go, how do we communicate what's been fixed?

Honestly, the average consumer (and quite a few of them have the device), will probably not want to search for bug fixes all the time so they're likely to not bother finding fixes to what's bugging them (pun intended). But if you do it automatically then they'd probably like to know that their email clients now work perfectly etc.
Application Manager supports changelogs for individual updates (if the package maintainer bothers to fill them in), so I would argue that if individual updates were released one-by-one the changes in each package would be more visible to the user than if hundreds of updates were rolled into one SSU.
 

The Following 3 Users Say Thank You to pelago For This Useful Post:
Posts: 73 | Thanked: 11 times | Joined on Nov 2009 @ uk
#68
Originally Posted by Andre Klapper View Post
If that is https://bugs.maemo.org/show_bug.cgi?id=5315 , it is fixed internally.
i knew that thanks, but just getting it on the device would be good.
 
Posts: 107 | Thanked: 94 times | Joined on Dec 2007
#69
Originally Posted by Texrat View Post
Understand that this platform started from the direction of closed (ie, commercial world), unlike something like, say, Pandora. If you look back over the history of Maemo you can easily see the steady (but slow) progress toward increased openness.
Changing a corporate behemoth to operate in a new way is like steering an oil supertanker. A super tanker can't turn on a dime, and neither a large corporation. So nice and steady change is the best pace one can hope for.
 
Helmuth's Avatar
Posts: 1,259 | Thanked: 1,341 times | Joined on Oct 2009 @ Germany
#70
Fixed internally is a good beginning, but, now... 3 weeks after the fix nothing happens... and no way to get a internally version.

Have we all together start to work for Nokia?
Is buying the phone not enought?

Okay, stop kidding. Is that the way that we must wait many weeks or month for every single small fix?

There are a lot of even small issues in the calendar, in the contacts and so one. Sometimes only about 1 oder 2 hour's of work including testing, I guess.

Release small Hotfixes for this small bugs and issues would really disarm a lot of the upset!
 
Reply


 
Forum Jump


All times are GMT. The time now is 00:23.