RE: Creating Release Candidate for UserALE.js

[Poore, Joshua C.]

We have a bi-monthly webEx for the committers, and would like to start opening 
this up to the public. I'd love it if you could join. Would you be able to join 
@lewis if we made this Friday's @ 1600 EST (1300 PST). Twice a month. Might be 
good for getting guidance from you about and pacing the flurry of release 
candidates that are on the horizon.

@lewis if you can make this time. I will post details of this meeting to @dev 
as well as on Confluence.

-Original Message-
From: lewis john mcgibbney [mailto:lewi...@apache.org]
Sent: Thursday, January 11, 2018 9:50 AM
To: dev@senssoft.incubator.apache.org
Subject: Re: Creating Release Candidate for UserALE.js

Hi Josh,
Replies inline

On Thu, Jan 11, 2018 at 8:31 AM, <
dev-digest-h...@senssoft.incubator.apache.org> wrote:

>
> From: Joshua Poore <poor...@me.com>
> To: dev@senssoft.incubator.apache.org
> Cc:
> Bcc:
> Date: Tue, 09 Jan 2018 20:57:47 -0500
> Subject: Re: Creating Release Candidate for UserALE.js None.
> UserAle.js 0.1.0 is ready. It’s a solid product. Distill 0.1.0 is also
> ready. It’s very simple and primarily works with Tap, but we are
> building 0.2.0 now.
>

OK doke. Moving forward, I would encourage anyone from the existing SensSoft 
community to come forward and act as release manager.
We have the following documentation to guide existing and new release managers, 
so I encourage anyone to come forward so we can start spinning up new releases. 
This is a major part of moving towards graduation and growing awareness of 
SensSoft.

https://cwiki.apache.org/confluence/display/SENSSOFT/UserALE.js+Release+Management+Procedure

I'll personally go ahead and make a release for UserAle.js 0.1.0 and Distill 
0.1.0 and also augment the release documentation with whatever issues I 
encounter.

>
> I’ll admit we still remain confused about the lingering issue the
> Apache bot found with UserAle.js commits.
>

I am not aware of this, can you point me to the issue please?
Thanks

 Notice: This email and any attachments may contain proprietary (Draper 
non-public) and/or export-controlled information of Draper. If you are not the 
intended recipient of this email, please immediately notify the sender by 
replying to this email and immediately destroy all copies of this email.

RE: Creating Release Candidate for UserALE.js

[Poore, Joshua C.]

Hi Lewis,

I've gone through and made sure our tickets in each release are accurate.

UserALE.js 0.1.0 is good to go. The blocker is SENSSOFT-250. I'm not sure we 
understand what needs to happen. Can you comment and give a bit more clarity?

We're also confirming whether some of the remaining tickets under UserALE.js 
0.2.0 are still lingering. That could be a candidate for release VERY soon 
after 0.1.0.

