View Single Post
Posts: 560 | Thanked: 422 times | Joined on Mar 2011
#1109
Dear Pali and kernel-dev team

All the work you're doing is great. It's amazing that you're able to maintain the momentum and keep us informed of what's happening. My question is - when the version nudges on to .49 or .48 becomes stable enough to start developing addons, please would you start a new thread for each addon/update e.g "kernel development: abc for v.XY"?

I ask this for a few reasons:
- kernel development extends across so many features thus questions and discussions will be equally diverse. Therefore, they [dicussions] can appear disjointed, which makes finding answers a bit difficult and will in turn result in a lot of people repeating the same question.
- Reading through over a thousand posts to get up to speed on testing things to watch out for is beyond most of us!
- The thread title doesn't accurately reflect its content: it started by pulling together the v0.46 patches, it goes right through all the v0.47 work and now we're discussing pre-extras-devel 0.48.

Consiolidation and evolution are good but but it's quite confusing, especially with the number of sub-topics.

On a completely different note, have you had any news about updating the package interface. I see Titan is still the sole maintainer for a few of the associated packages - might that be something to do with it? A work-around, which would be a pain to start withe because it would break the auto updates would be to upload a package with a new name, say "power-kernel", instead of "kernel-power"? If you did this it might be an idea to make a member of the council a silent 2nd maintainer so it can "change hands" easily in case you can't/dont't want to continue?

I would also like to reiterate that both the code and efforts to update the docs are amazing and really help us all to make the most of this device. I have noticed the irony of this now slightly verbose, multi-themed post so, over-and-out!
 

The Following User Says Thank You to demolition For This Useful Post: