Re: [RESULT] [VOTE] Retire AriaTosca Podling

al Liron wrote: > >> On Thu, Jun 28, 2018 at 8:09 AM Thomas Nadeau >> wrote: >> >>> I fully intend to take the ASF Committer role seriously and help out/ >>> contribute to other projects as time permits going forward and look >>> forward to working >>&g

Re: [RESULT] [VOTE] Retire AriaTosca Podling

>> Binding +1 : 5 (Jakob Homan, Tal Liron, Thomas Nadeau, John Ament, Suneel >> Marthi) >> >> The Vote to retire this podling has passed and will move forward with next >> steps to retire this podling. >> >> Thanks for all the votes. >> >> Suneel >>

Re: [VOTE] Retire AriaTosca Podling

Precisely. The project, even after its pushed into the attic (assuming the votes stay as they are now) so you can fork from there if you would like. The existing Committers can help you with finding/forking if you need it. —Tom > On Jun 28, 2018, at 2:58 AM, Tal Liron wrote: > > Hi

Re: [VOTE] Retire AriaTosca Podling

+1 > On Jun 25, 2018, at 10:40 AM, Suneel Marthi wrote: > > In light of the discussion on > https://lists.apache.org/thread.html/ccad17927b23573e0bef3062c98e7a72455415be959b2f5859ed6898@%3Cdev.ariatosca.apache.org%3E > > and given that the project has not seen any activity over the past 5

Re: Updated: Discuss The Future Of AriaTosca - Meeting Minutes

t into Cloudify Community Edition, which is a serious orchestrator. >> The Cloudify folk might be interested in assisting on that, since they do >> want TOSCA support in their product. >> >> I am planning on a public release on Monday, assuming I don't have to much >>

Re: Updated: Discuss The Future Of AriaTosca - Meeting Minutes

> Hi Tom, > > There are some internal delays anyway. But I thought we will be having for > some info from Tal's work and assess the same, before we can make a final > decision. > > Thanks, > /Shen > > -----Original Message- > From: Thomas Nadeau [mailto:tnadeaua...@gmail.

Re: Updated: Discuss The Future Of AriaTosca - Meeting Minutes

stamp PRs. But we can accept them and then we can >>> vote to accept DJ etc... as a new committers. That is the nuclear option. >>> >>> Suneel: The question is: is this really worth it for a single vendor >>> to run this project? >>> >>> Ido: If you w

Re: Podling Report Reminder - June 2018

I read over the doc and I think it sums things up correctly. —Tom > On Jun 2, 2018, at 1:12 PM, Suneel Marthi wrote: > > I put together a doc - > https://docs.google.com/document/d/1UZndvPXs9j4ydjje_uZLIU3NNEsqmDsogd4dDnJCPsM/edit?usp=sharing > > Please feel free to edit. > > On Sat, Jun 2,

Re: Updated: Discuss The Future Of AriaTosca - Meeting Minutes

o do. Suneel: would you also like to look at what Tal is looking at? DJ: yes. > On May 18, 2018, at 2:39 PM, Thomas Nadeau <tnad...@lucidvision.com> wrote: > > > Sorry for the fits and starts with the last invite. That was the first > meeting invite

Reminder about call today

Just a reminder that I have scheduled a call to discuss the future of the Aria project today at 10AM EST. Call details were in my previous email, but ping me if you need them. —Tom

Fwd: Updated: Discuss The Future Of AriaTosca

Sorry for the fits and starts with the last invite.  That was the first meeting invite I’d created with the BJeans system.   This one should be correctly scheduled for Monday, May 21 at 10AM EST and have a more appealing headline/title. —TomBegin forwarded message:From: Thomas Nadeau via

Conference Info for Monday, June 21, 10AM EST Session

Hi, Below is the conference info for our call on Monday regarding the discussion around closing down AriaTosca. Anyone in the community is invited to participate and can use this conference info to connect. The invite supports as many people as I expect to show

Re: [Discuss] Future of AriaTosca

eel Marthi <suneel.mar...@gmail.com> wrote: > > On Wed, May 16, 2018 at 4:17 PM, Thomas Nadeau <tnad...@lucidvision.com> > wrote: > >> >>I meant that he was 2 ahead of Israel. *) >> > > Neh... its 3.5 hrs ahead of Israel. > >>

Re: [Discuss] Future of AriaTosca

