Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Set FINOS badge to “Released” ahead of 1.0 release #68

Merged
merged 1 commit into from
Mar 25, 2019

Conversation

rikoe
Copy link
Contributor

@rikoe rikoe commented Mar 24, 2019

Relating to #32 release checklist for 1.0 release.

Also fix StackOverflow tag in badge

Also fix StackOverflow tag in badge
@rikoe rikoe added the repo label Mar 24, 2019
@rikoe rikoe requested a review from nkolba March 24, 2019 23:26
@rikoe rikoe added this to the 1.0 milestone Mar 25, 2019
@nkolba nkolba merged commit 540b50a into finos:master Mar 25, 2019
@rikoe rikoe deleted the finos-badge branch March 26, 2019 16:29
@mindthegab
Copy link
Member

mindthegab commented Mar 27, 2019

Folks (@nkolba @rikoe)

I believe there is some confusion here and understandably so.

Let me try to elaborate:

So FDC3, until the PMC takes a vote to "activate" (because all the boxes in https://finosfoundation.atlassian.net/wiki/spaces/FINOS/pages/75530376/Activation are checked), is in state "Incubating".

I am very supportive of this vote happening ASAP (seems FDC3 would check all the boxes) but until then, can you please re-open this issue and re-instate the "incubating" badge?

@mindthegab
Copy link
Member

As per our convo on email today, @nkolba and @rikoe don't consider this a blocker for 1.0.0.

I or @brooklynrob will make sure to attend the next PMC meeting and explain the havoc.

I apologize for the confusion created by the state called "Released" (note the upper case) which clearly makes you think that once that you have "released" (note the lower case) the software then you qualify. Definitely not your fault and something we need to review.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants