Random Thoughts
Since I haven't posted anything here in a long time, today seems like a good day to do so...
First of all, there were LOTS of questions regarding the lack of updates to -current in late October and early November, and while Eric and I addressed it on AOLS, I'll do so again here. As is plainly obvious now, the batch of updates that went out after all that time had quite a few big changes - in particular, the move from 2.6.24.x to 2.6.27.x required quite a bit of research and testing. While it might be nice to have a weekly "status update" or some such, the fact of the matter is that doing so would take time away from doing *real* work; ultimately, it seems much better for everyone involved if the ChangeLog shows *results* of work rather than *ideas* of work.
Second, I think the -current tree has mostly stabilized to the point of being safe to build packages against it intended for long-term usage, so I've just released the first batch of my unofficial contributions on my packages page.
Third, for anyone who happens to be in the Tuscaloosa area, a few of us have started a Tuscaloosa Linux Users Group, so have a look at it.
Finally, we have closed the submission form at SlackBuilds.org to give us time to clear out pending and prepare for the release of Slackware 12.2.
posted by Robby Workman @ 16:09
2 Comments
2 Comments:
Thank you for answering my request of a weekly update! :)
I not meant a fully written update on -current if you have a lot of work of testing -current.
But there is no public developer mailing list and so it's the only source what happens.
If you are fully working on -current then a 'no weekly update for public, but we're alive' is enough at -current list and takes not more than 5 minutes.
If Patrik is ill again or something other happens, we live at nowhere.
As long as you see some of us alive on the IRC channels or doing package updates, all is well. :)
Post a Comment
Subscribe to Post Comments [Atom]
<< Home