Comments on: Not That Edgy http://netsplit.com/2006/10/27/not-that-edgy/ Tue, 07 Feb 2012 11:48:49 +0000 hourly 1 http://wordpress.org/?v=3.3.1 By: Raphael http://netsplit.com/2006/10/27/not-that-edgy/#comment-1307 Raphael Sat, 28 Oct 2006 11:39:35 +0000 http://netsplit.com/2006/10/27/not-that-edgy/#comment-1307 IMO, it would go along way towards better reviews and less user frustration if there was a page explaining _why_ X or Y didn't get in. For example, myself I can not really understand why NetworkManager didn't make it but I'm sure there's a good reason for that decision... IMO, it would go along way towards better reviews and less user frustration if there was a page explaining _why_ X or Y didn’t get in. For example, myself I can not really understand why NetworkManager didn’t make it but I’m sure there’s a good reason for that decision…

]]> By: jldugger http://netsplit.com/2006/10/27/not-that-edgy/#comment-1306 jldugger Sat, 28 Oct 2006 04:03:56 +0000 http://netsplit.com/2006/10/27/not-that-edgy/#comment-1306 I said it almost the moment I read Mark's release: He was "promising to impose (almost ;-) zero from-the-top requirements for Edgy" not because he wanted "cutting edge, perhaps bleeding edge, brand new code and infrastructure," but because there wasn't enough time to make significant improvements. You'll note that of the improvements hinted at in the release, none really made it to main. And really, that's fine by me. I'd rather upgrade from Dapper to a newer but marginally better Edgy than watch Edgy cut things from the safety of Dapper, knowing that in six months times things will be even better. It may be the case that many of the low lying fruit have been picked. In such a case, we should expect diminishing returns with the current six months from start to finish plan. That said, if you're subtly digging for MTV topics, I've got a few suggestions: 1) security-updates should go live the moment security updates can't make it to the regular archive. 2) ditch the keyring crap in networkManager (surely I'm not the only one who feels this way). and maybe help fix suspend, hibernate and resume, etc. 3) tabletPC improvements. this one would probably require the starting of a team to evaluate and implement various changes from drivers and middleware tools to alternate themes more suitable for pen input. I'm guessing this one would require me to step up and drive the initiative given how few developers have tablets. 4) Power consumption specs. Maybe send a few kill-a-watts meters to the right people, and drum up some measurements on how to improve battery performance. dropping from 21 to 19 W, while only a 2 watt gain would be close to a 10 percent improvement in battery life. But now that I think about it, you've probably still got your plate full on upstart. Hopefully when you're much closer to done, you'll have some sage advice for others on how to plan a large scale, long term project ;) I said it almost the moment I read Mark’s release: He was “promising to impose (almost ;-) zero from-the-top requirements for Edgy” not because he wanted “cutting edge, perhaps bleeding edge, brand new code and infrastructure,” but because there wasn’t enough time to make significant improvements. You’ll note that of the improvements hinted at in the release, none really made it to main.

And really, that’s fine by me. I’d rather upgrade from Dapper to a newer but marginally better Edgy than watch Edgy cut things from the safety of Dapper, knowing that in six months times things will be even better. It may be the case that many of the low lying fruit have been picked. In such a case, we should expect diminishing returns with the current six months from start to finish plan.

That said, if you’re subtly digging for MTV topics, I’ve got a few suggestions:

1) security-updates should go live the moment security updates can’t make it to the regular archive.

2) ditch the keyring crap in networkManager (surely I’m not the only one who feels this way). and maybe help fix suspend, hibernate and resume, etc.

3) tabletPC improvements. this one would probably require the starting of a team to evaluate and implement various changes from drivers and middleware tools to alternate themes more suitable for pen input. I’m guessing this one would require me to step up and drive the initiative given how few developers have tablets.

4) Power consumption specs. Maybe send a few kill-a-watts meters to the right people, and drum up some measurements on how to improve battery performance. dropping from 21 to 19 W, while only a 2 watt gain would be close to a 10 percent improvement in battery life.

But now that I think about it, you’ve probably still got your plate full on upstart. Hopefully when you’re much closer to done, you’ll have some sage advice for others on how to plan a large scale, long term project ;)

]]> By: mc http://netsplit.com/2006/10/27/not-that-edgy/#comment-1305 mc Fri, 27 Oct 2006 18:49:17 +0000 http://netsplit.com/2006/10/27/not-that-edgy/#comment-1305 Not Edgy? How about overturning 30 years of UNIX history! Ahem. Anyway, looking at the specs the sabdfl is pushing at MTV, I think feisty may be rather more edgy than edgy. BerylByDefault, eek. Also, please make wireless rock, kthxbye Not Edgy? How about overturning 30 years of UNIX history!

Ahem. Anyway, looking at the specs the sabdfl is pushing at MTV, I think feisty may be rather more edgy than edgy. BerylByDefault, eek.

Also, please make wireless rock, kthxbye

]]> By: Sean http://netsplit.com/2006/10/27/not-that-edgy/#comment-1304 Sean Fri, 27 Oct 2006 17:10:46 +0000 http://netsplit.com/2006/10/27/not-that-edgy/#comment-1304 I'm glad that you guys decided the route that you did with the Edgy release. I've just recently switched over from XP for good now and I may have had to switch back if the release wasn't stable. I’m glad that you guys decided the route that you did with the Edgy release. I’ve just recently switched over from XP for good now and I may have had to switch back if the release wasn’t stable.

]]>