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
