Hi Josh, On Tue, Jun 13, 2017 at 12:48 PM, < [email protected]> wrote:
> > From: "Poore, Joshua C." <[email protected]> > To: "[email protected]" <[email protected] > > > Cc: > Bcc: > Date: Tue, 13 Jun 2017 19:48:01 +0000 > Subject: Preparing for UserALE.js Release > @PMC, @Lewis- > > We have just a few tickets left in our UserALE.js v 0.1. pipeline in > preparation for a release. https://issues.apache.org/ > jira/secure/RapidBoard.jspa?rapidView=135&projectKey= > SENSSOFT&view=planning&selectedIssue=SENSSOFT-184&versions=visible& > selectedVersion=12339748 > > Very soon, you should see an update to our UserALE.js docs ( > senssoft.apache.org) reflecting updated test and contribution guides. > http://senssoft.apache.org/docs/useralejs/contributing.html > > We have also updated our Release Management Procs for UserALE.js > https://cwiki.apache.org/confluence/display/SENSSOFT/ > UserALE.js+Release+Management+Procedure > > All of the above is excellent. I am glad to see that UserALE.js is in this condition and this far along. A lot of work has been going on and it is looking tip top. Can I ask, does the release work apply to the entire SensSoft stack or is it just UserALE? > Can you walk us through the next steps leading up to a vote, including > scanning for licensing, staging code @release, and give us some guidance as > to where Apache might want us to put sensitive items like our NPM keys for > UserALE.js (if you have a preference). > > I am going to go ahead and begin some source code analysis tasks as well as walk m way through the Incubator release checklist which is a pretty solid resource for release candidate preparation and review. I'll begin opening Jira issues if and when I encounter issues sp keep your eyes peeled. I'll post back here once I'm done with the first pass. Thanks
