16 May
2017
16 May
'17
3:42 p.m.
Hi all!
We need a release candidate to be ready for testing at BattleMesh.
I added to lime-packages repository on Github a "WBMv10-RC" milestone
[1] and a "release-blocker" label [2] to use for prioritizing issues.
Bye!
Ilario
[1] https://github.com/libremesh/lime-packages/milestone/1
[2] https://github.com/libremesh/lime-packages/labels/release-blocker
25 May
25 May
7:24 p.m.
On 05/16/2017 05:42 PM, Ilario Gelmetti wrote:
We need a release candidate to be ready for testing at
BattleMesh.
Hi!!
As there was a strange mix between labels and milestones, I deleted
BattleMesh milestone in favor of the release-blocker label:
https://github.com/libremesh/lime-packages/labels/release-blocker
These are the problems we have to try to solve before the BattleMesh,
which is before June the 4th, in just 10 days!!
For the future we will use more intensively the milestones, there's
already a couple of them, one for the 20th of July and for the end of
September:
https://github.com/libremesh/lime-packages/milestones
There are also a few issues which are unclear and need more information
for deciding their priority, here you are, please fill them if you can:
https://github.com/libremesh/lime-packages/labels/needs%20more%20info
Bye!!
Ilario
2 Jun
2 Jun
3:03 p.m.
On 05/25/2017 09:24 PM, Ilario Gelmetti wrote:
On 05/16/2017 05:42 PM, Ilario Gelmetti wrote:
Hi all again!
Seems that there won't be a proper release candidate before BattleMesh.
Anyway they also say that images in
http://repo.libremesh.org/ (compiled every few days by Pau)
are working enough well to be used for testing.
The files including "11s" in the filename have ieee802.11s active by
default instead of adhoc.
There are still lots of issues and pull requests labeled as
"release-blocker" to focus on:
https://github.com/libremesh/lime-packages/labels/release-blocker
Bye!
Ilario
We need a release candidate to be ready for
testing at BattleMesh.
These are the problems we have to try to solve before the BattleMesh,
which is before June the 4th, in just 10 days!! 
5 Jun
5 Jun
8:14 a.m.
Am 02.06.2017 um 17:03 schrieb Ilario Gelmetti:
Anyway they also say that images in
http://repo.libremesh.org/
(compiled every few days by Pau) are working enough well to be used
for testing. The files including "11s" in the filename have
ieee802.11s active by default instead of adhoc.
hi, just checked the contents of
http://repo.libremesh.org/lime-17.04/targets/ar71xx/generic/tl-wr1043nd-v3/…
and inside lime-defaults there seems to be the adhoc default config. is
this on purpose or a "bug"?
regards,
micha
10:20 a.m.
On 06/05/2017 10:14 AM, Micha Stöcker wrote:
Am 02.06.2017 um 17:03 schrieb Ilario Gelmetti:
What surprises me is that there's no
/etc/uci-defaults/80-lime_set_11s.sh
https://github.com/libremesh/network-profiles/blob/master/libremesh/11s/etc…
file that should be included if 802.11s is activated via lime-sdk's
option "--community=libremesh/11s".
Anyway they also say that images in
http://repo.libremesh.org/
(compiled every few days by Pau) are working enough well to be used
for testing. The files including "11s" in the filename have
ieee802.11s active by default instead of adhoc.
hi, just checked the contents of
http://repo.libremesh.org/lime-17.04/targets/ar71xx/generic/tl-wr1043nd-v3/…
and inside lime-defaults there seems to be the adhoc default config. is
this on purpose or a "bug"? 
1:34 p.m.
On 05/06/17 12:20, Ilario Gelmetti wrote:
On 06/05/2017 10:14 AM, Micha Stöcker wrote:
Right, some problem on the compilation process, I'll check it.
Am 02.06.2017 um 17:03 schrieb Ilario Gelmetti:
What surprises me is that there's no
/etc/uci-defaults/80-lime_set_11s.sh
https://github.com/libremesh/network-profiles/blob/master/libremesh/11s/etc…
file that should be included if 802.11s is activated via lime-sdk's
option "--community=libremesh/11s".
Anyway they also say that images in
http://repo.libremesh.org/
(compiled every few days by Pau) are working enough well to be used
for testing. The files including "11s" in the filename have
ieee802.11s active by default instead of adhoc.
hi, just checked the contents of
http://repo.libremesh.org/lime-17.04/targets/ar71xx/generic/tl-wr1043nd-v3/…
and inside lime-defaults there seems to be the adhoc default config. is
this on purpose or a "bug"?
_______________________________________________
lime-dev mailing list
lime-dev(a)lists.libremesh.org
https://lists.libremesh.org/mailman/listinfo/lime-dev
--
./p4u
2510
days inactive
2530
days old
5 comments
3 participants
participants (3)
-
Ilario Gelmetti -
Micha Stöcker -
Pau