> On Wed, May 16, 2018 at 10:40 AM, Thomas Nadeau <tnad...@lucidvision.com> > wrote: > >> >>Sorry to not respond to this thread; been very busy with my new >> gig. >> >>I am happy to setup a Zoom for this Thursday or Friday and

Re: [Discuss] Future of AriaTosca

Sorry to not respond to this thread; been very busy with my new gig. I am happy to setup a Zoom for this Thursday or Friday and take meeting minutes which will be published to this list/Slack. The challenge has always been the spanning timezones. Tal is in Central, I am EST

Re: [Discuss] Future of AriaTosca

> On May 16, 2018, at 7:38 AM, John D. Ament wrote: > > While it may help to have meetings ultimately its a sign of the problems > here. All discussion, including PR questions, should be on list. All > github commentary is sent to a list as well. > > I personally had

Re: Aria slack channel

I just sent you an invite. Don’t forget to join the Aria channel, as I think it only adds you to general by default. —Tom > On Apr 1, 2018, at 10:39 AM, Mor Dabastany wrote: > > Hi, > > I would like to get invitation for the slack channel since I have a

Re: [aria] TOSCA YAML Profile version and Support for Topology Substitution

The current version of Aria supports Yaml profile 1.0 only. We recently started fleshing out what it would take to support 1.1. You can see our confluence entry for this here: https://cwiki.apache.org/confluence/display/ARIATOSCA/TOSCA+1.1+Simple+YAML+Profile The answers to your questions of

Re: moving grooming up 1 hour today?

ing (ECS), Room 412 > Victoria, BC > V8W 3p6 Canada > > On Mon, Mar 19, 2018 at 3:30 AM, Thomas Nadeau <tnadeaua...@gmail.com> > wrote: > >> Miguel (and and anyone else wishing to attend the second grooming): >> >> Can we move the meeting 30 minutes earlier o

moving grooming up 1 hour today?

Miguel (and and anyone else wishing to attend the second grooming): Can we move the meeting 30 minutes earlier or an hour later than normally booked? Specifically, moving to 10:30AM EST or 12 PM EST? I have a conflict at that time today. --Tom

meeting minutes Grooming #1

Attendees: Tom, Sudhakar Sprint 7 closed. Opened Sprint 8. Discussed release/agile/sprint process Reviewed ARIA-423 and ARIA-439. Details of Tosca 1.1 profile enhancements are detailed here: and https://cwiki.apache.org/confluence/display/ARIATOSCA/ TOSCA+1.1+Simple+YAML+Profile Sudhakar

Re: www.ariatosca.org

joint the one at 11AM EST at the zoom above. --Tom On Mon, Mar 19, 2018 at 9:31 AM, Sudhakar Reddy <sudhakar.re...@amdocs.com> wrote: > What is the time of the meeting? > > Thanks & Regards > Sudhakar Reddy > > -Original Message- > From: Thomas Nadea

www.ariatosca.org

Is anyone else experiencing issues getting to the website? --Tom

today's grooming reminder

See you all at the grooming today. Those planning to attend, these are the coordinates: https://cloudify.zoom.us/j/5055197842 < https://www.google.com/url?q=https%3A%2F%2Fcloudify.zoom.us%2Fj%2F5055197842 > I was hoping to discuss the Tosca 1.1 enhancements today that have been discussed on the

Re: Aria support for TOSCA-simple-1.1

r id: Sudhakar53 > Email: sudhakarreddy...@gmail.com > > Note: I'm using my personal email address for contribution purpose. > > Thanks & Regards > Sudhakar Reddy > Contact No:8758383421 > > -Original Message- > From: Thomas Nadeau [mailto:tnadeaua...@g

Grooming Meeting Monday, March 12, 2018

Grooming Meeting Monday, March 12, 2018 Attendees: Tom, DJ Podling report: completed, accepted and approved. Need to add Sudhakar Reddy sudhakar.re...@amdocs.com to users for Confluence. Tom will code review https://github.com/apache/incubator-ariatosca/pull/228 and merge if appropriate.

Today's Grooming Meeting Reminder

See you all at the grooming in an hour. A reminder, these are the coordinates: https://cloudify.zoom.us/j/5055197842 I was hoping to discuss the Tosca 1.1 enhancements today that have been discussed on the mailer.

Re: Aria support for TOSCA-simple-1.1

