Jim Klimov via Nut-upsuser <[email protected]> writes:
> While a few smaller PRs are still queued and iterated, it would be wise > of the community to run some builds of the current master against their > devices in their OS ecosystems of choice, to make sure we do not get big > facepalms within a week after a release :) My usual request is that if there is going to be a release (which is great), then we need a decent interval -- nominally a week -- after freeze for everthing but typos and version changing, before release. I don't know what the "smaller PRs" are, and I don't mind testing now and refreshing the build to test again. But if we want a good release we really need to stop making changes and have a testing period. Making that short discourages people from testing. > The plan is to cut off a snapshot of the `master` branch (slightly > pre-doctored as usual) into a NUT v2.8.4 release, and so begin the v2.8.5 > timeline, during the first week of August, probably before next Friday. Or > forever hold our silence (that is, until September or later). Given that you seem to intend to still merge things (unless the merges end today), that's too fast, but otherwise sounds good. My first-stage build (not in pkgsrc) has finished build/check/dist on NetBSD 10 amd64. On to building the distfile with pkgsrc, then on older NetBSD and on arm and arm64, and live-testing with Best Fortress. _______________________________________________ Nut-upsuser mailing list [email protected] https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsuser
