Would love to work with you on this and show you how it’s done!! You can find our release process here: https://cwiki.apache.org/confluence/display/FLAGON/UserALE.js+Release+Management+Procedure
Please let me know if you need access to view (looks like you can from my view). I’ll reach out for a meeting and I can walk you through things. Prior to that it would be good to review the procedure and download some of the utilities that are required to generate a Release Candidate (SVN, DRAT). Looking forward to it! V/r Josh > On Jul 19, 2023, at 8:50 PM, proton_mail_bridge > <jason_...@protonmail.com.INVALID> wrote: > > I’m also interested in the release process, and if anything can be automated. > > @Josh let me know when you plan on doing it, and I’ll tag along. > >> On Jul 19, 2023, at 1:07 PM, Austin Bennett <aus...@apache.org> wrote: >> >> Generally, I'd imagine minor releases. Unless breaking changes. So, >> sounds like this suffices. >> >> Time to dig into our release process and testing. Specifically, wondering >> what all additionally will people potentially do manually - since would >> want to work towards systematizing and automating. >> >> On Wed, Jul 19, 2023 at 10:00 AM Joshua Poore <poor...@apache.org> wrote: >> >>> Hi All, >>> >>> It’s high-time we do a UserALE.js release. We’ve had some great community >>> contributions and we should update packages through Apache and NPM distro >>> for security reasons. >>> >>> Given some of the adds to UserALE.js since last release. Given we have >>> substantive new features, but those features don’t include “breaking >>> changes”, I recommend that we do a MINOR release. This would advance >>> UserALE.js versioning from 2.3.0 —> 2.4.0. >>> >>> Before moving on this plan, I’d like to give the community 72 hours to >>> discuss. In the interim, I’ll begin working on an “RC” branch. >>> >>> -J > >
