[Was: Re: Firmware Selector Setup]

[Moritz Warning]

Hi Baptiste,

On 9/14/20 8:41 PM, Baptiste Jonglez wrote:
> Hi,
> 
> Congrats, great work!
> 
> Here is some feedback on the staging version:
> 
> - the latest stable release should probably be the default (currently,
>   snapshots is the default)
That is currently the date the overview.json file was last modified.
I think we need to change that. Maybe the creation date of the profiles.json file (build by OpenWrt for each target).

> 
> - the date is the same for all models, even for 19.07.4 images: "Mon, 14
>   Sep 2020 10:14:12 GMT".  I'm not sure what this date is supposed to
>   mean.

> 
> - is it possible to add 18.06?
Yes. But we would need to apply a patch [0] to a local copy of OpenWrt 18.06 and then build all images to get the JSON output for each image.
Maybe someone knows a shortcut to avoid actual the actual build of the toolchains etc..

> 
> Regarding 18.06, here is a use-case: I would like to search for a model,
> and then it would give me the latest stable version for it (18.06 or
> 19.07).  A bit like https://openwrt.org/toh/start
> 
> Currently, when I search "WR841", it only gives me TL-WR841N v13 because
> the earlier models are no longer built for 19.07.  It would be nice to
> show the other models; that is, propose 18.06 as a fallback when 19.07 is
> not supported.
> 
> If this is not straightforward to implement, this could be added to a
> later version of YAFS: the current version is already good!
It does not sound straightforward, but it should be doable.

> 
> Thanks,
> Baptiste
> 
> On 14-09-20, Moritz Warning wrote:
>> Hi Petr and everybody else,
>>
>> thank you very much in making this possible!
>> I think this will be a significant step forwards in end user usability.
>>
>> On 9/14/20 12:36 PM, Petr Štetiar wrote:
>>> Moritz Warning <moritzwarning at web.de> [2020-08-01 02:13:05]:
>>>
>>> Hi,
>>>
>>>> we have reached the point that we can finally set up the firmware selector [0]. Yay!
>>>> But somebody need to finally put it on the website...
>>>
>>> so https://firmware-selector.staging.openwrt.org is alive, deployed
>>> automatically from CI pipeline[1]. Any push into master branch deploys site at
>>> firmware-selector.staging.o.o (once all CI tests pass). Then after additional
>>> QA steps done usually by humans it's possible to manually trigger another CI
>>> pipeline which is going to deploy the site at production URL
>>> firmware-selector.openwrt.org.
>>>
>>> Next steps:
>>>
>>>  - fix the `web` group/repo name clash on GitLab.com/openwrt and setup mirroring and
>>>    CI/CD deployment from GitLab.com/openwrt/web/firmware-selector-openwrt-org.git
>>>  - fix remaining issues (if any) on staging and make the site officialy alive
>>>    on firmware-selector.openwrt.org
>>>
>>> I plan to tackle these in the upcoming days.
>>>
>>> 1. https://gitlab.com/ynezz/openwrt-firmware-selector/-/pipelines/189588455
>> Let me know if I can help.
>>
>>>
>>> Cheers,
>>>
>>> Petr
>>>
>>
>>
>> _______________________________________________
>> openwrt-adm mailing list
>> openwrt-adm at lists.openwrt.org
>> https://lists.openwrt.org/mailman/listinfo/openwrt-adm

[0] https://github.com/openwrt/openwrt/commit/881ed09ee6e23f6c224184bb7493253c4624fb9f


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: OpenPGP digital signature
URL: <http://lists.openwrt.org/pipermail/openwrt-adm/attachments/20200914/ed842482/attachment.sig>