pages/source.txt

   1 Source Code Repositories
   2 ========================
   3
   4 include::menu.inc[]
   5
   6 == The Source Code
   7
   8 The LEDE project source code start off with OpenWrt revision r49083. The code
   9 is stored inside a git tree which contains all branches and releases ever made
  10 by OpenWrt. While importing the sources the tree was normalised and some
  11 minor tweaks were made to comitter names and mail addresses.
  12
  13 All repositories can be browsed online through
  14 http://git.lede-project.org/[Gitweb] as well.
  15
  16 === Getting The _LEDE_ Code
  17
  18 Any _LEDE_ development happens in the main +source.git+ repository which is
  19 accessible via both HTTP and HTTPS:
  20
  21 ----
  22 git clone http://git.lede-project.org/source.git
  23 ----
  24
  25 === Getting the OpenWrt Code
  26
  27 We keep the original OpenWrt source code up to r49083 available, mostly as
  28 reference and for historic interest.
  29
  30 The original OpenWrt Subversion repository has been split up into several Git
  31 repositories mapping the various SVN directories and tags to proper Git
  32 branches.
  33
  34 ----
  35 git clone http://git.lede-project.org/openwrt/source.git
  36 git clone http://git.lede-project.org/openwrt/packages.git
  37 git clone http://git.lede-project.org/openwrt/feeds.git
  38 git clone http://git.lede-project.org/openwrt/docs.git
  39 ----
  40
  41 === The Web Presence
  42
  43 The pages you're reading are generated from text files using the
  44 http://www.methods.co.nz/asciidoc/[AsciiDoc] suite. Any changes made to the
  45 projects web site will be reflected in our +web.git+ repository:
  46
  47 ----
  48 git clone http://git.lede-project.org/web.git
  49 ----
  50
  51 === Submitting Patches
  52
  53 The biggest difference is that we now accept pull requests. The tree that shall
  54 be pulled from needs to be hosted publicly. Small fixes and minor patches can
  55 also be submitted via the mailing list (__LINK__). Submissions should follow
  56 these rules
  57
  58 . rule N+1
  59
  60 All patches need to be sent in a format that they are listed in patchwork (__LINK__).
  61 If the patch does not get listed in patchwork then it wont get processed.
  62
  63
  64 === Reporting Bugs
  65
  66 . *All* bug reports need to be submitted via the mailing list (__LINK__)
  67 . When reporting bugs please make sure to
  68   .. Name the tree/revision
  69   .. Name the effected device
  70   .. What does it do that it should not do / what does it not do that it should do
  71   .. Steps to reproduce
  72   .. What you have already done to fix the problem
  73   .. Any additional info you thinks is important
  74 . Reporting a bug means that you reported a bug. It does not constitute a claim that
  75   anyone has to work on fixing it.
  76 . Pointless/vague/silly/... bugs reports will be ignored
  77 . Feature requests are not Bugs. They will also be ignored.
  78 . The better your bug report, the more likely it is that it will be worked on.
  79
  80 All bug reports need to be sent in a format so that they are listed in the issue
  81 tracker (__LINK__). If the bug report does not get listed in the issue tracker then
  82 it wont get processed.
  83
  84
  85 === Patch Merging And Tree Life Cycle
  86
  87 We encourage committers to host their own staging trees where they aggregate patches
  88 that they feel responsible for and/or ones that they created themselves. Once the tree
  89 has been reviewed and tested it can be proposed for inclusion in the master branch.
  90
  91 . Trees will be merged into master during a merge window
  92 . The date when the next merge window opens will be announced in advance
  93 . The window should be less than a week
  94 . Only bug fixes can be merged outside the merge window via the fixes branch (__LINK__)
  95 . No new features/update/... may be merged outside the window
  96 . PRs can be sent to the patches mailing list from any source and will always be considered
  97   for inclusion if the quality of the tree is good and format of submission is correct
  98
  99
 100 === Kernel updates
 101
 102 It has proven impractical and a time killer to always be on the very latest kernel within
 103 2 days of its release. It has caused these issues.
 104
 105 . diversification of kernel versions
 106 . pressure on maintainers to constantly upgrade rather than stabilise
 107 . huge effort invested to upgrade 3-4 times between releases
 108 . huge workload to maintain kmod-* packaging
 109 . Upgrade to kernels that might not be fully tested
 110
 111 This is obviously not an invite to sit on ancient and dusty kernels. A sane path in between
 112 should be taken that give the community recent kernels without causing unnecessary workload
 113 and stability issues.
 114
 115 There should be a max of three concurrent kernel version. Having only two concurrent versions
 116 is better than three.
 117
 118 In Short - stability should be valued higher than bleeding edge, although bleeding edge is
 119 also important, but not as a trade-off to stability.
 120
 121
 122 === Releases
 123
 124 Generating Releases has already been vastly automated. The remaining parts of the process need
 125 to also be automated before the first _LEDE_ release. We will introduce a TESTERS file that is
 126 formatted similarly to the MAINTAINERS file of the kernel. Community members can list themselves
 127 as testers for a target/profile/device. Once a release has been generated testers should receive
 128 an email informing them of the requirement for images to be tested. It needs to be decided if only
 129 tested images should be included in the binary release.
 130
 131 Releases should
 132
 133 . Happen at least once a year
 134 . Have at least one maintenance update
 135 . Provide CVE/critical/... fixes for at least one year after the release
 136 . Only include maintained targets
 137 . Only include targets that have seen on device testing
 138 . Be ready when they are ready
 139
 140 See the TODO page for more info.