.com > > Let me know once u add me. I'll update the findings in Confluence. > > Thanks & Regards > Sudhakar Reddy > Contact No:8758383421 > > > -Original Message- > From: Thomas Nadeau [mailto:tnad...@lucidvision.com] > Sent: Wednesday, March 07, 2018

Re: Aria support for TOSCA-simple-1.1

> Probably I'll share the document after initial investigation. > > > Thanks & Regards > Sudhakar Reddy > Contact No:8758383421 > > > -----Original Message- > From: Thomas Nadeau [mailto:tnadeaua...@gmail.com] > Sent: Wednesday, March 07, 2018 5:55 PM > To:

Re: Aria support for TOSCA-simple-1.1

page in Confluence. > > Probably I'll share the document after initial investigation. > > > Thanks & Regards > Sudhakar Reddy > Contact No:8758383421 > > > -Original Message- > From: Thomas Nadeau [mailto:tnadeaua...@gmail.com] > Sent: Wednesday, March

Re: Aria support for TOSCA-simple-1.1

I agree. This is specifically why I created the area on the wiki yesterday. Sudhakar, there is no need to start with python code changes. If you can start by documenting what you think are the diffs in the specs and any other requirements for changes, that is a great place to start. Tal, welcome

Re: ASF Podling Report for AriaTosca

I forgot to include the URL for quick access to the report: https://wiki.apache.org/incubator/March2018#preview <https://wiki.apache.org/incubator/March2018#preview> —Tom > On Mar 6, 2018, at 10:59 AM, Thomas Nadeau <tnadeaua...@gmail.com> wrote: > > Ju

Re: ASF Podling Report for AriaTosca

wrote: > Added to the contributors group. > > On Mon, Mar 5, 2018 at 9:55 AM Thomas Nadeau <tnadeaua...@gmail.com> > wrote: > > > tnadeau > > > > On Mon, Mar 5, 2018 at 9:53 AM, John D. Ament <johndam...@apache.org> > > wrote: > > > > >

Re: Aria support for TOSCA-simple-1.1

This has been discussed and "loosely" on the agenda here since I started working on this project, but was put on the back burner so we could complete a few other things. Given that there seems to be good interest in moving this functionality into the project I have start a dedicated area on

Grooming Meeting Minutes March 5, 2018

Monday, March 5, 2018 Grooming #1 No attendees Grooming #2 Attendees: Tom, Miguel sends regrets and will attend next week. Groomed backlog. Still no indication of status on Aria-437 from DJ. Starting work on Aria-75 (tom) Podling report initial draft (tom)

Grooming #2 reminder

11AM EST today. https://cloudify.zoom.us/j/5055197842

Re: ASF Podling Report for AriaTosca

tnadeau On Mon, Mar 5, 2018 at 9:53 AM, John D. Ament <johndam...@apache.org> wrote: > What is your username? > > On Mon, Mar 5, 2018 at 9:52 AM Thomas Nadeau <tnadeaua...@gmail.com> > wrote: > > > Ok. I was able to create an account, but I still do not have

Re: ASF Podling Report for AriaTosca

rant u write access to wiki > > > > On Mon, Mar 5, 2018 at 9:20 AM, Thomas Nadeau <tnadeaua...@gmail.com> > > wrote: > > > > > I just tried logging in here but my apache.org credentials do not seem > > to > > > work. Does someone

Re: ASF Podling Report for AriaTosca

Please go ahead and post it to incubator wiki if u have access - else i can > do it later today and sign-off. > > On Mon, Mar 5, 2018 at 9:14 AM, Thomas Nadeau <tnad...@apache.org> wrote: > > > Community: > > > > It looks like we are on the next cycle for podl

ASF Podling Report for AriaTosca

Community: It looks like we are on the next cycle for podling reports, and we need to have one finished for John et al by March 7. Since not much has changed since I wrote one up in February, I simply renamed that one and it can be found here:

Re: Issue in the execution context when using Openstack plugin

It looks like you answered your own question. When you require SSH by calling "execute_with_ssh" but do not have it configured, its not going to work right? *) In any event, can you provide more diagnostic info so that we can see better where things are failing. I am actually starting to work on

Grooming Meeting Minutes Monday, February 26, 2018

Monday, February 26, 2018 Attendees: Tom Groomed backlog and closed one outstanding issue. Reached out to DJ about status of ARIA-437 Tom will begin work on ARIA-75 after talkign with Vish and Miguel about their status.

