[OpenWrt-Devel] High-level process for releases

[Baptiste Jonglez]

Following the 19.07.0 release, I have updated the "release process" page a bit:

  https://openwrt.org/docs/guide-developer/releases/release-process

It is supposed to reflect the current release process and link to the
relevant documentation: feel free to signal missing steps and add links as
needed.

Thomas, regarding the step "Update the ToH to work with the new release",
do you have documentation on how to do that, and an estimation of how much
time it takes?

Thanks,
Baptiste

On 03-12-19, Baptiste Jonglez wrote:
> Hi,
> 
> Following some discussion [1] that started with a focus on communication,
> it turns out that we are missing a high-level process for releases in
> general.  Such a process would have several uses:
> 
> - make sure everyone agrees on the steps towards a release
> - identify which tasks need help, and who can help with them
> - use this process as a checklist when making a new release
> 
> Here is a first draft: https://openwrt.org/inbox/release_process
> 
> Discussion is very welcome to converge to a process that everybody feels
> comfortable with.  The most difficult parts are obviously the ones
> involving decision-making.
> 
> Baptiste
> 
> [1] https://openwrt.org/meetings/20191121



> _______________________________________________
> openwrt-adm mailing list
> openwrt-adm at lists.openwrt.org
> http://lists.infradead.org/mailman/listinfo/openwrt-adm

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: not available
URL: <http://lists.infradead.org/pipermail/openwrt-devel/attachments/20200110/f4e728ac/attachment.sig>
-------------- next part --------------
_______________________________________________
openwrt-devel mailing list
openwrt-devel at lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel