I have been thinking of coming back to this and working on the release process aspect. Once it looks reasonably in hand against a fork I'd like to move forward and maybe cut a low-stakes / non security release.
I wanted to give folks one more chance to raise any blockers/concerns, either inline here or in the cwiki below: https://cwiki.apache.org/confluence/spaces/HTTPD/pages/311628229/Read+Write+git+migration On Tue, Aug 20, 2024 at 3:52 AM Ruediger Pluem <[email protected]> wrote: > > > > On 8/19/24 7:44 PM, Roy T. Fielding wrote: > >> On Aug 19, 2024, at 8:22 AM, Eric Covener <[email protected]> wrote: > >> > >> To bring the convo back here out of cwiki -- in a world where we moved > >> to read/write git, with reviews happening in the context of a pull > >> request, does anyone else have any feelings about ditching or keeping > >> the STATUS file? > > > > I created STATUS to help drive dev conversations toward a release. > > A resource-based window on open issues, organized by tag or priority, > > would be just as good and easier to maintain. +1 to a replacement. > > > > I suggest leaving STATUS as a static file containing a link to the new > > resource > > and maybe examples of using the GH API to download a local copy of issues. > > Let's try this. If it does not work out we just change it to something else > that works better. > > Regards > > Rüdiger > -- Eric Covener [email protected]