Re: Implementation for get_operation_output

After reviewing the thread/code, the proposal seems reasonable. I guess the devil is in the details of the implementation, but the general approach here seems ok. Can I suggest that you please write up a 'design spec' on the wiki as we've done for other bigger pieces of functionality. That will

grooming reminder

Just a reminder that we're having grooming at 9AM EST and 11AM EST today. The Zoom coordinates were published a few times, but let me know if you need them. --Tom

Grooming #2: February 19, 2018

Grooming #2: Attendees: Tom. I spoke with Miguel on Slack. He is returning from a trip and will groom his stories out of band. I need to catch-up with Vish and get an update on any stories he plans to continue working. I am going to start updating ARIA-423 in readiness of doing another

Re: Confluence access

Thanks much! --Tom On Mon, Feb 19, 2018 at 11:03 AM, Suneel Marthi <smar...@apache.org> wrote: > Added 'tnad...@apache.org' to Administrator and Committer roles. > > On Mon, Feb 19, 2018 at 2:32 PM, Thomas Nadeau <tnadeaua...@gmail.com> > wrote: > > > Yes I un

Grooming #2 Reminder/Zoom Info

The second grooming meeting is starting in a few minutes. This is the Zoom conferencing info: https://cloudify.zoom.us/j/5055197842 --Tom

Grooming #1 Meeting Minutes: Monday, February 19, 2018

Monday, February 19, 2018 Grooming #1: Attendees: Tom, DJ Repaired confluence permissions. Discussed Aria-438 and code review of ARIA-437 tentatively set for tomorrow. DJ is going to break down 438 into constituate sub-tasks for commits of smaller chunks, i ncluding updating the CI for any

Re: Confluence access

sions are not tied > together. > > John > > On Mon, Feb 19, 2018 at 9:17 AM Thomas Nadeau <tnadeaua...@gmail.com> > wrote: > > > John/Suneel, > > > > I conflated Confluence and Jira in my last note. I was able to fix DJ's > > permissions on Confluenc

Confluence access

John/Suneel, I conflated Confluence and Jira in my last note. I was able to fix DJ's permissions on Confluence. The key here is to modify permissions using the "Space Tools" (bottom left on the project main page). However, on Jira I am listed as a contributor still, and that should be fixed.

Confluence Permissions/Role changes

John/Suneel, Can you please update my role to "committer" on the Confluence administration area? Right now I am listed as a Contributor. This may be why I cannot alter DJ's access permissions (which are still incorrect and do not allow him to edit).

thoughts on ARIA-423: Release 0.3.0

