Hi all,
Although I'm not a developer, as someone who cares a lot about documentation, I
have a couple thoughts about this proposal.
1) "Throw out all the old stuff, and start fresh." It's easy to propose, and
maybe even a good idea. But it's worth asking why don't we already have good
dev docs
Folks,
This seems to be working perfectly (I did *not* stay up to see if there would
be a glitch). www.lede-project.org and wiki.lede-project.org now lead to the
same site.
Thanks for all who pitched in.
Rich
> On Nov 29, 2016, at 3:42 AM, John Crispin wrote:
>
> Hi,
>
> we will change DNS
To LEDE-adm and LEDE-dev,
A discussion about the criteria for a first stable LEDE release came up on the
Forum at:
https://forum.lede-project.org/t/criteria-for-first-lede-stable-release/552
Please add your thoughts. Thanks.
___
Lede-dev mailing list
Is it too soon to begin identifying/enumerating the features/packages that will
go into the 17.01 release? Thanks.
Rich
___
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev
If I remember correctly, there was a window for submitting updates for the
initial Release Candidate. Where does that process stand?
___
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev
The website team has been working on the LEDE Project site to prepare it for a
blast of new readers who will come when we make the first release. We think
it's in pretty good shape, but would welcome comments from the community.
Draft home page: https://lede-project.org/playground/start2
Draft
Hi Jo,
> there hasn't been much progress on the planning since I didn't follow
> any mails for the last week or so :)
>
> I plan to factor in the various suggestions into the roadmap I initially
> posted and put the result into the wiki tomorrow.
Excellent! Once that's public, we can spread the
> On Jan 16, 2017, at 1:37 PM, Jo-Philipp Wich wrote:
>
> this is just a heads-up to inform you that LEDE master has been branched
> into a new branch "lede-17.01" now.
And a hearty congratulations to everyone who helped get us this far. Thanks!
I haven't seen these discussed anywhere, but I t
> On Jan 16, 2017, at 1:37 PM, Jo-Philipp Wich wrote:
>
> this is just a heads-up to inform you that LEDE master has been branched
> into a new branch "lede-17.01" now.
Thanks to everyone who has contributed to the Release Notes. Here's the current
state: If you think something's missing, plea
Since no changes have occurred to the release notes in the last 5 days, I
assume they are complete and final.
If you wish to prove me wrong, please send me a note, or update them directly
at: https://lede-project.org/playground/draft-release-notes
I have pasted the current text below for your
A couple questions about the release images and what we want to call them:
1) When I got to downloads.lede-project.org, I see the following directory
structure:
../
releases/
packages/17.01/
...
snapshots/
faillogs/
packages/
targets/
I do NOT see any targets under the /releas
Hi Jo,
Thanks for all this information. I'll propagate it to the forum, since many
people are asking.
> On Jan 28, 2017, at 9:35 AM, Jo-Philipp Wich wrote:
>
> Hi Rich,
>
>> 1) When I got to downloads.lede-project.org, I see the following
>> directory structure: [...] I do NOT see any targets
Hi Jaap,
> On Jan 28, 2017, at 6:36 AM, Jaap Buurman wrote:
>
> Great job on the release notes! One minor thing that I think looks
> nicer would be the removal of "nothing specific" after "improved
> performance", since it adds no additional information. But that's just
> me.
Thanks for the kin
Folks,
There have been a couple questions on the forum about what needs to be tested
in the LEDE release candidate.
I put together a draft of a note that lists how to install, what to test, and
how to report problems. It's at:
https://lede-project.org/playground/releasecandidatetestplan
Comme
Update on the release documentation. There's a new top-level page to describe
Release Builds at: https://lede-project.org/releases/start
jow has updated and coalesced the release documentation into a single directory
at /releases/17.01 You can read the improved documents at:
Overview: https://l
A multi-part question:
1) Does the LEDE community have any favorite scripts that might be included in
the basic LEDE distribution?
For example, I wrote a "getstats.sh" script
(https://github.com/richb-hanover/OpenWrtScripts/blob/master/getstats.sh) that
collects a consistent set of informatio
> On Feb 1, 2017, at 12:25 PM, Ben Greear wrote:
>
> On 02/01/2017 09:13 AM, Rich Brown wrote:
>> A multi-part question:
>>
>> 1) Does the LEDE community have any favorite scripts that might be included
>> in the basic LEDE distribution?
>>
>>
Hi Ben,
> On Feb 2, 2017, at 8:54 AM, Ben Greear wrote:
>
> I think you would have to make a new LEDE package to allow users to choose
> your script
> to be included at compile time so that it is available on the FS.
>
> Or possibly, it is worth extending ct-bugcheck to have your tool in it an
To all who devoted so much effort into rolling out LEDE 17.01.0...
This has been a monumental project, requiring thousands of updates, bug fixes,
and serious re-designing of so many parts of the code base and build machinery.
I also thank those who worked to create the supporting infrastructure
Hi folks,
[This is a followup to my Getting Started issue on github
(https://github.com/lede-project/web/issues/18) I suspect this is a better
place to ask questions than on github...]
I'm screwing up my courage to install LEDE on a router at home. As I promised
in the github issue, once I ge
Update: I had good success getting LEDE installed on two routers (Netgear
WNDR3800 and mqmaker WiTi Router).
Based on that experience, I created a "Getting Started with LEDE" page that
could become the home page of the Documentation section. I submitted a PR for
review and (hopefully) incorpora
I have always wanted to try out homenet. In light of the recommendation
expressed in
http://lists.infradead.org/pipermail/lede-dev/2016-July/001772.html, it looks
as if LEDE would be a good platform for further experimentation.
I followed Tore Anderson's excellent instructions at:
https://blo
Folks,
I was planning to advocate for a forum as well. I have enjoyed using the
Discourse forum (http://discourse.org) with several projects. (If you haven't
seen it, it's a new forum system, designed by people who have used lots of bad
ones, and intend to fix those problems.) I have some exper
Folks,
I was planning to advocate for a forum as well. I have enjoyed using the
Discourse forum (http://discourse.org) with several projects. (If you haven't
seen it, it's a new forum system, designed by people who have used lots of bad
ones, and intend to fix those problems.) I have some exper
Another thought: I strongly recommend that any forum software we choose support
Markdown.
BBcode was astonishing in the last 90's when it first came out. But requiring
BBcode to to make decent formatting for messages is a big disincentive 15 years
later.
Rich
_
> On Jul 27, 2016, at 4:06 PM, Russell Senior wrote:
>
>>>>>> "Rich" == Rich Brown writes:
>
> Rich> Another thought: I strongly recommend that any forum software we
> Rich> choose support Markdown. BBcode was astonishing in the last 90'
Hi Daniel,
(I feel like a one-trick pony here, but...) Could this be bufferbloat? Maybe
not, but here's how to test:
Use the procedure for "A Quick Test for Bufferbloat" at
https://www.bufferbloat.net/projects/cerowrt/wiki/Tests_for_Bufferbloat/#a-quick-test-for-bufferbloat
Watch to see if the
advocate that we set up:
1) A Wiki that serves as documentation for LEDE
2) A Forum that lets the community talk to each other
I'll talk about each in their own threads, so each conversation can continue on
its own. Thanks.
Rich Brown
_
documentation systems. If we decide to reserve edit permission for top-level
pages to certain admins, we can leave the rest of the pages open to any
logged-in member.
Thanks for listening.
Rich Brown
PS To those who advocate choosing a different wiki system, please include in
your proposal an
named in the original "forum
thread" in the list starting at:
http://lists.infradead.org/pipermail/lede-dev/2016-July/001996.html
most of those listed seem to have a feel of "we've always done it this
way". None seems to offer all the good at
ToH maintainer, Gardener, Editor
N.N.wiki admin / enabler / maintenance
ToH maintainer
Alberto Bursi (alberto.bu...@outlook.it) Editor, Gardener
Rich Brown (richb.hano...@gmail.com) Editor, Gardener, and maybe maintenance
---
I posted some thoughts about how the wiki navigation might work on the ToDo
page at: https://wiki.lede-project.org/talk:to_do_list
Comments please!
Rich
___
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinf
Two items re: wiki
1) I finished importing the entire www.lede-project.org site into the wiki. You
can see the current (draft) pages at:
https://wiki.lede-project.org/playground:experiment:docs:start
2) I added a comment about potential organization at:
https://wiki.lede-project.org/talk:to_do
The "experimental" section of the Wiki now substantially clones the entire web
presence of www.lede-project.org. See the update info at:
https://wiki.lede-project.org/talk:to_do_list
Rich
___
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://li
The question has come up on the forums about the status of a 18.05 release.
Back on 1 April 2018, Hauke wrote:
> I would propose this timeline:
> 1. Branch of openwrt-18.05 at 7. April
> 2. Create openwrt-18.05-rc1 release on 14. April
> 3. Create openwrt-18.05-rc2 release on 28. April
> 4. Creat
Hi folks,
It has been exactly a month since Hauke sent his note recommending a release
process for the next OpenWrt stable.
http://lists.infradead.org/pipermail/lede-dev/2018-April/011704.html I have not
seen any further discussion of this proposal.
Given that the OpenWrt/LEDE merger was found
36 matches
Mail list logo
