Excuse me, which year did they mean?
Topic: Last day in July - final release candidate: 8.08 RC-1
The content of this topic has been archived on 24 Apr 2018. There are no obvious gaps in this topic, but there may still be some posts missing at the end.
Excuse me, which year did they mean?
do you need a refund?
flux wrote:Excuse me, which year did they mean?
do you need a refund?
why? Do you have one for me?
No I'm simply curious if it shall happen in my life time
depends on how long you plan to live
depends on how long you plan to live
does it really depend on this? Then I have to disappoint you guys, you'd better stick to 7.09
(Last edited by flux on 1 Aug 2008, 16:50)
With all due respect to everyone involved......
Wouldn't it be fruitful to change the announcement on the main page?
If the release date has slipped a lot, the 30 seconds it would take to revise that or write a one-line update, seems preferable to posting here in the forums about it.
No I'm simply curious if it shall happen in my life time
lmao ... one day late and you're shitting bricks.
A touchy subject these self-imposed deadlines..
loswillios wrote:depends on how long you plan to live
does it really depend on this?
I reckon so because the release may and/or may not happen in your life time. Cheers.
With all due respect to everyone involved......
Wouldn't it be fruitful to change the announcement on the main page?
If the release date has slipped a lot, the 30 seconds it would take to revise that or write a one-line update, seems preferable to posting here in the forums about it.
openwrt is a free and a good thing. it needs more contributors and less leechers, like everything else in this life. I would like to take the opportunity and express my gratitude for the amount of work that the few developers put for free on this project on a daily basis for so many years.
(Last edited by acoul on 2 Aug 2008, 08:15)
Agreed, I spent many hours doing whatever I could to assist the WRTSL54GS port a year or so ago. Plus about $300 in hardware counting the SL unit I mailed to Kaloz.
However that was a drop in the bucket and a short-term thing compared to their long-haul commitment.
That being said......
The acrimony of forum postings back and forth, could easily be resolved in 30 seconds of web announcement update.
The starting point of all this, was a very public and specific release date which has slipped past without comment. If they had said "late July-early August" then I doubt you would have nitpickers like FLUX in here making snippy comments to start with.
My 2 cents US....worth less and less every day.
(Last edited by vincentfox on 2 Aug 2008, 19:15)
Yes, we are behind. Kaloz has two new servers to configure, but he has been waiting on me to let him know which virtualization platform we should go with, and the state of virtualization on Debian based distros is "interesting" to say the least. I spent several weeks with mbm trying to track down a Xen instability while also testing KVM to see if it would provide decent performance, (not decent enough.) We resolved the Xen problem roughly a week ago and I was able to switch back to working on the impending release. XOrg is building on all platforms, it has been a major PITA to debug, two days ago I asked thepeople and blogic to help working on that. thepeople and myself have been preparing ipkg and opkg for committing, we will be switching to one of them for the release as busybox ipkg is broken and this is the more time expedient solution. nbd has been committing madwifi and boot fixes like a madman.
There are several major patches are being testing, but as the feature freeze date has come and gone I don't know if they will be included in 8.08 or will have to wait until 8.08+1. We are working as fast as we can, and will try to put out an official status update ASAP.
There are several major patches are being testing, but as the feature freeze date has come and gone I don't know if they will be included in 8.08 or will have to wait until 8.08+1. We are working as fast as we can, and will try to put out an official status update ASAP.
Personally, I would say that they should be included if they are useful.
The 'last day in July' deadline should not force you to release an inferior product (or miss your mother's birthday). Just change the date on the main web page and release when the product is ready.
You can tell people have been doing a lot of work to get the latest release ready. I can say this because i have been watching the svn change log on dev.openwrt.org and over the past few weeks i would say the amount of commits daily have tripled if not more.
Just wanted to thank the devs and everyone who commits patch's for all there hard work i have learned a lot in my dealings with OpenWRT and working on enabling and customizing things to work on my wrt600n. It has got my interest back into software and hardware development.
As long as bugs keep getting closed, I'm happy to wait...
7.09 has been remarkebly stable for me (probably a reason why so long to next official release), so no worries about waiting a liitle longer for 8.08.
openwrt is a free and a good thing. it needs more contributors and less leechers, like everything else in this life. I would like to take the opportunity and express my gratitude for the amount of work that the few developers put for free on this project on a daily basis for so many years.
As would I, but I have no knowledge of how to do anything productive towards working with the firmwares so all I can really do is load up what gets released. I am quite grateful for openwrt since its allowed me to get networking to my shed reliably vs the crap dlink bridges I had tried to use in the past, and it also reliably lets me roam between the accesspoints at each end of the link, unlike the crappy powerline networking I used in the past. All up pretty good for something that was at no cost and supported in their spare time by a team of pretty damn talented (IMO) people.
Bartman007 wrote:There are several major patches are being testing, but as the feature freeze date has come and gone I don't know if they will be included in 8.08 or will have to wait until 8.08+1. We are working as fast as we can, and will try to put out an official status update ASAP.
Personally, I would say that they should be included if they are useful.
The 'last day in July' deadline should not force you to release an inferior product (or miss your mother's birthday). Just change the date on the main web page and release when the product is ready.
Just wanted to add as well that I really, really appreciate your work. I'm running different flavors of kamikaze on several WGT634U, and it works great.
So no bickering intended here.
But please, please, update the homepage to reflect the slip of the RC date!
It just confuses peoples, who will be looking around the complete site to find the RC.
I agree with posters' suggestions that it would be nice to update the announcement posted at openwrt.org that intended release dates have slipped, but really, it would only be "nice," not somehow mandatory. Openwrt.org and derivative projects like X-Wrt and Kamikaze are noble volunteer projects that contribute much to the open hardware community, and they're clearly in need of more volunteers.
If it helps others, my current difficulty with Kamikaze v7.09 exhibiting a bad memory leak when I try to run the QOS scripts on a Fonera 2100 router has lead me to hunt down newer copies of the Openwrt codebase elsewhere. In particular, this page German explaining how to install the Funkfeuer OLSR meshing software on Fonera...
http://wiki.freifunk-hannover.de/Fonera_mit_OLSR
...and it links to someone's unofficial Openwrt repository here...
http://ipkg.k1k2.de/
This repo appears to contain updated Openwrt firmware images for the Fonera with the 2.6.24 kernel (Kamikaze v7.09 uses 2.6.21, by comparison), although the ipkg repository itself looks outdated. I hope to test these newer images on the Fonera soon, and can report back to this forum (or elsewhere) for those interested.
I agree with posters' suggestions that it would be nice to update the announcement posted at openwrt.org that intended release dates have slipped, but really, it would only be "nice," not somehow mandatory. Openwrt.org and derivative projects like X-Wrt and Kamikaze are noble volunteer projects that contribute much to the open hardware community, and they're clearly in need of more volunteers.
While I generally agree that they are in no way obligated to steady news, it does not leave a good impression for potential volunteers. And having no current and complete documentation for the (build) system does not help either.
But this is not a problem special to OpenWRT, it is a general problem of many open source projects (and many closed source projects). Writing documentation is always the least favoured part. I recently tried using GnuCash for online banking, and it seems that this program assumes you have serious background in accounting (and the documentation wasn't better ... ).
But I don't claim to be better, I am also often putting it off in favour of adding new features. And while writing good documentation for other users who have experience in the field isn't easy, writing documentation for the casual user is much harder.
It also isn't that easy to be a volunteer tester for openwrt, as probably many use their router as their main router, and can't just test builds every few days or just make an upgrade/downgrade (as it is possible in normal linux distributions). At least I have only one router which needs to be running (I am not the one connected to it). So the best I can do is test packages, but not fixes/changes for the kernel.
But back to topic: OpenWRT-next (lets call it that is done when it's done, and not earlier.
While I generally agree that they are in no way obligated to steady news, it does not leave a good impression for potential volunteers. And having no current and complete documentation for the (build) system does not help either.
What's this about not having documentation?
7.09 documentation can be found easily enough: http://downloads.openwrt.org/kamikaze/docs/
As for more current documentation, you need to read the README that comes in trunk:
https://dev.openwrt.org/cgi-bin/trac.fc … unk/README
"make -C docs/" works for me.
The discussion might have continued from here.