Hi, I wanted to ask that folks take a look at Aria-423 which is our bucket of main features we want to target for the next release. If you have thoughts/ideas/specific items, please add them to 423 so we can discuss at grooming/etc... Please include a Jira reference link (and create one if it

Grooming Meeting Minutes: Feb 12, 2018

Feb 12, 2018 Grooming Meeting 1: Attendees: Tom, DJ Discussed DJ's patch, attempted to correct his access permissions, Aria-118 is broken out into 3 issues that DJ will work the second two now in this sprint. Closed current sprint, started Sprint 7. Theme is Plugins and website improvements.

Re: ARIA-118 plugin.yaml importing

his from our side as we have a strong use case > for it. > > Regards, > DJ > -Original Message- > From: Tal Liron [mailto:t...@cloudify.co] > Sent: Monday, December 04, 2017 7:22 PM > To: dev@ariatosca.incubator.apache.org > Subject: Re: ARIA-118 plugin.yaml importing

Confluence Permissions

Mentors: I was just trying to debug why DJ doesn't have write/create access to confluence (not Jira), and realized that I am not in the jira-administrators or committers. Can one of you guys please take a look and correct this? This is the URL for quick reference.

Grooming Reminder

Team: Just a reminder that we are now having not one but TWO grooming meetings on Mondays: 9AM EST and 11AM EST. The Zoom meeting info is the same for both: https://cloudify.zoom.us/j/5055197842 See you online.

Re: Confluence wiki page write access

> website? > http://ariatosca.incubator.apache.org/community/ > > Miguel > > -- > Miguel Jimenez, PhD student > Department of Computer Science > University of Victoria > Engineering/Computer Science Building (ECS), Room 412 > Victoria, BC > V8W 3p6 Canada > > On Fri, Feb 9,

Re: Confluence wiki page write access

Can you check now. I added you to the list of people with write access. —Tom > On Feb 5, 2018, at 9:58 AM, D Jayachandran > wrote: > > Hi All, > > I would like to write up in the wiki for all the major PR's which am > contributing. > Could

Podling Report: February 2018

Community: I've posted the latest podling report here for your review: https://cwiki.apache.org/confluence/pages/editpage.action?pageId=75966486 Please take a look at this as soon as possible and either edit or comment on my proposal. We need to get this to our mentors today. Apologies for the

pairwise code reviews

Community: I've started to do pairwise code reviews with the authors of pull requests with significant amounts of changes. I think this is a good idea IMHO for us all as it not only lets the author explain to someone else what they *think* they have coded, but also lets the reviewer better

code review for ARIA-118

DJ and I sat down this morning and did a pairwise code review of his patch set. The functionally things look cool. My requests for changes have to do with adding more comments and transforming literal strings/integers into constants which have been discussed in detail during our code review. So

Re: Confluence wiki page write access

Adding General. --Tom On Mon, Feb 5, 2018 at 9:58 AM, D Jayachandran wrote: > Hi All, > > I would like to write up in the wiki for all the major PR's which am > contributing. > Could you please provide me with the write access for it. > > > Regards, > DJ >

Grooming Meeting Minutes: Monday, Feb 5, 2017

Feb 5, 2017 Grooming Meeting 1: Attendees: Tom, DJ Discuss status of project. DJ discussing Ericsson's requirements and which contributions he would like to push into Aria. There are challenges with E's pushing code pertaining to internal requirements on how code is pushed upstream (in

Re: Grooming Meeting Minutes: January 22, 2018

gt; > -Original Message- > From: Thomas Nadeau [mailto:tnad...@apache.org] > Sent: Wednesday, January 31, 2018 7:23 PM > To: dev@ariatosca.incubator.apache.org > Subject: Re: Grooming Meeting Minutes: January 22, 2018 > > I can make it at 9AM EST on Monday. If that works for y

Re: Grooming Meeting Minutes: January 22, 2018

Jayachandran <d.jayachand...@ericsson.com > wrote: > Hi Tom, > > Can we have the meeting scheduled by 9AM on Monday ? > > Regards, > DJ > > -Original Message- > From: Thomas Nadeau [mailto:tnadeaua...@gmail.com] > Sent: Tuesday

Re: Grooming Meeting Minutes: January 22, 2018

day, January 29, 2018 9:30 PM > To: dev@ariatosca.incubator.apache.org > Subject: Re: Grooming Meeting Minutes: January 22, 2018 > > Hi everyone, > I'm fine with having two grooming meetings. I'd continue joining at > 11:00AM EST though. > Cheers, > Miguel > > On Thu, J

grooming meeting minutes January 29, 2018

Attendees: Tom, Miguel Topics discussed: reviewed current backlog. Miguel is going to look at assigning himself a few items to tackle this week. We will discuss details on the mailing list as well as perhaps get together Wednesday for further pair-wise coding. Also discussed having a second

Today's grooming

I am doing my planning for grooming in about 30 minutes. Any topics to discuss? Miguel and I were planning on going over the documentation-related Jira items and formulating a plan for resolving all of these. Also, I started an email thread on the date/time of the grooming meeting but haven't

Re: Grooming Meeting Minutes: January 22, 2018

.com> wrote: > >> Hi Tom, >> >> I would like to attend the grooming meeting in future. My timezone is GST >> + 5:30 . >> What can be the best possible time which you can have the meeting >> scheduled ? >> Also where can I find the grooming meeting

Grooming Meeting Minutes: January 22, 2018

Attendees: Tom Reviewed Jira backlog Ended early to update release KEYS file and MIT Key server entries. --Tom

Today's grooming

Good morning all: Ill be finishing the key stuff mentioned on slack last week this morning and preparing for grooming later. If there are any issues you guys want discussed let me know. Miguel also asked for a tutorial on how the web site/docs worked, so Ill be sitting down with him at some

Re: ARIA-400

Fantastic! We will need to sit down and go over a bit of a tutorial on how the site is generated/etc... Lets figure out a time/date offline. --Tom On Tue, Jan 16, 2018 at 2:37 PM, Miguel Angel Jimenez Achinte < mig...@rigiresearch.com> wrote: > Hi, > > I'd like to help with the developer

Aria Tosca 0.2.0 Released!

As I noted yesterday, I have successfully pushed the approved candidate artifacts for AriaTosca 0.2.0 just now. I verified that the PIP install worked and is present on pypi, that the github tags are there and the released artifacts have been copied to

AriaTosca Release 0.2.0

I have confirmed that we received 3 +1 binding votes on the IPMC for candidate release 0.2.0, and so am announcing that here. I will be invoking the release process shortly that will push the artifacts out to the official repositories. Thank you all for your patience and help through this

today's grooming

We'll have grooming this morning as usual. I understand that its a holiday in the US, but lets go ahead. If people want to meet up later this week or groom their own stories, go for it too. --Tom

Naming release artifacts question for our Mentors

Mentors: Justin just posted some comments on the following thread over on general complaining that some of the release artifacts do not have -incubating in the name. https://lists.apache.org/thread.html/dbba91d463fe16329e0138fddf5aabdd91e0dda515f84d669dc9409a@%3Cgeneral.incubator.apache.org%3E

Re: Apache and committer account

AM, D Jayachandran < > d.jayachand...@ericsson.com> > wrote: > > > It was communicated by Ran Ziv, to submit the ICLA, so I thought I was > > necessary even to contribute. > > Now it's clear to me. > > > > -Original Message- > > From: Thomas Nade

Re: merging paused until release is completed

is finalized and have been rebased > off of the latest master. > > Ofcourse you could always have development continue on a different branch > if you are comfortable with merging and rebasing the branches to master. > > On Tue, Jan 9, 2018 at 7:52 AM, Thomas Nadeau <tnadeaua...@

Re: merging paused until release is completed

d > merge that in when done? I'd hate to see development slow down due to the > release window in flight. Most other projects don't stop committing while > this is happening. > > On Tue, Jan 9, 2018 at 7:41 AM Thomas Nadeau <tnadeaua...@gmail.com> > wrote: > > > I

merging paused until release is completed

I just saw a PR pushed Vaish and realized we probably had not communicated that we're holding off on merging PRs until the release is finished. The reasoning is to leave master in its current state in case anything odd happens and we need to redo the release (which has happened). Note that PRs

Re: Apache and committer account

Why are you submitting the ICLA? You only need to do that after you have been voted as a committer by the existing Committers. --Tom On Tue, Jan 9, 2018 at 2:00 AM, D Jayachandran wrote: > Hi All, > > I have already submitted the Apache ICLA and got the below

Re: Status of ARIA-19 JIRA issue

Are you closing the issue or would you like me to? Are you going to move onto ARIA-423? https://issues.apache.org/jira/browse/ARIA-423 --Tom On Sun, Jan 7, 2018 at 3:45 PM, Vishwanath Jayaraman < vishwana...@hotmail.com> wrote: > Thanks. > > I checked and found that it is linked to ARIA-1 >

Grooming Meeting: Monday, January 8, 2017

Attendees: Tom We ended the meeting early as no one joined. I started grooming the existing backlog, completed Sprint 4 and started Sprint 5. Update for the release is as you have seen, the AriaTosca Committers voted positively to release 0.2.0, and I've pushed this to a vote at Apache. --Tom

Today's Grooming meeting Info

A few folks asked me directly for the Zoom conf information for the weekly grooming meeting, so I am posting it here. https://cloudify.zoom.us/j/5055197842 See you all in an hour. --Tom

Re: [VOTE] publish ariatosca 0.2.0

The vote status on the 0.2.0 release candidate is: There were 4 positive binding votes from Tom, Tal, Suneel, Maxim There were no negative votes, so the release vote now will be pushed to the Apache PMC. Thank you, --Tom On Thu, Jan 4, 2018 at 11:54 AM, Thomas Nadeau <tnad...@apache.

Re: [VOTE] publish ariatosca 0.2.0

> On Jan 5, 2018, at 12:04 PM, John D. Ament <john.d.am...@gmail.com> wrote: > > On Thu, Jan 4, 2018 at 11:54 AM Thomas Nadeau <tnad...@apache.org> wrote: > >> I updated the script and pushed the artifacts again. The issue is that >> test.pypi.org do

Re: [VOTE] publish ariatosca 0.2.0

sing "pip install ." >5. Ran tests using "make test" > > +1 > > On Thu, Jan 4, 2018 at 5:59 PM Thomas Nadeau <tnad...@apache.org> wrote: > > > Aria Community: > > > > This is a vote to release Apache AriaTosca (Incubating) 0.2.0. If t

Re: [VOTE] publish ariatosca 0.2.0

cleared with this release. --Tom On Thu, Jan 4, 2018 at 11:38 AM, John D. Ament <johndam...@apache.org> wrote: > Can you use the one that is checked in ? > https://github.com/apache/incubator-ariatosca/blob/ > master/release/asf-release.sh#L138 > > > On Thu, Jan 4, 2018 a

Re: [VOTE] publish ariatosca 0.2.0

"sha512" > > John > > On Thu, Jan 4, 2018 at 10:59 AM Thomas Nadeau <tnad...@apache.org> wrote: > > > Aria Community: > > > > This is a vote to release Apache AriaTosca (Incubating) 0.2.0. If the > vote > > passes, another vote for approvi

[VOTE] publish ariatosca 0.2.0

Aria Community: This is a vote to release Apache AriaTosca (Incubating) 0.2.0. If the vote passes, another vote for approving the release will take place on the Apache Incubator's PMC. Please verify the various release artifacts and respond to the list with your results. Instructions for

AriaTosca 0.2.0 Release Candidate Process Sorted

I just wanted to let everyone know that I've now figured out the process, and gotten a bunch of related stuff sorted (i.e.: pypi access), and so we are now ready to re-start the review candidate voting process. Artifacts are signed, and in place at Apache's dist area as well as at pypi tests

Re: [VOTE] publish ariatosca 0.2.0

uded libraries that would require inclusion in > LICENSE > > > > Also, just to clarify on the voting procedure. The entire community > > is encouraged to vote on releases, although on the Podling Project > > Management Committee (PPMC) has binding votes. Testing and voting o

first grooming of the year

Happy New Year! I propose we either postpone grooming this week to a later time/date or skip it until next week. There are some folks not in today, and I am still fighting with the release script to push the updated release artifacts, so I'd like to focus on that until I finish. If you wish to

Re: [VOTE] publish ariatosca 0.2.0

ged to vote on releases, although on the Podling Project > Management Committee (PPMC) has binding votes. Testing and voting on > releases is an excellent way to contribute to project. > > -Jakob > > On 28 December 2017 at 07:15, Thomas Nadeau <tnadeaua...@gmail.com> wr

Re: [VOTE] publish ariatosca 0.2.0

layed around with Clearwater example. > > > On Tue, Dec 26, 2017 at 10:11 AM, Thomas Nadeau <tnadeaua...@gmail.com> > wrote: > > > Aria Community: > > > > This is a vote to release Apache AriaTosca (Incubating) 0.2.0. If the > vote > > passes,

[VOTE] publish ariatosca 0.2.0

Aria Community: This is a vote to release Apache AriaTosca (Incubating) 0.2.0. If the vote passes, another vote for approving the release will take place on the Apache Incubator's PMC. I created a tarball candidate for the 0.2.0 release and placed it in ARIA's /dist/dev folder:

Latest Aria Podcast Posted

AriaTosca-ers: Tal, Arthur and I recorded a podcast (video and audio) a few weeks back on the topic of the origins of the AriaTosca project. Check it out here: Audio+Video: https://youtu.be/Is6oZUr2Ccs Audio-only: https://soundcloud.com/theopensourcepodcast/the-aria-tosca-podcast-episode-2

Grooming on Dec 25/Jan 1 Canceled

Enough people expressed an interest in punting on next week's grooming or the one after that I wanted to send out a note to cancel them. Please continue discussing on the list and/or grooming any stories you might be working on w Jira. --Tom

Re: meeting minutes Monday, December 18, 2017

:30 timezone > > Regards, > DJ > -Original Message- > From: Thomas Nadeau [mailto:tnadeaua...@gmail.com] > Sent: Monday, December 18, 2017 9:42 PM > To: dev@ariatosca.incubator.apache.org > Subject: meeting minutes Monday, December 18, 2017 > > Attendees: Tom &

meeting minutes Monday, December 18, 2017

Attendees: Tom No one else showed up today, so I ended the meeting at 10 after. If anyone would like to discuss the backlog this week, send a note here to the list to discuss. Cheers, --Tom

  1   2   3   >