Distill 0.1.0 and TAP 0.1.0 are very much tethered. We are rebuilding Distill 
now (0.2.0; see requirements and discussion here: 
https://cwiki.apache.org/confluence/display/SENSSOFT/Distill+0.2.0

We could either released Distill 0.1.0 and TAP 0.1.0 together. Or we could wait 
and make Distill 0.2.0 the first release. Major overhaul on TAP on the horizon.

Thoughts??

Noted about release managers. The Draper contingent of the community has some 
interesting operating assumptions as you know--we service some very odd 
contracts, which don't necessarily align 100% with the products here. We commit 
back sometimes at deluges and sometimes at a trickle. That is changing and soon 
we'll have 3 release managers--Alex Ford, Michelle Beard, and Laura Mariano 
with projects that should produce more regular releases.

-Original Message-
From: lewis john mcgibbney [mailto:lewi...@apache.org]
Sent: Thursday, January 11, 2018 9:50 AM
To: dev@senssoft.incubator.apache.org
Subject: Re: Creating Release Candidate for UserALE.js

Hi Josh,
Replies inline

On Thu, Jan 11, 2018 at 8:31 AM, <
dev-digest-h...@senssoft.incubator.apache.org> wrote:

>
> From: Joshua Poore <poor...@me.com>
> To: dev@senssoft.incubator.apache.org
> Cc:
> Bcc:
> Date: Tue, 09 Jan 2018 20:57:47 -0500
> Subject: Re: Creating Release Candidate for UserALE.js None.
> UserAle.js 0.1.0 is ready. It’s a solid product. Distill 0.1.0 is also
> ready. It’s very simple and primarily works with Tap, but we are
> building 0.2.0 now.
>

OK doke. Moving forward, I would encourage anyone from the existing SensSoft 
community to come forward and act as release manager.
We have the following documentation to guide existing and new release managers, 
so I encourage anyone to come forward so we can start spinning up new releases. 
This is a major part of moving towards graduation and growing awareness of 
SensSoft.

https://cwiki.apache.org/confluence/display/SENSSOFT/UserALE.js+Release+Management+Procedure

I'll personally go ahead and make a release for UserAle.js 0.1.0 and Distill 
0.1.0 and also augment the release documentation with whatever issues I 
encounter.

>
> I’ll admit we still remain confused about the lingering issue the
> Apache bot found with UserAle.js commits.
>

I am not aware of this, can you point me to the issue please?
Thanks

 Notice: This email and any attachments may contain proprietary (Draper 
non-public) and/or export-controlled information of Draper. If you are not the 
intended recipient of this email, please immediately notify the sender by 
replying to this email and immediately destroy all copies of this email.

Re: Creating Release Candidate for UserALE.js

[lewis john mcgibbney]

Hi Josh,
Replies inline

On Thu, Jan 11, 2018 at 8:31 AM, <
dev-digest-h...@senssoft.incubator.apache.org> wrote:

>
> From: Joshua Poore <poor...@me.com>
> To: dev@senssoft.incubator.apache.org
> Cc:
> Bcc:
> Date: Tue, 09 Jan 2018 20:57:47 -0500
> Subject: Re: Creating Release Candidate for UserALE.js
> None. UserAle.js 0.1.0 is ready. It’s a solid product. Distill 0.1.0 is
> also ready. It’s very simple and primarily works with Tap, but we are
> building 0.2.0 now.
>

OK doke. Moving forward, I would encourage anyone from the existing
SensSoft community to come forward and act as release manager.
We have the following documentation to guide existing and new release
managers, so I encourage anyone to come forward so we can start spinning up
new releases. This is a major part of moving towards graduation and growing
awareness of SensSoft.

https://cwiki.apache.org/confluence/display/SENSSOFT/UserALE.js+Release+Management+Procedure

I'll personally go ahead and make a release for UserAle.js 0.1.0 and
Distill 0.1.0 and also augment the release documentation with whatever
issues I encounter.

>
> I’ll admit we still remain confused about the lingering issue the Apache
> bot found with UserAle.js commits.
>

I am not aware of this, can you point me to the issue please?
Thanks

Re: Creating Release Candidate for UserALE.js

[Joshua Poore]

None. UserAle.js 0.1.0 is ready. It’s a solid product. Distill 0.1.0 is also 
ready. It’s very simple and primarily works with Tap, but we are building 0.2.0 
now.

I’ll admit we still remain confused about the lingering issue the Apache bot 
found with UserAle.js commits.

Joshua Poore


> On Jan 9, 2018, at 8:54 PM, lewis john mcgibbney  wrote:
> 
> Hi Folks,
> Does anyone have an objection against me generating a release for, at a
> minimum, UserALE.js?
> Is there any other part of the SensSoft stack which is suitable for release?
> Thanks
> lewis
> 
> 
> -- 
> http://home.apache.org/~lewismc/
> @hectorMcSpector
> http://www.linkedin.com/in/lmcgibbney