On 16/06/14 19:44, Arne Babenhauserheide wrote: > Am Montag, 16. Juni 2014, 06:00:07 schrieb xor: >> On Sunday, June 15, 2014 07:46:37 AM Steve Dougherty wrote: >>> Maybe this is something that's not helpful until we have more active >>> developers, but I'd be up for making regularly scheduled releases. Fixes >>> for security or stability problems could still be released sooner. >>> >>> How about the last Friday of each month? >> If you are not annoyed by having to do frequent releases, of course everyone >> would be glad if you did that! :) >> >> Just ensure to have proper testing - we don't want to end up with using half >> of our already small userbase due to something breaking autoupdate. > I also think it would be great to have regular releases. And actually > as I understand it, next should always be releasable. Maybe we can > stricten the rules for next, so a merge to next may only be > commited/pushed if all tests pass. Yes, more testing is good. However it's not clear that we want lots of people to be able to push to next. And there are tests that are fairly costly to run; we should run the "easy" tests locally by default but also rely on continuous integration infrastructure to regularly run the extended tests.
Bigger issue: An update causes a certain amount of network disruption. We should avoid making a release just because we haven't done one recently, at least until this is fixed (there are several solutions on the bug tracker).
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Devl mailing list [email protected] https://emu.freenetproject.org/cgi-bin/mailman/listinfo/devl
