Happy to help with this as well, feel free to reach out if the dependencies get gnarly!
On Tue, Aug 8, 2023 at 11:21 PM Joshua Poore <poor...@apache.org> wrote: > Hi All, > > Looking forward to coordinating with you on the release. There are still a > few issues to do—mostly dependency management. > > Could really use help with a few tickets—especially updating Cypress for > Journey Tests. > > Also, we should look into testing against Node 19.x, 20.x. We’re seeing > some failing tests on 19.x which may be due to some libs like Rollup that > need updating. > > I’ve added some tickets and updated our project related to the release > (candidate). Once, we close the dev/maintenance issues, I think we’ll be > ready to pull together the release candidate, which is where the ASF > process really kicks in. See below for the GH project. > > [image: flagon-useralejs.png] > > Apache Flagon UserALE.js v2.4.0 · apache/flagon-useralejs > <https://github.com/apache/flagon-useralejs/projects/9> > github.com <https://github.com/apache/flagon-useralejs/projects/9> > <https://github.com/apache/flagon-useralejs/projects/9> > > > On Aug 7, 2023, at 12:15 AM, Joshua Poore <poor...@apache.org> wrote: > > 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 > > > > > >
