Error

tbenzies (Thu, 06 Apr 2017 00:17:38 GMT):
JonathanLevi

JonathanLevi (Thu, 06 Apr 2017 00:18:02 GMT):
User User_1 added by JonathanLevi.

JonathanLevi (Thu, 06 Apr 2017 00:18:28 GMT):
User User_2 added by JonathanLevi.

rjones (Thu, 06 Apr 2017 00:20:26 GMT):
Has joined the channel.

JonathanLevi (Thu, 06 Apr 2017 00:20:44 GMT):
User User_3 added by JonathanLevi.

rjones (Thu, 06 Apr 2017 00:20:50 GMT):
cbf

JonathanLevi (Thu, 06 Apr 2017 00:21:09 GMT):
User User_4 added by JonathanLevi.

greg.haskins (Thu, 06 Apr 2017 00:21:35 GMT):
lets do this

JonathanLevi (Thu, 06 Apr 2017 00:22:08 GMT):
Yup, adding all the maintainers... and shooting an email.

JonathanLevi (Thu, 06 Apr 2017 00:22:38 GMT):
User User_5 added by JonathanLevi.

JonathanLevi (Thu, 06 Apr 2017 00:23:12 GMT):
User User_6 added by JonathanLevi.

JonathanLevi (Thu, 06 Apr 2017 00:23:28 GMT):
User User_7 added by JonathanLevi.

JonathanLevi (Thu, 06 Apr 2017 00:24:09 GMT):
User User_8 added by JonathanLevi.

JonathanLevi (Thu, 06 Apr 2017 00:24:48 GMT):
User User_9 added by JonathanLevi.

JonathanLevi (Thu, 06 Apr 2017 00:26:21 GMT):
User User_10 added by JonathanLevi.

JonathanLevi (Thu, 06 Apr 2017 00:27:35 GMT):
User User_11 added by JonathanLevi.

JonathanLevi (Thu, 06 Apr 2017 00:27:55 GMT):
User User_12 added by JonathanLevi.

JonathanLevi (Thu, 06 Apr 2017 00:28:28 GMT):
User User_13 added by JonathanLevi.

JonathanLevi (Thu, 06 Apr 2017 00:31:57 GMT):
User User_14 added by JonathanLevi.

JonathanLevi (Thu, 06 Apr 2017 00:32:11 GMT):
User User_15 added by JonathanLevi.

JonathanLevi (Thu, 06 Apr 2017 00:32:39 GMT):
User User_16 added by JonathanLevi.

JonathanLevi (Thu, 06 Apr 2017 00:33:27 GMT):
User User_17 added by JonathanLevi.

JonathanLevi (Thu, 06 Apr 2017 00:33:48 GMT):
User User_18 added by JonathanLevi.

JonathanLevi (Thu, 06 Apr 2017 00:35:17 GMT):
User User_19 added by JonathanLevi.

JonathanLevi (Thu, 06 Apr 2017 00:35:37 GMT):
User User_20 added by JonathanLevi.

JonathanLevi (Thu, 06 Apr 2017 00:35:49 GMT):
User User_21 added by JonathanLevi.

JonathanLevi (Thu, 06 Apr 2017 00:36:16 GMT):
User User_22 added by JonathanLevi.

JonathanLevi (Thu, 06 Apr 2017 00:36:27 GMT):
User User_23 added by JonathanLevi.

JonathanLevi (Thu, 06 Apr 2017 00:36:48 GMT):
User User_24 added by JonathanLevi.

JonathanLevi (Thu, 06 Apr 2017 00:36:57 GMT):
User User_25 added by JonathanLevi.

JonathanLevi (Thu, 06 Apr 2017 00:39:30 GMT):
User User_26 added by JonathanLevi.

JonathanLevi (Thu, 06 Apr 2017 00:41:44 GMT):
User User_27 added by JonathanLevi.

JonathanLevi (Thu, 06 Apr 2017 00:42:25 GMT):
User User_28 added by JonathanLevi.

JonathanLevi (Thu, 06 Apr 2017 00:53:42 GMT):
User User_29 added by JonathanLevi.

JonathanLevi (Thu, 06 Apr 2017 01:00:16 GMT):
User User_30 added by JonathanLevi.

JonathanLevi (Thu, 06 Apr 2017 01:00:52 GMT):
User User_31 added by JonathanLevi.

JonathanLevi (Thu, 06 Apr 2017 01:36:20 GMT):
Release-related questions, surveys, feedback, enquiries, requests, along with discussions of all sorts around: priorities, planning, schedule, milestones, and, of course, announcements!

JonathanLevi (Thu, 06 Apr 2017 01:36:50 GMT):
OK, first things first:

JonathanLevi (Thu, 06 Apr 2017 01:37:36 GMT):
1. I have added (an initial list of) 35 members, and expect 100s to join.

JonathanLevi (Thu, 06 Apr 2017 01:37:54 GMT):
2. As required, I have updated the wiki with this channel information: https://wiki.hyperledger.org/community/slack_channels?&#hyperledger_fabric_channels

JonathanLevi (Thu, 06 Apr 2017 01:37:54 GMT):
2. As required, I have updated this wiki: https://wiki.hyperledger.org/community/slack_channels?&#hyperledger_fabric_channels

JonathanLevi (Thu, 06 Apr 2017 01:38:19 GMT):
3. We will make a few announcements, of course, and/but please feel free to invite others to this.

JonathanLevi (Thu, 06 Apr 2017 01:39:09 GMT):
3. We will make a few announcements, of course, and/but please feel free to invite others to this channel.

rjones (Thu, 06 Apr 2017 01:45:41 GMT):
greg.haskins

JonathanLevi (Thu, 06 Apr 2017 03:17:46 GMT):
User User_32 added by JonathanLevi.

JonathanLevi (Thu, 06 Apr 2017 03:18:38 GMT):
User User_33 added by JonathanLevi.

JonathanLevi (Thu, 06 Apr 2017 03:18:55 GMT):
User User_32 removed by JonathanLevi.

JonathanLevi (Thu, 06 Apr 2017 03:20:17 GMT):
(sorry Sean, have added you twice - kept the _Sovrin one)

JonathanLevi (Thu, 06 Apr 2017 03:20:17 GMT):
[sorry Sean, have added you twice initially, before I realized that we have two of you ;-) - kept the _Sovrin one, please amend if needed]

JonathanLevi (Thu, 06 Apr 2017 03:27:11 GMT):
User User_34 added by JonathanLevi.

gatakka (Thu, 06 Apr 2017 06:35:53 GMT):
Has joined the channel.

Jonas.Hedin (Thu, 06 Apr 2017 06:35:55 GMT):
Has joined the channel.

AbhilekhSingh (Thu, 06 Apr 2017 06:41:59 GMT):
Has joined the channel.

jerry10301 (Thu, 06 Apr 2017 06:49:10 GMT):
Has joined the channel.

jansony1 (Thu, 06 Apr 2017 06:55:31 GMT):
Has joined the channel.

Vadim (Thu, 06 Apr 2017 06:55:36 GMT):
Has joined the channel.

Vadim (Thu, 06 Apr 2017 06:58:40 GMT):
Hello @here, in the fabric roadmap slide (https://jira.hyperledger.org/secure/attachment/10627/Fabric%20Roadmap%20March2017-v6.pptx) I've seen a feature called "Side DB for private data" planned for the release V Next. Could anybody elaborate what is this? Is this for securely storing some encryption keys in the blockchain? Thanks.

Vadim (Thu, 06 Apr 2017 06:58:40 GMT):
Hello @here, in the fabric roadmap slide (https://jira.hyperledger.org/secure/attachment/10627/Fabric%20Roadmap%20March2017-v6.pptx) I've seen a feature called "Side DB for private data" planned for the release V Next. Could anybody elaborate what this is? Is this for securely storing some encryption keys in the blockchain? Thanks.

saism (Thu, 06 Apr 2017 07:44:18 GMT):
Has joined the channel.

HansDeLeenheer (Thu, 06 Apr 2017 07:52:50 GMT):
Has joined the channel.

Hangyu (Thu, 06 Apr 2017 08:20:35 GMT):
Has joined the channel.

liutc (Thu, 06 Apr 2017 08:24:15 GMT):
Has joined the channel.

raanaaray (Thu, 06 Apr 2017 08:37:13 GMT):
Has joined the channel.

smallant (Thu, 06 Apr 2017 08:55:04 GMT):
Has joined the channel.

vvnick (Thu, 06 Apr 2017 08:55:58 GMT):
Has joined the channel.

aguchi (Thu, 06 Apr 2017 08:59:55 GMT):
Has joined the channel.

nickmelis (Thu, 06 Apr 2017 09:15:13 GMT):
Has joined the channel.

harsha (Thu, 06 Apr 2017 09:46:46 GMT):
Has joined the channel.

Senthil1 (Thu, 06 Apr 2017 10:07:16 GMT):
Has joined the channel.

Senthil1 (Thu, 06 Apr 2017 10:18:35 GMT):
@Vadim please refer to the design doc -- https://docs.google.com/document/d/1OOoE062XMsZr-T5S-JvxG7ujkU10dipx9r1CCBqi8NE/edit

VictoriaH (Thu, 06 Apr 2017 11:27:33 GMT):
Has joined the channel.

scottz (Thu, 06 Apr 2017 13:48:16 GMT):
Has joined the channel.

mgk (Thu, 06 Apr 2017 13:50:14 GMT):
Has joined the channel.

nickgaski (Thu, 06 Apr 2017 13:50:38 GMT):
Has joined the channel.

ssaddem (Thu, 06 Apr 2017 13:57:17 GMT):
Has joined the channel.

albrandt (Thu, 06 Apr 2017 14:05:33 GMT):
Has joined the channel.

mbaizan (Thu, 06 Apr 2017 14:08:51 GMT):
Has joined the channel.

hmchen (Thu, 06 Apr 2017 14:14:37 GMT):
Has joined the channel.

mihaig (Thu, 06 Apr 2017 14:26:58 GMT):
Has joined the channel.

mohamoud.egal (Thu, 06 Apr 2017 15:00:15 GMT):
Has joined the channel.

ryokawajp (Thu, 06 Apr 2017 15:55:12 GMT):
Has joined the channel.

yuki-kon (Thu, 06 Apr 2017 16:34:16 GMT):
Has joined the channel.

JonathanLevi (Thu, 06 Apr 2017 16:40:47 GMT):
Yes, maybe it will be easier to remember/associate it with the *Side DB* JIRA ticket https://jira.hyperledger.org/browse/FAB-1151 (thank you @Senthil1 )

fbenhamo (Thu, 06 Apr 2017 17:42:01 GMT):
Has joined the channel.

vdods (Thu, 06 Apr 2017 19:16:37 GMT):
Has joined the channel.

akm4 (Thu, 06 Apr 2017 20:05:41 GMT):
Has joined the channel.

DrTES (Thu, 06 Apr 2017 21:29:25 GMT):
Has joined the channel.

tortuga90 (Thu, 06 Apr 2017 23:50:14 GMT):
Has joined the channel.

tenc (Fri, 07 Apr 2017 00:27:23 GMT):
Has joined the channel.

jadhavajay (Fri, 07 Apr 2017 03:30:15 GMT):
Has joined the channel.

JayXie (Fri, 07 Apr 2017 03:38:27 GMT):
Has joined the channel.

aybekbuka (Fri, 07 Apr 2017 04:03:52 GMT):
Has joined the channel.

baohua (Fri, 07 Apr 2017 11:07:27 GMT):
would welcome for any discussion if this decoupling can be included in the release, thanks! https://jira.hyperledger.org/browse/FAB-3035

baohua (Fri, 07 Apr 2017 11:10:18 GMT):
If necessary, would take it on hand and target 1.0, thanks!

sarkoi (Fri, 07 Apr 2017 17:18:59 GMT):
Has joined the channel.

binhn (Fri, 07 Apr 2017 18:23:29 GMT):
@JonathanLevi @tbenzies @rjones thanks for creating this channel

binhn (Fri, 07 Apr 2017 18:24:07 GMT):
@JonathanLevi perhaps we should start with the summary list from your email

JonathanLevi (Fri, 07 Apr 2017 18:25:32 GMT):
Hi @binhn, thank you. Sure, let's do it... I have also put it also here, so that it's easy to comment upon (and track). https://docs.google.com/document/d/1sAsa389InUieQ0DsnVaw9qsPAWoJKZeUwBVf6R2dCD4/edit

JonathanLevi (Fri, 07 Apr 2017 18:25:50 GMT):
I plan to start adding sections with the things we all agree on.

binhn (Fri, 07 Apr 2017 18:26:21 GMT):
ah, better there

JonathanLevi (Fri, 07 Apr 2017 18:26:42 GMT):
(noting, for all, that the Release Strategy and the final vote is for the maintainers... but feedback is welcome)

JonathanLevi (Fri, 07 Apr 2017 18:28:44 GMT):
(channel: noting, that the Release Strategy is visible/available and 100% transparent, but at the same time the final vote/approval is up to all the maintainers...), with that in mind: all sorts of feedback/input is welcome!

JonathanLevi (Fri, 07 Apr 2017 18:28:44 GMT):
(channel): noting, that the Release Strategy is visible/available and 100% transparent, but at the same time the final vote/approval is up to all the maintainers...), with that in mind: all sorts of feedback/input is welcome!

binhn (Fri, 07 Apr 2017 18:44:02 GMT):
it looks like we have 2 camps on release strategy https://docs.google.com/document/d/1sAsa389InUieQ0DsnVaw9qsPAWoJKZeUwBVf6R2dCD4/edit At this point, i'd prefer to focus on hardening 1.0 before cutting the branch to minimize the distraction. It is critical that we do these the next 2 weeks (sprint 16) - addressing bugs - usability (easy to bring up a simple network), doc, samples - performance We can leverage any help from anyone

Adeel Qureshi (Sat, 08 Apr 2017 15:13:53 GMT):
Has joined the channel.

king3000 (Mon, 10 Apr 2017 01:48:51 GMT):
Has joined the channel.

yahtoo (Mon, 10 Apr 2017 04:37:29 GMT):
Has joined the channel.

zian (Mon, 10 Apr 2017 14:01:59 GMT):
Has joined the channel.

troyronda (Mon, 10 Apr 2017 23:35:27 GMT):
Just checking if you guys have updates on this topic?

baohua (Tue, 11 Apr 2017 07:12:19 GMT):
A quick fix, welcome for review, thanks! https://gerrit.hyperledger.org/r/#/c/7885/

cbf (Tue, 11 Apr 2017 18:02:13 GMT):
@baohua think this was mis-posted, should have been in #fabric-pr-review

cbf (Tue, 11 Apr 2017 18:02:51 GMT):
@troyronda I sent a leengthy note to the hyperledger-fabric mailing list

cbf (Tue, 11 Apr 2017 18:03:22 GMT):
@binhn yes, we need to harden before we cut a branch - too much to be done at this point

Lin-YiTang (Tue, 11 Apr 2017 21:16:37 GMT):
Has joined the channel.

baohua (Wed, 12 Apr 2017 03:35:16 GMT):
aha, sorry for the incorrect posting

leungjob (Wed, 12 Apr 2017 03:41:54 GMT):
Has joined the channel.

msoumeit (Wed, 12 Apr 2017 17:08:51 GMT):
Has joined the channel.

troyronda (Thu, 13 Apr 2017 01:33:07 GMT):
@cbf - I see a focus on maintainers in the note. Of course in many development efforts there is a focus on what stakeholders need (sometimes represented by product owners in scrum). So I am curious how stakeholders (and similar) fit into a community process, such as this one.

troyronda (Thu, 13 Apr 2017 01:33:07 GMT):
@cbf - thanks for thoughts and for taking the time for process improvement. I see a focus on maintainers in the note. Of course in many development efforts there is a focus on what stakeholders need (sometimes represented by product owners in scrum). So I am curious how stakeholders (and similar) fit into a community process, such as this one.

troyronda (Thu, 13 Apr 2017 01:33:07 GMT):
@cbf - thanks for your thoughts and for taking the time for process improvement. I see a focus on maintainers in the note. Of course in many development efforts there is a focus on what stakeholders need (sometimes represented by product owners in scrum). So I am curious how stakeholders (and similar) fit into a community process, such as this one.

troyronda (Thu, 13 Apr 2017 01:33:11 GMT):
Also - I think there should be a clear path for bringing a contribution in (particularly for those who aren't maintainers) - need to ensure this is encouraged and successful.

troyronda (Thu, 13 Apr 2017 01:34:20 GMT):
I also think there needs to be improvement to the next release process so that feature development is not blocked for an extended period of time.

troyronda (Thu, 13 Apr 2017 01:35:28 GMT):
I am also wondering how certain characteristics are shepherded - like security, confidentiality, privacy, ...

troyronda (Thu, 13 Apr 2017 01:35:28 GMT):
I am also wondering how certain characteristics are shepherded - like security, confidentiality, privacy, decentralization, ...

ZengLingYou (Thu, 13 Apr 2017 01:42:50 GMT):
Has joined the channel.

eyalron (Thu, 13 Apr 2017 06:24:34 GMT):
Has joined the channel.

shamckm (Thu, 13 Apr 2017 07:16:49 GMT):
Has joined the channel.

PreetCS (Thu, 13 Apr 2017 09:54:50 GMT):
Has joined the channel.

mwall (Thu, 13 Apr 2017 10:47:38 GMT):
Has joined the channel.

somashekarn (Thu, 13 Apr 2017 12:32:01 GMT):
Has joined the channel.

cbf (Thu, 13 Apr 2017 14:52:39 GMT):
@troyronda absolutely, but I see the maintainers responsibility to take user requirements into consideration in their decision-making process

cbf (Thu, 13 Apr 2017 14:53:35 GMT):
I would like to see stakeholders weighing in on JIRA with comments

cbf (Thu, 13 Apr 2017 14:54:43 GMT):
and votes

cbf (Thu, 13 Apr 2017 14:55:08 GMT):
of course, that can be abused since the JIRA is open... I don't believe that there are constraints on that function

cbf (Thu, 13 Apr 2017 14:55:29 GMT):
bottom line, squeaky wheel gets the grease

cbf (Thu, 13 Apr 2017 14:55:39 GMT):
that is and has always been the case

cbf (Thu, 13 Apr 2017 14:56:18 GMT):
also, if there are missing items you think need to be added, add them (you being anyone)

cbf (Thu, 13 Apr 2017 14:58:22 GMT):
I am aggressively trying to clean up JIRA for this very reason - right now, there garden has gone to seed and we need to clean up the mess

troyronda (Thu, 13 Apr 2017 15:00:20 GMT):
So I think there are different uses of Fabric, and I think a discussion needs to happen on how to ensure these various uses are getting attention & shepherded - there may even be contrasting requirements that need to be fixed - like confidentiality vs analytics.

troyronda (Thu, 13 Apr 2017 15:02:59 GMT):
(different assumption on the usage of fabric)

troyronda (Thu, 13 Apr 2017 15:03:20 GMT):
(and different patches applied to fabric to enable them)

troyronda (Thu, 13 Apr 2017 15:07:09 GMT):
Example: blocks and RW sets being sent to clients might be handy for someone doing analytics but isn't good for those who need confidentiality. https://jira.hyperledger.org/browse/FAB-2679

mastersingh24 (Thu, 13 Apr 2017 15:42:08 GMT):
1) It is naive to believe that we can just keep on merging feature requests at the same time as trying to get to a release / release branch. Yes - you can continue feature development and you can submit CRs and keep them up to date by rebasing while they are waiting to be merged, but we can't simply merge code which actually changes core files and then attempt to cut a release after that. We must first get to code complete on the existing set of agreed on features (now how we do a better job of getting the release feature list is part of the release planning document) 2) There may be a mis-use and/or overuse of a specific function when the reality is that perhaps 2 or more features / function are actually needed. Eventhub is probably the greatest example of that. So perhaps we need to have clearly defined stories rather than getting into details of implementation and calling that the story / feature. Let me expand on Eventhub as it is a good example: At a high level, there are at least 2 separate use cases / requirements being handled by the eventhub implementation: - client submits a transaction and simply wants to know when that transaction has been committed - entity who "owns / runs" the peer wishes to integrate the peer with its existing systems Those are 2 very different requirements and should be treated as such 3) As we move forward, I do think having an initial agreed upon set of features for the next release milestones will be very helpful. BUT - as @cbf points out - we then need to figure out who is going to implement them. It's hard to control what people will choose to implement. Now if we see a group of people ignoring major features the community asked for and just doing their own thing, we can try to address it but in many ways the community will address it by simply leaving and moving on to using something else 4) When considering features, we have to make sure that we are not building a multi-headed, unmanageable and unusable monster. There are some things which simply are not appropriate for the direction of the "product"

skarim (Thu, 13 Apr 2017 15:54:14 GMT):
Has joined the channel.

troyronda (Thu, 13 Apr 2017 15:56:57 GMT):
@mastersingh24 - 1) I hear you, of course. However, when you need to work on the next version - it becomes difficult to collaborate and you just end up with a bunch of patches. And the longer a freeze lasts, the more painful it gets. 2) Yes - this is partly relates to my comment about shepherding characteristics of the system like confidentiality. 4) So when this situation happens, there has to be a careful consideration about sufficient plugability to enable that use case. Stakeholders still need the functionality they are looking for...

troyronda (Thu, 13 Apr 2017 15:56:57 GMT):
@mastersingh24 - 1) I hear you, of course. However, when you need to work on the next version - it becomes difficult to collaborate and you just end up with a bunch of patches. And the longer a freeze lasts, the more painful it gets. 2) Yes - this is partly relates to my comment about shepherding characteristics of the system like confidentiality. 3) And there needs to be flexibility, as different contributors have different interests and expertise. 4) So when this situation happens, there has to be a careful consideration about sufficient plugability to enable that use case. Stakeholders still need the functionality they are looking for...

mastersingh24 (Thu, 13 Apr 2017 16:00:12 GMT):
for 4) - sure - I think there are some place where plug points are definitely reasonable but you cannot solve every problem or requirement. Anyone who has ever tired this has built something which fails. You know I also STRONGLY believe that we cannot build everything into the peer

mastersingh24 (Thu, 13 Apr 2017 16:02:43 GMT):
But I think the major thing right now is how we turn the corner. Unfortunately, we have to reset a bit here and the only way to do that is to slow down now for a bit and get the house in order so we can move forward :)

troyronda (Thu, 13 Apr 2017 16:03:15 GMT):
I also don't think that everything is the peer ;)

troyronda (Thu, 13 Apr 2017 16:03:15 GMT):
I also don't think that everything is in the peer ;)

troyronda (Thu, 13 Apr 2017 16:03:31 GMT):
but there is a bare minimum ;)

troyronda (Thu, 13 Apr 2017 16:03:31 GMT):
but there is a minimum that is somewhere in-between ;)

troyronda (Thu, 13 Apr 2017 16:05:15 GMT):
on 4 - yes i know this... however there are major use cases that need to be handled that involve core aspects like data processing and appropriate confidentiality for the deployment.

troyronda (Thu, 13 Apr 2017 16:08:08 GMT):
And features that are about multi-organization confidentiality, privacy, consistency and data segregation need a path forward :)

mastersingh24 (Thu, 13 Apr 2017 16:08:22 GMT):
yeah - but that does not mean it all has to be done in a single process I guess is my point

mastersingh24 (Thu, 13 Apr 2017 16:08:33 GMT):
been there, done that, lived the nightmare ;)

troyronda (Thu, 13 Apr 2017 16:09:03 GMT):
Sure but the plugin point can execute something in another process. But the point remains that it needs to exist

troyronda (Thu, 13 Apr 2017 16:09:03 GMT):
Sure but the plugin point can execute something in another process - depending on the case. But the point remains that the plugability needs to exist when something is in the middle of the processing flow.

troyronda (Thu, 13 Apr 2017 16:10:27 GMT):
This is effectively what use chain code does after all

troyronda (Thu, 13 Apr 2017 16:10:27 GMT):
This is effectively what user chain code does after all

mastersingh24 (Thu, 13 Apr 2017 16:10:47 GMT):
we should probably move this to another channel (the technical aspects)

mastersingh24 (Thu, 13 Apr 2017 16:10:55 GMT):
I'll leave you with this: https://github.com/jpmorganchase/constellation

mastersingh24 (Thu, 13 Apr 2017 16:11:00 GMT):
I kinda like the model

troyronda (Thu, 13 Apr 2017 16:12:14 GMT):
sure - thanks. Looks interesting... did you see the encryption notes in section 4 of the Private Data document

troyronda (Thu, 13 Apr 2017 16:12:14 GMT):
sure - thanks. Looks interesting... did you see the encryption notes in section 4 of the Private Data (side DB) document

troyronda (Thu, 13 Apr 2017 16:12:24 GMT):
ok we can go to another channel

mastersingh24 (Thu, 13 Apr 2017 16:15:10 GMT):
I did - and that's what brought me back to some thoughts I previously has when looking at Quroum

mastersingh24 (Thu, 13 Apr 2017 16:15:10 GMT):
I did - and that's what brought me back to some thoughts I previously has when looking at Quorum

troyronda (Thu, 13 Apr 2017 16:28:47 GMT):
cool

troyronda (Thu, 13 Apr 2017 16:28:47 GMT):
nice.. cool - i also had PGP in my head when I wrote that ;)...

JonathanLevi (Thu, 13 Apr 2017 19:24:26 GMT):
Hello @troyronda, @mastersingh24, ...: [Putting aside Constellation, PGP, the peer, etc. for now.] I want to focus back for a moment on the argument against focusing only on stabilizing the current `master` branch (ironing out the issues there and making it more stable). We need to make a call, and I don't want to miss important feedback/input. 2 quick questions: 1. Other than @troyronda, how many people (maintainers, who are also people, included. Is any of the maintainer who) believe that in the coming 6-8 months, we should work on more than stabilizing the 1.0 branch? 2. @troyronda and others, what are the high level points / reasons for preferring 2 branches these coming weeks?

JonathanLevi (Thu, 13 Apr 2017 19:24:26 GMT):
Hello @troyronda, @mastersingh24, ...: [Putting aside Constellation, PGP, the peer, etc. for now.] I want to focus back for a moment on the argument against focusing only on stabilizing the current `master` branch (ironing out the issues there and making it more stable). We need to make a call, and I don't want to miss important feedback/input. 2 quick questions: 1. Other than @troyronda, how many people (maintainers, who are also people, included. Is any of the maintainer who) believe that in the coming 6-8 weeks (~2 months), we should work on more than stabilizing the 1.0 branch? 2. @troyronda and others, what are the high level points / reasons for preferring 2 branches these coming weeks?

JonathanLevi (Thu, 13 Apr 2017 19:24:26 GMT):
Hello @troyronda, @mastersingh24, ...: [Putting aside Constellation, PGP, the peer, etc. for now.] I want to focus back for a moment on the argument against focusing only on stabilizing the current `master` branch (ironing out the issues there and making it more stable). We need to make a call, and I don't want to miss important feedback/input. 2 quick questions: 1. Other than @troyronda, how many people (maintainers, who are also people ;-) included.) believe that in the coming 6-8 weeks (~2 months), we should work on more than stabilizing the 1.0 branch? 2. @troyronda and others, what are the high level points / reasons for preferring 2 branches these coming weeks?

troyronda (Thu, 13 Apr 2017 19:25:32 GMT):
When did the idea of 6-8 months get floated?

JonathanLevi (Thu, 13 Apr 2017 19:25:33 GMT):
Am I right that the main concern is that if we all focus only on Fabric 1.0 during (say, ) April/May, we may lose contributions from other developers that would really like new features to get merged "now" ?

JonathanLevi (Thu, 13 Apr 2017 19:25:33 GMT):
Am I right that *the main concern is that if we all focus only on Fabric 1.0 during (say, ) April/May, we may lose contributions from other developers that would really like new features to get merged "now" * ?

troyronda (Thu, 13 Apr 2017 19:25:50 GMT):
That's not a possibility

troyronda (Thu, 13 Apr 2017 19:25:50 GMT):
I'm not understanding the idea there

troyronda (Thu, 13 Apr 2017 19:25:50 GMT):
I'm not understanding the idea there (re: 6-8 months)

rjones (Thu, 13 Apr 2017 19:25:52 GMT):
@JonathanLevi it lets developers that want to run ahead do so on master, remaining enganged

troyronda (Thu, 13 Apr 2017 19:28:19 GMT):
@JonathanLevi other developers end up with patches in the ether

JonathanLevi (Thu, 13 Apr 2017 19:30:18 GMT):
OK, I think I see - so the argument is that *the main concern is that if we all focus only on Fabric 1.0 during (say, ) April/May, we may lose contributions from other developers that would really like new features to get merged "now" - and they may end up with patches in the ether* ?

JonathanLevi (Thu, 13 Apr 2017 19:33:05 GMT):
I would like to also bring a little bit context. We are lucky to have a relatively diverse group of maintainers - and each of us has an area of familiarity. I should tell you that almost any maintainer told me that he believes that there is *so much work to do* in order to really test and stability the 1.0 branch...

JonathanLevi (Thu, 13 Apr 2017 19:33:40 GMT):
At the same time (and I don't mean to offend anyone - just stating a fact): *we still seem to break the APIs*

JonathanLevi (Thu, 13 Apr 2017 19:34:14 GMT):
[*break* as in *improve, enhance, solidify* of course ;-) ]

troyronda (Thu, 13 Apr 2017 19:34:16 GMT):
The issue is that 1.0 isn't feature complete

troyronda (Thu, 13 Apr 2017 19:34:16 GMT):
The issue is that 1.0 needs additional features for use cases that focus more on confidentiality

troyronda (Thu, 13 Apr 2017 19:34:16 GMT):
The issue is that 1.0 needs additional features for use cases that focus more on confidentiality and privacy

JonathanLevi (Thu, 13 Apr 2017 19:34:23 GMT):
Ye.

troyronda (Thu, 13 Apr 2017 19:34:38 GMT):
And needs to be extended for some use cases

troyronda (Thu, 13 Apr 2017 19:34:38 GMT):
And needs to be extended for some use cases (but these are bumped to 1.1)

JonathanLevi (Thu, 13 Apr 2017 19:34:39 GMT):
1.0 isn't feature complete and not even API frozen, almost.

troyronda (Thu, 13 Apr 2017 19:34:47 GMT):
I mean from the current scope

troyronda (Thu, 13 Apr 2017 19:35:04 GMT):
we already have patches in the ether

JonathanLevi (Thu, 13 Apr 2017 19:35:22 GMT):
Sorry I'm being boring: Are we talking now about *adding missing featuers* to 1.0 or to, say, Fabric 1.2 ?

mastersingh24 (Thu, 13 Apr 2017 19:35:24 GMT):
Feature complete from who's perspective?

JonathanLevi (Thu, 13 Apr 2017 19:35:31 GMT):
(one sec, Gari)

troyronda (Thu, 13 Apr 2017 19:36:22 GMT):
I'm talking about 1.1 or 1.2

rjones (Thu, 13 Apr 2017 19:36:24 GMT):
@JonathanLevi perhaps fabric could consider something like the plan here for moving from M0->RC?

JonathanLevi (Thu, 13 Apr 2017 19:36:36 GMT):
I'm trying to laser-zoom/focus: what is the biggest issue/concern?

JonathanLevi (Thu, 13 Apr 2017 19:36:40 GMT):
New featuers for 1.1 ?

troyronda (Thu, 13 Apr 2017 19:36:42 GMT):
based on the current scope of 1.0

troyronda (Thu, 13 Apr 2017 19:37:01 GMT):
yes new features for 1.1 due to the current definition of 1.0

JonathanLevi (Thu, 13 Apr 2017 19:38:16 GMT):
OK, so you have a few suggestions/features that are not part of the 1.0 roadmap (current, immediate plan).... and you would like to start merging these new features into some public repository, while `Fabric 1.0` is being worked out?

troyronda (Thu, 13 Apr 2017 19:39:05 GMT):
@mastersingh24 - adjusted my wording - sorry for the confusion

troyronda (Thu, 13 Apr 2017 19:40:09 GMT):
@JonathanLevi - looking for suggestions on this, yes

JonathanLevi (Thu, 13 Apr 2017 19:40:46 GMT):
OK, no problem. That's what I'm trying to understand.

JonathanLevi (Thu, 13 Apr 2017 19:41:21 GMT):
So in order to make a (my, at least) suggestion, I need another data point:

troyronda (Thu, 13 Apr 2017 19:42:01 GMT):
(And some bumped features like TCerts)

JonathanLevi (Thu, 13 Apr 2017 19:42:01 GMT):
Why would you not rather wait just a bit until we fix the not-so-stable-yet fabric 1.0 branch?

troyronda (Thu, 13 Apr 2017 19:42:11 GMT):
The timeline is too long

troyronda (Thu, 13 Apr 2017 19:42:11 GMT):
The timeline is too long (6-8 more weeks of freeze)

JonathanLevi (Thu, 13 Apr 2017 19:43:02 GMT):
But 1.1 will be released in months to come (if not more), anyway... wouldn't it?

troyronda (Thu, 13 Apr 2017 19:43:27 GMT):
I am interested on what the release cadence is anticipated to be

JonathanLevi (Thu, 13 Apr 2017 19:43:28 GMT):
So it is not as if we will release F 1.1 on May 1st...

troyronda (Thu, 13 Apr 2017 19:43:44 GMT):
Sure but the longer it takes to start means the more it pushes

troyronda (Thu, 13 Apr 2017 19:44:16 GMT):
what is the hard deadline for cutover to 1.1

troyronda (Thu, 13 Apr 2017 19:44:22 GMT):
or is it open-ended

JonathanLevi (Thu, 13 Apr 2017 19:44:28 GMT):
Well, the concern I have (for you) is that, say you "branch out"... and in the coming weeks, we start merging heavily (like we normally do close to releases)....

JonathanLevi (Thu, 13 Apr 2017 19:45:11 GMT):
You will end up (re)solving so many issues, with "merging up" from Fabric 1.0 - Release Candidate 1 (for example)

JonathanLevi (Thu, 13 Apr 2017 19:45:18 GMT):
... into your "feature branch"

JonathanLevi (Thu, 13 Apr 2017 19:45:32 GMT):
(that you can share amongst a few devs).

JonathanLevi (Thu, 13 Apr 2017 19:45:35 GMT):
---

JonathanLevi (Thu, 13 Apr 2017 19:46:16 GMT):
Mind you, that as part of the plan/release strategy we are also trying to consider/evaluate/estimate/allocate `resources`.

troyronda (Thu, 13 Apr 2017 19:46:26 GMT):
So look - I'm saying there is no hard schedule here - there is open-ended bug fixing

JonathanLevi (Thu, 13 Apr 2017 19:46:58 GMT):
Well, we are trying to "harden it". That's why I'm collecting all this info...

JonathanLevi (Thu, 13 Apr 2017 19:47:19 GMT):
Binhn suggested a schedule, Gari provided feedback, etc...

JonathanLevi (Thu, 13 Apr 2017 19:48:41 GMT):
We are looking something like (at it is up to the voting, etc.): - Around 4-6 more weeks of dev/tests for the core features - 2 Release Candidates (mid-May, end of May) - Beta/Release cut (around June)

JonathanLevi (Thu, 13 Apr 2017 19:48:41 GMT):
We are looking something like (not final yet - consider this as WIP - as it is up to the maintainers' voting, etc.): - Around 4-6 more weeks of dev/tests for the core features - 2 Release Candidates (mid-May, end of May) - Beta/Release cut (around June)

troyronda (Thu, 13 Apr 2017 19:48:56 GMT):
Enabling a privacy & confidentiality focused deployment needs 1.1 so this makes it hard

JonathanLevi (Thu, 13 Apr 2017 19:49:02 GMT):
Not carved in stone as are still planning.

troyronda (Thu, 13 Apr 2017 19:49:30 GMT):
So what is the concept around 1.1 then

JonathanLevi (Thu, 13 Apr 2017 19:49:52 GMT):
At this point, we are trying to harden and release the best `1.0` we can.

troyronda (Thu, 13 Apr 2017 19:50:23 GMT):
I hear you but still there is a portion of the community (including me) that is very focused on privacy and confidentiality

troyronda (Thu, 13 Apr 2017 19:50:23 GMT):
I hear you but still there is a portion of the community (at least me) that is very focused on privacy and confidentiality

troyronda (Thu, 13 Apr 2017 19:50:23 GMT):
I hear you but still there is a portion of the community that is very focused on privacy and confidentiality

JonathanLevi (Thu, 13 Apr 2017 19:50:33 GMT):
I, personally, have not voted/been asked much/anything about `1.1`... other than the roadmap doc.

troyronda (Thu, 13 Apr 2017 19:51:33 GMT):
(sure i was getting at release cadence)

JonathanLevi (Thu, 13 Apr 2017 19:51:45 GMT):
Troy, I am 200% with you. You know I also run a product that provides/brings extra features to the game.

JonathanLevi (Thu, 13 Apr 2017 19:52:14 GMT):
(HACERA) - but we have our own build, CI, tests, schedule...

JonathanLevi (Thu, 13 Apr 2017 19:52:27 GMT):
... and we adjust it to the Fabric 1.0 roadmap (at this point).

mastersingh24 (Thu, 13 Apr 2017 19:52:43 GMT):
BTW - there was a note sent to the mailing list from Chris about some of this stuff but I never really saw any additional responses

JonathanLevi (Thu, 13 Apr 2017 19:52:50 GMT):
I can't foresee what will happen at the end of Q4 2017. Trying to work out with the resources we currently have.

troyronda (Thu, 13 Apr 2017 19:53:05 GMT):
yikes - end of Q4?

troyronda (Thu, 13 Apr 2017 19:53:05 GMT):
End of Q4? I was wondering if there would be a faster cadence

JonathanLevi (Thu, 13 Apr 2017 19:53:08 GMT):
(e.g., Hyperledger's CI)

JonathanLevi (Thu, 13 Apr 2017 19:53:33 GMT):
I'm just saying: I'm not running polls now about Fabric 1.1.

troyronda (Thu, 13 Apr 2017 19:54:29 GMT):
This is the issue with open-ended timing on releases i guess

mastersingh24 (Thu, 13 Apr 2017 19:54:36 GMT):
ok - I think we have sorta moved off subject (although still related)

troyronda (Thu, 13 Apr 2017 19:55:06 GMT):
it would be good to have somewhat predictable cadence between releases

JonathanLevi (Thu, 13 Apr 2017 19:55:08 GMT):
(not arguing, btw): trying to develop/understand why suggesting that you work with a feature branch (in the coming weeks)... will not solve the issue.

JonathanLevi (Thu, 13 Apr 2017 19:55:34 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-release?msg=6auR39bhJiTwT6Qxe) How is this related to the question?

JonathanLevi (Thu, 13 Apr 2017 19:57:05 GMT):
Troy: I am not arguing, btw, merely trying to develop/understand why suggesting that you work with a feature branch (in the coming weeks)... will not solve the issue.

mastersingh24 (Thu, 13 Apr 2017 19:57:19 GMT):
@troyronda - it's hard to do that if you don't have the somewhat planned list of features which would comprise some type of cohesive "release" - but I agree that it is somewhat doable. You can say that you'll put out a point release every 2 months and that means you have let's say 6 weeks to develop a cohesive set of features. If you don't make the window, you are pushed to the next release

JonathanLevi (Thu, 13 Apr 2017 19:57:46 GMT):
I'm totally fine with a 2 months cycle.

JonathanLevi (Thu, 13 Apr 2017 19:57:54 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-release?msg=4XHu2kT7iMaR4ro6z)

mastersingh24 (Thu, 13 Apr 2017 19:57:57 GMT):
that was just an example

JonathanLevi (Thu, 13 Apr 2017 19:58:12 GMT):
(yes, understood)

mastersingh24 (Thu, 13 Apr 2017 19:58:23 GMT):
You might also have to classify features as incremental versus massive change

JonathanLevi (Thu, 13 Apr 2017 19:58:34 GMT):
I'm pinning down the specific question about the current "state":

JonathanLevi (Thu, 13 Apr 2017 19:58:43 GMT):
We don't yet have a set of frozen APIs.

mastersingh24 (Thu, 13 Apr 2017 19:58:45 GMT):
right

mastersingh24 (Thu, 13 Apr 2017 19:59:06 GMT):
right - and "we" had set a target of getting to the point by the end of this month

JonathanLevi (Thu, 13 Apr 2017 19:59:07 GMT):
Having 2 CIs now working on two branches.... (up)merging strategies, etc....

JonathanLevi (Thu, 13 Apr 2017 19:59:07 GMT):
@troyronda: Yes, *I am sure you appreciate that it does not come for free*. E.g., setting up now 2/parallel CIs now working on two branches.... [(up)merging strategies, etc. issues/sprints/JIRA ticket management/priorities/) that is with all the required/associated coordination.

troyronda (Thu, 13 Apr 2017 19:59:23 GMT):
@JonathanLevi - didn't intend to say solve or didn't solve.

JonathanLevi (Thu, 13 Apr 2017 19:59:52 GMT):
Troy, if you like, I can put it forward to a "vote"...

JonathanLevi (Thu, 13 Apr 2017 20:00:12 GMT):
I need to know if there are others that share the same concern/view of yours... ?

mastersingh24 (Thu, 13 Apr 2017 20:00:51 GMT):
Let me give this a try:

troyronda (Thu, 13 Apr 2017 20:05:12 GMT):
@JonathanLevi - we also deal with these issues already - yes (CI, merging upstream, ...)

mastersingh24 (Thu, 13 Apr 2017 20:05:55 GMT):
1) Do most people agree that we will need to cut release branch(es)? (I had a proposal that we always have 2 branches - master and the current major release branch) 2) Assuming that people agree with 1), then you have to agree when the right time to cut a release branch is. My proposal had been that we do that when we declare all features are complete and APIs are frozen and other than major exception we are then in bug fix only mode 3) At the point we cut the release branch, we can then open up the master branch for feature development (ideally for features that are on some type of list of planned features so people know what is being worked on) 4) This mean new code goes to master and bug fixes will need to go to both the release branch and master (at least until we actually get the "final" release out the door)

mastersingh24 (Thu, 13 Apr 2017 20:07:05 GMT):
BUT - in the meantime, nothing would prevent someone from submitting a patch that is not a v1.0.0 feature at this time for people to review and also to actively keep it up to date over the coming weeks while we get to API / feature complete and cut a 1.0.0 branch

mastersingh24 (Thu, 13 Apr 2017 20:07:19 GMT):
That was my proposal

JonathanLevi (Thu, 13 Apr 2017 20:07:27 GMT):
So in a line: *master is the "cutting-edge" stuff, and we "down-merge" from the "latest" to "1.0" when we believe that it's important enough?

mastersingh24 (Thu, 13 Apr 2017 20:07:31 GMT):
Anyway - that's the type of thing we need to vote on

JonathanLevi (Thu, 13 Apr 2017 20:08:32 GMT):
OK. So to "quantify" a little bit: of the 100% developers we have now:

mastersingh24 (Thu, 13 Apr 2017 20:08:41 GMT):
actually - bug fixes would be targetted at 1.0.0 and "up-merged" to master (or maybe you could do it the other way around - I guess any fixes needed for 1.0.0 branch need to make it to master)

JonathanLevi (Thu, 13 Apr 2017 20:08:51 GMT):
- How many "new features" that are 1.1 and not 1.0 are we expecting?

mastersingh24 (Thu, 13 Apr 2017 20:09:19 GMT):
for the record, we (IBM) would likely focus 90+% of our resource on 1.0.0

JonathanLevi (Thu, 13 Apr 2017 20:09:20 GMT):
That is, what percentage of the "workforce" in the coming 6-8 weeks, will work on the "next, next version"?

JonathanLevi (Thu, 13 Apr 2017 20:10:05 GMT):
Because most of the burden will now be the "down-merge"/test.

mastersingh24 (Thu, 13 Apr 2017 20:10:28 GMT):
So we would have 90-100% of IBM people working on getting to feature / API complete for the current set of 1.0.0 features

JonathanLevi (Thu, 13 Apr 2017 20:10:48 GMT):
We can keep master at `1.0` and have 90%+ of the IBMers, and say 75% of the Hyperledger fabric deveopers working on master.

mastersingh24 (Thu, 13 Apr 2017 20:10:53 GMT):
Then the top priority after that would be testing and fixing bugs on 1.0.0 across a couple of release candidates

JonathanLevi (Thu, 13 Apr 2017 20:11:28 GMT):
And,say, the 25% enthusiast that work on the next features - will need to keep in synch with the "getting-stabilzed" master branch.

JonathanLevi (Thu, 13 Apr 2017 20:11:28 GMT):
And,say, the 25% of the other developers/enthusiasts that work on the next features - will need to keep in synch with the "getting-stabilzed" master branch.

mastersingh24 (Thu, 13 Apr 2017 20:11:54 GMT):
if we are able to triage bugs correctly, we should not get into too big of a mess merging bugs fixes to the release and master branches

JonathanLevi (Thu, 13 Apr 2017 20:12:01 GMT):
Informally, this is what we do in HACERA. We really don't work with the nightly "master" branch.

JonathanLevi (Thu, 13 Apr 2017 20:12:28 GMT):
We take a weekly snapshot, develop on top, and frequently merge the new additional stuff from "master" into our local branch.

mastersingh24 (Thu, 13 Apr 2017 20:12:38 GMT):
so Docker uses a master branch and a release branch

JonathanLevi (Thu, 13 Apr 2017 20:12:48 GMT):
(so the burned is on the person who "merges")

mastersingh24 (Thu, 13 Apr 2017 20:12:56 GMT):
(and of course they use tags as well for historical purposes)

mastersingh24 (Thu, 13 Apr 2017 20:13:23 GMT):
right

mastersingh24 (Thu, 13 Apr 2017 20:13:25 GMT):
BUT

JonathanLevi (Thu, 13 Apr 2017 20:13:32 GMT):
We can use the docker model - but, all, remember, their codebase is more stable.

JonathanLevi (Thu, 13 Apr 2017 20:13:40 GMT):
(I honestly don't have a strong opinion)

JonathanLevi (Thu, 13 Apr 2017 20:13:49 GMT):
We merge weekly here. I can tell you this.

JonathanLevi (Thu, 13 Apr 2017 20:14:10 GMT):
I fetch master, merge to a local branch, run everything, and only then "vendor" fabric.

JonathanLevi (Thu, 13 Apr 2017 20:14:30 GMT):
It's probably the same "work-flow"

mastersingh24 (Thu, 13 Apr 2017 20:14:58 GMT):
in the interim, let's say we are still on master (until feature / API complete) and we are not merging non v1.0.0 features. I think that if people want to submit v1.1 or later features to master, go ahead although we won't merge them. They would need to keep them up to date and perhaps this might even help with making the changes more modular and less invasive ;)

mastersingh24 (Thu, 13 Apr 2017 20:15:13 GMT):
I also hate vendoring :(

JonathanLevi (Thu, 13 Apr 2017 20:15:20 GMT):
Ok, focus ;-)

JonathanLevi (Thu, 13 Apr 2017 20:15:49 GMT):
Troy: works for you?

troyronda (Thu, 13 Apr 2017 20:16:00 GMT):
@mastersingh24 - how do you deal with patches that depend on each other

mastersingh24 (Thu, 13 Apr 2017 20:16:26 GMT):
write better code ;)

troyronda (Thu, 13 Apr 2017 20:16:35 GMT):
the patches will look huge

troyronda (Thu, 13 Apr 2017 20:16:53 GMT):
that's all fine and good when merge happens soon after

troyronda (Thu, 13 Apr 2017 20:17:53 GMT):
(which i assume is why branches become needed)

JonathanLevi (Thu, 13 Apr 2017 20:18:07 GMT):
Troy, my two cents here: we can vote - but even if it is approved that others would like to work with 2 version in parallel in the coming 6-8 weeks...

JonathanLevi (Thu, 13 Apr 2017 20:18:32 GMT):
... remember that you won't be really able to make *huge* changes to the 1.1 API in the interim.

mastersingh24 (Thu, 13 Apr 2017 20:18:36 GMT):
if a stack of patches is the incremental development of a feature, then it should not be too difficult to manage this. if 2 new features depend on each other and you stack patches, I think that is bad. I think that's where you need to do a better job of defining interface / function boundaries

JonathanLevi (Thu, 13 Apr 2017 20:19:01 GMT):
Because you won't be able to merge.... that's where the bigger challenge is.

mastersingh24 (Thu, 13 Apr 2017 20:19:04 GMT):
BTW - I don't support 2 branches until we call 1.0.0 feature / API complete

mastersingh24 (Thu, 13 Apr 2017 20:19:17 GMT):
which should be in the next couple fo weeks

mastersingh24 (Thu, 13 Apr 2017 20:19:17 GMT):
which should be in the next couple of weeks

JonathanLevi (Thu, 13 Apr 2017 20:19:22 GMT):
How much can you really "push" in 1.1 while 1.0 is not "stable"...

JonathanLevi (Thu, 13 Apr 2017 20:19:50 GMT):
Yes, I agree. We much "freeze" first (at least the first milestone)

JonathanLevi (Thu, 13 Apr 2017 20:19:50 GMT):
Yes, I agree. We must/should "freeze" first (at least the first milestone)

mastersingh24 (Thu, 13 Apr 2017 20:19:58 GMT):
Indeed

mastersingh24 (Thu, 13 Apr 2017 20:20:07 GMT):
Else we will NEVER get to where we want to be

mastersingh24 (Thu, 13 Apr 2017 20:20:26 GMT):
we should be pretty close

JonathanLevi (Thu, 13 Apr 2017 20:20:28 GMT):
Troy, it's actually an advice.

troyronda (Thu, 13 Apr 2017 20:20:31 GMT):
It's the 6-8 + weeks part that bothered me

JonathanLevi (Thu, 13 Apr 2017 20:20:56 GMT):
You may end up ("figuratively") working with, say a team of 20 people... on 1.1 features.

JonathanLevi (Thu, 13 Apr 2017 20:21:21 GMT):
While needing to merge/consolidate 80-100 contributers/contributions a week.

JonathanLevi (Thu, 13 Apr 2017 20:21:52 GMT):
I would rather fork/branch only in a few weeks...

JonathanLevi (Thu, 13 Apr 2017 20:22:13 GMT):
... (with anything post 1.0)... but that's just from what I have seen around here.

mastersingh24 (Thu, 13 Apr 2017 20:22:33 GMT):
I also think we need to do a MUCH better job of modularizing the code in certain areas. So maybe if we can get to the 2 branches we can work on this as well as we see how invasive bug fixes are

JonathanLevi (Thu, 13 Apr 2017 20:22:33 GMT):
Gerrit some gets FLOODED with fixes, closer to milestones!

troyronda (Thu, 13 Apr 2017 20:23:52 GMT):
I appreciate your guy's efforts on thinking about this - we're all trying to get to the same place

troyronda (Thu, 13 Apr 2017 20:24:37 GMT):
I'm just caught a little bit on certain aspects

JonathanLevi (Thu, 13 Apr 2017 20:25:05 GMT):
Troy: NP. In addition, show me the JIRA tickets for the features for 1.1 (and not 1.0)

JonathanLevi (Thu, 13 Apr 2017 20:25:12 GMT):
(TCerts, or otherwise)

troyronda (Thu, 13 Apr 2017 20:25:14 GMT):
I'm not trying to disturb things ;)

JonathanLevi (Thu, 13 Apr 2017 20:25:29 GMT):
Are they API breaking?

troyronda (Thu, 13 Apr 2017 20:25:35 GMT):
but am trying to figure out the best way to solve this little pickle that I'm in

troyronda (Thu, 13 Apr 2017 20:25:35 GMT):
but am trying to figure out the best way forward

troyronda (Thu, 13 Apr 2017 20:25:40 GMT):
:)

troyronda (Thu, 13 Apr 2017 20:26:08 GMT):
Right now it effectively means that we are just merging in our private git.

JonathanLevi (Thu, 13 Apr 2017 20:26:12 GMT):
(you are not disturbing. I'm just trying to give this enough weight/consideration - in case we need to vote)

JonathanLevi (Thu, 13 Apr 2017 20:26:33 GMT):
I see. So final question about it from me, I believe:

JonathanLevi (Thu, 13 Apr 2017 20:27:00 GMT):
How will having a `fabric-1.1.-dev` branch with a CI help you?

JonathanLevi (Thu, 13 Apr 2017 20:27:24 GMT):
(And do you believe we should run it ourselves? HL Fabric? The LInux Foundation, etc.?)

JonathanLevi (Thu, 13 Apr 2017 20:27:39 GMT):
(just in the coming, say 4-6 weeks)

troyronda (Thu, 13 Apr 2017 20:28:01 GMT):
I guess there are two things at play.

troyronda (Thu, 13 Apr 2017 20:29:05 GMT):
1) determining how things will be accepted when 1.1 opens up; 2) depends on if others start on some 1.1 features

JonathanLevi (Thu, 13 Apr 2017 20:29:49 GMT):
Yes, please share with me the JIRA tickets?

JonathanLevi (Thu, 13 Apr 2017 20:30:38 GMT):
(if possible)

JonathanLevi (Thu, 13 Apr 2017 20:30:58 GMT):
At the moment, most of the votes we have/had are around should feature X get into 1.0

JonathanLevi (Thu, 13 Apr 2017 20:30:58 GMT):
At the moment, most of the votes we have/had are around should feature X get into 1.0 (yes/no for 1.0)

JonathanLevi (Thu, 13 Apr 2017 20:31:01 GMT):
(yes/no)

JonathanLevi (Thu, 13 Apr 2017 20:31:34 GMT):
We haven't set up the full plan for 1.1, 1.2 VNext.... there are some roadmaps/proposals, but nothing is set in stone.

JonathanLevi (Thu, 13 Apr 2017 20:32:01 GMT):
I really want to make a decision about the "2 versions" today or tomorrow.

JonathanLevi (Thu, 13 Apr 2017 20:32:01 GMT):
I really want to make a decision about the "supporting 2 versions/branches/sets of CIs" today or tomorrow.

JonathanLevi (Thu, 13 Apr 2017 20:33:07 GMT):
This should help: who else wants/needs/plans on working on features that he believes should be part of`fabric 1.1` and not part of `fabric `1.0` in the coming 4-6 weeks?

JonathanLevi (Thu, 13 Apr 2017 20:34:39 GMT):
This should help: who else wants/needs/plans on working on features that he believes should be part of `fabric 1.1` and not part of `fabric 1.0` in the coming 4-6 weeks?

phengel (Thu, 13 Apr 2017 20:53:47 GMT):
Has joined the channel.

rjones (Thu, 13 Apr 2017 20:56:30 GMT):
@mastersingh24 please see the document I linked earlier for @JonathanLevi

rjones (Thu, 13 Apr 2017 20:56:46 GMT):
On phone or I would do it directlt

rjones (Thu, 13 Apr 2017 20:56:46 GMT):
On phone or I would do it directly

mastersingh24 (Thu, 13 Apr 2017 20:57:53 GMT):
will do

alys (Fri, 14 Apr 2017 23:04:50 GMT):
Has joined the channel.

rjkuro (Sat, 15 Apr 2017 02:23:28 GMT):
Has joined the channel.

saism (Mon, 17 Apr 2017 05:54:02 GMT):
Has left the channel.

pd93 (Mon, 17 Apr 2017 13:09:03 GMT):
Has joined the channel.

rogeriofza (Mon, 17 Apr 2017 21:53:11 GMT):
Has joined the channel.

ada-wang (Thu, 20 Apr 2017 01:56:30 GMT):
Has joined the channel.

nhrishi (Thu, 20 Apr 2017 10:17:02 GMT):
Has joined the channel.

ankursam (Thu, 20 Apr 2017 18:24:34 GMT):
Has joined the channel.

feronti (Thu, 20 Apr 2017 19:10:12 GMT):
Has joined the channel.

mrkiouak (Sat, 22 Apr 2017 00:38:55 GMT):
Has joined the channel.

MichalMalka (Sun, 23 Apr 2017 06:30:21 GMT):
Has joined the channel.

MichalMalka (Sun, 23 Apr 2017 08:06:20 GMT):
@JonathanLevi - Do we have already a decision about the "supporting 2 versions/branches/sets of CIs"? Can you please share?

mastersingh24 (Sun, 23 Apr 2017 12:30:00 GMT):
@MichalMalka - Not yet - but there's a new proposal on the table which was sent to the mailing list. It has not been finalized and no decisions have been made, but here's the link for reference and please add any comments / concerns: https://docs.google.com/document/d/1ZQYEAET3o_tVDzTC218b_J1AkpHM30TnLTx0YMfegec/edit?usp=sharing

MichalMalka (Sun, 23 Apr 2017 13:33:19 GMT):
thanks

JonathanLevi (Mon, 24 Apr 2017 16:06:24 GMT):
Hi @MichalMalka , and everyone - yes, I appreciate that there are several ongoing threads over these, . I am actually working to summarize these (and will send out an update or two... as a good portion of the Hackfest in DC is dedicated to these)

LoupTheron (Mon, 24 Apr 2017 20:27:42 GMT):
Has joined the channel.

JonathanLevi (Wed, 26 Apr 2017 16:48:54 GMT):
FYI: https://chat.hyperledger.org/channel/fabric-maintainers?msg=uWLicRfiwRa79WhYk

marek.dapps (Thu, 27 Apr 2017 10:19:32 GMT):
Has joined the channel.

zupan (Thu, 27 Apr 2017 12:40:11 GMT):
Has joined the channel.

wsh_bob (Fri, 28 Apr 2017 08:12:22 GMT):
Has joined the channel.

vugranam (Fri, 28 Apr 2017 12:16:35 GMT):
Has joined the channel.

aybekbuka (Mon, 01 May 2017 17:44:33 GMT):
Hello, I have several questions about the release and performance of hyperledger/fabric. I started working on v0.6 in october 2016, now migrating the project to v1.0-alpha. 1) when fabric v1.0 will be stable enough to use in production mode ? 2) Should I start a project on v1-alpha and upgrade it after or wait till stable v1.0 is released ? 3) What is the number of maximum peers that fabric can handle ?

rjones (Mon, 01 May 2017 18:29:47 GMT):
Has left the channel.

feronti (Tue, 02 May 2017 12:49:48 GMT):
Has left the channel.

weeds (Tue, 02 May 2017 13:32:19 GMT):
Hi @aybekbuka The maintianers need to decide on exit criteria for Hyperledger-fabric v1,0 and are not declaring a date yet. I would start using the alpha, but I think they are planning on cutting a new alpha or potentially calling it Beta. 3) The maximum number of peers is really dependent on the type of chaincode, the number of endorsers. There is going to be more system type testing happening over next 2 months where I think we will get more details on this aspect of performance.

aybekbuka (Tue, 02 May 2017 13:35:07 GMT):
@weeds thanks

jljordan_bcgov (Tue, 02 May 2017 18:37:44 GMT):
Has joined the channel.

Paulo.Rodrigues (Wed, 03 May 2017 17:38:13 GMT):
Has joined the channel.

denis4inet (Sun, 07 May 2017 16:56:46 GMT):
Has joined the channel.

denis4inet (Sun, 07 May 2017 16:57:44 GMT):
Hey everyone. Does anyone can tell me, where I can download a release.tar.gz. The tarball by https://logs.hyperledger.org/sandbox/vex-yul-hyp-jenkins-2/fabric-binaries/release.tar.gz is not available.Actually I built fabric by myself but script `/opt/gopath/src/github.com/hyperledger/fabric/examples/dchackfest/samples/e2e/network_setup.sh` fails with ```panic: Fatal error when setting up MSP from directory /opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/ordererOrganizations/example.com/orderers/orderer.example.com: err Could not load a valid signer certificate from directory /opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/ordererOrganizations/example.com/orderers/orderer.example.com/signcerts, err Could not read directory open /opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/ordererOrganizations/example.com/orderers/orderer.example.com/signcerts: no such file or directory, err /opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/ordererOrganizations/example.com/orderers/orderer.example.com/signcerts```

denis4inet (Sun, 07 May 2017 16:57:44 GMT):
Hey everyone. Does anyone can tell me, where I can download a release.tar.gz. The tarball by https://logs.hyperledger.org/sandbox/vex-yul-hyp-jenkins-2/fabric-binaries/release.tar.gz is not available.Actually I built fabric by myself but script `/opt/gopath/src/github.com/hyperledger/fabric/examples/dchackfest/samples/e2e/network_setup.sh` fails with `panic: Fatal error when setting up MSP from directory /opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/ordererOrganizations/example.com/orderers/orderer.example.com: err Could not load a valid signer certificate from directory /opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/ordererOrganizations/example.com/orderers/orderer.example.com/signcerts, err Could not read directory open /opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/ordererOrganizations/example.com/orderers/orderer.example.com/signcerts: no such file or directory, err /opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/ordererOrganizations/example.com/orderers/orderer.example.com/signcerts`

stu2 (Sun, 07 May 2017 21:05:23 GMT):
Has joined the channel.

mffrench (Mon, 08 May 2017 11:46:16 GMT):
Has joined the channel.

mffrench (Mon, 08 May 2017 11:46:28 GMT):
Hi

mffrench (Mon, 08 May 2017 11:46:55 GMT):
a little question regarding fabric binaries release

mffrench (Mon, 08 May 2017 11:48:15 GMT):
the getting starting doc say to download them with following command : ``` curl -L https://logs.hyperledger.org/sandbox/vex-yul-hyp-jenkins-2/fabric-binaries/release.tar.gz -o release.tar.gz 2> /dev/null; tar -xvf release.tar.gz ```

mffrench (Mon, 08 May 2017 11:48:45 GMT):
but unfortunately this return an error : ``` ```

mffrench (Mon, 08 May 2017 11:48:45 GMT):
but unfortunately this return an error : ``` curl -L https://logs.hyperledger.org/sandbox/vex-yul-hyp-jenkins-2/fabric-binaries/release.tar.gz -o release.tar.gz 2> /dev/null; tar -xvf release.tar.gz 2 ↵ tar: This does not look like a tar archive gzip: unknown compression format tar: Child returned status 1 tar: Error is not recoverable: exiting now ```

mffrench (Mon, 08 May 2017 11:51:24 GMT):
Is there another new download address ?

harsha (Mon, 08 May 2017 12:18:07 GMT):
I guess that's bcoz URL doesn't exist

harsha (Mon, 08 May 2017 12:18:07 GMT):
I guess that's bcoz URL doesn't exist anymore

mffrench (Mon, 08 May 2017 12:19:08 GMT):
yes. I'm trying to get the new one ;)

mffrench (Mon, 08 May 2017 12:19:23 GMT):
if exists

mffrench (Mon, 08 May 2017 12:19:51 GMT):
I'd like to download the released cryptogen and configtxgen tools

harsha (Mon, 08 May 2017 12:20:39 GMT):
Can you try `make release` inside `fabric` for now until the above it fixed.

harsha (Mon, 08 May 2017 12:20:39 GMT):
Can you try `make release` inside `fabric` for now until the above is fixed.

mffrench (Mon, 08 May 2017 12:20:49 GMT):
yeah sure I can

mffrench (Mon, 08 May 2017 12:21:10 GMT):
but I try to avoid dependency on the fabric dev in my script in fact

mffrench (Mon, 08 May 2017 12:21:52 GMT):
so I'll wait ;)

harsha (Mon, 08 May 2017 13:13:48 GMT):
`curl -L https://nexus.hyperledger.org/content/repositories/snapshots/sandbox/vex-yul-hyp-jenkins-2/fabric-binaries/release.tar.gz -o release.tar.gz 2> /dev/null; tar -xvf release.tar.gz`

harsha (Mon, 08 May 2017 13:13:53 GMT):
Can you try this ?

JonathanLevi (Mon, 08 May 2017 13:28:42 GMT):
--- FYI, (from @weeds) Announcement: We hold a quick scrum call on Monday, Wednesday, Friday for Hyperledger-Fabric. The dial in for today at 9:30 EST is 1-888-426-6840 with passcode 33682113. We review what has passed or failed out of the daily build from CI, the highest priority bugs that must be addressed, CR's that need special attention from maintainers, unit test coverage, and serviceability. Also at the end of the call, developers sometimes talk about additional technical questions that should be addressed to stabilizing release where interlock needs to occur. We also try to take notes as best we can in the fabric-peer-endorser-comitter channel for those that are not able to attend or are in a geographical location that is not a good time for them to dial in. https://chat.hyperledger.org/channel/fabric-maintainers?msg=F7MDnvXyhEqccf7f4

JonathanLevi (Mon, 08 May 2017 13:28:50 GMT):
Everybody is welcome to join !

dave.enyeart (Mon, 08 May 2017 13:53:24 GMT):
Has joined the channel.

tkuhrt (Mon, 08 May 2017 13:58:55 GMT):
Has joined the channel.

richard.holzeis (Mon, 08 May 2017 14:25:10 GMT):
Has joined the channel.

binhn (Mon, 08 May 2017 17:23:11 GMT):
@JonathanLevi @cbf @greg.haskins @mastersingh24 @muralisr @dave.enyeart @jeffgarratt @kostas @elli-androulaki @C0rWin I compiled a potential list for alpha2 this week below. Please add/remove as appropriate ``` https://jira.hyperledger.org/browse/FAB-3301 cr 8995 https://jira.hyperledger.org/browse/FAB-2923 cr 8905 https://jira.hyperledger.org/browse/FAB-2940 cr 8905 https://jira.hyperledger.org/browse/FAB-2982 cr 8059 https://jira.hyperledger.org/browse/FAB-3574 cr 8853 https://jira.hyperledger.org/browse/FAB-3289 cr 8335 https://jira.hyperledger.org/browse/FAB-3690 fail to get chaincode https://jira.hyperledger.org/browse/FAB-1163 cc timeout and crash https://jira.hyperledger.org/browse/FAB-3525 stuck at startup with big ledger https://jira.hyperledger.org/browse/FAB-3310 grpc timeout ```

binhn (Mon, 08 May 2017 17:23:11 GMT):
@JonathanLevi @cbf @greg.haskins @mastersingh24 @muralisr @dave.enyeart @jeffgarratt @kostas @elli-androulaki @C0rWin I compiled a potential list for alpha2 this week below. Please add/remove as appropriate https://jira.hyperledger.org/browse/FAB-3301 cr 8995 https://jira.hyperledger.org/browse/FAB-2923 cr 8905 https://jira.hyperledger.org/browse/FAB-2940 cr 8905 https://jira.hyperledger.org/browse/FAB-2982 cr 8059 https://jira.hyperledger.org/browse/FAB-3574 cr 8853 https://jira.hyperledger.org/browse/FAB-3289 cr 8335 https://jira.hyperledger.org/browse/FAB-3690 fail to get chaincode https://jira.hyperledger.org/browse/FAB-1163 cc timeout and crash https://jira.hyperledger.org/browse/FAB-3525 stuck at startup with big ledger https://jira.hyperledger.org/browse/FAB-3310 grpc timeout

binhn (Mon, 08 May 2017 17:23:11 GMT):
@JonathanLevi @cbf @greg.haskins @mastersingh24 @muralisr @dave.enyeart @jeffgarratt @kostas @elli-androulaki @C0rWin I compiled a potential list for alpha2 this week below. Please add/remove as appropriate https://jira.hyperledger.org/browse/FAB-3301 cr 8995 https://jira.hyperledger.org/browse/FAB-2923 cr 8905 https://jira.hyperledger.org/browse/FAB-2940 cr 8905 https://jira.hyperledger.org/browse/FAB-2982 cr 8059 https://jira.hyperledger.org/browse/FAB-3574 cr 8853 https://jira.hyperledger.org/browse/FAB-3289 cr 8335 https://jira.hyperledger.org/browse/FAB-3690 fail to get chaincode https://jira.hyperledger.org/browse/FAB-1163 cc timeout and crash https://jira.hyperledger.org/browse/FAB-3525 stuck at startup with big ledger https://jira.hyperledger.org/browse/FAB-3310 grpc timeout https://jira.hyperledger.org/browse/FAB-3732 cr 9103

binhn (Mon, 08 May 2017 17:23:11 GMT):
@JonathanLevi @cbf @greg.haskins @mastersingh24 @muralisr @dave.enyeart @jeffgarratt @kostas @elli-androulaki @C0rWin I compiled a potential list for alpha2 this week below. Please add/remove as appropriate https://jira.hyperledger.org/browse/FAB-3301 cr 8995 https://jira.hyperledger.org/browse/FAB-2923 cr 8905 https://jira.hyperledger.org/browse/FAB-2940 cr 8905 https://jira.hyperledger.org/browse/FAB-2982 cr 8059 https://jira.hyperledger.org/browse/FAB-3574 cr 8853 https://jira.hyperledger.org/browse/FAB-3289 cr 8335 https://jira.hyperledger.org/browse/FAB-3690 fail to get chaincode https://jira.hyperledger.org/browse/FAB-1163 cc timeout and crash https://jira.hyperledger.org/browse/FAB-3525 stuck at startup with big ledger https://jira.hyperledger.org/browse/FAB-3310 grpc timeout https://jira.hyperledger.org/browse/FAB-3732 cr 9103 https://jira.hyperledger.org/browse/FAB-3655 cr 9075

binhn (Mon, 08 May 2017 17:23:11 GMT):
@JonathanLevi @cbf @greg.haskins @mastersingh24 @muralisr @dave.enyeart @jeffgarratt @kostas @elli-androulaki @C0rWin I compiled a potential list for alpha2 this week below. Please add/remove as appropriate https://jira.hyperledger.org/browse/FAB-3301 cr 8995 https://jira.hyperledger.org/browse/FAB-2923 cr 8905 https://jira.hyperledger.org/browse/FAB-2940 cr 8905 https://jira.hyperledger.org/browse/FAB-2982 cr 8059 https://jira.hyperledger.org/browse/FAB-3574 cr 8853 https://jira.hyperledger.org/browse/FAB-3289 cr 8335 https://jira.hyperledger.org/browse/FAB-3690 cr 9059 done https://jira.hyperledger.org/browse/FAB-1163 cc timeout and crash https://jira.hyperledger.org/browse/FAB-3525 stuck at startup with big ledger https://jira.hyperledger.org/browse/FAB-3310 grpc timeout https://jira.hyperledger.org/browse/FAB-3732 cr 9103 https://jira.hyperledger.org/browse/FAB-3655 cr 9075

binhn (Mon, 08 May 2017 17:23:11 GMT):
@JonathanLevi @cbf @greg.haskins @mastersingh24 @muralisr @dave.enyeart @jeffgarratt @kostas @elli-androulaki @C0rWin I compiled a potential list for alpha2 this week below. Please add/remove as appropriate https://jira.hyperledger.org/browse/FAB-3301 cr 8995 https://jira.hyperledger.org/browse/FAB-2923 cr 8905 https://jira.hyperledger.org/browse/FAB-2940 cr 8905 https://jira.hyperledger.org/browse/FAB-2982 cr 8059 https://jira.hyperledger.org/browse/FAB-3574 cr 8853 https://jira.hyperledger.org/browse/FAB-3289 cr 8335 https://jira.hyperledger.org/browse/FAB-3690 cr 9059 done https://jira.hyperledger.org/browse/FAB-1163 cc timeout and crash https://jira.hyperledger.org/browse/FAB-3525 stuck at startup with big ledger https://jira.hyperledger.org/browse/FAB-3310 grpc timeout https://jira.hyperledger.org/browse/FAB-3732 cr 9103 done https://jira.hyperledger.org/browse/FAB-3655 cr 9075

binhn (Mon, 08 May 2017 17:23:11 GMT):
@JonathanLevi @cbf @greg.haskins @mastersingh24 @muralisr @dave.enyeart @jeffgarratt @kostas @elli-androulaki @C0rWin I compiled a potential list for alpha2 this week below. Please add/remove as appropriate https://jira.hyperledger.org/browse/FAB-3301 cr 8995 done https://jira.hyperledger.org/browse/FAB-2923 cr 8905 https://jira.hyperledger.org/browse/FAB-2940 cr 8905 https://jira.hyperledger.org/browse/FAB-2982 cr 8059 https://jira.hyperledger.org/browse/FAB-3574 cr 8853 https://jira.hyperledger.org/browse/FAB-3289 cr 8335 https://jira.hyperledger.org/browse/FAB-3690 cr 9059 done https://jira.hyperledger.org/browse/FAB-1163 cc timeout and crash https://jira.hyperledger.org/browse/FAB-3525 stuck at startup with big ledger https://jira.hyperledger.org/browse/FAB-3310 grpc timeout https://jira.hyperledger.org/browse/FAB-3732 cr 9103 done https://jira.hyperledger.org/browse/FAB-3655 cr 9075

binhn (Mon, 08 May 2017 17:23:11 GMT):
@JonathanLevi @cbf @greg.haskins @mastersingh24 @muralisr @dave.enyeart @jeffgarratt @kostas @elli-androulaki @C0rWin I compiled a potential list for alpha2 this week below. Please add/remove as appropriate https://jira.hyperledger.org/browse/FAB-3301 cr 8995 done https://jira.hyperledger.org/browse/FAB-2923 cr 8905 https://jira.hyperledger.org/browse/FAB-2940 cr 8905 https://jira.hyperledger.org/browse/FAB-2982 cr 8059 https://jira.hyperledger.org/browse/FAB-3574 cr 8853 done https://jira.hyperledger.org/browse/FAB-3289 cr 8335 https://jira.hyperledger.org/browse/FAB-3690 cr 9059 done https://jira.hyperledger.org/browse/FAB-1163 cc timeout and crash https://jira.hyperledger.org/browse/FAB-3525 stuck at startup with big ledger https://jira.hyperledger.org/browse/FAB-3310 grpc timeout https://jira.hyperledger.org/browse/FAB-3732 cr 9103 done https://jira.hyperledger.org/browse/FAB-3655 cr 9075

binhn (Mon, 08 May 2017 17:23:11 GMT):
@JonathanLevi @cbf @greg.haskins @mastersingh24 @muralisr @dave.enyeart @jeffgarratt @kostas @elli-androulaki @C0rWin I compiled a potential list for alpha2 this week below. Please add/remove as appropriate https://jira.hyperledger.org/browse/FAB-3301 cr 8995 done https://jira.hyperledger.org/browse/FAB-2923 cr 8905 https://jira.hyperledger.org/browse/FAB-2940 cr 8905 https://jira.hyperledger.org/browse/FAB-2982 cr 8059 https://jira.hyperledger.org/browse/FAB-3574 cr 8853 done https://jira.hyperledger.org/browse/FAB-3289 cr 8335 https://jira.hyperledger.org/browse/FAB-3690 cr 9059 done https://jira.hyperledger.org/browse/FAB-1163 cc timeout and crash https://jira.hyperledger.org/browse/FAB-3525 stuck at startup with big ledger https://jira.hyperledger.org/browse/FAB-3310 grpc timeout https://jira.hyperledger.org/browse/FAB-3732 cr 9103 done https://jira.hyperledger.org/browse/FAB-3655 cr 9075 https://jira.hyperledger.org/browse/FAB-3156 cr 8313

jeffgarratt (Mon, 08 May 2017 17:23:11 GMT):
Has joined the channel.

binhn (Mon, 08 May 2017 17:38:38 GMT):
@jimthematrix ^^

nnao (Mon, 08 May 2017 18:23:02 GMT):
Has joined the channel.

cbf (Mon, 08 May 2017 18:49:03 GMT):
@binhn these are MUST HAVE... absolutely positively no way can we cut a release without these CRs that need to be merged?

cbf (Mon, 08 May 2017 18:52:11 GMT):
https://gerrit.hyperledger.org/r/#/c/8853/ is failing on power, but builds cleanly on X and Z

cbf (Mon, 08 May 2017 18:58:15 GMT):
https://gerrit.hyperledger.org/r/#/c/8905/ is SDK, is this absolutely necessary? It says in review but in reality being reworked

cbf (Mon, 08 May 2017 18:59:14 GMT):
https://gerrit.hyperledger.org/r/#/c/8995/ is failing CI and cannot be merged

rameshthoomu (Mon, 08 May 2017 19:07:53 GMT):
@cbf https://gerrit.hyperledger.org/r/#/c/8853 is failing on power due to build timeout.. Power nodes are taking more than 50 mins to complete fabric-ca tests where as z is taking 15-20 mins...

rameshthoomu (Mon, 08 May 2017 19:08:23 GMT):
I am working with @bsmita on this

bsmita (Mon, 08 May 2017 19:08:23 GMT):
Has joined the channel.

rameshthoomu (Mon, 08 May 2017 19:09:10 GMT):
Will increase build timeout for now to proceed further

binhn (Mon, 08 May 2017 19:21:38 GMT):
@cbf i said `a potential list for alpha2`, meaning a starting point for discussion; some are more critical than others

JonathanLevi (Mon, 08 May 2017 19:51:22 GMT):
Fair enough - yes, let's see what do we need to do in order to cut an `alpha2`. BTW: I'm collecting all the issue I am aware of (and/or hear about) here: https://jira.hyperledger.org/browse/FAB-3040 Trying to help us all to collect everything we are aware of (for v1.0.0) in one place, including Java SDK. Similarly, it does not have the granularity/differentiation between `1.0.0-alpha2` and `1.0.0`(yet).

JonathanLevi (Mon, 08 May 2017 19:51:22 GMT):
Fair enough - yes, let's see what do we need to do in order to cut an `alpha2`. BTW: I'm collecting all the issues I am/we are aware of (and/or hear about) here: https://jira.hyperledger.org/browse/FAB-3040 Trying to help us all to collect everything we are aware of (for v1.0.0) in one place, including Java SDK. Similarly, it does not have the granularity/differentiation between `1.0.0-alpha2` and `1.0.0`(yet).

JonathanLevi (Mon, 08 May 2017 19:51:22 GMT):
Fair enough - yes, let's see what do we need to do in order to cut an `alpha2`. BTW: I'm collecting all the issues I am/we are aware of (and/or hear about) here: https://jira.hyperledger.org/browse/FAB-3040 Trying to help us all to collect everything we are aware of (for v1.0.0) in one place, including Java SDK. Similarly, it does not (currently) have the granularity/differentiation between `1.0.0-alpha2` and `1.0.0`(yet).

JonathanLevi (Mon, 08 May 2017 19:51:22 GMT):
Fair enough - yes, let's see what do we need to do in order to cut an `alpha2`. BTW: I'm collecting all the issues I am/we are aware of (and/or hear about) here: https://jira.hyperledger.org/browse/FAB-3040 Trying to help us all to collect everything we are aware of (for v1.0.0) in one place, including Java SDK. Similarly, it does not (currently) have the granularity/differentiation between `1.0.0-alpha2` and `1.0.0`(yet) - which we'll discuss.

JonathanLevi (Mon, 08 May 2017 19:52:45 GMT):
Please chime in (if you are aware of more issues). Also, please keep in mind that we are still trying to release an `alpha2` sooner rather than later... as we really need a good round of meaningful feedback from new/existing users who try the latest.

JonathanLevi (Mon, 08 May 2017 19:55:44 GMT):
Please chime in (if you are aware of more issues). Also, please keep in mind that we are still trying to release an `alpha2` sooner rather than later... as we really need a good round of meaningful feedback from new/existing users who [will] try the latest.

JonathanLevi (Mon, 08 May 2017 19:56:16 GMT):

Message Attachments

jimthematrix (Mon, 08 May 2017 20:47:04 GMT):
@cbf 8905 and 8995 are both requested by the composer team. 8905 should be really close with remaining work in updating the tests; 8995 not further work expected just waiting for https://gerrit.hyperledger.org/r/#/c/9059/ to make the build green again

jimthematrix (Mon, 08 May 2017 20:47:04 GMT):
@cbf 8905 and 8995 are both requested by the composer team. 8905 should be really close with remaining work in updating the tests; 8995 no further work expected just waiting for https://gerrit.hyperledger.org/r/#/c/9059/ to make the build green again

jimthematrix (Mon, 08 May 2017 20:47:43 GMT):
@binhn we actually need one more on the list: https://gerrit.hyperledger.org/r/#/c/9103/

jimthematrix (Mon, 08 May 2017 20:48:03 GMT):
which is preventing node and Java builds from succeeding

binhn (Mon, 08 May 2017 20:59:06 GMT):
@jimthematrix thanks -- added to the list

jimthematrix (Mon, 08 May 2017 21:17:28 GMT):
@binhn @cbf also need https://jira.hyperledger.org/browse/FAB-3655 (https://gerrit.hyperledger.org/r/#/c/9075/), requested by community user who were blocked by the package.json pulling an NPM dependency from a github because his CI environment disallows access to github

jimthematrix (Mon, 08 May 2017 21:18:02 GMT):
it's simply cleaning up unused dependencies without code change (also removed an unused class)

foravneet (Mon, 08 May 2017 23:37:17 GMT):
Has joined the channel.

binhn (Tue, 09 May 2017 02:55:08 GMT):
@jimthematrix added -- note that 9075 failed ci

jimthematrix (Tue, 09 May 2017 03:47:13 GMT):
https://gerrit.hyperledger.org/r/#/c/9059/ has the fixes to overcome recent breaking changes (instantiation policy), which just built successfully

mutexing (Tue, 09 May 2017 04:37:03 GMT):
Has joined the channel.

saism (Tue, 09 May 2017 09:56:37 GMT):
Has joined the channel.

simsc (Tue, 09 May 2017 14:36:56 GMT):
Has joined the channel.

simsc (Tue, 09 May 2017 15:52:07 GMT):
I added a new widget to Defect Dashboard to track the list above. The query is based off fixed version 1.0.0-alpha. So use this to add / remove candidates

bkvellanki (Wed, 10 May 2017 14:24:26 GMT):
Has joined the channel.

cbf (Wed, 10 May 2017 16:23:24 GMT):
@here https://jira.hyperledger.org/browse/FAB-3040

cbf (Wed, 10 May 2017 16:23:36 GMT):
please see my comment, I think we need to wrap this puppy up

cbf (Wed, 10 May 2017 19:24:15 GMT):
@here so, we are pretty close. I picked off a couple of blockers that were not critical per discussions logged in comments to FAB-3040. I also pinged folk on the remaining items.

cbf (Wed, 10 May 2017 19:28:11 GMT):
I think I'd like to see others weigh in on java chaincode comment

jimthematrix (Wed, 10 May 2017 19:35:37 GMT):
@cbf just added FAB-3806 to 3040 list of must-have's (readme update for NPM purposes)

jimthematrix (Wed, 10 May 2017 19:51:59 GMT):
@here added comment to https://jira.hyperledger.org/browse/FAB-3040 regarding java SDK

cbf (Wed, 10 May 2017 19:52:11 GMT):
thx

jimthematrix (Wed, 10 May 2017 19:52:12 GMT):
i'd like to propose it be included in the alpha2. see details in the JIRA

akash42145 (Thu, 11 May 2017 06:39:02 GMT):
Has joined the channel.

akash42145 (Thu, 11 May 2017 06:41:35 GMT):
Hello EveryOne , Could you please let me know which version of Fabric-SDK-node is stable version of v1 ?

JonathanLevi (Thu, 11 May 2017 13:05:27 GMT):
Hello @akash42145, Fabric v1 has not been released yet. There was a `v1.0.0-alpha` tag, and we are about to cut a `v1.0.0-alpha2` this week (give or take a day).

JonathanLevi (Thu, 11 May 2017 13:06:05 GMT):
The upcoming `v1.0.0-alpha2` which will include the SDK Node, will include the latest cut from the `master` branch.

JonathanLevi (Thu, 11 May 2017 13:06:53 GMT):
(we are in a *feature-freeze* mode)

JonathanLevi (Thu, 11 May 2017 13:07:17 GMT):
You are more than welcome to try it out and provide feedback/ask questions.

JonathanLevi (Thu, 11 May 2017 13:07:37 GMT):
(or wait until we tag the alpha2 very soon)

nickmelis (Thu, 11 May 2017 13:50:30 GMT):
will the Java SDK be included in alpha2?

nickmelis (Thu, 11 May 2017 13:50:30 GMT):
will the Java SDK be included in alpha2? Not very clear from the comments in FAB-3040

HansDeLeenheer (Thu, 11 May 2017 15:36:34 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-release?msg=A4LYSceXp7uFWK3Ro) @nickmelis this one makes the answer to your question disturbing; https://jira.hyperledger.org/browse/FAB-3850

nickmelis (Thu, 11 May 2017 15:51:27 GMT):
@HansDeLeenheer I believe FAB-3850 is about Java chaincode, bad news anyway.

JonathanLevi (Thu, 11 May 2017 16:21:31 GMT):
Yes, sorry about the bad news regarding the Java CC - as per the Jira ticket - despite the good progress wrt the Java SDK, we do not feel that is it quite ready yet.

JonathanLevi (Thu, 11 May 2017 16:22:05 GMT):
I still feel that the SDK Node is a lot more mature, which is why I voted in FAB-3040 the way I did.

nickmelis (Thu, 11 May 2017 16:22:17 GMT):
@JonathanLevi is there going to be an alpha3 too?

JonathanLevi (Thu, 11 May 2017 16:23:21 GMT):
The plan is to release a baseline (alpha2), and keep the API locked/frozen. If we feel that it is stable enough (subject to feedback from the wider community), our next milestone is actually a *beta*.

JonathanLevi (Thu, 11 May 2017 16:24:49 GMT):
So the short(er) answer is "hopefully not". But let's see. We are trying to do the best we can to incorporate in `v1.0.0-alpha2` everything we are aware of, while releasing it shortly.

webdaford (Thu, 11 May 2017 18:57:46 GMT):
Has joined the channel.

cbf (Fri, 12 May 2017 11:27:43 GMT):
https://jira.hyperledger.org/browse/FAB-3891

cbf (Fri, 12 May 2017 11:28:01 GMT):
created a task that we can use to track the process of cutting the release

cbf (Fri, 12 May 2017 11:28:55 GMT):
@greg.haskins @mastersingh24 @binhn @JonathanLevi and anyone else please weigh in

cbf (Fri, 12 May 2017 11:29:24 GMT):
I think we just need to merge the two JavaCC CRs and the changelog CR and we can begin the process of cutting the release

greg.haskins (Fri, 12 May 2017 12:51:25 GMT):
I think until we have the CI mechanism in place to manage the branches, just KISS and manage this like we did the last one

greg.haskins (Fri, 12 May 2017 12:51:51 GMT):
that is keep single branch (master), cut/tag alpha2, and continue one with master frozen

greg.haskins (Fri, 12 May 2017 12:51:51 GMT):
that is keep single branch (master), cut/tag alpha2, and continue on with master frozen

greg.haskins (Fri, 12 May 2017 12:52:25 GMT):
if we end up needing "alpha2.1" we can retro cut a branch from the tag

greg.haskins (Fri, 12 May 2017 12:53:08 GMT):
IOW, I am not a fan of implementing the "develop" branch strategy until we hit 1.0 GA

cbf (Fri, 12 May 2017 12:55:49 GMT):
well, some want to develop for 1.1

cbf (Fri, 12 May 2017 12:55:55 GMT):
eg post 1.0

greg.haskins (Fri, 12 May 2017 12:56:25 GMT):
understood, and that is precisely why I say "dont do it", heh

cbf (Fri, 12 May 2017 12:56:26 GMT):
note that I am not a fan of this, and it would mean frequent rebases, but there is demand (not from IBM I might add)

cbf (Fri, 12 May 2017 12:56:32 GMT):
LOL

greg.haskins (Fri, 12 May 2017 12:56:47 GMT):
that is exactly what happened in v0.6

greg.haskins (Fri, 12 May 2017 12:57:18 GMT):
people went nuts with the v1.0 stuff and were completely out of sync with what was being carefully curated for v0.6

greg.haskins (Fri, 12 May 2017 12:57:38 GMT):
the merge was a multi-day nightmare that @muralisr and I had to slog through

greg.haskins (Fri, 12 May 2017 12:58:14 GMT):
if the v0.6 were trickling out CR by CR to the master branch (by some automated CI merge process, for instance) it wouldnt have been bad

greg.haskins (Fri, 12 May 2017 12:58:29 GMT):
but because we waited weeks/months, it was a headache

greg.haskins (Fri, 12 May 2017 13:00:02 GMT):
so, for lack of a sufficient merge process in place to manage that correctly, my suggestion is the far more conservative thing is to just keep things simple...one branch, its frozen, only v1.0 targeted CRs go in

greg.haskins (Fri, 12 May 2017 13:00:47 GMT):
users that want to hack on v1.1 can do so with a bajillion other options (working in github, for instance) but the main point is this model would crowdsource the merge work

greg.haskins (Fri, 12 May 2017 13:01:24 GMT):
each group working on a featurebranch would have the impetus to keep up with gerrit::master, rather than have someone like Murali and myself have to resolve _everyones_ featurebranch at once

greg.haskins (Fri, 12 May 2017 13:03:32 GMT):
In case its not clear: I understand the ask and the proposed model...i just dont think we are ready to use it yet

cbf (Fri, 12 May 2017 13:14:17 GMT):
well, don't disagree, but I do think that there is value in having master be always stable release

cbf (Fri, 12 May 2017 13:14:46 GMT):
eg have the default branch from git clone always be stable

cbf (Fri, 12 May 2017 13:14:55 GMT):
in case people choose to go that route

cbf (Fri, 12 May 2017 13:15:18 GMT):
so I can see cutting a branch that becomes develop, and then locking down master

cbf (Fri, 12 May 2017 13:15:54 GMT):
@rjones can probably work some magic that we can restrict access to master branch (he asks)

rjones (Fri, 12 May 2017 13:15:54 GMT):
Has joined the channel.

rjones (Fri, 12 May 2017 13:18:58 GMT):
@cbf we probably could do that (differential access to merging on branches) but I'm not sure what you mean. do you mean people couldn't push to refs/for/master, for instance, unless they were in the list?

cbf (Fri, 12 May 2017 13:19:19 GMT):
yes, restrict who can push

cbf (Fri, 12 May 2017 13:19:24 GMT):
to master

JonathanLevi (Fri, 12 May 2017 13:19:27 GMT):
(into master)

rjones (Fri, 12 May 2017 13:19:50 GMT):
to the maintainers only?

JonathanLevi (Fri, 12 May 2017 13:19:56 GMT):
@rjones, it's more like a merge up into master.

cbf (Fri, 12 May 2017 13:20:13 GMT):
think that makes sense if we could (and if we agree to have master and develop)

JonathanLevi (Fri, 12 May 2017 13:20:15 GMT):
So that nobody actually works directly against (the new) master.

cbf (Fri, 12 May 2017 13:20:21 GMT):
right

cbf (Fri, 12 May 2017 13:20:25 GMT):
always stable

cbf (Fri, 12 May 2017 13:20:50 GMT):
we could still lock down develop until post 1.0

cbf (Fri, 12 May 2017 13:21:02 GMT):
and that I think would make @greg.haskins happy

rjones (Fri, 12 May 2017 13:21:04 GMT):
I'll ask how we can support this, but perhaps walk the idea around on the mailing list a little?

rjones (Fri, 12 May 2017 13:21:34 GMT):
we're going to end up asking people to essentially abandon any pending changes on master RN

rjones (Fri, 12 May 2017 13:21:44 GMT):
which is quite a few

cbf (Fri, 12 May 2017 13:21:45 GMT):
and by lock down, I mean limit which FABs can get merged that are not bug fixes

cbf (Fri, 12 May 2017 13:22:02 GMT):
yes, but they can repush to develop

cbf (Fri, 12 May 2017 13:22:25 GMT):
and we could modify the git review setup instructions to push to develop

cbf (Fri, 12 May 2017 13:22:35 GMT):
refs/for/develop that is

rjones (Fri, 12 May 2017 13:26:24 GMT):
I'll see what it would take.

mastersingh24 (Fri, 12 May 2017 13:28:22 GMT):
[But this was not due to branching really - it was due to many other factors. The biggest of which is that 1.0 should have been fresh :( ](https://chat.hyperledger.org/channel/fabric-release?msg=RjxzMLRHNW6kxufux) @greg.haskins

mastersingh24 (Fri, 12 May 2017 13:29:12 GMT):
I'm trying to follow this, but I'm clearly missing something

greg.haskins (Fri, 12 May 2017 13:29:41 GMT):
ultimately it was though

greg.haskins (Fri, 12 May 2017 13:30:23 GMT):
i understand what you are saying @mastersingh24 ...v1.0 was a major re-write...but there was plenty that was carry over and plenty of conflict was just in the common substrate

greg.haskins (Fri, 12 May 2017 13:30:26 GMT):
in any case...

greg.haskins (Fri, 12 May 2017 13:30:33 GMT):
i want to avoid that fiasco ;)

rjones (Fri, 12 May 2017 13:30:50 GMT):
TBH I think creating a `release` branch that is carefully curated, with changes that land on `release` being cherry-picked to `master` would be a more straight forward mechanic, but really it's all just pointers

cbf (Fri, 12 May 2017 13:31:06 GMT):
but what do you think about having a stable master and develop branch for the 1.0 end-game?

mastersingh24 (Fri, 12 May 2017 13:31:16 GMT):
So how is it that projects like Kafka and Docker manage to do this? Certainly they are not smarter than us

greg.haskins (Fri, 12 May 2017 13:31:22 GMT):
@rjones: i really think you have to do it that way

yacovm (Fri, 12 May 2017 13:31:28 GMT):
How far are we code-wise from alpha2 until V1.0 ? Does anyone have any estimate? I think that's the key here with regard to Greg's concern no?

cbf (Fri, 12 May 2017 13:31:44 GMT):
CF moved from master to develop and master == just published releases

greg.haskins (Fri, 12 May 2017 13:31:49 GMT):
the main thing I am asking for is to make the "cherry-pick to master" be automated, because the manual mode in gerrit is terrible at this

cbf (Fri, 12 May 2017 13:32:12 GMT):
@yacovm just 3 CRs I think and they are all ready to merge

greg.haskins (Fri, 12 May 2017 13:32:18 GMT):
(and by automated, I dont mean that a computer makes a unilateral decision

greg.haskins (Fri, 12 May 2017 13:32:29 GMT):
but rather, it just helps enforce the need

cbf (Fri, 12 May 2017 13:32:35 GMT):
see my comment on https://jira.hyperledger.org/browse/FAB-3040

cbf (Fri, 12 May 2017 13:32:35 GMT):
see my last comment on https://jira.hyperledger.org/browse/FAB-3040

greg.haskins (Fri, 12 May 2017 13:33:13 GMT):
"automated" could me that a jenkins dashboard goes RED until a maintainer does a merge, or something

greg.haskins (Fri, 12 May 2017 13:33:13 GMT):
"automated" could mean that a jenkins dashboard goes RED until a maintainer does a merge, or something

greg.haskins (Fri, 12 May 2017 13:33:32 GMT):
what I want to avoid is silent neglect

mastersingh24 (Fri, 12 May 2017 13:33:36 GMT):
Let me plug the "long game": 1) We put out a 1.0.0 release 2) We start working on 1.X release 3) People start using 1.0.0 and file several bugs which need to be fixed 4) We want people to be able to release 1.0.X patch releases which are based on 1.0.0 release

cbf (Fri, 12 May 2017 13:34:17 GMT):
I think the question comes down to: how long between releases?

cbf (Fri, 12 May 2017 13:35:11 GMT):
if the period between releases is short, we just have to deal with urgent fixes which per @dhuseby would be merged directly from a branch off of master

yacovm (Fri, 12 May 2017 13:35:24 GMT):
Wait, these are all the stories for V1.0.0? @cbf I don't see Gossip mutual TLS there

cbf (Fri, 12 May 2017 13:35:25 GMT):
and also to develop

rjones (Fri, 12 May 2017 13:35:32 GMT):
@greg.haskins do you care about the difference between a merge and a cherry pick? on my previous project I did a merge once a day or so, unless there was a conflict

greg.haskins (Fri, 12 May 2017 13:35:43 GMT):
@rjones: no

cbf (Fri, 12 May 2017 13:35:55 GMT):
@yacovm I never said that - just look at blockers for now

cbf (Fri, 12 May 2017 13:36:00 GMT):
that is alpha2

yacovm (Fri, 12 May 2017 13:36:03 GMT):
ok

mastersingh24 (Fri, 12 May 2017 13:36:28 GMT):
So my point is simple: 1) Keep a release branch where you only apply fixes and cut patch releases - it - keeps rolling out 1.0.1,1.0.2,...,1.0.N 2) You have the active development branch 3) Fixes get applied (if relevant) to both

cbf (Fri, 12 May 2017 13:36:32 GMT):
we still have to decide on 1.0

rjones (Fri, 12 May 2017 13:36:36 GMT):
@greg.haskins so I could just add that as something I do every day (the merge) and we could move on

greg.haskins (Fri, 12 May 2017 13:36:56 GMT):
@rjones: main concern is to avoid having either a situation where two branches inadvertently diverge and then need a bulk conflict resolution after a period of time

JonathanLevi (Fri, 12 May 2017 13:37:05 GMT):
Can I ask one question? (I feel like 4 people are typing)

mastersingh24 (Fri, 12 May 2017 13:37:06 GMT):
You are not always going to be able to atuo merge fixes for 1.0.X to 1.N development branch

rjones (Fri, 12 May 2017 13:37:07 GMT):
the only time that gets tricky is when version numbers are added

mastersingh24 (Fri, 12 May 2017 13:37:16 GMT):
How can they diverge?

mastersingh24 (Fri, 12 May 2017 13:37:24 GMT):
If you look at my option(s)

greg.haskins (Fri, 12 May 2017 13:37:43 GMT):
too many threads, heh

cbf (Fri, 12 May 2017 13:37:44 GMT):
@greg.haskins so long as we apply the patches to release also to develop, we should be good

mastersingh24 (Fri, 12 May 2017 13:37:47 GMT):
Indeed

JonathanLevi (Fri, 12 May 2017 13:37:55 GMT):
OK, I know how to get attention:

JonathanLevi (Fri, 12 May 2017 13:38:04 GMT):
---- I agree with Greg ----

mastersingh24 (Fri, 12 May 2017 13:38:05 GMT):
This is how people develop and support products

mastersingh24 (Fri, 12 May 2017 13:38:14 GMT):
Which part?

JonathanLevi (Fri, 12 May 2017 13:38:28 GMT):
(thanks ;-))

greg.haskins (Fri, 12 May 2017 13:38:36 GMT):
@cbf correct...i am just saying that unless there is some automation the "as long as we apply" part is tricky in gerrit

JonathanLevi (Fri, 12 May 2017 13:38:37 GMT):
I think we should focus today only on `alpha2`

JonathanLevi (Fri, 12 May 2017 13:38:54 GMT):
That is, I am very happy to just tag the latest code that we are happy with.

JonathanLevi (Fri, 12 May 2017 13:39:04 GMT):
Then, get a branch/CI job to run in the background.

cbf (Fri, 12 May 2017 13:39:17 GMT):
we need to publish a release, not just tag

JonathanLevi (Fri, 12 May 2017 13:39:21 GMT):
It's totally find (from my end) to have a few days of a total freeze.

JonathanLevi (Fri, 12 May 2017 13:39:21 GMT):
It's totally fine (from my end) to have a few days of a total freeze.

greg.haskins (Fri, 12 May 2017 13:39:28 GMT):
@mastersingh24 I totally agree with the model that I think you are eluding too...

cbf (Fri, 12 May 2017 13:39:31 GMT):
that means images, maven, npm etc

JonathanLevi (Fri, 12 May 2017 13:39:40 GMT):
Yes, and have that release off a branch, that is tracked, etc.

JonathanLevi (Fri, 12 May 2017 13:39:46 GMT):
The whole thing, yes.

greg.haskins (Fri, 12 May 2017 13:39:55 GMT):
can have a v1.0.x branch were only v1.0.x fixes go in, and not all of those fixes belong in v1.1

JonathanLevi (Fri, 12 May 2017 13:40:18 GMT):
Realistically, it is difficult to work with gerrit and "dynamic" feature branches.

mastersingh24 (Fri, 12 May 2017 13:40:27 GMT):
[Yes ](https://chat.hyperledger.org/channel/fabric-release?msg=x6uQejSN23Q6dJxqR) @greg.haskins

cbf (Fri, 12 May 2017 13:40:30 GMT):
note that for alpha2, I don't see a need for alpha2.1 we can just do alpha3

JonathanLevi (Fri, 12 May 2017 13:40:34 GMT):
We can pre-set a few of them... and have the workflow around these.

greg.haskins (Fri, 12 May 2017 13:40:37 GMT):
@mastersingh24: but do note this: _some_ of those fixes _do_ belong in v1.1...

JonathanLevi (Fri, 12 May 2017 13:40:43 GMT):
Yes, alpha2, alpha3, etc.

cbf (Fri, 12 May 2017 13:40:44 GMT):
we don't need to treat alpha2 like a 1.0

mastersingh24 (Fri, 12 May 2017 13:40:44 GMT):
correct

greg.haskins (Fri, 12 May 2017 13:40:54 GMT):
and without some order, it will get hard to keep track of whether it was done or neglected

JonathanLevi (Fri, 12 May 2017 13:41:04 GMT):
We just want all the 1.0 stuff to be in "one direction" so that we converge.

greg.haskins (Fri, 12 May 2017 13:41:29 GMT):
right...and to be clear, I think we totally need something more diverse than one branch after v1.0 is cut

mastersingh24 (Fri, 12 May 2017 13:41:38 GMT):
@greg.haskins - we seem to manage this fine for IBM products

yacovm (Fri, 12 May 2017 13:41:52 GMT):
I think it's impossible to have an automated process for merging fixes for both branches like @greg.haskins wants, but I think it's worth to somehow make a "policy"/"protocol" that ensures that both go into both branches, and at the same time it won't be a big "stress" on the maintainers. I think this can only be done if we try to avoid merging to master, unless it's a must.

JonathanLevi (Fri, 12 May 2017 13:41:53 GMT):
@mastersingh24: how?

greg.haskins (Fri, 12 May 2017 13:41:59 GMT):
i just think that right now, we are not sophisticated enough to manage more than one branch and its not critical to support v1.1 folks

cbf (Fri, 12 May 2017 13:42:03 GMT):
I'm failing to understand why having a stable master is not a good thing

greg.haskins (Fri, 12 May 2017 13:42:37 GMT):
what is critical is a quality v1.0 release

greg.haskins (Fri, 12 May 2017 13:42:42 GMT):
therefore, KISS

mastersingh24 (Fri, 12 May 2017 13:42:51 GMT):
I'll give you an example: When I worked on DataPower, we supported N-2 versions at any given time. If a bug is filed against any of those versions, the person who triages and/or fixes the bug determines for which releases it is relevant We then submit the fix against the 3 branches (we use Perforce) and then release it in the appropriate patch release for each version

cbf (Fri, 12 May 2017 13:43:01 GMT):
IMO, the experience that one gets from building or just using published images should be the same or we will go crazy with trying to figure out which software people are using when they file a bug

JonathanLevi (Fri, 12 May 2017 13:43:17 GMT):
That's for sure.

JonathanLevi (Fri, 12 May 2017 13:43:29 GMT):
We have to keep track, report, reproduce, fix, etc.

cbf (Fri, 12 May 2017 13:43:33 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-release?msg=5L3XuFKcvkJTeHms8) @greg.haskins amen

greg.haskins (Fri, 12 May 2017 13:43:48 GMT):
@mastersingh24 thats the model that I've always used too...the problem here is how gerrit works

greg.haskins (Fri, 12 May 2017 13:44:00 GMT):
or at least, how we use it

greg.haskins (Fri, 12 May 2017 13:44:25 GMT):
in most projects ive worked on, thats exactly what weve done...developer targets the right branch and then merges out as appropriate

greg.haskins (Fri, 12 May 2017 13:44:38 GMT):
but here, with our gerrit setup, gerrit makes that awkward

mastersingh24 (Fri, 12 May 2017 13:44:40 GMT):
[ I'll admit that I don't understand everything that was in your note about gerrit and how we use it / what it is capable of](https://chat.hyperledger.org/channel/fabric-release?msg=iDsyaFu95u8waY42X) @greg.haskins

greg.haskins (Fri, 12 May 2017 13:45:04 GMT):
so think of it this way

greg.haskins (Fri, 12 May 2017 13:45:16 GMT):
we currently do not allow merges between branches (and for a good reason)

greg.haskins (Fri, 12 May 2017 13:45:44 GMT):
so in order to do the model that you and I are talking about, a user has to submit a CR against all relevant branches

mastersingh24 (Fri, 12 May 2017 13:46:02 GMT):
correct - we have to do that here at IBM typically as well

mastersingh24 (Fri, 12 May 2017 13:46:20 GMT):
it gets tracked in the defect netry

mastersingh24 (Fri, 12 May 2017 13:46:20 GMT):
it gets tracked in the defect entry

greg.haskins (Fri, 12 May 2017 13:46:24 GMT):
whats worse, even if you can get people to be dilligent about this and not make mistakes....you have other problems

greg.haskins (Fri, 12 May 2017 13:46:36 GMT):
for instance, the CR may be accepted in one branch but not another

greg.haskins (Fri, 12 May 2017 13:46:52 GMT):
even if its accepted in lockstep, its not easy to see the relationship of the patch

mastersingh24 (Fri, 12 May 2017 13:47:09 GMT):
Right - fixes are not going to always be 100% compatible across release boundaries

cbf (Fri, 12 May 2017 13:47:12 GMT):
@greg.haskins this should be rare

greg.haskins (Fri, 12 May 2017 13:47:16 GMT):
(it looks like a discrete commit in each branch from gits point of view)

davidkel (Fri, 12 May 2017 13:47:35 GMT):
Has joined the channel.

mastersingh24 (Fri, 12 May 2017 13:47:45 GMT):
Sure - but JIRA could / would tie it all together

greg.haskins (Fri, 12 May 2017 13:48:12 GMT):
so it becomes really hard to answer questions like: was the patch applied in all branches it should be applied in?

mastersingh24 (Fri, 12 May 2017 13:48:19 GMT):
So @greg.haskins - what would you propose? ;)

cbf (Fri, 12 May 2017 13:48:31 GMT):
in @dhuseby model, only CVEs are merged against master (release, whatever) - these are merged with develop as needed and you FF merge develop into release

mastersingh24 (Fri, 12 May 2017 13:48:43 GMT):
JIRA should be the source of truth IMHO when it comes to tracking things

cbf (Fri, 12 May 2017 13:48:48 GMT):
y

yacovm (Fri, 12 May 2017 13:49:59 GMT):
I have a side question about this 2 branch split - could we make an automated process in CI (like a merge job) that "simulates" a merge between dev and master?

greg.haskins (Fri, 12 May 2017 13:50:02 GMT):
@cbf yes, i understand his model (I think)...its really not any different than, for instance, having a v1.0.x branch and a master branch

yacovm (Fri, 12 May 2017 13:50:14 GMT):
We could "detect" early that something is "wrong"

greg.haskins (Fri, 12 May 2017 13:50:39 GMT):
in either case, you have this notion that some branch is more delicate and only gets very targeted patches

yacovm (Fri, 12 May 2017 13:50:56 GMT):
Otherwise we'll come to the day when we need to "use" the development branch and nothing would work at all and go find the problem

cbf (Fri, 12 May 2017 13:50:58 GMT):
@greg.haskins right but my point is that there should be relatively few of these

cbf (Fri, 12 May 2017 13:51:16 GMT):
other fixes get bundled into the next release

greg.haskins (Fri, 12 May 2017 13:51:17 GMT):
the issue is that in my experience, things that are appropriate for the targeted branch have a reasonably probability of bring appropriate elsewhere

greg.haskins (Fri, 12 May 2017 13:51:17 GMT):
the issue is that in my experience, things that are appropriate for the targeted branch have a reasonably probability of being appropriate elsewhere

mastersingh24 (Fri, 12 May 2017 13:51:22 GMT):
For the record - I really just have one concern: how to put out patch releases without bring along anything but the prior patch release

mastersingh24 (Fri, 12 May 2017 13:51:22 GMT):
For the record - I really just have one concern: how to put out patch releases without bringing along anything but the prior patch release

greg.haskins (Fri, 12 May 2017 13:51:45 GMT):
and the gerrit model (or our use of it) makes it really hard to ensure that is happening properly

cbf (Fri, 12 May 2017 13:52:18 GMT):
@greg.haskins so @mastersingh24 asked what you would propose then...

cbf (Fri, 12 May 2017 13:52:37 GMT):
IMO, a single branch is not doing us any favors

greg.haskins (Fri, 12 May 2017 13:52:50 GMT):
so yes, we could say "we'll be super careful and make sure we merge it everywhere" but that makes it a human process and thus inviting mistakes

greg.haskins (Fri, 12 May 2017 13:52:59 GMT):
ones that are really easy to make

greg.haskins (Fri, 12 May 2017 13:53:26 GMT):
so, what I propose is:

cbf (Fri, 12 May 2017 13:53:32 GMT):
actually it could be automated

mastersingh24 (Fri, 12 May 2017 13:53:35 GMT):
Of course humans program the automation as well - and a bad automated process wreaks more havoc than a error prone manual one ;)

greg.haskins (Fri, 12 May 2017 13:53:47 GMT):
between now and 1.0 GA, just consider master frozen and a single stream

cbf (Fri, 12 May 2017 13:54:00 GMT):
you could have a bot cherry pick any merges that were not ff to master/release

greg.haskins (Fri, 12 May 2017 13:54:55 GMT):
@mastersingh24 yes, of course...but by that argument, everything is subject to that

greg.haskins (Fri, 12 May 2017 13:55:12 GMT):
the main point is: computers are good at rote tasks like monitoring something consistently

greg.haskins (Fri, 12 May 2017 13:55:26 GMT):
so I am not saying we need a fully automated merge process

cbf (Fri, 12 May 2017 13:55:29 GMT):
right, SMOP

mastersingh24 (Fri, 12 May 2017 13:55:46 GMT):
OK so - @greg.haskins : 1) between now and 1.0 GA, just consider master frozen and a single stream

greg.haskins (Fri, 12 May 2017 13:55:48 GMT):
but what would be minimal, i think, is some way to at least detect that a human needs to intervene

greg.haskins (Fri, 12 May 2017 13:56:17 GMT):
e.g. a dashboard on jenkins that goes RED when the master branch has a patch that develop doesn.t

cbf (Fri, 12 May 2017 13:56:33 GMT):
so, and let's be clear here, what I am proposing is actually not different, but it does provide a stable master branch

greg.haskins (Fri, 12 May 2017 13:56:35 GMT):
and the maintainer can make a decision to cherry-pick or "merge -sours" it out

cbf (Fri, 12 May 2017 13:57:02 GMT):
from now until 1.0, we update master exclusively via FF merges from develop

greg.haskins (Fri, 12 May 2017 13:58:01 GMT):
@cbf i see what you are saying

greg.haskins (Fri, 12 May 2017 13:58:44 GMT):
the plumbing is in place for develop->master flow but they are kept in sync since develop is just our frozen v1.0 track?

greg.haskins (Fri, 12 May 2017 13:58:48 GMT):
what does that buy us though?

greg.haskins (Fri, 12 May 2017 14:00:40 GMT):
aside from the seeming futility of turning this one now (I might just need to better understand), the other concern I have is that IIUC, most things that you would want on "stable branch" should be developed against stable branch and merged out, not the other way around

greg.haskins (Fri, 12 May 2017 14:00:40 GMT):
aside from the seeming futility of turning this on now (I might just need to better understand), the other concern I have is that IIUC, most things that you would want on "stable branch" should be developed against stable branch and merged out, not the other way around

cbf (Fri, 12 May 2017 14:00:42 GMT):
ok, @mastersingh24 reminded me we can choose the default branch on GH, so we could cut release for alpha2, change default to release and that would be less disruptive

greg.haskins (Fri, 12 May 2017 14:01:26 GMT):
trying to cherry pick something from the "everything goes" branch to the "stable branch" is suboptimal and should only be used as a last resort

greg.haskins (Fri, 12 May 2017 14:01:44 GMT):
e.g. someone fixed something in the development stream that was then later deemed critical for the release stream

cbf (Fri, 12 May 2017 14:01:46 GMT):
no, I wasn't suggesting that

JonathanLevi (Fri, 12 May 2017 14:02:20 GMT):
Let me pull up Dave's chart.

cbf (Fri, 12 May 2017 14:02:23 GMT):
that was @dhuseby feature branch idea - not sure it will work for us until we get our house in order

JonathanLevi (Fri, 12 May 2017 14:03:27 GMT):
https://i.stack.imgur.com/F00b8.png

JonathanLevi (Fri, 12 May 2017 14:03:48 GMT):
Something around this.

greg.haskins (Fri, 12 May 2017 14:03:55 GMT):
anyway, I am not against any of these ideas in general...my only argument is we dont need them _right now_

JonathanLevi (Fri, 12 May 2017 14:04:12 GMT):
The idea is that we let soem stuff "sit" in a branch, see that it works... and only the "merge up"

greg.haskins (Fri, 12 May 2017 14:04:13 GMT):
single stream development towards v1.0 is fine, IMO

greg.haskins (Fri, 12 May 2017 14:05:10 GMT):
@JonathanLevi yeah, i fully support that

JonathanLevi (Fri, 12 May 2017 14:05:10 GMT):
That's what I mean by "one way" yes.

greg.haskins (Fri, 12 May 2017 14:05:32 GMT):
this is in line with what i have been saying for a while...that "gerrit submit" should just be the front stage of the pipe

greg.haskins (Fri, 12 May 2017 14:06:01 GMT):
right now, human submits CR, other humans approve CR, its live

mastersingh24 (Fri, 12 May 2017 14:06:03 GMT):
Here's the big elephant in the room .......

JonathanLevi (Fri, 12 May 2017 14:06:09 GMT):
I'm also in favor of "auto-reverting" stuff that's not working.

mastersingh24 (Fri, 12 May 2017 14:06:14 GMT):
and maybe with stable ABI we are ok .....

mastersingh24 (Fri, 12 May 2017 14:06:20 GMT):
Go SUCKS with versioning

greg.haskins (Fri, 12 May 2017 14:06:31 GMT):
with that model, the "humans approve" part should just be the first gate...

JonathanLevi (Fri, 12 May 2017 14:06:38 GMT):
I used to believe it just sux.

JonathanLevi (Fri, 12 May 2017 14:06:39 GMT):
;-)

cbf (Fri, 12 May 2017 14:06:49 GMT):
@JonathanLevi we cannot do that (auto-revert) until the tests don't yield false positives like every other build

mastersingh24 (Fri, 12 May 2017 14:06:54 GMT):
If we can make it such that for 95% of the folks who use alpha2 they NEVER need to clone, go install, etc, then we are good with a single branch

mastersingh24 (Fri, 12 May 2017 14:07:40 GMT):
So the delivering the binaries of the tools will likely help and as long as we don't break chaincode then we should be ok

mastersingh24 (Fri, 12 May 2017 14:08:18 GMT):
@greg.haskins - ^^^^^

JonathanLevi (Fri, 12 May 2017 14:08:52 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-release?msg=ZD38fR8kQYPqynFxz) True, but this is something that we should aspire to achieve.

JonathanLevi (Fri, 12 May 2017 14:09:36 GMT):
At the moment, we don't even trust the `passing` tests ;-)

JonathanLevi (Fri, 12 May 2017 14:09:46 GMT):
(because of coverage, etc. etc.)

cbf (Fri, 12 May 2017 14:09:50 GMT):
ok, for alpha2 there is no urgency to cut a branch, but I still maintain that a stable branch as default on GH is a Good Thing(tm) and will make our lives easier when people file bugs when they built themselves from a git clone

JonathanLevi (Fri, 12 May 2017 14:09:59 GMT):
But let's get back to @mastersingh24's thread.

JonathanLevi (Fri, 12 May 2017 14:11:32 GMT):
Just to qualify a bit what I said above (for getting the attention) - I like to KISS, and not wait or create a dependency on CI jobs, re-branching and changing the workflow "today".

JonathanLevi (Fri, 12 May 2017 14:11:44 GMT):
(so in that sense, I agree with Greg)

cbf (Fri, 12 May 2017 14:11:55 GMT):
ok, I can live with this for TODAY

JonathanLevi (Fri, 12 May 2017 14:12:00 GMT):
I would love to get a tag today. Yup.

JonathanLevi (Fri, 12 May 2017 14:12:00 GMT):
I would love to get a tag *today*. Yup.

JonathanLevi (Fri, 12 May 2017 14:12:25 GMT):
I suspect that the CI job(s), servers, redirecting CRs... will take a few days.

JonathanLevi (Fri, 12 May 2017 14:13:46 GMT):
But at the same time, we do need "release" branches, in my opinion. I'd just rather have that work begin "off the main track" at this point.

dave.enyeart (Fri, 12 May 2017 14:13:53 GMT):
Absent from this discussion is 'feature toggles', I thought the industry was moving in that direction to support continuous release with release trains of targeted features. So one master with everything, and no merge hell. Easier said than done, but worth some thought. For example there is some 1.1 Side DB work starting, and we could easily merge the component pieces and unit tests into master without exposing any of it to live 1.0 code paths. Again, easier said than done but worth some thought at least on a feature by feature basis.

cbf (Fri, 12 May 2017 14:14:16 GMT):
FAB-3737 generate changelog for v1.0.0-alpha2 IN REVIEW FAB-3218 Sync Java/Golang ChaincodeStub interface IN REVIEW FAB-3850 don't allow Java CC access for alpha2 as its not quite usable yet. IN REVIEW

cbf (Fri, 12 May 2017 14:14:33 GMT):
the three FABs above are the last of the blockers for alpha2

cbf (Fri, 12 May 2017 14:14:41 GMT):
all ready (I believe) to be merged

cbf (Fri, 12 May 2017 14:14:50 GMT):
@here do we agree to merge these?

greg.haskins (Fri, 12 May 2017 14:16:29 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-release?msg=NNf6bu2nzXzBynuGX) @dave.enyeart Thats the direction I would like to go in as well.. But to your point, "easier said than done" and we are even further from that than managing the branches properly.

dave.enyeart (Fri, 12 May 2017 14:16:50 GMT):
ok, just wanted to ensure it was on the radar

yacovm (Fri, 12 May 2017 14:18:25 GMT):
It's impossible to have toggle-ed features in some subcomponents @dave.enyeart

dave.enyeart (Fri, 12 May 2017 14:18:56 GMT):
yeah, that's why i suggest feature by feature basis where feasible, to minimize the merge hell

muralisr (Fri, 12 May 2017 14:19:28 GMT):
@cbf +1 to merging FAB-3737, FAB-3218, FAB-3850

muralisr (Fri, 12 May 2017 14:20:11 GMT):
(apologize for jumping in the discussion!)

cbf (Fri, 12 May 2017 14:20:30 GMT):
@muralisr no apology needed

JonathanLevi (Fri, 12 May 2017 14:20:30 GMT):
To save some time, same list, with links: https://jira.hyperledger.org/browse/FAB-3737 generate changelog for v1.0.0-alpha2 https://gerrit.hyperledger.org/r/#/c/9167/ https://jira.hyperledger.org/browse/FAB-3218 Sync Java/Golang ChaincodeStub interface https://gerrit.hyperledger.org/r/#/c/8529/ https://jira.hyperledger.org/browse/FAB-3850 don't allow Java CC access for alpha2 as its not quite usable yet. https://gerrit.hyperledger.org/r/#/c/9245

cbf (Fri, 12 May 2017 14:21:17 GMT):
I'd like @greg.haskins to look at https://gerrit.hyperledger.org/r/#/c/9167/

cbf (Fri, 12 May 2017 14:24:09 GMT):
and we need to get that merged so that we have a link to add to the commit message to create the release

cbf (Fri, 12 May 2017 14:25:00 GMT):
otherwise there won't be release notes (or a sort) - I at least want to have the changelog linked from the releases page

binhn (Fri, 12 May 2017 14:27:05 GMT):
@muralisr effectively fab-3850 negates fab-3218, so why should we merge fab-3218?

cbf (Fri, 12 May 2017 14:28:58 GMT):
@binhn I think we need 3850 regardless, to your point

muralisr (Fri, 12 May 2017 14:29:09 GMT):
@binhn with https://gerrit.hyperledger.org/r/#/c/8529/, what we are really merging is FAB-3235 ... it is the last item for fab-3218

cbf (Fri, 12 May 2017 14:29:23 GMT):
I don't think it makes a difference if we do or don't merge Luis's CR

muralisr (Fri, 12 May 2017 14:29:58 GMT):
not to users or code path, true

muralisr (Fri, 12 May 2017 14:30:36 GMT):
its just that FAB-3218 is an umbrella for many checkins all of which have been merged

binhn (Fri, 12 May 2017 14:30:39 GMT):
yeah, 8529 is all java, so would not make any difference

muralisr (Fri, 12 May 2017 14:30:43 GMT):
except FAB-3235

muralisr (Fri, 12 May 2017 14:31:30 GMT):
why leave out a low-impact straggler that'll effectively close the umbrella FAB

binhn (Fri, 12 May 2017 14:31:59 GMT):
ok, i agreed to merge those

cbf (Fri, 12 May 2017 14:32:33 GMT):
anyone else want to weigh in? I think we can merge all three

cbf (Fri, 12 May 2017 14:32:43 GMT):
s/can/should/

JonathanLevi (Fri, 12 May 2017 14:34:57 GMT):
Let's wait for @greg.haskins to look at https://gerrit.hyperledger.org/r/#/c/9167 then?

cbf (Fri, 12 May 2017 14:35:16 GMT):
ok, pushing the button on JavaCC ones

JonathanLevi (Fri, 12 May 2017 14:35:27 GMT):
Yes. I feel like we should merge.

greg.haskins (Fri, 12 May 2017 14:35:50 GMT):
patch looks fine...only question is: when/how is it run?

greg.haskins (Fri, 12 May 2017 14:36:13 GMT):
i guess it should be run by whomever makes the IS_RELEASE=true CR?

cbf (Fri, 12 May 2017 14:38:58 GMT):
@greg.haskins right now, it would be as you suggest, and the updated CHANGELOG.md would be part of that commit and the commit message would (in addition to whatever else) include a link to the changelog

greg.haskins (Fri, 12 May 2017 14:39:27 GMT):
ok, sounds good

greg.haskins (Fri, 12 May 2017 14:39:48 GMT):
i just +2'd it

cbf (Fri, 12 May 2017 14:40:14 GMT):
thx

cbf (Fri, 12 May 2017 14:40:17 GMT):
need 1 more

JonathanLevi (Fri, 12 May 2017 14:40:46 GMT):
Hallelujah ?

JonathanLevi (Fri, 12 May 2017 14:40:46 GMT):
I have just merged the 3rd one. Hallelujah ?

JonathanLevi (Fri, 12 May 2017 14:40:52 GMT):
(part 1)

cbf (Fri, 12 May 2017 14:41:01 GMT):
then I think one of us can create the tag and we can start the process of producing a published alpha2 release

cbf (Fri, 12 May 2017 14:46:24 GMT):
ok @greg.haskins you want to do the honors and tag and create the IS_RELEASE CR?

greg.haskins (Fri, 12 May 2017 14:46:51 GMT):
sure thing

cbf (Fri, 12 May 2017 14:46:54 GMT):
thx

JonathanLevi (Fri, 12 May 2017 14:49:01 GMT):
Thank you Greg.

bkvellanki (Fri, 12 May 2017 15:13:40 GMT):
Guys..I checked out the code today and using mac..I think the e2e_cli is broken Pulling orderer.example.com (hyperledger/fabric-orderer:latest)... ERROR: manifest for hyperledger/fabric-orderer:latest not found ERROR !!!! Unable to pull the images Pulling cli (hyperledger/fabric-testenv:latest)... ERROR: repository hyperledger/fabric-testenv not found: does not exist or no pull access ERROR !!!! Unable to pull the images I think couple of images are missing..I tried download docker images and it installed the orderer latest..but the fabric-testenv is not available.. Any suggestions about the what is the stable and working release we should use that includes e2e clu

cbf (Fri, 12 May 2017 15:20:37 GMT):
@bkvellanki did you build? run make dist-clean native docker first

cbf (Fri, 12 May 2017 15:21:21 GMT):
we have not published the images yet, v1.0.0-alpha2 images should be available later today

bkvellanki (Fri, 12 May 2017 15:29:13 GMT):
@cbf THanks for a alpha2..Trying Dist clean and running again

cbf (Fri, 12 May 2017 15:36:39 GMT):
@greg.haskins I realized that we need changelog for fabric-ca and fabric-sdk-node too

cbf (Fri, 12 May 2017 15:36:54 GMT):
just submitted fabric-ca https://gerrit.hyperledger.org/r/#/c/9291/

greg.haskins (Fri, 12 May 2017 16:50:57 GMT):
https://gerrit.hyperledger.org/r/#/c/9303/

greg.haskins (Fri, 12 May 2017 17:04:55 GMT):
https://gerrit.hyperledger.org/r/#/c/9307/

greg.haskins (Fri, 12 May 2017 17:05:55 GMT):
(to any reviewer/submitter: recall that both the Release/Prepare CRs should be committed together

joe-alewine (Fri, 12 May 2017 17:33:54 GMT):
Has joined the channel.

rameshthoomu (Fri, 12 May 2017 18:02:58 GMT):
@greg.haskins do you want me to include `testenv` image in docker push from CI? I see testenv reference in few docker-compose files ex: https://github.com/hyperledger/fabric/blob/master/examples/e2e_cli/docker-compose-cli.yaml#L37

binhn (Fri, 12 May 2017 20:56:17 GMT):
@cbf do we need ci to run on https://gerrit.hyperledger.org/r/#/c/9291/ ? it looks like ci on fabric-ca is down or something @rameshthoomu ?

cbf (Fri, 12 May 2017 20:57:11 GMT):
I have been out, I thought there seemed to be a lull

cbf (Fri, 12 May 2017 20:58:14 GMT):
yes, we should run for the merges

rameshthoomu (Fri, 12 May 2017 20:59:02 GMT):
@binhn we had jenkins outage an hour back for few mins..

rameshthoomu (Fri, 12 May 2017 20:59:16 GMT):
that could be the reason..

binhn (Fri, 12 May 2017 20:59:33 GMT):
@rameshthoomu ok, thanks

rameshthoomu (Fri, 12 May 2017 21:01:35 GMT):
Shall trigger on verify job?

jimthematrix (Fri, 12 May 2017 21:33:27 GMT):
hi Ramesh, what's the expected tag for the alpha2 docker images?

jimthematrix (Fri, 12 May 2017 21:33:27 GMT):
hi @rameshthoomu , what's the expected tag for the alpha2 docker images?

jimthematrix (Fri, 12 May 2017 21:34:26 GMT):
want to update the docker-compose.yaml in the release-triggering CR so it'll correspond to the alpha2 versions

jimthematrix (Fri, 12 May 2017 21:35:32 GMT):
`x86_64-1.0.0-alpha2` sounds about right?

rameshthoomu (Fri, 12 May 2017 21:35:35 GMT):
@jimthematrix it's going to be this.. https://gerrit.hyperledger.org/r/#/c/9303/1/Makefile

jimthematrix (Fri, 12 May 2017 21:36:22 GMT):
hmm, guess that'll create a problem with the CI job

jimthematrix (Fri, 12 May 2017 21:36:22 GMT):
hmm, guess that'll create a problem with the CI job for s390

rameshthoomu (Fri, 12 May 2017 21:36:40 GMT):
ARCH is based on the system you are running..

rameshthoomu (Fri, 12 May 2017 21:37:10 GMT):
once images are published.. the tag for x86_64 should `x86_64-1.0.0-alpha2`

jimthematrix (Fri, 12 May 2017 21:37:42 GMT):
understood, i just realized we can't realize tag it in the docker-compose.yaml used by node SDK end2end

jimthematrix (Fri, 12 May 2017 21:38:06 GMT):
because it'll be used by both x86 and s390 builds

jimthematrix (Fri, 12 May 2017 21:38:21 GMT):
ok never mind

jimthematrix (Fri, 12 May 2017 21:40:49 GMT):
http://gerrit.hyperledger.org/r/9331 - releasing alpha2 for node SDK

jimthematrix (Fri, 12 May 2017 21:43:09 GMT):
http://gerrit.hyperledger.org/r/9333 - preparing for alpha3

rickr (Fri, 12 May 2017 21:45:30 GMT):
Has joined the channel.

rickr (Fri, 12 May 2017 23:36:55 GMT):
What's the actual tag being used in gerrit/git v1.0.0-alpha2 ?

greg.haskins (Sat, 13 May 2017 01:38:45 GMT):
@rickr it will be...note that we cant push a tag until the release CRs are merged

greg.haskins (Sat, 13 May 2017 01:38:50 GMT):
last I checked, they werent

greg.haskins (Sat, 13 May 2017 01:38:53 GMT):
will look again

binhn (Sat, 13 May 2017 03:07:42 GMT):
could someone bless this one -- the only one holding my the release CRs https://gerrit.hyperledger.org/r/#/c/9291/

binhn (Sat, 13 May 2017 03:07:42 GMT):
could someone bless this one https://gerrit.hyperledger.org/r/#/c/9291/ -- the only one holding the release CRs

jimthematrix (Sat, 13 May 2017 03:14:21 GMT):
just merged it

jimthematrix (Sat, 13 May 2017 03:15:17 GMT):
saw @JonathanLevi comment on one mal-formated entry, it think given this being the first go-around, it's forgivable (was tempted to patch it)

jimthematrix (Sat, 13 May 2017 03:15:17 GMT):
saw @JonathanLevi comment on one mal-formated entry, I think given this being the first go-around, it's forgivable (was tempted to patch it)

jimthematrix (Sat, 13 May 2017 03:15:44 GMT):
@binhn ^^^

binhn (Sat, 13 May 2017 20:21:26 GMT):
@JonathanLevi @cbf @mastersingh24 release CRs are ready https://gerrit.hyperledger.org/r/#/c/9303, https://gerrit.hyperledger.org/r/#/c/9307

JonathanLevi (Sat, 13 May 2017 21:12:46 GMT):
I have merged them both. Off we go!

jimthematrix (Sun, 14 May 2017 02:57:49 GMT):
@JonathanLevi @binhn @greg.haskins @cbf @mastersingh24 can't declare alpha2 without the SDKs, don't think for a second the fabric is usable without the SDKs ;-) https://gerrit.hyperledger.org/r/#/c/9331/ https://gerrit.hyperledger.org/r/#/c/9335/

rickr (Sun, 14 May 2017 11:26:58 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-release?msg=jaJMX7gu79qQPKcJw) Where are we going ? I just looked on docker hub *Last pushed: 2 months ago*

rickr (Sun, 14 May 2017 11:26:58 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-release?msg=jaJMX7gu79qQPKcJw) Where are we going ? I just looked on docker hub *Last pushed: 2 months ago* https://hub.docker.com/r/hyperledger/fabric-peer/

rickr (Sun, 14 May 2017 12:27:42 GMT):
I'm trying to bring up my docker-compose with tags *:x86_64-1.0.0-alpha2* ``` ERROR: manifest for hyperledger/fabric-orderer:x86_64-1.0.0-alpha2 not found ``` docker-compose snippet: ``` orderer.example.com: container_name: orderer.example.com image: hyperledger/fabric-orderer:x86_64-1.0.0-alpha2 environment: ```

rameshthoomu (Sun, 14 May 2017 14:37:13 GMT):
@JonathanLevi @binhn @cbf @greg.haskins @mastersingh24 Don't merge any changes before we release alpha2 docker images.. Below are the changes we have to make to do this 1) Create a new tag for alpha2 or 2) keep both fabric and fabric-ca repos back to alpha2.. I mean revert this change https://github.com/hyperledger/fabric/commit/2470d3505cb736b267d4a1b2404e3b90975397db 3) once fabric and fabric-ca repos are ready with alpha2 commit changes and IS_RELEASE=true then will trigger release jobs manually by removing Gerrit ref spec from CI job.

rameshthoomu (Sun, 14 May 2017 14:37:13 GMT):
@JonathanLevi @binhn @cbf @greg.haskins @mastersingh24 Don't merge any changes before we release alpha2 docker images.. Below are the changes required to release 1) Create a new tag for alpha2 or 2) keep both fabric and fabric-ca repos back to alpha2.. I mean revert this change https://github.com/hyperledger/fabric/commit/2470d3505cb736b267d4a1b2404e3b90975397db 3) once fabric and fabric-ca repos are ready with alpha2 commit changes and IS_RELEASE=true then will trigger release jobs manually by removing Gerrit ref spec from CI job.

rameshthoomu (Sun, 14 May 2017 14:40:00 GMT):
existing release jobs are expecting tags

greg.haskins (Sun, 14 May 2017 14:40:19 GMT):
@rameshthoomu the release was already cut and merged. I just need to push the tag which should trigger the docker push

greg.haskins (Sun, 14 May 2017 14:40:30 GMT):
Not sure what you are referring to

rameshthoomu (Sun, 14 May 2017 14:40:42 GMT):
wow..

greg.haskins (Sun, 14 May 2017 14:40:47 GMT):
Are you saying we need to abandon the tag?

rameshthoomu (Sun, 14 May 2017 14:41:02 GMT):
no..

rameshthoomu (Sun, 14 May 2017 14:41:11 GMT):
you will create tags for this release right..

greg.haskins (Sun, 14 May 2017 14:41:16 GMT):
Yes

rameshthoomu (Sun, 14 May 2017 14:41:29 GMT):
perfect.

rameshthoomu (Sun, 14 May 2017 14:41:40 GMT):
ignore my previous comments..

greg.haskins (Sun, 14 May 2017 14:42:02 GMT):
The tagging is still a manual process and the CRs weren't accepted before I logged out for the weekend

greg.haskins (Sun, 14 May 2017 14:42:23 GMT):
But they are now I believe. I'll push tag later today

rameshthoomu (Sun, 14 May 2017 14:43:14 GMT):
Awesome.. Ty

rameshthoomu (Sun, 14 May 2017 14:43:42 GMT):
also you will create tag based on this commit https://github.com/hyperledger/fabric/commit/6b6bfcfbd1e798a8a08fa9c3bf4dc0ff766a6b87 correct ? not on latest commit...

greg.haskins (Sun, 14 May 2017 14:47:33 GMT):
Yes, tag is always applied to the commit that says "release"

greg.haskins (Sun, 14 May 2017 14:48:29 GMT):
Applying it to HEAD would generally be wrong on a few different levels

rameshthoomu (Sun, 14 May 2017 14:49:27 GMT):
yes.. Thanks @greg.haskins

cbf (Sun, 14 May 2017 14:52:44 GMT):
we need to document the process, please

rameshthoomu (Sun, 14 May 2017 15:00:11 GMT):
sure

JonathanLevi (Sun, 14 May 2017 18:44:21 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-release?msg=jXRC4e9GKE6Tu3hSY)

JonathanLevi (Sun, 14 May 2017 18:44:30 GMT):
Just to be clear, we are still in *CODE FREEZE*. No merging of anything other than stuff that is in agreement (in writing), until we have the release published and we declare otherwise.

greg.haskins (Mon, 15 May 2017 01:37:03 GMT):
https://github.com/hyperledger/fabric/releases/tag/v1.0.0-alpha2

greg.haskins (Mon, 15 May 2017 01:41:42 GMT):
https://github.com/hyperledger/fabric-ca/releases/tag/v1.0.0-alpha2

greg.haskins (Mon, 15 May 2017 01:45:07 GMT):
@rjones @rameshthoomu FYI, it does _not_ look like jenkins kicked off the -release job in response to the tag

smallX (Mon, 15 May 2017 02:03:21 GMT):
Has joined the channel.

rameshthoomu (Mon, 15 May 2017 02:35:24 GMT):
Will check

jimthematrix (Mon, 15 May 2017 02:41:07 GMT):
the node SDK release process and CI job design is documented here: https://jira.hyperledger.org/browse/FAB-2802 @cbf @greg.haskins

jongeun.park (Mon, 15 May 2017 03:24:46 GMT):
Has joined the channel.

rameshthoomu (Mon, 15 May 2017 03:41:25 GMT):
@greg.haskins checked job configuration and nothing has been changed.. Will check why `ref-updated-event` event is not triggered

rameshthoomu (Mon, 15 May 2017 03:42:22 GMT):
triggered all release jobs (fabric and fabric-ca)... 1.0.0-alpha2 images are now available in dockerhub...

rjones (Mon, 15 May 2017 03:42:50 GMT):
@rameshthoomu I'm bouncing Jenkins to see if the gerrit trigger is still alive

rameshthoomu (Mon, 15 May 2017 03:43:18 GMT):
ok

rameshthoomu (Mon, 15 May 2017 03:44:10 GMT):
about to ping you regarding the current jenkins status..

rjones (Mon, 15 May 2017 03:45:16 GMT):
it's back up, I manually did a query and fired off some builds

rjones (Mon, 15 May 2017 03:45:40 GMT):
and they're working. I have no idea why the previously working tag driven builds aren't working now

rameshthoomu (Mon, 15 May 2017 03:47:54 GMT):
yes that's strange.. I have checked job configuration and nothing is changed..

rameshthoomu (Mon, 15 May 2017 03:49:00 GMT):
I am executing node-sdk (e2e) tests by pulling newly published images..

rjones (Mon, 15 May 2017 03:49:11 GMT):
the regex for tags changed last week

rjones (Mon, 15 May 2017 03:49:27 GMT):
let's discuss in ci-pipeline perhaps

rameshthoomu (Mon, 15 May 2017 03:49:34 GMT):
sure

LordGoodman (Mon, 15 May 2017 07:01:15 GMT):
Has joined the channel.

reoim10 (Mon, 15 May 2017 11:28:30 GMT):
Has joined the channel.

hanhzf (Mon, 15 May 2017 12:01:41 GMT):
Has joined the channel.

greg.haskins (Mon, 15 May 2017 12:37:15 GMT):

Message Attachments

greg.haskins (Mon, 15 May 2017 13:09:51 GMT):

Message Attachments

jtclark (Mon, 15 May 2017 13:57:35 GMT):
Has joined the channel.

weeds (Mon, 15 May 2017 14:27:26 GMT):
Just a heads up- i had a couple of people in community contact me this am- i guess there is confusion on where we are in Alpha 2. not sure what to do about it- but did feel I should mention it.

clasoncjDA (Mon, 15 May 2017 14:48:48 GMT):
Has joined the channel.

CarlitoIBM (Mon, 15 May 2017 14:49:06 GMT):
Has joined the channel.

weeds (Mon, 15 May 2017 14:50:01 GMT):
They were confused as to where things were published,etc,.. and whether we really published or not.

JonathanLevi (Mon, 15 May 2017 14:50:55 GMT):
We will send out an email with details. The ink has not dried yet (it's a few hours old tag)

JonathanLevi (Mon, 15 May 2017 14:51:54 GMT):
BTW: https://github.com/hyperledger/fabric/releases

weeds (Mon, 15 May 2017 14:56:43 GMT):
@JonathanLevi ++ Jonathan. Wanted awareness that the fabric-release channel might have gotten lost by some people in community-it's a good reminder to use the Hyperledger email as a result.

weeds (Mon, 15 May 2017 14:57:09 GMT):
(and Jira)

JonathanLevi (Mon, 15 May 2017 16:14:30 GMT):
@weeds, we are on it.

JonathanLevi (Mon, 15 May 2017 16:14:30 GMT):
@weeds, we are all [still] on it.

JonathanLevi (Mon, 15 May 2017 16:14:30 GMT):
@weeds, we are all [still] on it. -----

JonathanLevi (Mon, 15 May 2017 16:14:54 GMT):
BTW: Another pair of eyes on the release notes? https://gerrit.hyperledger.org/r/#/c/9367

jimthematrix (Mon, 15 May 2017 16:38:57 GMT):
@cbf @JonathanLevi I gave -1 on the point of "feature complete" and suggested an update to the release note content

JonathanLevi (Mon, 15 May 2017 16:40:32 GMT):
Yes, noted. Thank you Jim. Do we have a list of all the "tooling" we would like to add, as part of the 1.0 release?

JonathanLevi (Mon, 15 May 2017 16:40:48 GMT):
Shall we add them here, as JIRA tickets? https://jira.hyperledger.org/browse/FAB-3040

JonathanLevi (Mon, 15 May 2017 16:41:18 GMT):
I see a lot of "error handling" planned.

JonathanLevi (Mon, 15 May 2017 16:41:18 GMT):
I see a lot of "error handling" (service-ability) planned.

JonathanLevi (Mon, 15 May 2017 16:41:58 GMT):
I see a lot of "error handling" (service-ability) planned.

JonathanLevi (Mon, 15 May 2017 16:42:43 GMT):
At least that's the approved/agreed-upon part that is planned for v1.0.0 (and not 1.0.0-alpha2)

jimthematrix (Mon, 15 May 2017 16:44:27 GMT):
https://jira.hyperledger.org/browse/FAB-1678 is the main thing (and the only tooling still under way as far as I'm aware)

jimthematrix (Mon, 15 May 2017 16:44:40 GMT):
(this was included in the comment to 9367)

weeds (Mon, 15 May 2017 16:50:50 GMT):
@JonathanLevi did take a look at 9367 thanks Jonathan... one thing that we did a while back for alpha release is we had the following link in Hyperledger: https://wiki.hyperledger.org/projects/fabric/proposedv1alphacontent . Do you think we need to produce something similar or update it to reflect Alpha2?

weeds (Mon, 15 May 2017 16:54:12 GMT):
so much of this should really be in the documentation itself- so I'm not quite sure if needed or not, which is why I was asking for an opinion.

JonathanLevi (Mon, 15 May 2017 16:59:23 GMT):
Hi again @weeds. We have these in the plan. https://gerrit.hyperledger.org/r/#/c/9303/ which I have merged over the weekend https://gerrit.hyperledger.org/r/#/c/9307/ which I have merged over the weekend

JonathanLevi (Mon, 15 May 2017 16:59:26 GMT):
https://jira.hyperledger.org/browse/FAB-3075 by @markparz (marked In Progress)

JonathanLevi (Mon, 15 May 2017 16:59:48 GMT):
(with a request, inline, to get a reference to the automated diffs)

JonathanLevi (Mon, 15 May 2017 16:59:48 GMT):
(with a request, inline, to get a reference to the automated diffs, that were merged)

JonathanLevi (Mon, 15 May 2017 17:00:28 GMT):
(with a request, inline, to get a reference to the automated diffs, that were merged)

JonathanLevi (Mon, 15 May 2017 17:00:39 GMT):
@weeds ^^^

JonathanLevi (Mon, 15 May 2017 17:02:07 GMT):
If we feel like we should add another JIRA ticket and add it to the plan (as that `alphacontent` is really well formatted/laid out)... then I'm down. Sure, let's do it... At the same time, we may probably just need to update a paragraph or two, and under 3075. What do you think?

JonathanLevi (Mon, 15 May 2017 17:02:32 GMT):
It may probably a paragraph or two added under 3075...

cbf (Mon, 15 May 2017 17:43:30 GMT):
@jimthematrix I assume that by not being feature complete you are referring to SDKs?

cbf (Mon, 15 May 2017 17:46:15 GMT):
or just the lack of effective tooling

cbf (Mon, 15 May 2017 17:46:44 GMT):
because I will say that at some point, you have to fish or cut bait, and we agreed that we are at code freeze

cbf (Mon, 15 May 2017 17:47:12 GMT):
there might be new tools developed and published but we need to focus on just the hardening

mastersingh24 (Mon, 15 May 2017 17:54:13 GMT):
@jimthematrix @cbf @JonathanLevi - 1) From a runtime perspective - peer, orderer, fabric-ca - we are feature complete. We may have to fix/harden some things, but there's no new features / API/ABI changes 2) I think we are OK with some hardening of the SDKs now that the runtimes are finally complete 3) We do need tooling to support configuring the ordering service (specifically for updating channels, etc). This will not involve any changes to the the runtimes / ABI and will be a separate / standalone tool. I believe this is what @jimthematrix is referring to above and I don't think anyone has an issue with finishing the work on this tool?

JonathanLevi (Mon, 15 May 2017 17:54:49 GMT):
Please let's open JIRA tickets for these?

JonathanLevi (Mon, 15 May 2017 17:55:06 GMT):
I want to formalize and have the description/scope....

cbf (Mon, 15 May 2017 17:55:08 GMT):
right but this is about making the statement in release notes that we are feature complete - I think it is an important statement to make and that it should be made

cbf (Mon, 15 May 2017 17:55:29 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-release?msg=ZdvbL7WuzWvnWEdLh) @JonathanLevi +2

JonathanLevi (Mon, 15 May 2017 17:56:06 GMT):
I agree. It's a big thing to be feature complete + we want to evaluate our beta-readiness pretty soon too (so locking API/ABI is indeed key).

cbf (Mon, 15 May 2017 17:59:22 GMT):
@JonathanLevi apparently there is a JIRA that was just added to FAB-3040

cbf (Mon, 15 May 2017 17:59:55 GMT):
@jimthematrix @mastersingh24 we really need to discuss and agree on changes like this

cbf (Mon, 15 May 2017 18:00:35 GMT):
this is one case where that discussion may have happened, but I never saw it nor had any say, and AFAIK, neither did @JonathanLevi

JonathanLevi (Mon, 15 May 2017 18:02:19 GMT):
Yes, sorry, I wasn't aware. OK, looking.

cbf (Mon, 15 May 2017 18:03:38 GMT):
as release managers, you'd think that that would have been expected

JonathanLevi (Mon, 15 May 2017 18:04:04 GMT):
I should probably also send a proper email about that bit too ;-)

cbf (Mon, 15 May 2017 18:04:09 GMT):
yes

mastersingh24 (Mon, 15 May 2017 18:06:36 GMT):
I did not update FAB-3040 - I am simply stating the fact that FAB-1678 is needed for most of the channel functionality to be useful and that work is underway on it.

cbf (Mon, 15 May 2017 18:08:48 GMT):
@mastersingh24 sorry if I made it seem as if you did, was just intending to draw your attention

cbf (Mon, 15 May 2017 18:09:24 GMT):
@rameshthoomu I thought that we had a process for publishing native binaries for configtxgen and cryptogen

cbf (Mon, 15 May 2017 18:09:24 GMT):
@rameshthoomu I thought that we had a process for publishing native binaries for configtxgen and cryptogen to nexus

cbf (Mon, 15 May 2017 18:09:46 GMT):
we need to do that and provide a link to Nick for his update

rameshthoomu (Mon, 15 May 2017 18:11:01 GMT):
yes we have a CI job in sandbox to do that.. This patch has to merge to publish from production CI https://gerrit.hyperledger.org/r/#/c/8939/

rameshthoomu (Mon, 15 May 2017 18:11:42 GMT):
Working on this... Will publish one from sandbox for now..

jimthematrix (Mon, 15 May 2017 18:42:02 GMT):
@cbf I added FAB-1678 to the list in FAB-3040 in response to @JonathanLevi 's suggestion, but maybe I was over-zealous... https://chat.hyperledger.org/channel/fabric-release?msg=osha7LKpRCpfdirR9

cbf (Mon, 15 May 2017 18:42:38 GMT):
@rameshthoomu thanks!

cbf (Mon, 15 May 2017 18:42:47 GMT):
LMK when they are published

cbf (Mon, 15 May 2017 18:43:19 GMT):
@jimthematrix no worries, let's just formalize a process going forward

cbf (Mon, 15 May 2017 18:43:52 GMT):
this is one of the things that post 1.0 we want to firm up, but we can certainly start applying now to the 1.0 epic

weeds (Mon, 15 May 2017 19:13:29 GMT):
@JonathanLevi with respect to your earlier comment for alpha 2. I did see content listed in 9303, 9307, and now 3075. I had not seen FAB-3075 until later this AM, and I think it fits what i thought had been reflected in proposedv1alphacontent. I wanted to make sure we had something that told people what you could and could not do with the alpha2 cut. I will track that JIRA - THANKS!

JonathanLevi (Mon, 15 May 2017 19:14:49 GMT):
NP. BTW: At this point, I'm mainly trying to collect and gather all the stuff that we know that is needed for 1.0, and wanting to make sure that really are "feature complete"...

JonathanLevi (Mon, 15 May 2017 19:15:15 GMT):
Tests, documentations, getting started/user guides and examples - are always welcome.

JonathanLevi (Mon, 15 May 2017 19:15:15 GMT):
Tests, documentation, getting started/user guides and examples - are always welcome.

czar0 (Mon, 15 May 2017 20:09:27 GMT):
Has joined the channel.

Jay (Tue, 16 May 2017 01:40:57 GMT):
Has joined the channel.

dave.enyeart (Tue, 16 May 2017 11:51:46 GMT):
I’ve just tested end-to-end (Getting Started) on alpha2 and it was not a good experience. There were several blocking problems with the end-to-end instructions and docker-compose that need to be fixed for alpha2. Luckily @nickgaski and @AdnanC already had work in progress in gerrit, and with a couple small tweaks to them I was able to get things going. These both need to be reviewed/merged as soon as possible: https://jira.hyperledger.org/browse/FAB-3947 https://gerrit.hyperledger.org/r/#/c/8981/ e2e_cli (Getting Started) instructions do not work https://jira.hyperledger.org/browse/FAB-3733 https://gerrit.hyperledger.org/r/#/c/9107/ Getting Started (e2e): Does not work with CouchDB After the docs are merged in FAB-3947, they will be used as the basis for Getting Started in FAB-3925.

AdnanC (Tue, 16 May 2017 11:51:46 GMT):
Has joined the channel.

JonathanLevi (Tue, 16 May 2017 12:03:58 GMT):
@dave.enyeart, what about ? https://jira.hyperledger.org/browse/FAB-3201 (https://gerrit.hyperledger.org/r/#/c/8887)

JonathanLevi (Tue, 16 May 2017 12:04:47 GMT):
Is there an overlap/contradiction? Shall we consider all three?

JonathanLevi (Tue, 16 May 2017 12:04:48 GMT):
Thank you.

dave.enyeart (Tue, 16 May 2017 12:05:08 GMT):
no overlaps. Agreed that we should consider all.

JonathanLevi (Tue, 16 May 2017 12:05:26 GMT):
Noted, thanks.

dave.enyeart (Tue, 16 May 2017 13:20:13 GMT):
Thanks for merging these two quickly!

weeds (Tue, 16 May 2017 13:51:06 GMT):
@rameshthoomu Ramesh based on these new merges- we will have to repost the new images on dockerhub when you guys are ready

rameshthoomu (Tue, 16 May 2017 13:53:40 GMT):
@weeds I don't think we have to publish docker images..

rameshthoomu (Tue, 16 May 2017 13:54:03 GMT):
I was mentioning about alpha2 fabric binaries to nexus

weeds (Tue, 16 May 2017 13:56:59 GMT):
@rameshthoomu I think it's the docker compose piece that had an update.. how does that get published?

bkvellanki (Tue, 16 May 2017 14:06:36 GMT):
@here can we use alpha2 now?

bkvellanki (Tue, 16 May 2017 14:08:50 GMT):
@here is it better to stick with alpha.1 . We are doing a prototype and was wondering if alpha 2 has any major issues respect to fabric peer, orderer ..Not worried about e2e tests

JonathanLevi (Tue, 16 May 2017 14:10:39 GMT):
I'd recommend *alpha2* (which was cut yesterday)

mastersingh24 (Tue, 16 May 2017 14:10:40 GMT):
@bkvellanki - alpha2 is the way to go

JonathanLevi (Tue, 16 May 2017 14:11:15 GMT):
But it is the way forward (indeed), as it also has a lot of bug fixes, most likely the final API, etc.

JonathanLevi (Tue, 16 May 2017 14:11:23 GMT):
I agree with @mastersingh24.

JonathanLevi (Tue, 16 May 2017 14:11:23 GMT):
I agree with @mastersingh24

bkvellanki (Tue, 16 May 2017 14:17:25 GMT):
@mastersingh24 @JonathanLevi thanks

weeds (Tue, 16 May 2017 14:22:19 GMT):
@nickgaski is all the getting started up to date now? please advz. if not what still has to be merged?

nickgaski (Tue, 16 May 2017 14:25:31 GMT):
we need one final CR to incorporate the new tarball hosted on nexus. This will essentially be the e2e_cli folder. And then I will use the end-to-end.rst file with an updated curl command to retrieve the artifacts. Waiting on ramesh's CR

weeds (Tue, 16 May 2017 14:26:17 GMT):
What is the CR number?

rameshthoomu (Tue, 16 May 2017 14:27:14 GMT):
@weeds https://gerrit.hyperledger.org/r/#/c/8939/

rameshthoomu (Tue, 16 May 2017 14:27:54 GMT):
I am updating one final change. will complete in 10 mins..

weeds (Tue, 16 May 2017 14:40:46 GMT):
thanks

muralisr (Tue, 16 May 2017 14:46:47 GMT):
are we allowing defects for alpha2 during this code-freeze period @cbf @JonathanLevi ? if so will there be a notification on what those are ?

muralisr (Tue, 16 May 2017 14:46:58 GMT):
maybe they are tagged and I'm just missing it ?

cbf (Tue, 16 May 2017 14:47:53 GMT):
@muralisr you mean against alpha2 that need another release?

cbf (Tue, 16 May 2017 14:47:58 GMT):
confused

muralisr (Tue, 16 May 2017 14:48:57 GMT):
sorry, yes, alpha2

muralisr (Tue, 16 May 2017 14:49:07 GMT):
against

cbf (Tue, 16 May 2017 14:49:23 GMT):
file JIRAs yes, fix bugs, sure... we will start merging fixes very soon

muralisr (Tue, 16 May 2017 14:49:29 GMT):
I thought there was some comments on how we are allowing some CRs

muralisr (Tue, 16 May 2017 14:49:29 GMT):
ok

muralisr (Tue, 16 May 2017 14:49:31 GMT):
thanks

cbf (Tue, 16 May 2017 14:49:37 GMT):
see above

muralisr (Tue, 16 May 2017 14:50:28 GMT):
ah never mind. thanks, @cbf

cbf (Tue, 16 May 2017 14:51:50 GMT):
there was a proposal that started here https://chat.hyperledger.org/channel/fabric-maintainers?msg=WQ5EAv8NxJCZJpnfX

cbf (Tue, 16 May 2017 14:52:33 GMT):
it was the third category that waarrants scrutiny

cbf (Tue, 16 May 2017 14:52:33 GMT):
it was the third category that warrants scrutiny

JonathanLevi (Tue, 16 May 2017 14:53:00 GMT):
Yup. Whatever is clearly in 1 + 2, can go in. When in doubt, let's all chat.

JonathanLevi (Tue, 16 May 2017 14:53:00 GMT):
Yup. Whatever is clearly in group 1 or 2, can go in. When in doubt, let's all chat.

yacovm (Tue, 16 May 2017 15:08:04 GMT):
@JonathanLevi but how do we "chat" ? RC is a rotating replicated log and it's hard to track. Maybe we can do something as follows? A code submitter opens a JIRA and submits it to #fabric-pr-review . He/She can also upload a patch set if it's ready. If the item belongs to category (3) in one of the maintainer's opinion, He writes in the gerrit item (if such exists) that he proposed to discuss that on JIRA. Next maintainers would then go to the JIRA and express their opinions. Once a write-quorum (how many?) votes on getting this in, the CR can be reviewed on gerrit.

yacovm (Tue, 16 May 2017 15:08:04 GMT):
@JonathanLevi but how do we "chat" ? RC is a rotating replicated log and it's hard to track. Maybe we can do something as follows? A code submitter opens a JIRA and a change set (if ready) and submits it to #fabric-pr-review . If the item belongs to category (3) in one of the maintainer's opinion, He writes in the gerrit item (if such exists) that he proposed to discuss that on JIRA. Next maintainers would then go to the JIRA and express their opinions. Once a write-quorum (how many?) votes on getting this in, the CR can be reviewed on gerrit. @cbf

JonathanLevi (Tue, 16 May 2017 15:11:24 GMT):
It may be useful to actually categorize way before Gerrit.

muralisr (Tue, 16 May 2017 15:11:48 GMT):
can we look at current list and decide on what needs to go in ? There's enough to keep us busy till alpha2 freeze can be lifted IMO :-)

JonathanLevi (Tue, 16 May 2017 15:13:11 GMT):
@yacovm: With enough information at the JIRA stage/ticket... we should see, given the steps to reproduce, etc... whether it is really not in group 1 or 2, and require to vote. @greg.haskins suggested the JIRA vote... (which, btw, seems plausible to me).

JonathanLevi (Tue, 16 May 2017 15:13:42 GMT):
@muralisr: let's have everything (we know of) in FAB-3040... we actually are merging things.

JonathanLevi (Tue, 16 May 2017 15:14:28 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-release?msg=iHw8onBbwsCwj5HiM) @dave.enyeart : both are merged.

JonathanLevi (Tue, 16 May 2017 15:14:36 GMT):
(thank you)

yacovm (Tue, 16 May 2017 15:14:58 GMT):
I don't think we should categorize way before gerrit for items 1 and 2.

yacovm (Tue, 16 May 2017 15:15:09 GMT):
That's an overhead we don't want to pay IMO

JonathanLevi (Tue, 16 May 2017 15:16:29 GMT):
I, too, do not want to prematurely optimize. We can evaluate this new proposal... and I'm happy with your 3 groups/categories.

JonathanLevi (Tue, 16 May 2017 15:17:28 GMT):
We do need more information in JIRA (than we used to before), but I'm fine with anything that's logical and reasonable.

JonathanLevi (Tue, 16 May 2017 15:18:18 GMT):
There may be cases that are really straight-forward, that we can categorize right away in JIRA, and others that we may need to (re)categorize after the implementation is examined.

yacovm (Tue, 16 May 2017 15:19:00 GMT):
All I'm trying to say is, and maybe I'm not clear - If I (or anyone else) am/is working on an item that's clearly (1) or (2) I shouldn't need approval to start working on it

JonathanLevi (Tue, 16 May 2017 15:19:30 GMT):
Oh - then I'm 100% with that. Yes.

yacovm (Tue, 16 May 2017 15:19:33 GMT):
So we might get to cases where a maintainer sees the JIRA and the gerrit change set at the same time :)

JonathanLevi (Tue, 16 May 2017 15:21:01 GMT):
I was thinking/focusing on when do we need to vote... and that "It *may* (=sometimes) be useful to actually categorize way before Gerrit." Thanks for clarifying.

samwood (Tue, 16 May 2017 16:35:32 GMT):
Has joined the channel.

mastersingh24 (Tue, 16 May 2017 16:47:13 GMT):
Probably missing half the conversation - but there are plenty of bugs entered in JIRA already and we know that there are missing UTs. I am ok with entering a *new* JIRA item for adding UTs (since likely there are no entries). But other than that, unless there is a new bug discovered as part of fixing a bug, beefing up UT or that comes in from our users, we should not be opening new JIRAs and working on them. There are plenty of tickets to handle already

mastersingh24 (Tue, 16 May 2017 16:49:27 GMT):
I think the maintainers are generally good at following the guidelines, we just need to make sure others do as well. I also think beefing up UT is some areas will help us as we fix bugs

weeds (Tue, 16 May 2017 17:00:57 GMT):
++ mastersingh24 a good example of the tests that people are asking to check in is what you see in pr-review channel

bmatsuo (Tue, 16 May 2017 17:19:42 GMT):
Has joined the channel.

cbf (Tue, 16 May 2017 18:22:35 GMT):
so, I think this is where we are:

cbf (Tue, 16 May 2017 18:23:48 GMT):
@yacovm's category 1 and 2 includes: new/revised tests, whether UT or FVT etc, documentation, and fixes that don't affect production code

cbf (Tue, 16 May 2017 18:24:43 GMT):
it also includes critical bug fixes which are not overly complex

cbf (Tue, 16 May 2017 18:24:43 GMT):
it also includes critical bug fixes to production which are not overly complex

cbf (Tue, 16 May 2017 18:25:26 GMT):
these, we will just handle as usual. Maintainers check that the JIRA is referenced, review for completeness and merge etc

cbf (Tue, 16 May 2017 18:27:29 GMT):
for type 3 maintainers should flag the JIRA and/or CR as such and we can label the JIRA for discussion

cbf (Tue, 16 May 2017 18:27:59 GMT):
then we can have a daily discussion on those so tagged

cbf (Tue, 16 May 2017 18:27:59 GMT):
then we can have a daily discussion on those JIRA so tagged and either add them to 3040 or defer them

JonathanLevi (Tue, 16 May 2017 18:51:20 GMT):
@cbf: `+2`

cbf (Tue, 16 May 2017 19:02:05 GMT):
@JonathanLevi https://wiki.hyperledger.org/projects/fabric/release_exit_criteria see review criteria section at the bottom of the page

JonathanLevi (Tue, 16 May 2017 22:44:44 GMT):
@cbf: I have slightly modified/updated it... but effectively it should say the same thing. Please re-verify...

bur (Wed, 17 May 2017 08:33:01 GMT):
Has joined the channel.

bur (Wed, 17 May 2017 09:48:26 GMT):
Hi all, I've just tried to write, build, and deploy a hello world chaincode by following the documentation on alpha 2 and would like to share my experience here. I am a Fabric beginner. In my case (Getting Started) section was not really useful once I realized that it does not explain how to setup a dev environment and build fabric. In the appendix I found the sections "Setting up the dev env" and "Building the fabric". I continued there. For Java chaincode developer the prerequisites section may mention Java 8 already here. Ok, build successful what's next? Starting a network, jumping back to "Getting Started" and searched for how to start a network without docker. No luck. Ok, by just looking in build/bin I realized there is my orderer and a peer. I started the orderer and a single peer by trail and error approach. At some point I also realized that I can configure them using the config files in sampleconfig. Nothing about that in the documentation. Ok, orderer and peer are running. Let's deploy an example chaincode. Back in the "getting started" section I followed the description how to install and instantiate some chaincode, in my case example02. At some point it worked. Next, writing my own hello world chaincode. It seems the current documentations has currently no "getting started writing your own chaincode" section. But an outdated version is still in the repository (https://github.com/hyperledger/fabric/blob/master/docs/source/Setup /Chaincode-setup.rst). In particular, the description still contains the "old" chaincode deployment model (with peer chaincode deploy instruction). In particular, the description still contains the old chaincode deployment model with peer chaincode deploy instruction.)

elli-androulaki (Wed, 17 May 2017 11:43:39 GMT):
Hi, went through the "getting started" instructions in a MAC and came across issues. The issue i documented in https://jira.hyperledger.org/browse/FAB-3973.

yacovm (Wed, 17 May 2017 12:07:31 GMT):
Mac, MAC is something that is related to #fabric-crypto

greg.haskins (Wed, 17 May 2017 12:09:52 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-release?msg=YNkwqgAowpSfWmNzp) @bur I agree with you that guidance is lacking right now

yacovm (Wed, 17 May 2017 12:10:29 GMT):
This doesn't look like a *Mac* specific problem, @elli-androulaki

elli-androulaki (Wed, 17 May 2017 12:10:54 GMT):
Could be, but i only tested it in MAC.

elli-androulaki (Wed, 17 May 2017 12:10:54 GMT):
Could be, but i only tested it on a MAC; let me know if you think the title is misleading and needs change

elli-androulaki (Wed, 17 May 2017 12:10:54 GMT):
Could be, but i only tested it on a Mac; let me know if you think the title is misleading and needs change

greg.haskins (Wed, 17 May 2017 12:11:20 GMT):
@bur not that this helps you per se, but I had proposed this: https://github.com/ghaskins/hyperledger-fabric-alpha2-challenge to try to rally the maintainers to ensure the process you are trying to do is well documented and easy

greg.haskins (Wed, 17 May 2017 12:11:35 GMT):
but that process has only just begun

weeds (Wed, 17 May 2017 12:44:38 GMT):
@nickgaski @markparz see up above- there is great input from @bur and @elli-androulaki on documentation updates

weeds (Wed, 17 May 2017 12:48:59 GMT):
see above @ajodowd

weeds (Wed, 17 May 2017 12:49:50 GMT):
@odowdaibm

odowdaibm (Wed, 17 May 2017 12:49:50 GMT):
Has joined the channel.

bmos299 (Wed, 17 May 2017 13:57:27 GMT):
Has joined the channel.

bmos299 (Wed, 17 May 2017 13:58:38 GMT):
@here This message went out to the hyperledger-fabric mail group. Comments are appreciated. Hello, The functional and system automated regression tests are being checked into the https://github.com/hyperledger/fabric/tree/master/test/regression folder and the associated tools are in https://github.com/hyperledger/fabric/tree/master/test/tools. The objective is to have daily, weekly, and release tests to run as per the naming convention (daily/weekly/release). The results will be published in Jenkins under a view with the corresponding name (daily/weekly/release). The name of the test will contain high-level information including - what the test does and the associated Jira item. If the reader wants more details they can inspect the Jira item . In the Jira item there will be a detailed test description with details on the artifacts needed for the test (client driver, associated files, etc). This is somewhat in PoC mode as we haven't been able to get CRs merged, so Ramesh created the link in a sandbox and cherry-picked the CRs. Here is the Jenkins view, https://jenkins.hyperledger.org/sandbox/job/daily/test_results_analyzer/, now click the 'expand all' button in the top right of the page (we are trying to make this the default). The results are clearly shown (PASS/FAIL/SKIPPED) and log files will be available (wip). Let's walk through an example. Scroll down under the ledger_lte tests and you will see, "test_FAB_3870_VaryNumParallelTxPerChain". The name gives some indiction of the test, but if you want more information you can go to the Jira task, FAB-3870 (https://jira.hyperledger.org/browse/FAB-3870) which uses a test template and describes the test and artifacts associated with the test. The goal is that the reader can see the test from a high level, or drill down into the code itself. This is a WIP and all comments are welcome. Greg Haskins had a thread last week on creating a new repository for fabric integration work. We are open to what the community decides and could easily port the work to a new repo if necessary. Thanks for reading. Barry Mosakowski (a.k.a bmos299)

dave.enyeart (Wed, 17 May 2017 14:44:40 GMT):
@rameshthoomu , @mastersingh24 was asking for per-platform downloads on nexus, is that possible?

rameshthoomu (Wed, 17 May 2017 14:45:47 GMT):
yes this script will do that https://gerrit.hyperledger.org/r/#/c/8939/20/jjb/fabric/include-raw-fabric-push-fabric-binaries.sh

dave.enyeart (Wed, 17 May 2017 14:46:01 GMT):
so there will be a link per platform?

mastersingh24 (Wed, 17 May 2017 14:46:04 GMT):
I thought it did but was not sure

mastersingh24 (Wed, 17 May 2017 14:46:22 GMT):
And do we have an example of the new package(s)?

rameshthoomu (Wed, 17 May 2017 14:46:35 GMT):
and for my testing I have posted binaries to sandbox.. Will delete these once we publish to releases

rameshthoomu (Wed, 17 May 2017 14:46:47 GMT):
@mastersingh24 check this link https://nexus.hyperledger.org/content/repositories/snapshots/sandbox/vex-yul-hyp-jenkins-2/fabric-binaries-x86_64/

rameshthoomu (Wed, 17 May 2017 14:48:18 GMT):
these platform specific tarballs are packaged with cryptogen, configtxgen and e2e_cli folder

rameshthoomu (Wed, 17 May 2017 14:48:33 GMT):
to run e2e_cli tests without cloning fabric repository

dave.enyeart (Wed, 17 May 2017 14:55:26 GMT):
@rameshthoomu Now that I see the tarball content, I understand that the docker-compose volume mapping that I changed a few days ago will not work, will need to update that:

dave.enyeart (Wed, 17 May 2017 14:55:27 GMT):
- ../chaincode/go/:/opt/gopath/src/github.com/hyperledger/fabric/examples/chaincode/go

dave.enyeart (Wed, 17 May 2017 14:56:53 GMT):
I know understand why example02 was copied to be within /examples/e2e_cli

dave.enyeart (Wed, 17 May 2017 14:57:06 GMT):
I will need to copy marbles02 in there as well, since Getting Started references both of them

rameshthoomu (Wed, 17 May 2017 14:57:08 GMT):
yes.. these are build on top of old commits..

dave.enyeart (Wed, 17 May 2017 14:58:38 GMT):
no, we still have a problem, the updated path in the docker-compose will not work with the tarball. i will need to update the path in docker-compose to be consistent with tarball

dave.enyeart (Wed, 17 May 2017 14:59:34 GMT):
can example02 and marbles02 chaincode examples be copied into tarball at build time, instead of maintaining two copies in source

dave.enyeart (Wed, 17 May 2017 15:01:25 GMT):
currently we have two copies in source: /examples/chaincode/go/chaincode_example02 and /examples/e2e_cli/examples/chaincode/go/chaincode_example02

dave.enyeart (Wed, 17 May 2017 15:01:45 GMT):
that doesnt make much sense... would be better to copy the chaincode examples into tarball at build time

rameshthoomu (Wed, 17 May 2017 15:01:51 GMT):
yes we can do that.. but are we testing marbels in e2e_cli?

dave.enyeart (Wed, 17 May 2017 15:02:25 GMT):
yes both. example02 is done first, and then in the Using CouchDB section of Getting Started we use marbles02

Ratnakar (Wed, 17 May 2017 15:02:33 GMT):
Has joined the channel.

dave.enyeart (Wed, 17 May 2017 15:02:36 GMT):
(couchdb query requires json)

rameshthoomu (Wed, 17 May 2017 15:24:46 GMT):
@dave.enyeart Do you want me to publish tarballs on latest fabric commit?

dave.enyeart (Wed, 17 May 2017 15:26:12 GMT):
yes, we made fixes to e2e_cli instructions and docker-compose scripts after alpha2. Therefore for instructions and docker-compose to work, we need to use latest e2e_cli material rather than alpha2.

dave.enyeart (Wed, 17 May 2017 15:26:23 GMT):
The latest docker compose uses mapping of:

dave.enyeart (Wed, 17 May 2017 15:26:30 GMT):
- ../chaincode/go/:/opt/gopath/src/github.com/hyperledger/fabric/examples/chaincode/go

dave.enyeart (Wed, 17 May 2017 15:26:57 GMT):
Therefore when you copy example02 and marbles02 into tarball, you will have to use this path

dave.enyeart (Wed, 17 May 2017 15:28:02 GMT):
After today, we can also delete the copy of example02 from e2e_cli source, since you will be copying /examples/chaincode/go/chaincode_example02 at tarball build time.

rameshthoomu (Wed, 17 May 2017 15:28:35 GMT):
ok.

dave.enyeart (Wed, 17 May 2017 15:29:05 GMT):
@mastersingh24 ^^^^^^^ Just wanted you to be aware of the action plan

dave.enyeart (Wed, 17 May 2017 15:29:05 GMT):
@mastersingh24 @Ratnakar ^^^^^^^ Just wanted you to be aware of the action plan

mastersingh24 (Wed, 17 May 2017 15:43:19 GMT):
sounds right

dave.enyeart (Wed, 17 May 2017 15:43:53 GMT):
@rameshthoomu As Greg mentioned in FAB-2986, URLs like "sandbox/vex-yul" are ugly... can you provide an example of what the 'final' URL would be?

mastersingh24 (Wed, 17 May 2017 15:44:15 GMT):
Also - is it possible to clean up the file structure a bit in the archive? The script / templates are a bit confusing if you ask me - but maybe best to improve on that in the future and go with what we have?

mastersingh24 (Wed, 17 May 2017 15:44:24 GMT):
Also - have people tested on Windows?

rameshthoomu (Wed, 17 May 2017 16:59:21 GMT):
@mastersingh24 we have to cleanup this script and will comeup with optimized script as soon as possible..

rameshthoomu (Wed, 17 May 2017 16:59:50 GMT):
Working with @jwagantall from LF team

jwagantall (Wed, 17 May 2017 16:59:50 GMT):
Has joined the channel.

odowdaibm (Wed, 17 May 2017 17:21:20 GMT):
@greg @bur Much agreed with you - fancy having a chat about this in a small working group? I posted a proposal for a couple of meetings (geo friendly timezones) to see who might be interested in helping to structure, write, draw and review the docs. It seems like there's agreement that Getting Started needs work, and looking at Key Concepts, that needs some work too. Personally, I'd like to see Getting Started walk through what is happening better by it being broken into much clearer sections that describe what's happening by gradually introducing the concepts e.g. :(empty fabric), create identities, add orderer, add peer(s), install sample chaincode, instantiate sample chancode, run sample query, run sample transaction etc etc. As we go through these steps, we could both pictorially represent and show the commands to do it, so that by the end of GS, you understood the basic concepts and had a working system. If you wanted to learn more, then see fuller descriptions in Key Concepts. To your point of writing apps, it would be good to look at high level TOC structure, and how we might flesh that out too. Happy to chat here to initiate out some ideas, and then maybe have a community wide call for anyone else who'd like to help. Make sense?

odowdaibm (Wed, 17 May 2017 17:21:50 GMT):
@greg.haskins gotcha wrong above

greg.haskins (Wed, 17 May 2017 17:24:01 GMT):
@odowdaibm sounds great, thank you

greg.haskins (Wed, 17 May 2017 17:24:18 GMT):
that is one of the things I am hoping the alpha2-challenge produces

greg.haskins (Wed, 17 May 2017 17:24:54 GMT):
the other would be an understanding of what software design changes we need to optimize the experience

jeffgarratt (Wed, 17 May 2017 19:53:48 GMT):
@odowdaibm this is precisely the purpose of the bdd subsytem's boostrap feature https://github.com/hyperledger/fabric/blob/master/bddtests/features/bootstrap.feature

cbf (Wed, 17 May 2017 23:15:31 GMT):
@odowdaibm there is work to be done to improve the Getting Started, no doubt

cbf (Wed, 17 May 2017 23:15:49 GMT):
However, the priority at this point is just making it correct for alpha2

cbf (Wed, 17 May 2017 23:16:03 GMT):
let's not let perfect get in the way of making progress, please

cbf (Wed, 17 May 2017 23:16:34 GMT):
I know the e2e has been somewhat updated, but we cannot have the front door be pointing to a past release

cbf (Wed, 17 May 2017 23:16:55 GMT):
we have not announced the release because we need the Getting Started to actually reference the alpha2 images and code.

cbf (Wed, 17 May 2017 23:18:29 GMT):
@mastersingh24 @greg.haskins same with the published binaries etc. at this point, an ugly URL is immaterial

cbf (Wed, 17 May 2017 23:18:29 GMT):
@mastersingh24 @greg.haskins same with the published binaries etc. at this point, an ugly URL is immaterial and how they are produced is also at this point immaterial given the time constraint

cbf (Wed, 17 May 2017 23:18:36 GMT):
what we need are published binaries

cbf (Wed, 17 May 2017 23:18:51 GMT):
we can always fix things and move things around and assign vanity URLs

cbf (Wed, 17 May 2017 23:19:17 GMT):
thanks

greg.haskins (Thu, 18 May 2017 00:23:56 GMT):
@mastersingh24 my main concern is that trying to onboard new teams to hyperledger was really challenging when the URLs were either returning 404s or artifacts that didn't actually work properly. I also don't want to have an environment where the artifact publication/documentation process allows bypassing governance controls like maintainer approval for a release. I simply want to avoid repeating those mistakes if it can be helped because it can be damaging to the project if that is a users first exposure. I can appreciate the sense of urgency here. However, if there is agreement that these are the proper goals, we should strive to put the proper things in place sooner rather than later so we don't repeatedly find ourselves in this tough spot at each release point. If, on the other hand, you all think I am overly concerned about unimportant issues, tell me to shut up ;)

JonathanLevi (Thu, 18 May 2017 04:01:24 GMT):
@rameshthoomu, @nickgaski: [ ](https://chat.hyperledger.org/channel/fabric-maintainers?msg=dKokMCQ4e8TphsuAK) What's the status of the *Getting Started* guide? It is still on *v1.0.0-alpha* (and not *v1.0.0-alpha2*)

JonathanLevi (Thu, 18 May 2017 04:01:51 GMT):
What can I/we do to expedite or assist, please?

rameshthoomu (Thu, 18 May 2017 04:03:11 GMT):
@JonathanLevi We are still working on this.. script and tarballs are ready for each platform but we are unable to publish it to nexus repository.. Working with @jwagantall (from LF team)..

rameshthoomu (Thu, 18 May 2017 04:05:09 GMT):
earlier it worked as expected but after recent permissions changes it stopped working.. It seems some configuration issue betwen maven, jenkins and nexus...

JonathanLevi (Thu, 18 May 2017 04:05:19 GMT):
How can I assist?

JonathanLevi (Thu, 18 May 2017 04:06:27 GMT):
We really want (and need) to announce the availability of the *alpha2* widely, so that people can report issues. But I won't do it without a working *Getting Started* guide. That's really the basics.

JonathanLevi (Thu, 18 May 2017 04:06:27 GMT):
We really want (and need) to announce the availability of the *alpha2* widely, so that people can report issues, but I won't do it without a working *Getting Started* guide. That's really the basics.

JonathanLevi (Thu, 18 May 2017 04:07:25 GMT):
We really want (and need) to announce the availability of the *alpha2* widely, so that people can report issues, but I won't do it without a working *Getting Started* guide. That's really the basics.

rameshthoomu (Thu, 18 May 2017 04:07:54 GMT):
yes.. trying my best..

rameshthoomu (Thu, 18 May 2017 04:08:29 GMT):
Will give you an update before I go to bed.. @jwagantall submitted patch in fabric https://gerrit.hyperledger.org/r/#/c/9487/

rameshthoomu (Thu, 18 May 2017 04:09:33 GMT):
this is regarding pom.xml but this is not helping much.. this file is basically building jar file and publishing the same.. but we need pom.t which deploy tar.gz files to nexus..

JonathanLevi (Thu, 18 May 2017 04:13:12 GMT):
Understood. Yes, I see a `-1` there as well. What else is missing? Other dependencies? Is there a pending CR for updating the Getting Started guide? For starters, to remove the references to `alpha` or the PowerPC...

JonathanLevi (Thu, 18 May 2017 04:13:41 GMT):
BTW: I'm not *blaming you* ;-), I know you are doing your best. Trying to resolve conflicts, and see how I can help.

JonathanLevi (Thu, 18 May 2017 04:20:03 GMT):
Just to be clear, I'm not blaming anyone ;-), I know you are doing your best @rameshthoomu - I'm basically just trying to resolve conflicts, check our readiness so that we know when the last bits are done & see how I can help.

rameshthoomu (Thu, 18 May 2017 04:24:12 GMT):
not sure what we have to add to that pom.xml to make it work.. and even not sure whether that is correct approach or not.. Trying to push tar files without using pom.xml from sandbox (testing) but getting un-authorized error..

rameshthoomu (Thu, 18 May 2017 04:24:39 GMT):
checking all possible combinations..

rameshthoomu (Thu, 18 May 2017 04:26:28 GMT):
checking with @rjones @jwagantall in #ci-pipeline channel

jwagantall (Thu, 18 May 2017 05:44:02 GMT):
@rameshthoomu as mentioned earlier... the release needs to be deployed through the staging maven plugin.. which i showed earlier that works... that is what the credentials have permissions to do..

jwagantall (Thu, 18 May 2017 05:44:57 GMT):
that's the reason why i created the root pom file..

jwagantall (Thu, 18 May 2017 05:45:35 GMT):
but i am not familiar with the fabric code to understand rick's complain on not needing the pom at all.

jwagantall (Thu, 18 May 2017 05:46:12 GMT):
we can check if there is a way of using the staging deploy plugin to deploy files in particular.. but i have never used it that way

rameshthoomu (Thu, 18 May 2017 05:46:39 GMT):
basically the pom.xml what you have created is building artifact and publishing with `mvn deploy` (which is using staging plugin)

rameshthoomu (Thu, 18 May 2017 05:47:31 GMT):
but if we publish it only through pom.xml then it has to just publish tar files located in `release` folder

jwagantall (Thu, 18 May 2017 05:53:11 GMT):
could the problem be that we are moving everything to the release folder? and by the time the maven step runs it just doesnt find anything to unstall/deploy?

jwagantall (Thu, 18 May 2017 05:53:39 GMT):
again, we need the fabric devs to help out here with this step..

bur (Thu, 18 May 2017 07:37:16 GMT):
@odowdaibm SGTM! I'd like to help with structure and review of the docu.

RistoAlas (Thu, 18 May 2017 09:41:30 GMT):
Has joined the channel.

dave.enyeart (Thu, 18 May 2017 10:51:26 GMT):
@greg.haskins, would it be possible to move the v1.0.0-alpha2 tag a few commits? Reason: Yesterday the end-to-end.rst instructions added a comment for people in a dev environment to revert to v1.0.0-alpha2 if they want to run end to end trial: git checkout v1.0.0-alpha2 However, at that tag level, both the end-to-end instructions and docker-compose for end-to-end were not working, so this will result in many problems. The instructions and docker-compose were fixed just after the v1.0.0-alpha2 tag was put in place. If the v1.0.0.0-alpha2 tag is moved to commit 5c353eb , then all is good with end-to-end. I don’t think we’d have to re-spin docker images, since there were no functional changes in that timeframe. However, that would pick up your alpha3 update to Makefile. I’m not sure what the impact of that would be. Here’s the commit history in question:

dave.enyeart (Thu, 18 May 2017 10:51:44 GMT):
```* 5c353eb - (HEAD -> master, origin/master, origin/HEAD) Merge "[FAB-3947] - Update instructions for e2e" (2 days ago) |\ | * e2b4fa6 - (n_e2e_doc) [FAB-3947] - Update instructions for e2e (2 days ago) * | 9e68b12 - Merge "[FAB-3733] Fix the CouchDB option for e2e_cli" (2 days ago) |\ \ | |/ |/| | * 8f1fb01 - (a_compose_refactor) [FAB-3733] Fix the CouchDB option for e2e_cli (2 days ago) * | fa98b46 - FAB-3928 update release notes for v1.0.0-alpha2 (3 days ago) |/ * 2470d35 - Merge "Prepare for alpha3 development" (4 days ago) |\ | * 9693060 - Prepare for alpha3 development (6 days ago) * | c1c7bb7 - Merge "[FAB-3705] Removing unused found unused vars in ./bccsp" (4 days ago) |\ \ | |/ |/| | * 53084ed - [FAB-3705] Removing unused found unused vars in ./bccsp (6 days ago) * | 6b6bfcf - (tag: v1.0.0-alpha2) Release v1.0.0-alpha2 (6 days ago) ```

JonathanLevi (Thu, 18 May 2017 11:08:39 GMT):
@dave.enyeart, to you question: *would it be possible to move the v1.0.0-alpha2 tag a few commits?*

JonathanLevi (Thu, 18 May 2017 11:09:06 GMT):
Physically yes, easily. Not recommended at all !

dave.enyeart (Thu, 18 May 2017 11:11:49 GMT):
ok, as of now anybody following the instructions in dev env will have a broken e2e experience. Maybe we should just update the instructions to checkout 5c353eb instead of v1.0.0-alpha2.

odowdaibm (Thu, 18 May 2017 11:12:44 GMT):
@bur @greg.haskins @cbf

mastersingh24 (Thu, 18 May 2017 11:13:26 GMT):
@dave.enyeart - for RTD "Getting started" - which goes along with the alpha2 release - are the instructions correct?

dave.enyeart (Thu, 18 May 2017 11:14:06 GMT):
yes, Getting Started is ok, we decided yesterday to put the latest instructions in the release tarball, rather than the alpha2 version of the instructions.

dave.enyeart (Thu, 18 May 2017 11:14:16 GMT):
latest instructions are good

odowdaibm (Thu, 18 May 2017 11:14:18 GMT):
@bur @greg.haskins @cbf thanks for comments. I'm setting up conf details now - trying to get done in time for JST time zone. Plenty of replies which suggest we should have a couple of good meetings tomorrow - thanks to everyone.

mastersingh24 (Thu, 18 May 2017 11:15:21 GMT):
OK - then I'm not sure why we need to mess around with the tag?

dave.enyeart (Thu, 18 May 2017 11:15:32 GMT):
Nick has a Getting Started ready to go for readthedocs, and it is good. He'll pull the trigger once the tarball is on nexus.

odowdaibm (Thu, 18 May 2017 11:16:05 GMT):
is that a GS that's basically the same as today, but all "fixed up" to reflect the tarball?

dave.enyeart (Thu, 18 May 2017 11:16:23 GMT):
Only for people running the end-to-end in dev env. the instructions for dev env say to revert (checkout) v1.0.0-alpha2. If they revert to that level, the docs and docker-compose are bad.

mastersingh24 (Thu, 18 May 2017 11:16:38 GMT):
The stuff in examples/e2e_cli in the repo should always work against the content of the repo

dave.enyeart (Thu, 18 May 2017 11:17:30 GMT):
In theory yes, but @cbf suggested we have people revert to alpha2 level of e2e_cli, just in case

dave.enyeart (Thu, 18 May 2017 11:17:47 GMT):
but that advise backfired, since the alpha2 level of instructions and docker compose are bad

odowdaibm (Thu, 18 May 2017 11:18:02 GMT):
I'd like to see the GS structured to explain a little of the concepts as it progresses. Are either of you able to attend the doc WG kickoff tomorrow - we had quite a good reply on the mailing list, and I had half a dzen private notes too

mastersingh24 (Thu, 18 May 2017 11:18:20 GMT):
BUT - the whole point of the alpha2 (or any release) images is that we DON'T want people doing stuff out of the repo

dave.enyeart (Thu, 18 May 2017 11:19:40 GMT):
correct, 'consumers' will use the docker images and tarball of e2e_cli. It's only fabric 'developers' with a repo that will get hit by this. So i guess we should remove that guidance for developers to revert to alpha2

cbf (Thu, 18 May 2017 11:19:49 GMT):
exactly

cbf (Thu, 18 May 2017 11:19:49 GMT):
exactly (to Gari's point)

dave.enyeart (Thu, 18 May 2017 11:20:10 GMT):
@cbf, you suggested to add that guidance. i'm suggesting to remove that guidance.

mastersingh24 (Thu, 18 May 2017 11:20:35 GMT):
I agree - remove the guidance

cbf (Thu, 18 May 2017 11:20:42 GMT):
I think we need to take a step back

cbf (Thu, 18 May 2017 11:20:47 GMT):
what guidance?

dave.enyeart (Thu, 18 May 2017 11:21:23 GMT):
yesterday you had Nick update end-to-end.rst, to advise readers (developers) to revert to alpha2 before they run e2e_cli

cbf (Thu, 18 May 2017 11:21:34 GMT):
holy cow

dave.enyeart (Thu, 18 May 2017 11:21:38 GMT):
but at alpha2 level, e2e_cli was broken

cbf (Thu, 18 May 2017 11:22:00 GMT):
I want whatever we publish as getting started/end to end to be based on alpha2

mastersingh24 (Thu, 18 May 2017 11:22:03 GMT):
directions were broken or the e2e was broken?

cbf (Thu, 18 May 2017 11:22:12 GMT):
everything

dave.enyeart (Thu, 18 May 2017 11:22:24 GMT):
directions AND docker-compose were broken at alpha2 tag

dave.enyeart (Thu, 18 May 2017 11:22:28 GMT):
they were fixed right after that

cbf (Thu, 18 May 2017 11:22:55 GMT):
broken with regards to what, exactly

dave.enyeart (Thu, 18 May 2017 11:23:16 GMT):
for normal consumers it is ok, since the tarball on nexus uses latest e2e_cli instructions and docker-compose, rather than alpha2 level

dave.enyeart (Thu, 18 May 2017 11:24:05 GMT):
for example, at alpha2 tag level, Nick's updates for alpha2 were not yet merged, and therefore the instructions pointed to old shell script names

cbf (Thu, 18 May 2017 11:24:47 GMT):
to the docs?

dave.enyeart (Thu, 18 May 2017 11:25:16 GMT):
end-to-end.rst was outdated as of alpha2 tag

dave.enyeart (Thu, 18 May 2017 11:25:35 GMT):
the updates got merged right after alpha2 tag

cbf (Thu, 18 May 2017 11:25:36 GMT):
(bangs head against desk)

dave.enyeart (Thu, 18 May 2017 11:26:14 GMT):
the docker images are fine at alpha2 tag

dave.enyeart (Thu, 18 May 2017 11:26:30 GMT):
just this e2e content was bad

dave.enyeart (Thu, 18 May 2017 11:26:40 GMT):
for normal consumers it is ok, since the tarball on nexus uses latest e2e_cli instructions and docker-compose, rather than alpha2 level

dave.enyeart (Thu, 18 May 2017 11:29:22 GMT):
so, my suggestion, is for developers with a repo, to remove the guidance that they revert to alpha2 when doing e2e trial. developers with a repo should always use latest.

cbf (Thu, 18 May 2017 11:34:01 GMT):
what tarball?

cbf (Thu, 18 May 2017 11:34:15 GMT):
I thought that we couldn't publish - and that was the whole issue

dave.enyeart (Thu, 18 May 2017 11:34:58 GMT):
right, currently it is a proposed tarball, that will end up on nexus. as of this morning Ramesh is having issues pushing it.

cbf (Thu, 18 May 2017 11:35:04 GMT):
if we need to cut an alpha2.1 we can, to make things whole

cbf (Thu, 18 May 2017 11:35:09 GMT):
hacking things is not the answer

cbf (Thu, 18 May 2017 11:35:48 GMT):
right now, e2e or getting started are all wrong - I blame me for being too duistracted to notice

cbf (Thu, 18 May 2017 11:35:48 GMT):
right now, e2e or getting started are all wrong - I blame me for being too distracted to notice

cbf (Thu, 18 May 2017 11:36:33 GMT):
BUT, it also highlights that not all the information was in JIRA

dave.enyeart (Thu, 18 May 2017 11:36:54 GMT):
since it was just the e2e example content and not code in docker images, we thought it would be ok to hack up the tarball. but you're right, we could make things whole by doing alpha2.1.

dave.enyeart (Thu, 18 May 2017 11:36:54 GMT):
since it was just the e2e example content and not code in docker images, we thought it would be ok to hack up the tarball with latest e2e content. but you're right, we could make things whole by doing alpha2.1.

dave.enyeart (Thu, 18 May 2017 11:39:35 GMT):
Getting Started is not yet pushed to readthedocs. Nick has is prepared with the good instructions. He is ready to pull the trigger as soon as the nexus links become live. So again, for normal consumers all will be good.

mastersingh24 (Thu, 18 May 2017 11:42:01 GMT):
@dave.enyeart @rameshthoomu - we should remove `end-to-end.rst` from the tarball

cbf (Thu, 18 May 2017 11:42:10 GMT):
bingo

mastersingh24 (Thu, 18 May 2017 11:42:30 GMT):
People can use RTD with alpha2 and off they go

dave.enyeart (Thu, 18 May 2017 11:43:24 GMT):
agreed and correct

dave.enyeart (Thu, 18 May 2017 11:44:09 GMT):
its not just end-to-end.rst though, the docker-compose was also bad at alpha2 tag, and therefore those files in the tarball are hacked up to latest as well

cbf (Thu, 18 May 2017 11:44:28 GMT):
bad how

cbf (Thu, 18 May 2017 11:44:49 GMT):
and why wasn't someone saying something before we cut alpha2?

mastersingh24 (Thu, 18 May 2017 11:46:40 GMT):
Shoot - this is worse than I thought in some ways - although not hard to recover from

mastersingh24 (Thu, 18 May 2017 11:47:22 GMT):
I'm not sure why e2e was not working at alpha2 tag - I thought it was

mastersingh24 (Thu, 18 May 2017 11:47:35 GMT):
I don't care about the docs, but the e2e was working

mastersingh24 (Thu, 18 May 2017 11:47:56 GMT):
I'll take some of the blame as well

dave.enyeart (Thu, 18 May 2017 11:48:07 GMT):
the docker-compose was ok for leveldb, was broken for couch

dave.enyeart (Thu, 18 May 2017 11:48:14 GMT):
most people were testing leveldb

mastersingh24 (Thu, 18 May 2017 11:48:29 GMT):
I had a plan for how to produce the "release artifacts" as well

dave.enyeart (Thu, 18 May 2017 11:48:47 GMT):
ratnaker refactored the docker-compose, but nobody retested couch after that

cbf (Thu, 18 May 2017 11:50:07 GMT):
ok, now it is starting to make sense, because I had also tested e2e and it worked

cbf (Thu, 18 May 2017 11:50:17 GMT):
so clearly we need a TEST that TESTS both

cbf (Thu, 18 May 2017 11:50:34 GMT):
that said

cbf (Thu, 18 May 2017 11:51:23 GMT):
here is what I suggest

cbf (Thu, 18 May 2017 11:51:48 GMT):
and let me understand where we are --- have we published the alpha2 tarball, yes or now

cbf (Thu, 18 May 2017 11:51:48 GMT):
and let me understand where we are --- have we published the alpha2 tarball, yes or no

cbf (Thu, 18 May 2017 11:51:48 GMT):
and let me understand where we are --- have we published the alpha2 tarball, yes or no?

mastersingh24 (Thu, 18 May 2017 11:52:00 GMT):
we have not

dave.enyeart (Thu, 18 May 2017 11:52:05 GMT):
no, tarball is ready but ramesh is having issues pushing it

cbf (Thu, 18 May 2017 11:52:11 GMT):
ok

cbf (Thu, 18 May 2017 11:52:36 GMT):
so, IMNSHO, we should NOT be asking anyone to build anything

cbf (Thu, 18 May 2017 11:53:21 GMT):
so fine, reverse my guidance on checking out alpha2 - but that was given because the docs currently say just do a git clone of master (which will be bad)

cbf (Thu, 18 May 2017 11:53:43 GMT):
if we are REMOVING the git clone instructions, then obviously we don't need to checkout alpha2

dave.enyeart (Thu, 18 May 2017 11:53:47 GMT):
for normal consumers, we point them to Getting Started, which does not clone/make. Getting Started docs will say to download the images.

cbf (Thu, 18 May 2017 11:54:24 GMT):
that is the ONLY audience that matters

dave.enyeart (Thu, 18 May 2017 11:54:27 GMT):
for developers, they can clone/make. We just need to clarify the roles in the end-to-end.rst

cbf (Thu, 18 May 2017 11:54:33 GMT):
nevermind them

cbf (Thu, 18 May 2017 11:54:51 GMT):
should probably remove e2e_cli.rst

cbf (Thu, 18 May 2017 11:55:06 GMT):
seriously

cbf (Thu, 18 May 2017 11:55:10 GMT):
we do this all the time

cbf (Thu, 18 May 2017 11:55:35 GMT):
there should be one place that says how to use getting started

cbf (Thu, 18 May 2017 11:55:40 GMT):
only one

mastersingh24 (Thu, 18 May 2017 11:58:13 GMT):
We should remove `end-to-end.rst` from the release artifact

mastersingh24 (Thu, 18 May 2017 12:00:32 GMT):
OK - so what do we want to do here?

dave.enyeart (Thu, 18 May 2017 12:04:30 GMT):
Ramesh can easily remove `end-to-end.rst` from tarball

dave.enyeart (Thu, 18 May 2017 12:11:50 GMT):
I would suggest refactor end-to-end.rst into three documents going forward. 1) Consumer Getting Started (how to download images and end-to-end artifacts) 2) Developer Getting Started (how to clone/make). 3) Executing the end-to-end example.

dave.enyeart (Thu, 18 May 2017 12:12:01 GMT):
Both Getting Started docs would point to #3 as the last step

cbf (Thu, 18 May 2017 12:14:24 GMT):
@dave.enyeart 2 should be completely independent of e2e

cbf (Thu, 18 May 2017 12:14:52 GMT):
and frankly, If they cannot figure out from Makefile...

cbf (Thu, 18 May 2017 12:15:03 GMT):
there should just be getting started

dave.enyeart (Thu, 18 May 2017 12:15:38 GMT):
agreed that #2 should be later in the docs. but i do think we need an easy on-ramp for developers too.

cbf (Thu, 18 May 2017 12:24:12 GMT):
CONTRIBUTING.rst could be improved, sure

cbf (Thu, 18 May 2017 12:24:29 GMT):
let's focus on 1) fixing tarball

cbf (Thu, 18 May 2017 12:24:43 GMT):
2) merging e2e content into getting started

greg.haskins (Thu, 18 May 2017 12:24:52 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-release?msg=2x3e43hymLgcCtJra) @dave.enyeart I would strongly discourage moving a tag...it's far better to reduce emphasis on the name of the release than to try to alter history...therefore, I would suggest we simply cut an alpha2.1

cbf (Thu, 18 May 2017 12:24:59 GMT):
3) multiple independent testers

cbf (Thu, 18 May 2017 12:25:28 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-release?msg=3xz7ij3YLAvRQDnc2) @greg.haskins +2

cbf (Thu, 18 May 2017 12:25:46 GMT):
but it is also unclear that we need another release

cbf (Thu, 18 May 2017 12:26:11 GMT):
just get the correct content in the tarball that works against published images

cbf (Thu, 18 May 2017 12:26:14 GMT):
for alpha2

cbf (Thu, 18 May 2017 12:26:57 GMT):
what we may want to do is to tag a RTD "release"

greg.haskins (Thu, 18 May 2017 12:28:02 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-release?msg=xRkjDP5Mvv9Y2KH2T) @dave.enyeart I see no problem in creating an alpha2.x branch, cherry picking what you wanted to include

greg.haskins (Thu, 18 May 2017 12:28:21 GMT):
then we could point to the branch rather than a sha

cbf (Thu, 18 May 2017 12:28:21 GMT):
@greg.haskins I think that is overkill

greg.haskins (Thu, 18 May 2017 12:28:50 GMT):
@cbf ok...just offering what I think would be acceptable from an SCM perspective

cbf (Thu, 18 May 2017 12:28:55 GMT):
look, the release is what it is

dave.enyeart (Thu, 18 May 2017 12:28:59 GMT):
agreed, we'll just remove the guidance in end-to-end.rst about checking out alpha2

cbf (Thu, 18 May 2017 12:29:02 GMT):
it has bugs

cbf (Thu, 18 May 2017 12:29:04 GMT):
we know this

dave.enyeart (Thu, 18 May 2017 12:29:13 GMT):
and then refactor end-to-end.rst going forward

cbf (Thu, 18 May 2017 12:29:30 GMT):
what we DO want though is for there to be clear instructions on how to deploy it

cbf (Thu, 18 May 2017 12:29:48 GMT):
we can address with the 3 steps above

dave.enyeart (Thu, 18 May 2017 12:30:24 GMT):
@rameshthoomu You probably haven't been following along... but the action for you is to remove `end-to-end.rst` from tarball, before publishing it to nexus

dave.enyeart (Thu, 18 May 2017 12:30:55 GMT):
we will focus consumers on the upcoming Getting Started updates in readthedocs

odowdaibm (Thu, 18 May 2017 14:02:11 GMT):
@dave.enyeart @cbf @bur @mastersingh24 I know you're all interested. I posted details of tomorrow's documentation meetings on the mailing list: https://lists.hyperledger.org/pipermail/hyperledger-fabric/2017-May/000992.html Great if you can join, but either way we'll post minutes there after the calls.

dave.enyeart (Thu, 18 May 2017 14:10:23 GMT):
@odowdaibm I am immensely interested, but not available tomorrow, i'll review and engage

mastersingh24 (Thu, 18 May 2017 14:10:32 GMT):
@cbf @dave.enyeart - so can someone clearly list the steps for the current release plan?

dave.enyeart (Thu, 18 May 2017 14:11:50 GMT):
@mastersingh24 cleaning up my notes on next actions, will post momentarily...

odowdaibm (Thu, 18 May 2017 14:15:33 GMT):
@dave.enyeart OK, that's totally fine - I'll look out for your post. Thanks again.

rameshthoomu (Thu, 18 May 2017 14:21:24 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-release?msg=HH5Lf36sdwvk8sF85) @dave.enyeart Do you want me to implement this change?

dave.enyeart (Thu, 18 May 2017 14:22:47 GMT):
@rameshthoomu as discussed at 9:30, the tarball is already pushed to nexus sandbox/logs. So as to not delay further, we'll go with the tarball as-is for today. Going forward we'll remove end-to-end.rst

rameshthoomu (Thu, 18 May 2017 14:23:13 GMT):
ok..

mastersingh24 (Thu, 18 May 2017 14:24:58 GMT):
LET"S PLEASE STOP WITH ANY CHANGE RELATED TO RELEASE ARTIFACTS

mastersingh24 (Thu, 18 May 2017 14:24:59 GMT):
;)

mastersingh24 (Thu, 18 May 2017 14:25:21 GMT):
I'm good with going with what we have for now

mastersingh24 (Thu, 18 May 2017 14:25:34 GMT):
Then we figure out what to do for the next release

dave.enyeart (Thu, 18 May 2017 14:28:41 GMT):
Here’s the FINAL steps for alpha2 release: 1) CR 8939 - Issue with maven deploy plugin pushing to staging/deploy/release. As a workaround, Ramesh has pushed the release tarball to nexus /sandbox/logs directory. Not ideal, but good enough for today. CHRIS will talk to Ry about the issue. 2) CR for changing test env image tag - RAMESH 3) FAB-4007/ CR 9525 bootstrap.sh script - CHRIS will make on update for ./download-dockerimages.sh -c x86_64-1.0.0-alpha2 -f x86_64-1.0.0-alpha2 4) Need to test CR 9525 on all environments - Mac confirmed - Linux - RAMESH - Windows (DAVE ENYEART will ask ARNAUD @lehors to test) 5) Getting Started doc for readthedocs (FAB-3925), point to new bootstrap.sh script - NICK will push a CR

dave.enyeart (Thu, 18 May 2017 14:28:41 GMT):
Here’s the FINAL steps for alpha2 release: 1) CR 8939 - Issue with maven deploy plugin pushing to staging/deploy/release. As a workaround, Ramesh has pushed the release tarball to nexus /sandbox/logs directory. Not ideal, but good enough for today. CHRIS will talk to Ry about the issue. 2) CR for changing test env image tag - RAMESH 3) FAB-4007/ CR 9525 bootstrap.sh script - CHRIS will make an update for ./download-dockerimages.sh -c x86_64-1.0.0-alpha2 -f x86_64-1.0.0-alpha2 4) Need to test CR 9525 on all environments - Mac confirmed - Linux - RAMESH - Windows (DAVE ENYEART will ask ARNAUD @lehors to test) 5) Getting Started doc for readthedocs (FAB-3925), point to new bootstrap.sh script - NICK will push a CR

dave.enyeart (Thu, 18 May 2017 14:28:41 GMT):
Here’s the FINAL steps for alpha2 release: 1) FAB-2986 / CR 8939 - Issue with maven deploy plugin pushing to staging/deploy/release. As a workaround, Ramesh has pushed the release tarball to nexus /sandbox/logs directory. Not ideal, but good enough for today. CHRIS will talk to Ry about the issue. 2) CR for changing test env image tag - RAMESH 3) FAB-4007/ CR 9525 bootstrap.sh script - CHRIS will make an update for ./download-dockerimages.sh -c x86_64-1.0.0-alpha2 -f x86_64-1.0.0-alpha2 4) Need to test CR 9525 on all environments - Mac confirmed - Linux - RAMESH - Windows (DAVE ENYEART will ask ARNAUD @lehors to test) 5) Getting Started doc for readthedocs (FAB-3925), point to new bootstrap.sh script - NICK will push a CR

dave.enyeart (Thu, 18 May 2017 14:28:41 GMT):
Here’s the FINAL steps for alpha2 release: 1) FAB-2986 / CR 8939 - Issue with maven deploy plugin pushing to staging/deploy/release. As a workaround, Ramesh has pushed the release tarball to nexus https://nexus.hyperledger.org/content/repositories/logs/sandbox/fabric-binary/. Not ideal, but good enough for today. CHRIS will talk to Ry about the issue. 2) CR for changing test env image tag - RAMESH 3) FAB-4007/ CR 9525 bootstrap.sh script - CHRIS will make an update for ./download-dockerimages.sh -c x86_64-1.0.0-alpha2 -f x86_64-1.0.0-alpha2 4) Need to test CR 9525 on all environments - Mac confirmed - Linux - RAMESH - Windows (DAVE ENYEART will ask ARNAUD @lehors to test) 5) Getting Started doc for readthedocs (FAB-3925), point to new bootstrap.sh script - NICK will push a CR

dave.enyeart (Thu, 18 May 2017 14:28:41 GMT):
Here’s the FINAL steps for alpha2 release: 1) FAB-2986 / CR 8939 - Issue with nexus-staging-maven-plugin pushing to staging/deploy/release. As a workaround, Ramesh has pushed the release tarball to nexus https://nexus.hyperledger.org/content/repositories/logs/sandbox/fabric-binary/. Not ideal, but good enough for today. CHRIS will talk to Ry about the issue. 2) CR for changing test env image tag - RAMESH 3) FAB-4007/ CR 9525 bootstrap.sh script - CHRIS will make an update for ./download-dockerimages.sh -c x86_64-1.0.0-alpha2 -f x86_64-1.0.0-alpha2 4) Need to test CR 9525 on all environments - Mac confirmed - Linux - RAMESH - Windows (DAVE ENYEART will ask ARNAUD @lehors to test) 5) Getting Started doc for readthedocs (FAB-3925), point to new bootstrap.sh script - NICK will push a CR

dave.enyeart (Thu, 18 May 2017 14:30:24 GMT):
@weeds @mastersingh24 @cbf @JonathanLevi ^^^^^^

mastersingh24 (Thu, 18 May 2017 14:34:21 GMT):
Thx @dave.enyeart - not perfect but good enough

mastersingh24 (Thu, 18 May 2017 14:36:41 GMT):
BTW - the tarball already includes a script in the /install directory which downloads the right images for any given platform :(

mastersingh24 (Thu, 18 May 2017 14:36:47 GMT):
oh well

mastersingh24 (Thu, 18 May 2017 14:36:59 GMT):
next time

JonathanLevi (Thu, 18 May 2017 14:49:13 GMT):
---

JonathanLevi (Thu, 18 May 2017 14:49:24 GMT):
Let's me try to make it Web 2.0 ready ;-)

JonathanLevi (Thu, 18 May 2017 14:49:24 GMT):
Let me try to make it Web 2.0 ready ;-)

JonathanLevi (Thu, 18 May 2017 14:49:26 GMT):
1. https://jira.hyperledger.org/browse/FAB-3123 @rameshthoomu https://gerrit.hyperledger.org/r/#/c/8939 2. https://jira.hyperledger.org/browse/FAB-4008 @rameshthoomu 3 (+4) . https://jira.hyperledger.org/browse/FAB-4007 https://gerrit.hyperledger.org/r/#/c/9525 @rameshthoomu - LInux @cbf - *download-dockerimages.sh* @dave.enyeart, @lehors: Windows 5. https://jira.hyperledger.org/browse/FAB-3925 Getting Started Guide @nickgaski

dave.enyeart (Thu, 18 May 2017 14:49:56 GMT):
thx

rameshthoomu (Thu, 18 May 2017 14:52:19 GMT):
@dave.enyeart it's the problem with `nexus-staging-maven-plugin` not with maven deploy plugin..

rameshthoomu (Thu, 18 May 2017 14:53:40 GMT):
Problem I mean to say.. existing approach is not working with this plugin.. as a workaround, using maven-deploy plugin published tarball to nexus/logs..

dave.enyeart (Thu, 18 May 2017 14:54:43 GMT):
ok, i edited the list above.

rameshthoomu (Thu, 18 May 2017 15:01:47 GMT):
@mastersingh24 I see VERSION is not updating to alpha2 in get-docker-images.sh.. I ran `make release-all` and verified script.. VERSION is still remains with 1.0.0-alpha

JonathanLevi (Thu, 18 May 2017 15:16:35 GMT):
BTW: Feel free to update the JIRAs/Comment there. We should all watch them!

JonathanLevi (Thu, 18 May 2017 15:16:52 GMT):
(that's why I put the hyperlinks above...)

cbf (Thu, 18 May 2017 15:20:51 GMT):
I've updated https://gerrit.hyperledger.org/r/#/c/9525/

weeds (Thu, 18 May 2017 15:38:22 GMT):
CR number for 4008 is 9529

JonathanLevi (Thu, 18 May 2017 15:38:45 GMT):
They haven't submitted the code to Gerrit yet, so no CRs yet.

weeds (Thu, 18 May 2017 15:41:24 GMT):
I've asked them to update jira-

weeds (Thu, 18 May 2017 15:42:46 GMT):
DAve is asking for +2 on 9525

weeds (Thu, 18 May 2017 15:42:46 GMT):
This means we will go with sandbox link for today

weeds (Thu, 18 May 2017 15:42:54 GMT):
this is Chris' submission

JonathanLevi (Thu, 18 May 2017 15:43:28 GMT):
Merged.

JonathanLevi (Thu, 18 May 2017 15:43:37 GMT):
(thank you Sharon)

weeds (Thu, 18 May 2017 15:44:48 GMT):
this means we will go with the sandbox link for today- https://nexus.hyperledger.org/content/repositories/logs/sandbox/fabric-binary

JonathanLevi (Thu, 18 May 2017 15:45:16 GMT):
Please note that we'd still need to test https://jira.hyperledger.org/browse/FAB-4007 on Windows.... ( @lehors ?), so please let's not close the JIRA

JonathanLevi (Thu, 18 May 2017 15:45:16 GMT):
Please note that we'd still need to test https://jira.hyperledger.org/browse/FAB-4007 on Windows.... ( @lehors ?), so please let's not close the JIRA just yet.

weeds (Thu, 18 May 2017 15:45:24 GMT):
Nick is working on FAB 3925 trying to finish up- he feels in the next 10 minutes

weeds (Thu, 18 May 2017 15:47:41 GMT):
since I haven't seen anything from @lehors I'm trying to see if anyone here can test it out also for us- chasing @JonathanLevi

weeds (Thu, 18 May 2017 15:47:52 GMT):
will let you know

dave.enyeart (Thu, 18 May 2017 15:51:47 GMT):
To summarize:

dave.enyeart (Thu, 18 May 2017 15:51:51 GMT):
1. https://jira.hyperledger.org/browse/FAB-3123 @rameshthoomu https://gerrit.hyperledger.org/r/#/c/8939 Already pushed tarball to https://nexus.hyperledger.org/content/repositories/logs/sandbox/fabric-binary. Therefore this one does not need to be merged today. Ramesh working on improvements for next time around. 2. https://jira.hyperledger.org/browse/FAB-4008 @rameshthoomu https://gerrit.hyperledger.org/r/#/c/9529 Not needed for today. 3 (+4) . https://jira.hyperledger.org/browse/FAB-4007 https://gerrit.hyperledger.org/r/#/c/9525 MERGED - Need a windows test. 5. https://jira.hyperledger.org/browse/FAB-3925 Getting Started Guide @nickgaski will push soon.

weeds (Thu, 18 May 2017 15:52:15 GMT):
Thanks @dave.enyeart

weeds (Thu, 18 May 2017 15:54:01 GMT):
DongMing is going to test right now on Windows

weeds (Thu, 18 May 2017 15:54:07 GMT):
He's just now sitting down and getting started

lehors (Thu, 18 May 2017 16:27:58 GMT):
Sorry guys, I would have been happy to test for you but I'm traveling

dave.enyeart (Thu, 18 May 2017 16:28:18 GMT):
no worries, DongMing is making progress here

lehors (Thu, 18 May 2017 16:29:01 GMT):
Ok

weeds (Thu, 18 May 2017 17:05:45 GMT):
We are still working through Windows at this time- there have to be changed to the script, (environment, volume mount problem)

lehors (Thu, 18 May 2017 17:16:56 GMT):
are we trying to get it to work on bare Windows or with cygwin or equivalent?

lehors (Thu, 18 May 2017 17:17:30 GMT):
I assume the latter

lehors (Thu, 18 May 2017 17:19:40 GMT):
it sucks, I have limited bandwith, otherwise I would try it

nickgaski (Thu, 18 May 2017 17:34:42 GMT):
@here - https://gerrit.hyperledger.org/r/#/c/9537/ - Getting Started

weeds (Thu, 18 May 2017 17:35:50 GMT):
Nick has pushed- Dave said he is reviewing

dave.enyeart (Thu, 18 May 2017 17:53:35 GMT):
It is looking like we won't get Windows working today. I think we could announce alpha2 without it. The windows restriction could be mentioned in the announce, or explicitly in the Getting Started instructions. What do people think?

anik (Thu, 18 May 2017 17:53:39 GMT):
Has joined the channel.

muralisr (Thu, 18 May 2017 18:07:25 GMT):
Also, any changes we make to get windows working would also entail a bit of re-testing on other platforms to make sure they continue to work. Given that, +1 from me so at least other platforms aren't blocked by this

muralisr (Thu, 18 May 2017 18:07:32 GMT):
@dave.enyeart ^^

lehors (Thu, 18 May 2017 18:15:29 GMT):
I think it's fine. I would just mention it in the announce and keep working on fixing it.

lehors (Thu, 18 May 2017 18:16:14 GMT):
I'll be back at my desk tomorrow and could help

mastersingh24 (Thu, 18 May 2017 18:27:30 GMT):
You don't need Cygwin

mastersingh24 (Thu, 18 May 2017 18:27:45 GMT):
You need to do everything through the Docker Quickstart Terminal

mastersingh24 (Thu, 18 May 2017 18:27:51 GMT):
I had this working 2 weeks ago

mastersingh24 (Thu, 18 May 2017 18:28:23 GMT):
On Windows 7 and 10

RistoAlas (Thu, 18 May 2017 18:28:54 GMT):
Hi, regarding the release date of the "V next" release (the one after 1.0), are there any guesses about the date, even rough ones? I am asking because of the hopefully upcoming privacy features, and any date range would be helpful...

odowdaibm (Thu, 18 May 2017 18:32:57 GMT):
Sorry to spam, but I wanted to remind folks of tomorrow's meetings to kick off the documentation workgroup. Here are the charts I'd like to use to start tomorrow's meeting. https://drive.google.com/file/d/0B-n-iLEM1iXrQ1diM0VnZDZIYjQ/view?usp=sharing If you cannot attend, please post comments to the mailing list, and I will include in the agenda; either this time or the next. It's your feedback, proposals, agreement and volunteering that are most important, so please take this chance to take part however you can. Thank you.

weeds (Thu, 18 May 2017 19:51:38 GMT):
@odowdaibm might be useful to post again Anthony on the hyperledger email list. Thanks!

dave.enyeart (Thu, 18 May 2017 20:30:31 GMT):
Update on alpha2 final steps... Final comments for Getting Started doc are being addressed:https://jira.hyperledger.org/browse/FAB-3925 / https://gerrit.hyperledger.org/r/#/c/9537. Once Nick re-pushes it can be +2ed and merged. After that is merged, it will be pushed to readthedocs (I believe automatically), and then we can announce alpha2 and point to Getting Started. We can just mention the windows limitation in the announce, we should be able to fix that in the next couple days since it is just the example scripting on nexus, not code in docker images.

dave.enyeart (Thu, 18 May 2017 20:30:31 GMT):
Update on alpha2 final steps... Final comments for Getting Started doc are being addressed:https://jira.hyperledger.org/browse/FAB-3925 / https://gerrit.hyperledger.org/r/#/c/9537. Once @nickgaski re-pushes it can be +2ed and merged. After that is merged, it will be pushed to readthedocs (I believe automatically), and then we can announce alpha2 and point to Getting Started. We can just mention the windows limitation in the announce, we should be able to fix that in the next couple days since it is just the example scripting on nexus, not code in docker images.

dave.enyeart (Thu, 18 May 2017 20:30:31 GMT):
Update on alpha2 final steps... Final comments for Getting Started doc are being addressed:https://jira.hyperledger.org/browse/FAB-3925 / https://gerrit.hyperledger.org/r/#/c/9537. Once @nickgaski re-pushes it can be +2ed and merged. After that is merged, it will be pushed to readthedocs (I believe automatically), and then we can announce alpha2 (I believe @JonathanLevi will do it) and point to Getting Started. We can just mention the windows limitation in the announce, we should be able to fix that in the next couple days since it is just the example scripting on nexus, not code in docker images.

rameshthoomu (Thu, 18 May 2017 21:36:20 GMT):
We have successfully published fabric-binary tar files to nexus releases URL.. https://nexus.hyperledger.org/content/repositories/releases/org/hyperledger/fabric/fabric-binary/.. I have tested this in linux-amd64 and it worked as expected..

rameshthoomu (Thu, 18 May 2017 21:36:58 GMT):
here is the updated bootstrap script in testing [ ](https://chat.hyperledger.org/channel/ci-pipeline?msg=XhhXjAETKa4qwFw3a) @rameshthoomu

ylsGit (Fri, 19 May 2017 01:15:02 GMT):
Has joined the channel.

guoger (Fri, 19 May 2017 01:35:28 GMT):
Has joined the channel.

dave.enyeart (Fri, 19 May 2017 02:21:05 GMT):
@rameshthoomu I'm adding this to the list of optional todos. See next post...

rameshthoomu (Fri, 19 May 2017 02:21:37 GMT):
ok

dave.enyeart (Fri, 19 May 2017 02:24:01 GMT):
Ok folks, we are very close to being done with alpha2 release activities. The final task is to merge the updated Getting Started instructions, which will update readthedocs. I’ve already +2ed, need another maintainer to +2 and merge: https://jira.hyperledger.org/browse/FAB-3925 https://gerrit.hyperledger.org/r/#/c/9537/ Once that is done then @JonathanLevi can announce alpha2 on the mailing list and point people to Getting Started docs. Also there are some improvements that have been discussed that could be done in the coming days. In an ideal world they would have been done before announce, but at this point they can be done after announce, as to not further delay the announce: https://jira.hyperledger.org/browse/FAB-2986 Parent Story for making release artifacts available (e2e, confixtxgen, cryptogen) https://jira.hyperledger.org/browse/FAB-3123 Build script to package and publish releases to Nexus from CI (https://gerrit.hyperledger.org/r/#/c/8939/) @rameshthoomu https://jira.hyperledger.org/browse/FAB-3122 Add e2e and release binaries to nexus /release location (instead of /logs/sandbox), and point download utilities there @rameshthoomu https://jira.hyperledger.org/browse/FAB-4031 bootstrap.sh should reside at a versioned location instead of an unversioned location

dave.enyeart (Fri, 19 May 2017 02:24:01 GMT):
Ok folks, we are very close to being done with alpha2 release activities. The final task is to merge the updated Getting Started instructions, which will update readthedocs. I’ve already +2ed, need another maintainer to +2 and merge: https://jira.hyperledger.org/browse/FAB-3925 https://gerrit.hyperledger.org/r/#/c/9537/ Once that is done then @JonathanLevi can announce alpha2 on the mailing list and point people to Getting Started docs. Also there are some improvements that have been discussed that could be done in the coming days. In an ideal world they would have been done before announce, but at this point they can be done after announce, as to not further delay the announce: https://jira.hyperledger.org/browse/FAB-2986 Parent Story for making release artifacts available (e2e, confixtxgen, cryptogen). Children subtasks include: https://jira.hyperledger.org/browse/FAB-3123 Build script to package and publish releases to Nexus from CI (https://gerrit.hyperledger.org/r/#/c/8939/) @rameshthoomu https://jira.hyperledger.org/browse/FAB-3122 Add e2e and release binaries to nexus /release location (instead of /logs/sandbox), and point download utilities there @rameshthoomu https://jira.hyperledger.org/browse/FAB-4031 bootstrap.sh should reside at a versioned location instead of an unversioned location https://jira.hyperledger.org/browse/FAB-4032 Fix release scripts for Windows environments

dave.enyeart (Fri, 19 May 2017 02:24:01 GMT):
Ok folks, we are very close to being done with alpha2 release activities. The final task is to merge the updated Getting Started instructions, which will update readthedocs. I’ve already +2ed, need another maintainer to +2 and merge: https://jira.hyperledger.org/browse/FAB-3925 https://gerrit.hyperledger.org/r/#/c/9537/ Once that is done then @JonathanLevi can announce alpha2 on the mailing list and point people to Getting Started docs. Also there are some improvements that have been discussed that could be done in the coming days. In an ideal world they would have been done before announce, but at this point they can be done after announce, as to not further delay the announce: https://jira.hyperledger.org/browse/FAB-2986 Parent Story for making release artifacts available (e2e, confixtxgen, cryptogen). Children subtasks include: >https://jira.hyperledger.org/browse/FAB-3123 Build script to package and publish releases to Nexus from CI (https://gerrit.hyperledger.org/r/#/c/8939/) @rameshthoomu >https://jira.hyperledger.org/browse/FAB-3122 Add e2e and release binaries to nexus /release location (instead of /logs/sandbox), and point download utilities there @rameshthoomu >https://jira.hyperledger.org/browse/FAB-4031 bootstrap.sh should reside at a versioned location instead of an unversioned location >https://jira.hyperledger.org/browse/FAB-4032 Fix release scripts for Windows environments

dave.enyeart (Fri, 19 May 2017 02:24:01 GMT):
Ok folks, we are very close to being done with alpha2 release activities. The final task is to merge the updated Getting Started instructions, which will update readthedocs. I’ve already +2ed, need another maintainer to +2 and merge: https://jira.hyperledger.org/browse/FAB-3925 https://gerrit.hyperledger.org/r/#/c/9537/ Once that is done then @JonathanLevi can announce alpha2 on the mailing list and point people to Getting Started docs. Also there are some improvements that have been discussed that could be done in the coming days. In an ideal world they would have been done before announce, but at this point they can be done after announce, as to not further delay the announce: https://jira.hyperledger.org/browse/FAB-2986 Parent Story for making release artifacts available (e2e, confixtxgen, cryptogen). Children subtasks include: >https://jira.hyperledger.org/browse/FAB-3123 Build script to package and publish releases to Nexus from CI in the future (https://gerrit.hyperledger.org/r/#/c/8939/) @rameshthoomu >https://jira.hyperledger.org/browse/FAB-4031 bootstrap.sh should reside at a versioned location instead of an unversioned location >https://jira.hyperledger.org/browse/FAB-4032 Fix release scripts for Windows environments

dave.enyeart (Fri, 19 May 2017 02:24:01 GMT):
Ok folks, we are very close to being done with alpha2 release activities. The final task is to merge the updated Getting Started instructions, which will update readthedocs. I’ve already +2ed, need another maintainer to +2 and merge: https://jira.hyperledger.org/browse/FAB-3925 https://gerrit.hyperledger.org/r/#/c/9537/ Once that is done then @JonathanLevi can announce alpha2 on the mailing list and point people to Getting Started docs. Also there are some improvements that have been discussed that could be done in the coming days. In an ideal world they would have been done before announce, but at this point they can be done after announce, as to not further delay the announce: https://jira.hyperledger.org/browse/FAB-2986 Parent Story for making release artifacts available (e2e, confixtxgen, cryptogen). Children subtasks include: >https://jira.hyperledger.org/browse/FAB-3122 Add e2e and release binaries to nexus /release location (instead of /logs/sandbox), and point download utilities there @rameshthoomu >https://jira.hyperledger.org/browse/FAB-4032 Fix release scripts for Windows environments >https://jira.hyperledger.org/browse/FAB-3123 Build script to package and publish releases to Nexus from CI in the future (https://gerrit.hyperledger.org/r/#/c/8939/) @rameshthoomu >https://jira.hyperledger.org/browse/FAB-4031 bootstrap.sh should reside at a versioned location instead of an unversioned location

dave.enyeart (Fri, 19 May 2017 02:24:01 GMT):
Ok folks, we are very close to being done with alpha2 release activities. The final task is to merge the updated Getting Started instructions, which will update readthedocs. I’ve already +2ed, need another maintainer to +2 and merge: https://jira.hyperledger.org/browse/FAB-3925 https://gerrit.hyperledger.org/r/#/c/9537/ Once that is done then @JonathanLevi can announce alpha2 on the mailing list and point people to Getting Started docs. Also there are some improvements that have been discussed that could be done in the coming days. In an ideal world they would have been done before announce, but at this point they can be done after announce, as to not further delay the announce: https://jira.hyperledger.org/browse/FAB-2986 Parent Story for making release artifacts available (e2e, confixtxgen, cryptogen). Children subtasks include: >https://jira.hyperledger.org/browse/FAB-3122 Add e2e and release binaries to nexus /release location (instead of /logs/sandbox), and point download utilities there @rameshthoomu >https://jira.hyperledger.org/browse/FAB-4032 Fix release scripts for Windows environments>https://jira.hyperledger.org/browse/FAB-3123 Build script to package and publish releases to Nexus from CI in the future (https://gerrit.hyperledger.org/r/#/c/8939/) @rameshthoomu >https://jira.hyperledger.org/browse/FAB-4031 bootstrap.sh should reside at a versioned location instead of an unversioned location

dave.enyeart (Fri, 19 May 2017 02:24:01 GMT):
Ok folks, we are very close to being done with alpha2 release activities. The final task is to merge the updated Getting Started instructions, which will update readthedocs. I’ve already +2ed, need another maintainer to +2 and merge: https://jira.hyperledger.org/browse/FAB-3925 https://gerrit.hyperledger.org/r/#/c/9537/ Once that is done then @JonathanLevi can announce alpha2 on the mailing list and point people to Getting Started docs. Also there are some improvements that have been discussed that could be done in the coming days. In an ideal world they would have been done before announce, but at this point they can be done after announce, as to not further delay the announce: https://jira.hyperledger.org/browse/FAB-2986 Parent Story for making release artifacts available (e2e, confixtxgen, cryptogen). Children subtasks include: >https://jira.hyperledger.org/browse/FAB-3122 Add e2e and release binaries to nexus /release location (instead of /logs/sandbox), and point download utilities there @rameshthoomu >https://jira.hyperledger.org/browse/FAB-4032 Fix release scripts for Windows environments >https://jira.hyperledger.org/browse/FAB-3123 Build script to package and publish releases to Nexus from CI in the future (https://gerrit.hyperledger.org/r/#/c/8939/) @rameshthoomu >https://jira.hyperledger.org/browse/FAB-4031 bootstrap.sh should reside at a versioned location instead of an unversioned location

dave.enyeart (Fri, 19 May 2017 02:24:01 GMT):
Ok folks, we are very close to being done with alpha2 release activities. The final task is to merge the updated Getting Started instructions, which will update readthedocs. I’ve already +2ed, need another maintainer to +2 and merge: https://jira.hyperledger.org/browse/FAB-3925 https://gerrit.hyperledger.org/r/#/c/9537/ Once that is done then @JonathanLevi can announce alpha2 on the mailing list and point people to Getting Started docs. Also there are some improvements that have been discussed that could be done in the coming days. In an ideal world they would have been done before announce, but at this point they can be done after announce, as to not further delay the announce: https://jira.hyperledger.org/browse/FAB-2986 Parent Story for making release artifacts available (e2e, confixtxgen, cryptogen). Children subtasks include (in priority order): >https://jira.hyperledger.org/browse/FAB-3122 Add e2e and release binaries to nexus /release location (instead of /logs/sandbox), and point download utilities there @rameshthoomu >https://jira.hyperledger.org/browse/FAB-4032 Fix release scripts for Windows environments >https://jira.hyperledger.org/browse/FAB-3123 Build script to package and publish releases to Nexus from CI in the future (https://gerrit.hyperledger.org/r/#/c/8939/) @rameshthoomu >https://jira.hyperledger.org/browse/FAB-4031 bootstrap.sh should reside at a versioned location instead of an unversioned location

dave.enyeart (Fri, 19 May 2017 02:31:45 GMT):
Note - I am traveling on Friday, I'll need somebody else to pick up the shepherd role.

dave.enyeart (Fri, 19 May 2017 02:31:45 GMT):
Note - I am traveling on Friday, I'll be on the 9:30 call, then will need somebody else to pick up the shepherd role.

dave.enyeart (Fri, 19 May 2017 02:31:45 GMT):
Note - I am traveling on Friday-Sunday, I'll be on the 9:30 call, then will need somebody else to pick up the shepherd role.

odowdaibm (Fri, 19 May 2017 04:58:53 GMT):
Hello everyone. If you're online and would like to say hello on the documentation workgroup, then we start in a few minutes

odowdaibm (Fri, 19 May 2017 05:00:07 GMT):
Details on how to join here: https://lists.hyperledger.org/pipermail/hyperledger-fabric/2017-May/000992.html

odowdaibm (Fri, 19 May 2017 05:00:51 GMT):
or just follow this link: https://ibm.zoom.us/my/ajodowd

JonathanLevi (Fri, 19 May 2017 05:15:53 GMT):
Hello Anthony @odowdaibm !

odowdaibm (Fri, 19 May 2017 05:18:28 GMT):
helllo jonathan

Yogendrasri (Fri, 19 May 2017 05:21:36 GMT):
Has joined the channel.

odowdaibm (Fri, 19 May 2017 05:32:54 GMT):
@JonathanLevi it's a bit quiet on our first documentation call. I'm hoping for a few more attendees on the call aimed at NA and Europe!

lehors (Fri, 19 May 2017 05:39:14 GMT):
sorry @odowdaibm difficult time to join a call in the mix of the start-of-day family activities

odowdaibm (Fri, 19 May 2017 05:40:17 GMT):
oh it's not a problem, we're rerunning later. I've taken your philosophical advice - this will take time. It's been short notice for our colleagues in the East and Middle East!

odowdaibm (Fri, 19 May 2017 05:41:24 GMT):
@lehors I'm on for another 20 minutes, and prepared for a good session to fit with NA, SA, and Europe later today - we'll be fine!

lehors (Fri, 19 May 2017 05:42:05 GMT):
sounds good, planning to be on the later call

cca88 (Fri, 19 May 2017 07:31:09 GMT):
Has joined the channel.

JonathanLevi (Fri, 19 May 2017 07:38:20 GMT):
Likewise. Noting that many people are flying today/tomorrow... the attendance rate will certainly pick up.

mastersingh24 (Fri, 19 May 2017 07:46:31 GMT):
hello

mastersingh24 (Fri, 19 May 2017 07:46:34 GMT):
;)

JonathanLevi (Fri, 19 May 2017 08:12:15 GMT):
Good evening ;-)

JonathanLevi (Fri, 19 May 2017 08:12:38 GMT):
Good evening @mastersingh24 ;-)

mastersingh24 (Fri, 19 May 2017 08:24:04 GMT):
:wave:

PhDev (Fri, 19 May 2017 08:36:38 GMT):
Has joined the channel.

lehors (Fri, 19 May 2017 08:50:55 GMT):
having sleep issues gari?

lehors (Fri, 19 May 2017 09:13:40 GMT):
> @mastersingh > You don't need Cygwin > You need to do everything through the Docker Quickstart Terminal Yes, makes sense. That's what I meant by "cygwin or equivalent". The Docker Quickstart Terminal used MinGW

lehors (Fri, 19 May 2017 09:13:40 GMT):
@mastersingh > You don't need Cygwin > You need to do everything through the Docker Quickstart Terminal Yes, makes sense. That's what I meant by "cygwin or equivalent". The Docker Quickstart Terminal used MinGW

mastersingh24 (Fri, 19 May 2017 10:28:59 GMT):
Right - but if you don't use the Quickstart Terminal, then Docker won't work at all ;)

mastersingh24 (Fri, 19 May 2017 10:29:48 GMT):
I'll mess around with it later today - as I mentioned, I built a release package a few weeks back and it work beautifully on Windows. I actually did it just for you @lehors (because I hate Vagrant)

lehors (Fri, 19 May 2017 11:03:13 GMT):
lol

lehors (Fri, 19 May 2017 11:03:33 GMT):
@mastersingh24 I started looking into it and it's a bit of mess

lehors (Fri, 19 May 2017 11:04:47 GMT):
generateArtifacts.sh calls make which is not part of that environment

lehors (Fri, 19 May 2017 11:05:34 GMT):
and boostrap.sh fails right off the bat because uname -s doesn't return what it expects

lehors (Fri, 19 May 2017 11:05:50 GMT):
$ uname -s MINGW64_NT-6.1

lehors (Fri, 19 May 2017 11:06:39 GMT):
and for what it's worth, it returns something different on the same machine using cygwin:

lehors (Fri, 19 May 2017 11:07:01 GMT):
$ uname -s CYGWIN_NT-6.1-WOW

lehors (Fri, 19 May 2017 11:07:39 GMT):
so it's going to take a bit more care to get those scripts running in various environments

dave.enyeart (Fri, 19 May 2017 11:15:04 GMT):
These are the exact windows issues that @dongming @rameshthoomu @muralisr are looking at in https://jira.hyperledger.org/browse/FAB-4032

dongming (Fri, 19 May 2017 11:15:04 GMT):
Has joined the channel.

lehors (Fri, 19 May 2017 11:16:53 GMT):
good to know

lehors (Fri, 19 May 2017 11:16:58 GMT):
I'm happy to help on that

lehors (Fri, 19 May 2017 11:17:15 GMT):
thanks

odowdaibm (Fri, 19 May 2017 11:21:35 GMT):
I put together a proposal to address people's feedback on the Getting Started section in the documentation. Here's a link to it: https://drive.google.com/file/d/0B-n-iLEM1iXrTFdkRV82S0wweWM/view?usp=sharing We might have time to go through on today's doc WG call (1B). I will set up separate meetings so that we can discuss properly whether or not we cover at this meeting.

JonathanLevi (Fri, 19 May 2017 11:47:13 GMT):
@nickgaski, please take a quick glance at my review comments https://gerrit.hyperledger.org/r/#/c/9537...

JonathanLevi (Fri, 19 May 2017 11:48:47 GMT):
As noted, unless you want to upload a quick patchset to fix some of these? Nothing in my review is life-saving, really ;-) I'm happy to merge as is. Please LMK.

JonathanLevi (Fri, 19 May 2017 11:48:47 GMT):
As noted, unless you want to upload a quick patchset to fix some of these (noting that nothing in my review is life-saving, really), I'm happy to merge as is. Please LMK.

JonathanLevi (Fri, 19 May 2017 11:53:19 GMT):
If I don't hear anything, I'm `+2`-ing & merging your work in 8 mins ;-)

lehors (Fri, 19 May 2017 12:12:47 GMT):
so, I got the scripts working but the network fails to start properly

JonathanLevi (Fri, 19 May 2017 12:13:30 GMT):
--- Merged (realized that the "threat" to merge @nickgaski 's good work was not intimidating.

JonathanLevi (Fri, 19 May 2017 12:13:30 GMT):
--- Merged (Realized that the "threat" to merge @nickgaski 's good work was not intimidating)

JonathanLevi (Fri, 19 May 2017 12:13:36 GMT):
@lehors: only on Windows?

lehors (Fri, 19 May 2017 12:13:53 GMT):
well, that's the only platform I have, so yes :)

lehors (Fri, 19 May 2017 12:14:53 GMT):
it's rather ironic that I find myself in that situation by the way because I started my career on unix and only started using windows in 2000

JonathanLevi (Fri, 19 May 2017 12:15:18 GMT):
OK, do you have any idea if it is easy/possible to fix in a matter of hours? (Others will soon wake up and join us, I hope)

lehors (Fri, 19 May 2017 12:15:56 GMT):
ERROR: for orderer.example.com Cannot start service orderer.example.com: oci runtime error: rootfs_linux.go:53: mounting "/mnt/sda1/var/lib/docker/aufs/mnt/233f346f32281d1526d570aa2c866615bd52948c2cb34b916900c455e969683 8/var/hyperledger/orderer/orderer.genesis.block" to rootfs "/mnt/sda1/var/lib/docker/aufs/mnt/233f346f32281d1526d570aa2c866615bd52948c2cb34b916900c455e9696838" caused "not a directory"

JonathanLevi (Fri, 19 May 2017 12:16:06 GMT):
Apparently, real developers work on Windows. I have to stop using Linux and Mac, I know I'm such a light-weight :-)

lehors (Fri, 19 May 2017 12:16:15 GMT):
lol

JonathanLevi (Fri, 19 May 2017 12:16:41 GMT):
"not a directory" !

lehors (Fri, 19 May 2017 12:16:49 GMT):
yeah, what's that about??

lehors (Fri, 19 May 2017 12:17:20 GMT):
this said, maybe the problem comes from generating the artifacts

JonathanLevi (Fri, 19 May 2017 12:17:32 GMT):
OK, here is a thought. Binaries are uploaded, the Getting Started guide is updated. We should report issues on Windows (also) here: https://jira.hyperledger.org/browse/FAB-4032 (and thank you @lehors and everyone helping last night)

JonathanLevi (Fri, 19 May 2017 12:18:08 GMT):
We should try to see whether this can be fixed in a few hours. I am a lightweight who is not using Windows ;-)

JonathanLevi (Fri, 19 May 2017 12:18:08 GMT):
... and try to see whether this can be fixed in a few hours. I am a lightweight who is not using Windows ;-)

lehors (Fri, 19 May 2017 12:18:22 GMT):
I think that's good progress

lehors (Fri, 19 May 2017 12:18:25 GMT):
you should announce alpha2 pointing out the caveat wrt windows

JonathanLevi (Fri, 19 May 2017 12:18:30 GMT):
But we currently have 2 options, try to see if we can fix the Window thing(s) in a few hours.

JonathanLevi (Fri, 19 May 2017 12:18:30 GMT):
But we currently have 2 options, 1. Try to see if we can fix the Window thing(s) in a few hours.

JonathanLevi (Fri, 19 May 2017 12:18:57 GMT):
Exactly, or, announce the alpha2, say in an hour or so, with the caveats.

JonathanLevi (Fri, 19 May 2017 12:18:57 GMT):
Exactly, or, 2. Announce the alpha2, say in an hour or so, with the caveats.

lehors (Fri, 19 May 2017 12:20:29 GMT):
given that the current situation only affects a minor of people (even if it includes some of the best ;-) I think it's reasonable to announce

lehors (Fri, 19 May 2017 12:20:29 GMT):
given that the current situation only affects a minority of people (even if it includes some of the best ;-) I think it's reasonable to announce

lehors (Fri, 19 May 2017 12:21:19 GMT):
of course we wait a bit and see if we could solve the problem

lehors (Fri, 19 May 2017 12:21:19 GMT):
of course we could wait a bit and see if we could solve the problem

lehors (Fri, 19 May 2017 12:21:50 GMT):
but while I can easily fix scripts I have to admit that I'm a bit out of depth with the error I'm seeing now

lehors (Fri, 19 May 2017 12:21:50 GMT):
but while I can easily fix scripts I have to admit that I'm a bit out of my depth with the error I'm seeing now

muralisr (Fri, 19 May 2017 12:22:45 GMT):
@lehors ...the error is to do with mounting volumes (that's what we were stuck at yesterday ...) ?

muralisr (Fri, 19 May 2017 12:22:45 GMT):
@lehors ...the error is to do with mounting volumes on windows (that's what we were stuck at yesterday ...) ?

lehors (Fri, 19 May 2017 12:23:50 GMT):
yeah, that looks like it

joe-alewine (Fri, 19 May 2017 12:27:13 GMT):
Something to keep in mind re: Getting Started. @nickgaski is traveling today. Not sure how much he'll be on, much less be able to work actual fixes to things.

lehors (Fri, 19 May 2017 12:27:40 GMT):
good to know, thanks

JonathanLevi (Fri, 19 May 2017 12:50:49 GMT):
Either way, please everyone who has Windows and faces these, let's report them on that JIRA ticket?

JonathanLevi (Fri, 19 May 2017 12:50:49 GMT):
And yes, @lehors, I mean YOU too ;-)

JonathanLevi (Fri, 19 May 2017 12:50:49 GMT):
----

JonathanLevi (Fri, 19 May 2017 12:50:49 GMT):
Other than this, are we aware of *ANYTHING* else that is new since yesterday, that might affect the announcement of `alpha2` ?

JonathanLevi (Fri, 19 May 2017 12:50:49 GMT):
If so, please let me/us know.

lehors (Fri, 19 May 2017 12:51:40 GMT):
lol

lehors (Fri, 19 May 2017 12:51:51 GMT):
ok, I'm going to

lehors (Fri, 19 May 2017 12:52:30 GMT):
holy smoke

lehors (Fri, 19 May 2017 12:52:36 GMT):
I got the orderer started

lehors (Fri, 19 May 2017 12:53:12 GMT):
there is something funky going on with mounting the genesis block file

lehors (Fri, 19 May 2017 12:53:35 GMT):
I copied the file to another location, change the docker-compose file to point to that new file and it started

lehors (Fri, 19 May 2017 12:56:19 GMT):
it's now running the cli script...

lehors (Fri, 19 May 2017 12:58:26 GMT):
I'm not sure that everything went well but I got to:

lehors (Fri, 19 May 2017 12:58:41 GMT):
←[34mcli |←[0m ←[34mcli |←[0m ===================== All GOOD, End-2-End execution completed =====================

dave.enyeart (Fri, 19 May 2017 13:00:18 GMT):
@JonathanLevi I confirmed Getting Started is live: https://hyperledger-fabric.readthedocs.io/en/latest/getting_started.html I copy/pasted the commands from there to my mac terminal to pull the release artifacts, ran e2e, and everything worked fine: ===================== All GOOD, End-2-End execution completed =====================

dave.enyeart (Fri, 19 May 2017 13:00:39 GMT):
So I'd vote to announce alpha2 with the windows caveat

lehors (Fri, 19 May 2017 13:01:08 GMT):
that's still fine with me but we may be able to fix that windows problem sooner than I thought

lehors (Fri, 19 May 2017 13:13:34 GMT):
so I do have network_setup up going through now

lehors (Fri, 19 May 2017 13:14:00 GMT):
it's silly though, I have to copy the genesis block to a different file to make it work

lehors (Fri, 19 May 2017 13:14:18 GMT):
so, not a complete fix but a workaround

lehors (Fri, 19 May 2017 13:15:16 GMT):
I will document in JIRA (to make @JonathanLevi happy ;-) how far I've gone so far

lehors (Fri, 19 May 2017 13:15:32 GMT):
and will further investigate after

JonathanLevi (Fri, 19 May 2017 13:26:56 GMT):
(As an aside ?) one of the biggest conferences will take place in NYC this Monday with a competition starting tomorrow (Sat-Sun. People are anticipating over 150 developers, some of which, are [ hardcore! ;-)] Windows users. Would be good to have them "covered" if we can.

JonathanLevi (Fri, 19 May 2017 13:26:56 GMT):
*Given the progress and the fact that we will certainly announce today*, I'm happy to wait another hours or two, in case indeed, it may be solved. It is only 6:15am in some places... ;-)

JonathanLevi (Fri, 19 May 2017 13:26:56 GMT):
*Given the progress and the fact that we will certainly announce today*, I'm happy to wait another hour or two, in case indeed, it may be solved. It is only 6:15am in some places... ;-)

JonathanLevi (Fri, 19 May 2017 13:26:56 GMT):
BTW: Is it possible that Rocket Chat is not built on a blockchain? It does feel very order preserving... to me ;-)

JonathanLevi (Fri, 19 May 2017 13:26:56 GMT):
--- BTW: Is it possible that Rocket Chat is not built on a blockchain? It does not feel to be order preserving... to me

aambati (Fri, 19 May 2017 13:40:45 GMT):
Has joined the channel.

RistoAlas (Fri, 19 May 2017 13:56:43 GMT):
risto

lehors (Fri, 19 May 2017 14:03:59 GMT):
lol

lehors (Fri, 19 May 2017 14:04:47 GMT):
so, I have no idea why but apparently the problem has to with the *name* of the file orderer.genesis.block

lehors (Fri, 19 May 2017 14:05:50 GMT):
all I actually have to do is change the name (with mv) and everything works fine

lehors (Fri, 19 May 2017 14:06:30 GMT):
I thought this might have to do with some permission settings (Windows is a source of problems there)

lehors (Fri, 19 May 2017 14:06:45 GMT):
which I was eliminating by creating a copy

lehors (Fri, 19 May 2017 14:06:47 GMT):
but no

lehors (Fri, 19 May 2017 14:06:56 GMT):
just renaming the file fixes the problem...

lehors (Fri, 19 May 2017 14:08:40 GMT):
so what do you guys think? I can certainly patch the code to rename the file and workaround the problem which will make things better for those on Windows, right now

lehors (Fri, 19 May 2017 14:08:56 GMT):
as in: they should be able to get through the getting started doc

lehors (Fri, 19 May 2017 14:09:23 GMT):
but anyone who's going to try and setup their own network may run into the same problem

lehors (Fri, 19 May 2017 14:09:36 GMT):
so we'll need to document

JonathanLevi (Fri, 19 May 2017 14:10:53 GMT):
So either changing the file (pushing a fix to the master branch)... Or a note suggesting that Windows users will need to rename a file?

lehors (Fri, 19 May 2017 14:12:02 GMT):
no, no, the question is: do we want to have such a weird workaround into the code?

JonathanLevi (Fri, 19 May 2017 14:12:11 GMT):
[ Trying to estimate comparing how embarrassing will such a note sound, vs., how much we need to (re) test on other platforms ]

JonathanLevi (Fri, 19 May 2017 14:12:11 GMT):
[ Trying to estimate/compare how embarrassing will such a note sound, vs., how much we need to (re) test on other platforms ]

lehors (Fri, 19 May 2017 14:12:20 GMT):
well, it's only in the script

JonathanLevi (Fri, 19 May 2017 14:12:45 GMT):
For Windows only?

lehors (Fri, 19 May 2017 14:12:47 GMT):
there is no reason this should impact any other platform

lehors (Fri, 19 May 2017 14:13:19 GMT):
on other platforms the change is unnecessary but should be harmless

JonathanLevi (Fri, 19 May 2017 14:13:35 GMT):
Can you please submit a PR ?

lehors (Fri, 19 May 2017 14:13:54 GMT):
I'm sure @dave.enyeart could test on Mac

lehors (Fri, 19 May 2017 14:13:57 GMT):
quickly

lehors (Fri, 19 May 2017 14:14:01 GMT):
I'm working on it! :)

lehors (Fri, 19 May 2017 14:14:30 GMT):
let me do one more test

JonathanLevi (Fri, 19 May 2017 14:14:48 GMT):
Haha. Evidently d.e tests quickly!.

JonathanLevi (Fri, 19 May 2017 14:15:02 GMT):
Thank you @lehors, I'd go for fixing (but let's take a look at the code first), and ask others to try it as well.

JonathanLevi (Fri, 19 May 2017 14:15:05 GMT):
(on Windows)

lehors (Fri, 19 May 2017 14:15:44 GMT):
yup! it doesn't matter where the file is, it's the name

lehors (Fri, 19 May 2017 14:16:11 GMT):
so we just need to use something different from orderer.genesis.block

lehors (Fri, 19 May 2017 14:17:00 GMT):
let me see if I can change it at the time we generate it

lehors (Fri, 19 May 2017 14:17:06 GMT):
that'd be less ugly

JonathanLevi (Fri, 19 May 2017 14:19:15 GMT):
Thanks [, and check globally for any other references? ;-) Sorry, I know I'm not a Windows dev ]

JonathanLevi (Fri, 19 May 2017 14:19:15 GMT):
Thanks [, and check globally for any other references? ;-) Sorry, I know I'm not a Windows dev ! ]

JonathanLevi (Fri, 19 May 2017 14:19:15 GMT):
Thanks [, and check globally for any other references? ;-) Sorry, sorry, I know I'm not a Windows dev! ]

lehors (Fri, 19 May 2017 14:23:25 GMT):
ok, this is wicked but I'm getting closer to a workaround I can live with

lehors (Fri, 19 May 2017 14:24:08 GMT):
if I change generateArtifacts to create the genesis block as genesis.block instead of orderer.genesis.block it works...

lehors (Fri, 19 May 2017 14:59:37 GMT):
@JonathanLevi CR submitted: https://gerrit.hyperledger.org/r/#/c/9567

tmenner (Fri, 19 May 2017 15:00:15 GMT):
Has joined the channel.

nickgaski (Fri, 19 May 2017 15:05:19 GMT):
That's a crazy fix. Does Windows not like two periods in a file name ? I'm mobile at the moment but should be on in 30 minutes or so

lehors (Fri, 19 May 2017 15:16:27 GMT):
@nickgaski yes, it is crazy

lehors (Fri, 19 May 2017 15:16:45 GMT):
it's not the two periods because calling the file orderer.genesis.block2 works!?

lehors (Fri, 19 May 2017 15:17:31 GMT):
so, I'm really at a loss as to what's really going on at the docker level

lehors (Fri, 19 May 2017 15:34:11 GMT):
@dave.enyeart could you please test my CR on Mac/

lehors (Fri, 19 May 2017 15:34:11 GMT):
@dave.enyeart could you please test my CR on Mac?

dave.enyeart (Fri, 19 May 2017 15:41:29 GMT):
@lehors i'll try now

lehors (Fri, 19 May 2017 15:42:06 GMT):
thanks

dave.enyeart (Fri, 19 May 2017 15:54:33 GMT):
@lehors Fix confirmed on mac. I have +2ed.

lehors (Fri, 19 May 2017 15:54:44 GMT):
great. thanks!

dave.enyeart (Fri, 19 May 2017 15:54:46 GMT):
I will merge in five minutes unless somebody objects

dave.enyeart (Fri, 19 May 2017 15:56:09 GMT):
note, we'll need @rameshthoomu to re-push tarball to /logs/sandbox to make this effective

dave.enyeart (Fri, 19 May 2017 15:56:51 GMT):
we could entertain the switch to nexus /release, but i thought that was riskier and would require more cross-platform test, since the folder structure changed a bit

rjones (Fri, 19 May 2017 15:57:26 GMT):
we're not going to be putting tarballs on the logs server again

rameshthoomu (Fri, 19 May 2017 15:57:41 GMT):
did cherry pick on @lehors patch and testing tarballs on windows7

rameshthoomu (Fri, 19 May 2017 15:57:50 GMT):
will let you know the update.

dave.enyeart (Fri, 19 May 2017 15:58:57 GMT):
@rameshthoomu how much cross-platform test has been done on the nexus /release tarball folder structure?

rameshthoomu (Fri, 19 May 2017 15:59:16 GMT):
tested on linux and mac..

dave.enyeart (Fri, 19 May 2017 16:00:56 GMT):
in CR 9567 (or a CR immediately after) we could change bootstrap.sh from nexus /logs/sandbox to nexus /release

dave.enyeart (Fri, 19 May 2017 16:01:05 GMT):
@rameshthoomu what is your confidence level on that?

dave.enyeart (Fri, 19 May 2017 16:09:41 GMT):
I have merged https://gerrit.hyperledger.org/r/#/c/9567/

dave.enyeart (Fri, 19 May 2017 16:09:52 GMT):
I will need to be pushed to nexus to become fully effective

dave.enyeart (Fri, 19 May 2017 16:09:52 GMT):
It will need to be pushed to nexus to become fully effective

dave.enyeart (Fri, 19 May 2017 16:11:03 GMT):
I suggest Ramesh update both nexus /logs/sandbox and /release

rameshthoomu (Fri, 19 May 2017 16:11:11 GMT):
before to that we have to test on platforms with this new patch..

dave.enyeart (Fri, 19 May 2017 16:12:47 GMT):
by default bootstrap.sh will continue to use /logs/sandbox

dave.enyeart (Fri, 19 May 2017 16:13:17 GMT):
if there is confidence in /release, then bootstrap.sh could be updated in a new CR accordingly

dave.enyeart (Fri, 19 May 2017 16:14:11 GMT):
Unfortunately I will not have access this afternoon. @rameshthoomu could you coordinate testing on /release with @lehors help on windows

rameshthoomu (Fri, 19 May 2017 16:15:00 GMT):
yes @rjones mentioned this [ ](https://chat.hyperledger.org/channel/fabric-release?msg=ipDPDdi3eeozYvTz9) @rjones

dave.enyeart (Fri, 19 May 2017 16:15:39 GMT):
it is already on /logs/sandbox, and bootstrap.sh already points to it. we are simply enhancing it there, while also testing on /release

rameshthoomu (Fri, 19 May 2017 16:16:47 GMT):
so better test tar balls on all platforms then push binaries to releases.. once testing is done will submit patch to change URL in bootstrap.sh

JonathanLevi (Fri, 19 May 2017 16:17:38 GMT):
@rameshthoomu, @rjones: fair enough/makes sense. Yes to ^^^, thank you.

JonathanLevi (Fri, 19 May 2017 16:17:38 GMT):
@rameshthoomu, @rjones: fair enough/makes sense.

dave.enyeart (Fri, 19 May 2017 16:18:34 GMT):
sure, @rameshthoomu are you comfortable coordinating test across platforms with @lehors help on windows? or do we need @bmos299 or somebody else involved?

rameshthoomu (Fri, 19 May 2017 16:19:08 GMT):
yes.. I have windows testing on both linux-amd64 and windows7

rameshthoomu (Fri, 19 May 2017 16:19:28 GMT):
will update bootstrap.sh and share it here..

dave.enyeart (Fri, 19 May 2017 16:20:33 GMT):
ok thanks and good luck. please chase down maintainer reviews/approvals while i'm out

dave.enyeart (Fri, 19 May 2017 16:26:37 GMT):
@rameshthoomu please use FAB-3122 so that we keep the books accurate

lehors (Fri, 19 May 2017 17:56:45 GMT):
for those of you curious about the status: the tar file has been updated and I've run the test multiple times successfully

lehors (Fri, 19 May 2017 17:57:00 GMT):
it isn't working for ramesh though

lehors (Fri, 19 May 2017 17:57:24 GMT):
he's one version behind on docker toolbox so he's now upgrading to see if it makes a difference

lehors (Fri, 19 May 2017 17:57:55 GMT):
I'm re-running everything again from scratch, including the download of all the docker images

rameshthoomu (Fri, 19 May 2017 18:01:32 GMT):
Below is the docker configuration on my windows 7 machine ``` docker version 17.03 docker-compose version 1.11 ```

rameshthoomu (Fri, 19 May 2017 18:03:59 GMT):
Here is the updated bootstrap.sh script which pulls new tar ball (still in testing) ``` #!/bin/bash export ARCH=$(uname -s|tr '[:upper:]' '[:lower:]'|sed 's/mingw64_nt.*/windows/')-$(go env GOARCH) echo "====> ${ARCH} " echo RELEASE_VERSION=1.0.0-alpha2 curl https://nexus.hyperledger.org/content/repositories/releases/org/hyperledger/fabric/fabric-binary/${ARCH}-${RELEASE_VERSION}-testing/fabric-binary-${ARCH}-${RELEASE_VERSION}-testing.tar.gz | tar xz cd release/${ARCH} sh download-dockerimages.sh -c $(uname -m)-${RELEASE_VERSION} -f $(uname -m)-${RELEASE_VERSION} ```

lehors (Fri, 19 May 2017 18:07:14 GMT):
so, the test I did from scratch has now passed

lehors (Fri, 19 May 2017 18:08:06 GMT):
but I did get once again an error that seems to happen every now and then (seems fairly rare though)

lehors (Fri, 19 May 2017 18:08:37 GMT):
[msp/identity] Sign -> DEBU 01f Sign: digest: 4C8E323872D0D2E942D9E3B18522087CDBA1973D92C8CEB5062ACCCDA0F370B8 2017/05/19 17:36:26 proto: textWriter unindented too far New state of 'nil' is invalid.

lehors (Fri, 19 May 2017 18:08:52 GMT):
this may not be platform specific at all though

lehors (Fri, 19 May 2017 18:09:00 GMT):
and unfortunately hard to reproduce

JonathanLevi (Fri, 19 May 2017 18:54:59 GMT):
Yes, I suspect so as well. Does look/seem, at first glance, as something more fundamental [ ](https://chat.hyperledger.org/channel/fabric-release?msg=Z7sD7oHixAk8FBDCP)

JonathanLevi (Fri, 19 May 2017 18:56:05 GMT):
BTW: @lehors, thank you vm for all your help and pushing forward (trying to address and fix, rather than release and apologize)...

JonathanLevi (Fri, 19 May 2017 18:58:03 GMT):
I have to say openly that it felt weird (yesterday) to think that we'd give up after @mastersingh24 confirmed that it worked just over a week ago. I'm sure this is not the last issue we'll encounter, yet still... it's much better to try and "fight it".

weeds (Fri, 19 May 2017 18:59:26 GMT):
@jonathanLevi what is left now Jonathan to be able to publish on the channel?

weeds (Fri, 19 May 2017 18:59:26 GMT):
@JonathanLevi what is left now Jonathan to be able to publish alpha2 availability to email? Anything left to check in and merge?

weeds (Fri, 19 May 2017 19:09:30 GMT):
or @cbf

rjones (Fri, 19 May 2017 19:17:24 GMT):
Has left the channel.

cbf (Fri, 19 May 2017 19:22:57 GMT):
Jonathan is about to send

JonathanLevi (Fri, 19 May 2017 19:45:40 GMT):
Should have been out already (airplane's wifi permitting)...

rameshthoomu (Fri, 19 May 2017 19:54:48 GMT):
@lehors we have tested on @harrijk's windows 7 machine and it worked as expected..

rameshthoomu (Fri, 19 May 2017 19:55:44 GMT):
mount is not working on windows 7 machine hence tests are failing..

rameshthoomu (Fri, 19 May 2017 19:55:44 GMT):
mount is not working on my windows 7 machine hence tests are failing..

lehors (Fri, 19 May 2017 20:00:59 GMT):
gee... it's failing on my other windows box

rameshthoomu (Fri, 19 May 2017 20:01:07 GMT):
:(

lehors (Fri, 19 May 2017 20:01:12 GMT):
the bootstrap script!

lehors (Fri, 19 May 2017 20:01:16 GMT):
hold on

rameshthoomu (Fri, 19 May 2017 20:01:19 GMT):
ok

lehors (Fri, 19 May 2017 20:01:57 GMT):
ARCH=windows-386

lehors (Fri, 19 May 2017 20:02:10 GMT):
so it fails to get the tar ball

lehors (Fri, 19 May 2017 20:03:28 GMT):
yes, it's go env GOARCH returns 386 instead of amd64

lehors (Fri, 19 May 2017 20:06:19 GMT):
this is what I meant when I said earlier in the FAB "It is very possible that further tweaking is necessary on different Windows setups."

lehors (Fri, 19 May 2017 20:06:37 GMT):
there are so many possible variations

lehors (Fri, 19 May 2017 20:08:34 GMT):
is that because I have a 32bit go installed on that machine? I think so...

lehors (Fri, 19 May 2017 20:09:27 GMT):
it's a small laptop so I've been installing 32bit versions to try and use less memory

lehors (Fri, 19 May 2017 20:09:38 GMT):
should it matter though?

rameshthoomu (Fri, 19 May 2017 20:12:33 GMT):
ok what are the next steps? Shall I publish latest binaries to releases URL and submit patches to update bootstrap.sh and getting-started.rst ?

lehors (Fri, 19 May 2017 20:12:55 GMT):
I think you should anyway

lehors (Fri, 19 May 2017 20:13:03 GMT):
this is still better than if you don't

lehors (Fri, 19 May 2017 20:13:13 GMT):
but it's clearly not the end of that story

rameshthoomu (Fri, 19 May 2017 20:17:00 GMT):
yes agree with you but at least it worked on 2 machines out of 3

lehors (Fri, 19 May 2017 20:17:14 GMT):
yes

lehors (Fri, 19 May 2017 20:17:30 GMT):
which is why I said it's still better

lehors (Fri, 19 May 2017 20:18:44 GMT):
one question I have to the maintainers (@cbf, @JonathanLevi) is that something we can change again as we improve on it or do we have to stick with what we have until the next release?

rameshthoomu (Fri, 19 May 2017 20:22:29 GMT):
I have tested and verified latest tarballs [ ](https://chat.hyperledger.org/channel/fabric-release?msg=2r6bggnAdP25HwcD9) @rameshthoomu on `darwin`, `linux-amd64`, `windows (tested on 4 machines but worked on 2)` and `linux-s390x`..

rameshthoomu (Fri, 19 May 2017 20:22:29 GMT):
tested and verified latest tarballs [ ](https://chat.hyperledger.org/channel/fabric-release?msg=2r6bggnAdP25HwcD9) @rameshthoomu on `darwin`, `linux-amd64`, `windows (tested on 4 machines but worked on 2)` and `linux-s390x`..

lehors (Fri, 19 May 2017 20:24:04 GMT):
why are we relying on go env GOARCH?

lehors (Fri, 19 May 2017 20:51:38 GMT):
and why is fabric-couchdb installed as part of getting started when it's only an option?

lehors (Fri, 19 May 2017 20:51:55 GMT):
on a small machine every bit counts...

lehors (Fri, 19 May 2017 20:52:37 GMT):
admittedly small machines aren't our primary target but it doesn't hurt to keep it easy to run on those machines too

lehors (Fri, 19 May 2017 20:53:33 GMT):
waiting for that image to download when I have no plan to use it isn't very nice

lehors (Fri, 19 May 2017 20:54:49 GMT):
ok, I'll stop whining for now :)

nickgaski (Fri, 19 May 2017 21:14:51 GMT):
arnaud sir, you're not the first to pose the couch question. It's a cool feature but I'm going to remove it from getting started and link to it elsewhere

nickgaski (Fri, 19 May 2017 21:15:18 GMT):
those containers gobble up quite a bit of compute (especially since every peer has one)

lehors (Fri, 19 May 2017 21:17:26 GMT):
@rameshthoomu good news: I passed the test on my second machine

lehors (Fri, 19 May 2017 21:17:46 GMT):
but so, I really want to know why we use this 'go env GOARCH'

nickgaski (Fri, 19 May 2017 21:19:13 GMT):
I don't have the answer on that one. perhaps ramesh or ratnakar

nickgaski (Fri, 19 May 2017 21:19:16 GMT):
or chris

lehors (Fri, 19 May 2017 21:20:00 GMT):
and by the way, this assumes go is installed to go through getting-started

lehors (Fri, 19 May 2017 21:20:22 GMT):
do we have anything else in there that actually requires go for this first steps?

lehors (Fri, 19 May 2017 21:21:07 GMT):
I understand that someone would probably want to install go eventually anyway but maybe in the spirit of making it easier for someone to get started we could avoid that dependency?

lehors (Fri, 19 May 2017 21:21:45 GMT):
getting started is all about docker images and scripts

lehors (Fri, 19 May 2017 21:22:08 GMT):
it seems silly to require go just to go env GOARCH which evidently falls on its face anyway

lehors (Fri, 19 May 2017 21:22:28 GMT):
I will document my finding on the JIRA...

rameshthoomu (Fri, 19 May 2017 21:29:31 GMT):
ok that's good news.. @lehors

rameshthoomu (Fri, 19 May 2017 21:30:06 GMT):
Will wait for @cbf @JonathanLevi inputs on this [ ](https://chat.hyperledger.org/channel/fabric-release?msg=5SzBzPcjwJA8w33wG) @lehors

lehors (Fri, 19 May 2017 21:30:32 GMT):
yep

lehors (Fri, 19 May 2017 21:30:53 GMT):
do you know why go env GOARCH is used?

cbf (Fri, 19 May 2017 21:31:28 GMT):
it predated my involvement

cbf (Fri, 19 May 2017 21:31:49 GMT):
we could use something else I suppose

lehors (Fri, 19 May 2017 21:31:59 GMT):
like uname? :)

lehors (Fri, 19 May 2017 21:32:06 GMT):
which is already used anyway!

rameshthoomu (Fri, 19 May 2017 21:32:26 GMT):
may be to match with this https://github.com/hyperledger/fabric/blob/master/Makefile#L284 line

lehors (Fri, 19 May 2017 21:33:09 GMT):
I see, so now we can blame @greg.haskins ? ;-)

cbf (Fri, 19 May 2017 21:33:48 GMT):
I suspect that it has to do with the way the go was compiled for the given platform

greg.haskins (Fri, 19 May 2017 21:33:52 GMT):
release target is @mastersingh24 's handiwork

cbf (Fri, 19 May 2017 21:34:05 GMT):
that guy is a loser

lehors (Fri, 19 May 2017 21:34:09 GMT):
oh, even better! :)

lehors (Fri, 19 May 2017 21:34:10 GMT):
lol

greg.haskins (Fri, 19 May 2017 21:34:32 GMT):
but I understand why its there

greg.haskins (Fri, 19 May 2017 21:34:41 GMT):
he allows you to build cross-compiled binaries

lehors (Fri, 19 May 2017 21:39:54 GMT):
in this case we're not even consistent

lehors (Fri, 19 May 2017 21:40:12 GMT):
because generateArtifacts uses uname -m

lehors (Fri, 19 May 2017 21:40:23 GMT):
so we might as well use that in both places

lehors (Fri, 19 May 2017 21:42:54 GMT):
so generateArtifacts uses this command to determine the ARCH

lehors (Fri, 19 May 2017 21:43:40 GMT):
echo "$(uname -s|tr '[:upper:]' '[:lower:]'|sed 's/mingw64_nt.*/windows/')-$(uname -m | sed 's/x86_64/amd64/g')" | awk '{print tolower($0)}'

lehors (Fri, 19 May 2017 21:44:02 GMT):
why don't we use the exact same command in bootstrap.sh?? @rameshthoomu

lehors (Fri, 19 May 2017 21:44:58 GMT):
can one of you guys on mac or linux tell me if it returns something different from what is done now:

lehors (Fri, 19 May 2017 21:45:21 GMT):
echo "$(uname -s|tr [:upper:] [:lower:]|sed s/mingw64_nt.*/windows/)-$(go env GOARCH)"

lehors (Fri, 19 May 2017 21:45:49 GMT):
the latter doesn't work for my case

lehors (Fri, 19 May 2017 21:46:01 GMT):
the former works on both of my windows boxes

rameshthoomu (Fri, 19 May 2017 21:49:58 GMT):
Checking on Linux-amd64

lehors (Fri, 19 May 2017 21:53:14 GMT):
so?

rameshthoomu (Fri, 19 May 2017 21:53:33 GMT):
linux-amd64.. worked..

rameshthoomu (Fri, 19 May 2017 21:53:39 GMT):
testing on mac

lehors (Fri, 19 May 2017 21:53:49 GMT):
thanks

rameshthoomu (Fri, 19 May 2017 21:59:10 GMT):
on mac darwin-amd64

lehors (Fri, 19 May 2017 21:59:50 GMT):
but you could just run that one command and if it returns the same, we're good

rameshthoomu (Fri, 19 May 2017 22:00:24 GMT):
which command ?

lehors (Fri, 19 May 2017 22:00:36 GMT):
the echo command

rameshthoomu (Fri, 19 May 2017 22:00:49 GMT):
I have executed this `echo "$(uname -s|tr '[:upper:]' '[:lower:]'|sed 's/mingw64_nt.*/windows/')-$(uname -m | sed 's/x86_64/amd64/g')" | awk '{print tolower($0)}' `

lehors (Fri, 19 May 2017 22:00:57 GMT):
ok

lehors (Fri, 19 May 2017 22:02:53 GMT):
and by the way, evidently this uses two different ways of changing a string to lowercase :)

lehors (Fri, 19 May 2017 22:03:22 GMT):
I don't know who's to blame for this but we can ignore it for now

lehors (Fri, 19 May 2017 22:15:00 GMT):
if it were up to me I would use the power of bash to make all those substitutions rather than sed, awk, tr, etc.

lehors (Fri, 19 May 2017 22:15:37 GMT):
it takes a few more lines of code but it's all run by bash directly without spawning off a bunch of execs

lehors (Fri, 19 May 2017 22:16:20 GMT):
in view of everything else it's not an optimization that matters but it's a style issue :)

lehors (Fri, 19 May 2017 22:26:13 GMT):
ok, I couldn't resist. I used to love write bash scripts...: S=`uname -s`;S=${S,,};S=${S/mingw64_nt*/windows} M=`uname -m`;M=${M,,};M=${M/x86_64/amd64} echo $S-$M

lehors (Fri, 19 May 2017 22:26:13 GMT):
ok, I couldn't resist. I used to love writing bash scripts...: S=`uname -s`;S=${S,,};S=${S/mingw64_nt*/windows} M=`uname -m`;M=${M,,};M=${M/x86_64/amd64} echo $S-$M

lehors (Fri, 19 May 2017 22:26:19 GMT):
that's how it's done :-D

lehors (Fri, 19 May 2017 22:28:08 GMT):
anyway, it's past midnight here so I'm going to leave it at that for tonight

lehors (Fri, 19 May 2017 22:28:45 GMT):
@rameshthoomu I think you should update the bootscript with that new command to set ARCH

lehors (Fri, 19 May 2017 22:28:45 GMT):
@rameshthoomu I think you should update the bootstrap script with that new command to set ARCH

lehors (Fri, 19 May 2017 22:29:24 GMT):
take care everybody

bmkor (Sat, 20 May 2017 03:48:08 GMT):
Has joined the channel.

lehors (Sat, 20 May 2017 07:52:35 GMT):
I submitted a new CR to address the issue I had on my second Windows machine: https://gerrit.hyperledger.org/r/#/c/9601/

lehors (Sat, 20 May 2017 08:09:38 GMT):
it uses the same command used in generateArtifacts.sh which is proven to work even though it begs for simplification

nickgaski (Sat, 20 May 2017 17:50:11 GMT):
https://gerrit.hyperledger.org/r/#/c/9619/ - URGENT

nickgaski (Sat, 20 May 2017 17:50:59 GMT):
@here ^^ - bootstrap.sh fails because tarballs are in a new location now. shocker

lehors (Sat, 20 May 2017 18:08:37 GMT):
There is nothing wrong with bootstrap.sh (well, theré is but that's irrelevant here)

lehors (Sat, 20 May 2017 18:09:37 GMT):
The problem is that the tarballs have not been uploaded at the right place

lehors (Sat, 20 May 2017 18:10:48 GMT):
Who can do it other than @rameshthoomu who's not around?

rameshthoomu (Sat, 20 May 2017 18:13:45 GMT):
Why in new location..

rameshthoomu (Sat, 20 May 2017 18:14:00 GMT):
Sorry I am on the way

rameshthoomu (Sat, 20 May 2017 18:16:01 GMT):
@lehors I did t push to releases URL.. keep it there

rameshthoomu (Sat, 20 May 2017 18:16:20 GMT):
Or do you want me to push to releases. Didn't get any confirmation

nickgaski (Sat, 20 May 2017 18:19:57 GMT):
ok well let's fix one of these issues. either we fix the bootstrap script with my CR or we leave bootstrap and get Ramesh's patch merged. Right now it doesn't work. FWIW my CR fixes it

lehors (Sat, 20 May 2017 18:22:58 GMT):
I think your cr is the wrong fix, sorry

lehors (Sat, 20 May 2017 18:24:05 GMT):
@rameshthoomu needs to finish the release by posting the tarballs at the right URLs

lehors (Sat, 20 May 2017 18:24:22 GMT):
Please ramesh go ahead

lehors (Sat, 20 May 2017 18:25:02 GMT):
No offense nick

nickgaski (Sat, 20 May 2017 18:40:51 GMT):
I think I agree Arnaud, no offense taken. I guess we just monitor these channels in the meantime and help folks

nickgaski (Sat, 20 May 2017 18:42:23 GMT):
ramesh can fix in about two hours he said

rameshthoomu (Sat, 20 May 2017 18:46:32 GMT):
Working on this. Once done will let you know.

cbf (Sat, 20 May 2017 19:13:53 GMT):
@lehors can you please test https://gerrit.hyperledger.org/r/#/c/9619/ on windoze?

cbf (Sat, 20 May 2017 19:14:19 GMT):
wait, are these conflicting?

cbf (Sat, 20 May 2017 19:15:43 GMT):
if https://gerrit.hyperledger.org/r/#/c/9619/ is incorrect then LMK ASAP and I will -2

cbf (Sat, 20 May 2017 19:15:51 GMT):
@nickgaski

rameshthoomu (Sat, 20 May 2017 19:17:07 GMT):
Nick you can remove -testing from the link

nickgaski (Sat, 20 May 2017 19:39:48 GMT):
can we take a look at 9619 and +2 again

nickgaski (Sat, 20 May 2017 19:43:21 GMT):
@lehors - can you test on windows please. https://gerrit.hyperledger.org/r/#/c/9619/

rameshthoomu (Sat, 20 May 2017 19:45:24 GMT):
Tested in Linux-amd64 and it's working

lehors (Sat, 20 May 2017 19:47:31 GMT):
sorry guys, boy now in bed, let me try

nickgaski (Sat, 20 May 2017 19:48:20 GMT):
I grabbed your patch and tested on top of it Arnaud

nickgaski (Sat, 20 May 2017 19:48:24 GMT):
looks good

lehors (Sat, 20 May 2017 19:48:38 GMT):
thanks

lehors (Sat, 20 May 2017 19:50:48 GMT):
has the getting-started doc been updated now? @rameshthoomu

lehors (Sat, 20 May 2017 19:51:30 GMT):
it doesn't look like it

nickgaski (Sat, 20 May 2017 19:52:33 GMT):
it doesn't need to change

rameshthoomu (Sat, 20 May 2017 19:52:36 GMT):
@nickgaski What is the final patch..could you pls share here..

nickgaski (Sat, 20 May 2017 19:52:49 GMT):
the bootstrap.sh patch should solve our problem

nickgaski (Sat, 20 May 2017 19:53:00 GMT):
https://gerrit.hyperledger.org/r/#/c/9619

rameshthoomu (Sat, 20 May 2017 19:53:09 GMT):
Ok

rameshthoomu (Sat, 20 May 2017 19:53:58 GMT):
LGTM

rameshthoomu (Sat, 20 May 2017 19:54:21 GMT):
If you submit another remove docker images command

rameshthoomu (Sat, 20 May 2017 19:54:30 GMT):
Another patch

nickgaski (Sat, 20 May 2017 19:55:15 GMT):
oh you mean don't list the images out

rameshthoomu (Sat, 20 May 2017 19:56:29 GMT):
Yes I am doing that from download docker images script

rameshthoomu (Sat, 20 May 2017 19:59:11 GMT):
LGTM now

lehors (Sat, 20 May 2017 20:00:11 GMT):
ok, I'm confused

lehors (Sat, 20 May 2017 20:00:37 GMT):
curl -sS https://raw.githubusercontent.com/hyperledger/fabric/master/examples/e2e_cli/bootstrap.sh | bash doesn't work for me

lehors (Sat, 20 May 2017 20:01:04 GMT):
it wants to fetch https://nexus.hyperledger.org/content/repositories/logs/sandbox/fabric-binary/windows-amd64-1.0.0-alpha2.tar.gz which doesn't exist

rameshthoomu (Sat, 20 May 2017 20:01:54 GMT):
Yes.. doc is still referring sandbox

lehors (Sat, 20 May 2017 20:02:12 GMT):
ok, so the doc does need fixing

lehors (Sat, 20 May 2017 20:02:15 GMT):
that's what I thought

rameshthoomu (Sat, 20 May 2017 20:03:00 GMT):
Once 9619 is merged it automatically pull from releases url

rameshthoomu (Sat, 20 May 2017 20:03:11 GMT):
No fix needed in doc

lehors (Sat, 20 May 2017 20:03:45 GMT):
ok

lehors (Sat, 20 May 2017 20:04:21 GMT):
do we have 2 maintainers to get the merge in?

lehors (Sat, 20 May 2017 20:07:56 GMT):
sorry, I don't know what you want me to test right now

lehors (Sat, 20 May 2017 20:08:58 GMT):
as a side note, we'll need to improve on those scripts so when something goes wrong people get more helpful error messages

lehors (Sat, 20 May 2017 20:09:12 GMT):
but we can look into that next, once that fire is out

rameshthoomu (Sat, 20 May 2017 20:09:41 GMT):
Yes will optimize later.

nickgaski (Sat, 20 May 2017 20:09:58 GMT):
the doc DOES NOT need fixing. the bootstrap.sh needs fixing :)

rameshthoomu (Sat, 20 May 2017 20:10:14 GMT):
😉

nickgaski (Sat, 20 May 2017 20:10:18 GMT):
let me go get jonathan and gari

rameshthoomu (Sat, 20 May 2017 20:10:49 GMT):
Inform Chris also

lehors (Sat, 20 May 2017 20:13:52 GMT):
ok, I'm around and ready to test as soon as the patch is merged

JonathanLevi (Sat, 20 May 2017 20:14:59 GMT):
https://gerrit.hyperledger.org/r/#/c/9619/ is merged.

JonathanLevi (Sat, 20 May 2017 20:15:29 GMT):
Thanks everyone ( even @mastersingh24 included ) !

rameshthoomu (Sat, 20 May 2017 20:23:07 GMT):
Thanks @JonathanLevi

lehors (Sat, 20 May 2017 20:31:34 GMT):
ok, it worked on one of my windows box

lehors (Sat, 20 May 2017 20:31:34 GMT):
ok, it worked on one of my windows boxes

lehors (Sat, 20 May 2017 20:33:48 GMT):
hmm, it's failing on the second one for some reason

lehors (Sat, 20 May 2017 20:34:02 GMT):
it's independent of the scripts though

lehors (Sat, 20 May 2017 20:34:08 GMT):
my env may not be clean

lehors (Sat, 20 May 2017 20:35:48 GMT):
yeah, it's running now

lehors (Sat, 20 May 2017 20:35:56 GMT):
I had some containers still running

lehors (Sat, 20 May 2017 20:37:04 GMT):
@nickgaski you were right: the doc DID NOT fixing ;-)

lehors (Sat, 20 May 2017 20:37:04 GMT):
@nickgaski you were right: the doc DID NOT need fixing ;-)

lehors (Sat, 20 May 2017 20:37:20 GMT):
ok, test on second box passed

lehors (Sat, 20 May 2017 20:37:27 GMT):
so 2/2 for me!

lehors (Sat, 20 May 2017 20:40:09 GMT):
we still have some crap in the tarballs that is going to confuse people

lehors (Sat, 20 May 2017 20:40:48 GMT):
there is an older version of bootstrap.sh and install/get-docker-images.sh

lehors (Sat, 20 May 2017 20:41:07 GMT):
I don't even think those files should be in there at all

lehors (Sat, 20 May 2017 20:41:26 GMT):
but at least now if people follow the doc it should work

rameshthoomu (Sat, 20 May 2017 20:44:01 GMT):
Yes tar ball is pushed before patch merge.. so for now will leave as is..

lehors (Sat, 20 May 2017 20:46:33 GMT):
I think that's ok

lehors (Sat, 20 May 2017 20:46:46 GMT):
now that the main fire is out we can start working on polishing things

rameshthoomu (Sat, 20 May 2017 20:48:45 GMT):
Yes.. thanks @lehors @nickgaski Have a good weekend

lehors (Sat, 20 May 2017 20:48:55 GMT):
you too

Calvin_Heo (Mon, 22 May 2017 02:54:14 GMT):
Has joined the channel.

baohua (Wed, 24 May 2017 14:09:16 GMT):
Has left the channel.

odowdaibm (Wed, 24 May 2017 19:49:42 GMT):
@here A reminder that we're having the regular Documentation Workgroup call on Friday: Details here: https://lists.hyperledger.org/pipermail/hyperledger-fabric/2017-May/001051.html Proposals are here: https://drive.google.com/open?id=0B-n-iLEM1iXrWk9WWERhaHVyeWc Read and comment on mailing list if you cannot make it. Thank you!

lehors (Thu, 25 May 2017 13:16:23 GMT):
@rameshthoomu why do we use x64_64 in the name of the docker images but windows-amd64 in the name of the tarball?

lehors (Thu, 25 May 2017 13:16:23 GMT):
@rameshthoomu why do we use x86_64 in the name of the docker images but windows-amd64 in the name of the tarball?

rameshthoomu (Thu, 25 May 2017 13:22:14 GMT):
We use ARCH (uname -m) while building docker images but in make release-all we are using ``` release/%-amd64: DOCKER_ARCH=x86_64 release/%-amd64: GOARCH=amd64 ```

rameshthoomu (Thu, 25 May 2017 13:22:14 GMT):
We use ARCH (uname -m) while building docker images but in make release-all we are using GOARCH ``` release/%-amd64: DOCKER_ARCH=x86_64 release/%-amd64: GOARCH=amd64 ```

lehors (Thu, 25 May 2017 13:24:07 GMT):
I have to admit not to understand if there is a meaningful difference between the two names but for our purpose it would seem better to settle on name or the other and use it throughout

rameshthoomu (Thu, 25 May 2017 13:25:54 GMT):
agree..

shaih (Thu, 25 May 2017 14:01:36 GMT):
Has joined the channel.

dave.enyeart (Thu, 25 May 2017 14:06:37 GMT):
agree, which name would you prefer to go with @rameshthoomu and @lehors? Seems`uname -m` would be the better consistent choice?

lehors (Thu, 25 May 2017 14:07:05 GMT):
yes, that'd be my preference

lehors (Thu, 25 May 2017 14:07:20 GMT):
because it also means we don't depend on Go for that

dave.enyeart (Thu, 25 May 2017 14:09:20 GMT):
exactly

lehors (Thu, 25 May 2017 14:09:30 GMT):
I understand @mastersingh24 uses go env GOARCH in Makefile to support cross-platform compilation, which may be fine there but other than that we should stick to using uname

dave.enyeart (Thu, 25 May 2017 14:09:54 GMT):
@rameshthoomu can you create a Jira item to make that change?

lehors (Thu, 25 May 2017 14:10:42 GMT):
I can do that

mastersingh24 (Thu, 25 May 2017 14:19:27 GMT):
Please do not change the Makefile

mastersingh24 (Thu, 25 May 2017 14:20:54 GMT):
This is why things end up all messed up

lehors (Thu, 25 May 2017 14:40:34 GMT):
hi Gari, what does "This" refer to in your statement?

lehors (Thu, 25 May 2017 14:40:34 GMT):
@mastersingh24 hi Gari, what does "This" refer to in your statement?

xchen1130 (Thu, 25 May 2017 16:23:21 GMT):
Has joined the channel.

mastersingh24 (Fri, 26 May 2017 08:50:35 GMT):
@lehors - it was not obvious ;)

mastersingh24 (Fri, 26 May 2017 08:51:10 GMT):
Seriously, we make too many uncoordinated changes and for example at the hackfest the bootstrap script was pulling the wrong URLs

mastersingh24 (Fri, 26 May 2017 08:52:12 GMT):
It may seem silly, but even changing naming conventions has far reaching consequences

mastersingh24 (Fri, 26 May 2017 08:52:39 GMT):
And when people make changes without understanding why things were done the way they were, we end up with issues

louismyu (Fri, 26 May 2017 22:55:10 GMT):
Has joined the channel.

rickr (Sat, 27 May 2017 12:59:34 GMT):
@cbf @mastersingh24 @jimthematrix @weeds I've gotten both publicly and privately people stating the the java sdk will not make V1. Now I'm not saying there aren't challenges and surely its not a guarantee but I'm getting the _impression_ given that input that decision has been made.

mastersingh24 (Sat, 27 May 2017 13:06:23 GMT):
@rickr - not sure what "not make v1" would actually mean ;) I think it comes down to being able to put out a v1.0.0 version when it's ready to go. It could be the same exact time as the fabric runtime or it could be slightly after. I think it all comes down to feeling it is solid and ready to go

rickr (Sat, 27 May 2017 13:14:42 GMT):
Well fine. I guess it depends on your perspective. Being on the SDK end and having people pointing to it as the source of their problems when it actually the Fabric and from it's logs error messages maks it almost impossible except for someone that knows logic intimately (the developer that wrote the code) to figure out what is wrong I guess I have my concerns about it too then.

rickr (Sat, 27 May 2017 13:14:42 GMT):
Well fine. I guess it depends on your perspective. Being on the SDK end and having people pointing to it as the source of their problems when it actually the Fabric and from it's logs error messages makes it almost impossible except for someone that knows logic intimately (the developer that wrote the code) to figure out what is wrong I guess I have my concerns about it too then.

cbf (Sat, 27 May 2017 18:34:58 GMT):
@rickr no one has ever said that to my knowledge

cbf (Sat, 27 May 2017 18:36:20 GMT):
we have been debating whether Java CC will be included. Right now it is disabled. There is discussion as to whether or not to make it optionally enabled, which I tend to think would be a mistake as it would only invite people to try it and then have issues or questions

bmalavan (Sat, 27 May 2017 20:08:50 GMT):
Has joined the channel.

raasiel (Sun, 28 May 2017 11:54:04 GMT):
Has joined the channel.

lehors (Mon, 29 May 2017 12:41:41 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-release?msg=bcHwMcG3uN5zXfJme) @mastersingh24 I agree and totally understand your concern. I don't think anybody is talking about making any changes without coordination though. Which is why I pinged you, as a matter of fact

lehors (Mon, 29 May 2017 12:42:24 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-release?msg=RpobHLJw9h4rwxwDG) @mastersingh24

lehors (Mon, 29 May 2017 12:42:24 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-release?msg=RpobHLJw9h4rwxwDG) @mastersingh24 I agree and understand your concern. I don't think anybody is suggesting changing this without coordination. This is why I pinged you as a matter of fact.

lehors (Mon, 29 May 2017 12:48:08 GMT):
Is there a reason to use a mix of amd64 and x86_64? or is it merely accidental because we use a mix of goenv GOARCH and uname -ml?

mastersingh24 (Mon, 29 May 2017 15:01:07 GMT):
@lehors - yeah - sorry - was on the road and frustrated about a few things that had been happening

mastersingh24 (Mon, 29 May 2017 15:01:40 GMT):
it's really accidental in the sense that cross compiling uses amd64 due to GOARCH

mastersingh24 (Mon, 29 May 2017 15:02:08 GMT):
I really wish Docker supported repo's based on arch

lehors (Mon, 29 May 2017 15:09:03 GMT):
did you see that there is an extra twist with go env GOARCH in that on Windows it returns different values depending on whether you have a 32bit or 64bit install

lehors (Mon, 29 May 2017 15:09:08 GMT):
on the same machine

lehors (Mon, 29 May 2017 15:10:47 GMT):
so the question is can we settle on a single name?

lehors (Mon, 29 May 2017 15:11:07 GMT):
and which one

lehors (Mon, 29 May 2017 15:12:12 GMT):
we'll have to work around the differences one way or another to use the same across the board

lehors (Mon, 29 May 2017 15:44:36 GMT):
I will go ahead and create a JIRA ticket for this, and we can discuss there the best route

mastersingh24 (Mon, 29 May 2017 22:00:50 GMT):
I don't see any reason to support 32bit Windows anyway

rickr (Mon, 29 May 2017 22:31:56 GMT):
But DOS is a must!

joe-alewine (Tue, 30 May 2017 05:08:24 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-release?msg=mJFj6bsH6oMx4Ns5M) @mastersingh24 This is something I've been wondering for a while. What percentage of Fabric users (or users of blockchain tech in general) have a 32 bit Windows system? I mean, I can understand that big banks will not be on tech that old, but one of the most common use cases we talk about is supply chains, which potentially involves many dozens of computers in warehouses and ports around the world. Do we have a sense of how many of *those* computers are 32 bit Windows systems? I mean, Microsoft does keep releasing every new operating system in a 32 bit format for a reason -- they have 10s of millions users with old systems that can't support a 64 bit OS. And while I understand that a lot of those people aren't likely to be joining a blockchain network any time soon, it is something I've wondered about, especially in the supply chain use case I mentioned.

K Sai Anirudh (Tue, 30 May 2017 08:40:08 GMT):
Has joined the channel.

mastersingh24 (Tue, 30 May 2017 09:58:18 GMT):
Guess I should have been more clear - both Docker Toolbox and Docker for Windows only support 64bit platforms

cbf (Tue, 30 May 2017 14:58:14 GMT):
https://chat.hyperledger.org/channel/fabric-maintainers?msg=7EZm6bi5GoJLgWZWu

akshay.lawange (Wed, 31 May 2017 06:25:51 GMT):
Has joined the channel.

cbf (Thu, 01 Jun 2017 13:10:25 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-release?msg=qTFwJ5rzfcE2xq3X2) @joe-alewine Joe, I started tracking downloads of the Getting Started bundle here https://goo.gl/#analytics/goo.gl/NIKLiU/all_time as you can see, Windows seems to be the predominant platform, at least for the download... that of course does not necessarily mean that is where they're deploying (I suspect many are using a cloud hosting provider)

cbf (Thu, 01 Jun 2017 13:11:29 GMT):
As @mastersingh24 mentioned, there is no reason to support Win 32 because it isn't supported by Docker for Windows

joe-alewine (Thu, 01 Jun 2017 13:32:02 GMT):
@cbf Thanks. Very interesting. Glad to see this is being tracked. I'm a bit surprised that there are twice as many referrers from facebook as from google, but the vast majority of the referrers are unknown (slack or rocket? Or maybe from email?) so I'm not really sure what to make of it either way. @mastersingh24 is right about Docker for Windows, of course. Hadn't thought about that

raheelz (Thu, 01 Jun 2017 16:36:29 GMT):
Has joined the channel.

cbf (Thu, 01 Jun 2017 18:03:34 GMT):
@greg.haskins https://gerrit.hyperledger.org/r/#/c/10029/ easy peasy as they say... I haven't done APT before but will take a look

greg.haskins (Thu, 01 Jun 2017 19:19:27 GMT):
cool...RPM is a little more straight forward than DEB in my experience, though there is some tooling to help

JonathanLevi (Thu, 01 Jun 2017 22:06:21 GMT):
--- We have assigned various people to the various sub-tasks here: https://jira.hyperledger.org/browse/FAB-4212

JonathanLevi (Thu, 01 Jun 2017 22:07:28 GMT):
We are thinking of tagging another version/revision next week. Not yet sure whether we'd call it *v1.0.0-alpha3*, *v1.0.0-beta*, or something else.

JonathanLevi (Thu, 01 Jun 2017 22:07:55 GMT):
Some thing(s) tell me that we should all practice "releasing" ;-)

JonathanLevi (Thu, 01 Jun 2017 22:08:51 GMT):
As for the first line of mine above, please reach out to me if you believe that you should not be assigned to any of the sub-tasks (e.g., holidays, it's someone else's "forte", or for any other reason).

JonathanLevi (Thu, 01 Jun 2017 22:08:51 GMT):
As for the first line of mine above, please reach out to me if you believe that you should not be assigned to any of the sub-tasks that you were assigned to (e.g., holidays, it's someone else's "forte", or for any other reason).

JonathanLevi (Thu, 01 Jun 2017 22:08:54 GMT):
Thank you

qsmen (Fri, 02 Jun 2017 07:55:48 GMT):
Has joined the channel.

JonathanLevi (Fri, 02 Jun 2017 13:25:39 GMT):
--- Hi @nickgaski, will you have some cycles to tackle the feedback we will be collecting here (https://jira.hyperledger.org/browse/FAB-4237) ?

nickgaski (Fri, 02 Jun 2017 13:26:39 GMT):
tour de france caliber cycles :bicyclist:

nickgaski (Fri, 02 Jun 2017 13:26:57 GMT):
yes I'm very available - I know there is lot's left to do on doc

JonathanLevi (Fri, 02 Jun 2017 13:31:32 GMT):
Yes, we need them tour de france caliber ones! ;-). Thank you.

dave.enyeart (Fri, 02 Jun 2017 13:33:55 GMT):
@JonathanLevi @bmos299 I think we'll want somebody from test lab to tackle FAB-4275 and FAB-4280 (test of release artifacts). I'm happy to help, but unfortunately I will be out June8-June19 and therefore want to ensure a 'test lead' is in place before I go.

dave.enyeart (Fri, 02 Jun 2017 13:34:04 GMT):
I added more detailed comments in the two FABs

JonathanLevi (Fri, 02 Jun 2017 13:35:54 GMT):
Yes, we saw your comment - they weren't assigned to you anyway @dave.enyeart

dave.enyeart (Fri, 02 Jun 2017 13:36:28 GMT):
You assigned one of them to me :) I just changed them to Barry

JonathanLevi (Fri, 02 Jun 2017 13:37:26 GMT):
Cool. Yes, I chatted with @binhn about it yesterday. Barry will lead the testing.

dave.enyeart (Fri, 02 Jun 2017 13:37:35 GMT):
thx

weeds (Fri, 02 Jun 2017 14:47:21 GMT):
@bmos299 is out today- he has quite a bit usually assigned to him, so adding him here to look at above.

weeds (Fri, 02 Jun 2017 14:47:34 GMT):
and will suggest in a private message to make sure he looks

JonathanLevi (Fri, 02 Jun 2017 14:59:21 GMT):
Noted, thank you @weeds

sstone1 (Fri, 02 Jun 2017 20:14:53 GMT):
@JonathanLevi do you have a view on whether or not the APIs will be locked down after the proposed release next week?

JonathanLevi (Fri, 02 Jun 2017 20:15:53 GMT):
I have a view [and quite a strong opinion ;-)] but it may not be only up to me.

JonathanLevi (Fri, 02 Jun 2017 20:17:17 GMT):
There are some issues that we became aware of that may break some of the API - but we are aware of them.

JonathanLevi (Fri, 02 Jun 2017 20:17:36 GMT):
More directly, how can I help? ;-)

sstone1 (Fri, 02 Jun 2017 20:18:11 GMT):
every time you change the APIs a composer dev cries ;)

JonathanLevi (Fri, 02 Jun 2017 20:18:49 GMT):
I know of one maintainer that dies inside too, at that same time. Believe me.

sstone1 (Fri, 02 Jun 2017 20:18:59 GMT):
i'm trying to figure out if we should try and deliver alpha 2 support next week or just hold back for alpha 3/beta and go straight to that

JonathanLevi (Fri, 02 Jun 2017 20:19:31 GMT):
Using the SDK ?

JonathanLevi (Fri, 02 Jun 2017 20:19:40 GMT):
Using Channels ?

sstone1 (Fri, 02 Jun 2017 20:19:51 GMT):
yeah, using the node SDK and channels

JonathanLevi (Fri, 02 Jun 2017 20:31:18 GMT):
Sounds like you should build stuff on the latest (even `master` right now).

JonathanLevi (Fri, 02 Jun 2017 20:31:40 GMT):
But if you can resist working during the entire weekend, then I/we would probably have a clearer view early next week.

sstone1 (Fri, 02 Jun 2017 21:39:39 GMT):
we can only build on what you publish to docker hub and more importantly npm ;)

sstone1 (Fri, 02 Jun 2017 21:39:51 GMT):
early next week is fine with me

cbf (Fri, 02 Jun 2017 23:18:08 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-release?msg=qJ3WnuoFHY8iHWW52) @sstone1 They were SUPPOSED to be locked down at alpha2

JonathanLevi (Fri, 02 Jun 2017 23:28:32 GMT):
^^^ Indeed !

JonathanLevi (Fri, 02 Jun 2017 23:29:44 GMT):
They were SUPPOSED to be locked down at alpha2... we really wanted (intended, at least) to release a *v1.0.0-beta* earlier in the week (before June 1st).

JonathanLevi (Fri, 02 Jun 2017 23:30:56 GMT):
At any rate, some API changes have been made (we have an approval/voting process) and the API has changed. Yes, please let's catch up early next week. Just being upfront.

JonathanLevi (Fri, 02 Jun 2017 23:31:47 GMT):
I believe it's really just a matter of a few days (and some of the upcoming issues, seem pretty important too).

jun (Mon, 05 Jun 2017 08:56:32 GMT):
Has joined the channel.

cbf (Mon, 05 Jun 2017 14:13:20 GMT):
@here so... are we READY to push for a release this week? I would think we should look for Thursday and that we should think about TUESDAY EOB for merging the last changes before beta (excepting those specifically related to preparing and producing the release)

muralisr (Mon, 05 Jun 2017 14:17:39 GMT):
@cbf ^^^ one "review-needed" on my immediate radar - https://jira.hyperledger.org/browse/FAB-3742. I had suggested a different approach for that ... will add comments this can be investigated post 1.0. Will also look at other review-needed

cbf (Mon, 05 Jun 2017 14:18:19 GMT):
Note that I think that the goal should be to close out any highest defects

cbf (Mon, 05 Jun 2017 14:18:51 GMT):
https://jira.hyperledger.org/browse/FAB-4136 is on my radar

cbf (Mon, 05 Jun 2017 15:06:24 GMT):
@jimthematrix @rameshthoomu https://jira.hyperledger.org/browse/FAB-4271 are we set for having 1.0.0-beta sdk-node automagically published to npm? Please update in comments

cbf (Mon, 05 Jun 2017 15:07:10 GMT):
this too please https://jira.hyperledger.org/browse/FAB-4272

cbf (Mon, 05 Jun 2017 15:07:19 GMT):
of course for maven

mastersingh24 (Mon, 05 Jun 2017 15:40:27 GMT):
@cbf - The final step to publish to Maven is not fully automatic as you know. So we need to include creating the detached signature for the jar artifact as a JIRA task

jimthematrix (Mon, 05 Jun 2017 15:50:45 GMT):
@cbf commented in 4271. in short we are fully automated (and tested during alpha and alpha2 releases)

jimthematrix (Mon, 05 Jun 2017 15:51:32 GMT):
java SDK to maven is still to be automated

cbf (Mon, 05 Jun 2017 15:52:10 GMT):
@jimthematrix thanks - @mastersingh24 yeah, just wanted to be sure I understood where we are - can you please create the JIRA for creating the signature? Assume that will be @rjones or @jwagantall signing?

rjones (Mon, 05 Jun 2017 15:52:11 GMT):
Has joined the channel.

mastersingh24 (Mon, 05 Jun 2017 15:52:58 GMT):
@cbf - sure thing

cbf (Mon, 05 Jun 2017 15:53:05 GMT):
danke

rameshthoomu (Mon, 05 Jun 2017 16:58:06 GMT):
@cbf updated comments in FAB-4272, FAB-4271

rameshthoomu (Mon, 05 Jun 2017 16:58:06 GMT):
@cbf updated FAB-4272, FAB-4271 items with the current progress

cbf (Mon, 05 Jun 2017 17:25:04 GMT):
thx

JonathanLevi (Mon, 05 Jun 2017 18:40:07 GMT):
FYI: https://jira.hyperledger.org/browse/FAB-4212

harsha (Mon, 05 Jun 2017 18:45:03 GMT):
So this means v1.0.0-beta is officially announced ?

troyronda (Mon, 05 Jun 2017 18:46:38 GMT):
I noticed a relabel from beta to alpha3 - I'm curious what's the criteria used to determine alpha vs beta label? e.g., Are APIs locked down?

troyronda (Mon, 05 Jun 2017 18:46:38 GMT):
I noticed a relabel from beta to alpha3 - I'm curious what's the criteria used to determine alpha vs beta label?

troyronda (Mon, 05 Jun 2017 18:46:38 GMT):
I noticed a relabel from beta to alpha3 - I'm curious what's the criteria used to determine alpha vs beta label? E.g., status of interface firmness

cbf (Mon, 05 Jun 2017 19:32:21 GMT):
we were looking for 0 Highest severity defects for beta and absolutely, positively NO MORE API CHANGES;-)

cbf (Mon, 05 Jun 2017 19:33:00 GMT):
so we will cut alpha3 this week and possibly get beta out next week assuming that we close out the remaining Highest defects

cbf (Mon, 05 Jun 2017 19:33:17 GMT):
https://jira.hyperledger.org/browse/FAB-4379

cbf (Mon, 05 Jun 2017 19:33:22 GMT):
is beta plan

jdockter (Mon, 05 Jun 2017 21:01:06 GMT):
Has joined the channel.

rameshthoomu (Mon, 05 Jun 2017 21:10:01 GMT):
@cbf @JonathanLevi it seems I have to publish hyperledger/fabric-tools docker image to docker hub and update this script with tools docker image https://github.com/hyperledger/fabric/blob/master/examples/e2e_cli/download-dockerimages.sh#L20

rameshthoomu (Mon, 05 Jun 2017 21:10:01 GMT):
@cbf @JonathanLevi it seems I have to publish `hyperledger/fabric-tools` docker image to docker hub and update this script with tools docker image https://github.com/hyperledger/fabric/blob/master/examples/e2e_cli/download-dockerimages.sh#L20

weeds (Mon, 05 Jun 2017 21:16:32 GMT):
@cbf up above- do we plan to cut a release this week ?- but in your post you put alpha 3 and beta- can you clarify?

weeds (Mon, 05 Jun 2017 21:16:49 GMT):
also posted in maintainer channel

jimthematrix (Mon, 05 Jun 2017 21:38:23 GMT):
for node SDK, https://jira.hyperledger.org/browse/FAB-4283 will be addressed with a CR to be pushed any minute (by @bretharrison ), and two related to grpc keepalive (https://jira.hyperledger.org/browse/FAB-3310 and https://jira.hyperledger.org/browse/FAB-2787) are done only pending the originator's verification

bretharrison (Mon, 05 Jun 2017 21:38:23 GMT):
Has joined the channel.

jimthematrix (Mon, 05 Jun 2017 21:39:03 GMT):
so node SDK as far as I'm aware will be ok with a beta imminently

JonathanLevi (Mon, 05 Jun 2017 21:39:03 GMT):
@weeds We are trying to work out whether we can (finally) lock the API. Of course we should cut a *beta* as soon as we can.

JonathanLevi (Mon, 05 Jun 2017 21:39:51 GMT):
The original plan was to lock the APIs right after the alpha. Let's see, if we can go straight to a *beta*, then let's do it.

JonathanLevi (Mon, 05 Jun 2017 21:40:18 GMT):
Otherwise/either way, I would still prefer to release/cut a version in the coming days. However we call it.

SriramaSharma (Mon, 05 Jun 2017 23:37:34 GMT):
Has joined the channel.

weeds (Tue, 06 Jun 2017 11:49:47 GMT):
@JonathanLevi What APIs are not locked down? but agree we should cut a release to get the practice

FenglianXu (Tue, 06 Jun 2017 14:07:32 GMT):
Has joined the channel.

FenglianXu (Tue, 06 Jun 2017 14:17:08 GMT):
Is there any plan to publish what API changes in alpha3 or beta?

JonathanLevi (Tue, 06 Jun 2017 14:41:50 GMT):
Good morning. @weeds, see some context above https://chat.hyperledger.org/channel/fabric-release?msg=knGQSEcCrSpmBXPCL

JonathanLevi (Tue, 06 Jun 2017 14:42:54 GMT):
But at the moment, I actually don't know what is going to change API-wise... we have already merged the SDK changes and the tests/examples are updated.

JonathanLevi (Tue, 06 Jun 2017 14:44:58 GMT):
So other than https://gerrit.hyperledger.org/r/#/c/10039 (which @kostas) is updating regularly as it progresses... if are good with locking down the API, then we can really call even this week's release a *beta*.

JonathanLevi (Tue, 06 Jun 2017 14:44:58 GMT):
So other than https://gerrit.hyperledger.org/r/#/c/10039 (which @kostas is updating regularly as it progresses..). if are good with locking down the API, then we can really call even this week's release a *beta*.

JonathanLevi (Tue, 06 Jun 2017 14:45:57 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-release?msg=86fgbszCTJYKgEDaW) I may be repeating this, but I don't mind how we call it. I'd rather push forward towards a beta, if people feel that we are there (rather than holding them back).

JonathanLevi (Tue, 06 Jun 2017 14:47:01 GMT):
The only/main thing I'd expect is that whatever we agree on ("shake on") we respect going forward. That is, really only *show stoppers* will get in, beyond that point, etc.

JonathanLevi (Tue, 06 Jun 2017 14:48:54 GMT):
--- https://chat.hyperledger.org/channel/fabric-release?msg=c3gX23Hd9eFKvbfhF So, we (= @cbf, mostly) have introduced an automated changeset that provides all the changes that are included in a given release. These include not only API changes, but also functionality and logic changes.

JonathanLevi (Tue, 06 Jun 2017 14:51:05 GMT):
We have also been trying to ask committers to provide details descriptions regarding the CR/changes also in the JIRA tickets. So hopefully, this time round, should have these right at the JIRA level as well.

JonathanLevi (Tue, 06 Jun 2017 14:51:05 GMT):
We have also been trying to ask committers to provide detailed descriptions regarding the CR/changes also in the JIRA tickets. So hopefully, this time round, should have these right at the JIRA level as well.

weeds (Tue, 06 Jun 2017 15:31:52 GMT):
Thanks Jonathan- that really helps provide more clarity!

guruce (Tue, 06 Jun 2017 16:37:45 GMT):
Has joined the channel.

simsc (Tue, 06 Jun 2017 17:30:54 GMT):
Here's what I captured from wipe boards discussion w/Binh/Dave E/Jim Z/Ramesh/Scott

simsc (Tue, 06 Jun 2017 17:30:55 GMT):
Here's what I captured from wipeboard build / publish discussion. I wanted to make sure we agree on what's captured first, then we have to get this documented in Jira, a run book, etc. Proposed: 0) Submit CR 1) When release = true - do full tests including 'gulp test' - fabric unit, e2ecli, bdd, full gulp, e2e java 2) Assuming test pass - TAG it (Ramesh to talk to greg to see if this can be automated) - create docker images -make release binaries (configtxgen, configgen) -publish to docker hub, npm, maven, nexus -update getting started started doc 3) Verify release binaries - QA uses docker images and uploaded release binaries to test on Mac, Linux, and Windows We will do manually this week. We need to have this in place for next week release of Beta.

cbf (Tue, 06 Jun 2017 17:31:35 GMT):
@simsc what is this?

cbf (Tue, 06 Jun 2017 17:34:37 GMT):
we are not doing this this week

simsc (Tue, 06 Jun 2017 17:35:30 GMT):
it captures a discussion on the desired state, my last comment - was we would have to do manually this week for sure

cbf (Tue, 06 Jun 2017 17:35:37 GMT):
who decided this? the release managers? were they even involved in the discussion? I said no before and I mean it

simsc (Tue, 06 Jun 2017 17:36:00 GMT):
w/Binh/Dave E/Jim Z/Ramesh/Scott

cbf (Tue, 06 Jun 2017 17:36:01 GMT):
we will not disrupt CI

simsc (Tue, 06 Jun 2017 17:36:52 GMT):
the intent was to post discussion here for comments etc

cbf (Tue, 06 Jun 2017 17:37:46 GMT):
I'm going to count to a hundred so my blood pressure subsides

cbf (Tue, 06 Jun 2017 17:37:57 GMT):
we are not changing anything

cbf (Tue, 06 Jun 2017 17:38:19 GMT):
the reason we will freeze is to STOP CODING and DO TESTING

cbf (Tue, 06 Jun 2017 17:38:30 GMT):
that means EVERYONE

cbf (Tue, 06 Jun 2017 17:38:43 GMT):
reading docs, testing downloads, installs, e2e everything

simsc (Tue, 06 Jun 2017 17:40:18 GMT):
this was a discussion on build, publishing, automation, improvements to streamline our build / publish proces

cbf (Tue, 06 Jun 2017 17:40:47 GMT):
maybe I am not making myself clear

gcuomo (Tue, 06 Jun 2017 17:46:35 GMT):
Has joined the channel.

Joseph (Tue, 06 Jun 2017 18:08:33 GMT):
Has joined the channel.

JonathanLevi (Tue, 06 Jun 2017 19:35:28 GMT):
---

JonathanLevi (Tue, 06 Jun 2017 19:36:00 GMT):
While I'm not going to take sides here... I see two "competing" forces:

JonathanLevi (Tue, 06 Jun 2017 19:37:19 GMT):
Given a deadline (say we fix a date): 1. A "release" with high quality super tested stuff, and only that gets "in". 2. A "release" that is packed with all sorts of features. Some heavily tested, other super brand new.

JonathanLevi (Tue, 06 Jun 2017 19:38:11 GMT):
Many (open-source) projects, choose to work with 2 separate targets/releases (like an LTS and a more "dev"-y like).

JonathanLevi (Tue, 06 Jun 2017 19:38:27 GMT):
Thinks about Ubuntu 16.04 vs 16.10... for example.

JonathanLevi (Tue, 06 Jun 2017 19:38:29 GMT):
---

JonathanLevi (Tue, 06 Jun 2017 19:39:11 GMT):
I get a feeling that most of the "arguments" / "debates" stem from us not clearly defining what we want or expect.

JonathanLevi (Tue, 06 Jun 2017 19:39:39 GMT):
I feel that many actions are based on "we really need to have that feature, without it the sky will fall"

JonathanLevi (Tue, 06 Jun 2017 19:39:39 GMT):
I feel that many actions are based on "we really need to have that feature, without *feature XYZ* the sky will fall"

JonathanLevi (Tue, 06 Jun 2017 19:40:25 GMT):
And many others, take actions based on "look, I don't want to add this, if it not tested enough, without *testing* this the sky will fall"

JonathanLevi (Tue, 06 Jun 2017 19:40:58 GMT):
---

JonathanLevi (Tue, 06 Jun 2017 19:41:51 GMT):
Maybe it will help to remind us all, that Fabric 1.0 is not going to be the *last* release. We will 1) add more *features like XYZ* We will 2) find more bugs/faults even with having 2-3 weeks of *testing*

JonathanLevi (Tue, 06 Jun 2017 19:43:11 GMT):

Message Attachments

JonathanLevi (Tue, 06 Jun 2017 19:43:53 GMT):
Just for perspective - this is Apple's first Control Panel, for those of us too young to have played with it.

JonathanLevi (Tue, 06 Jun 2017 19:44:24 GMT):
People actually LOVED it back in the day, and people still LOVE their products/design these days.

JonathanLevi (Tue, 06 Jun 2017 19:45:24 GMT):
I'm using an Apple laptop right now. I would not like their version 1.0 today... but it's all relative.

cbf (Wed, 07 Jun 2017 00:17:11 GMT):
https://jira.hyperledger.org/browse/FAB-4379 v1.0.0-beta release task

qsmen (Wed, 07 Jun 2017 05:22:20 GMT):
it is very difficult to curl https://goo.gl/NIKLiU because of network speed. it would be better if download can be continued after breakdown

sachikoy (Wed, 07 Jun 2017 09:07:31 GMT):
Has joined the channel.

cbf (Wed, 07 Jun 2017 11:19:09 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-release?msg=X74kJFu4wDLbyh3aP) @qsmen you mean after a network partition?

cbf (Wed, 07 Jun 2017 12:35:45 GMT):
@here ok, I think we're getting close... fabric needs https://gerrit.hyperledger.org/r/#/c/10247/ merged followed by https://gerrit.hyperledger.org/r/#/c/10153/ and then https://gerrit.hyperledger.org/r/#/c/10261/ needs to be updated before it is merged to update the changelog

cbf (Wed, 07 Jun 2017 12:36:28 GMT):
fabric-ca needs https://gerrit.hyperledger.org/r/#/c/10157/ followed by https://gerrit.hyperledger.org/r/#/c/10263/

cbf (Wed, 07 Jun 2017 12:36:59 GMT):
@JonathanLevi I will be consumed in client briefings this afternoon and giving a talk at 11 ET

cbf (Wed, 07 Jun 2017 12:47:56 GMT):
actually, the more I think of this, we should merge the docs after

cbf (Wed, 07 Jun 2017 12:48:00 GMT):
and test from staging

weeds (Wed, 07 Jun 2017 12:57:21 GMT):
10157 and 10263 looks like they passed he build- does it just need a +2 @cbf? or are we waiting for something more?

cbf (Wed, 07 Jun 2017 12:58:07 GMT):
waiting for more eyes to review

weeds (Wed, 07 Jun 2017 12:58:15 GMT):
ok got it

dave.enyeart (Wed, 07 Jun 2017 13:19:07 GMT):
I scanned all 5 CRs, just one minor comment in 10247

weeds (Wed, 07 Jun 2017 13:27:03 GMT):
maybe a silly question- but is there a certain sequencing to any of this stuff?

weeds (Wed, 07 Jun 2017 13:29:50 GMT):
like does one thing have to complete before another? just want to make sure

dave.enyeart (Wed, 07 Jun 2017 13:33:53 GMT):
my comment in 10247 was about configtxlator. i didnt think it was packaged into release artifacts yet, and therefore not pushed into nexus tar. This was one of the objectives of the blocking item FAB-4267. @rameshthoomu @jyellick , is there a plan for how beta consumers can exercise configtxlator?

dave.enyeart (Wed, 07 Jun 2017 13:33:53 GMT):
my comment in 10247 was about configtxlator. i didnt think it was packaged into release artifacts yet, and therefore not pushed into nexus tar. This was one of the objectives of the blocking item https://jira.hyperledger.org/browse/FAB-4267. @rameshthoomu @jyellick , is there a plan for how beta consumers can exercise configtxlator?

jyellick (Wed, 07 Jun 2017 13:38:52 GMT):
@dave.enyeart The extent of the initial pass of `configtxlator` CRs was to add it to the `RELEASE_PKGS` in the `Makefile`. I'm not an expert on what happens from here, I presumed that the things in `RELEASE_PKGS` were what ended up put into the release package. With respect to FAB-4267, I would agree, the homebrew file should be updated.

dave.enyeart (Wed, 07 Jun 2017 13:39:58 GMT):
Ok, we'll see if @rameshthoomu has scooped it up into the release artifacts that are pushed to nexus

rameshthoomu (Wed, 07 Jun 2017 13:42:36 GMT):
the release artificats I have pushed to nexus on alpha2 commits.. So existing release artifacts doesn't have this change..

rameshthoomu (Wed, 07 Jun 2017 13:43:00 GMT):
let me look into the change.

dave.enyeart (Wed, 07 Jun 2017 13:44:00 GMT):
ok, so only configtxgen and cryptogen are included i think. so the next question is, do we WANT configtxlator to be included and do we have instructions for how beta consumers would exercise it?

JonathanLevi (Wed, 07 Jun 2017 13:47:54 GMT):
@dave.enyeart Yes, of course we want it included. That's why Jason added it to the RELEASE_PKGS

JonathanLevi (Wed, 07 Jun 2017 13:48:21 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-release?msg=mWFdcKE7HZojTRrXN) Thanks, please let us know.

JonathanLevi (Wed, 07 Jun 2017 13:48:21 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-release?msg=mWFdcKE7HZojTRrXN) @rameshthoomu: Thanks, please let us know.

rameshthoomu (Wed, 07 Jun 2017 13:56:04 GMT):
yes..

rameshthoomu (Wed, 07 Jun 2017 13:56:04 GMT):
Sure will include this in tar file and publish to nexus

rameshthoomu (Wed, 07 Jun 2017 13:56:04 GMT):
Sure will include this in tar file and publish to nexus in next release

dave.enyeart (Wed, 07 Jun 2017 13:58:49 GMT):
ok, that would address first part of my question. second part of my question is @jyellick are there instructions for how beta consumers would exercise configtxlator? or is that something that needs to be worked on for next release milestone?

jyellick (Wed, 07 Jun 2017 14:00:55 GMT):
@dave.enyeart There is a doc I put together. It's at a fairly low level, because `configtxlator` is targeted at SDK users who wish to be able to manipulate the config, you may find it here: https://github.com/hyperledger/fabric/blob/master/examples/configtxupdate/README.md

jyellick (Wed, 07 Jun 2017 14:01:33 GMT):
My hope is to improve this doc before release, add additional examples, etc.

jyellick (Wed, 07 Jun 2017 14:01:51 GMT):
But I think there is enough there that someone eager could get started

jyellick (Wed, 07 Jun 2017 14:02:24 GMT):
I would love for @nickgaski or others to help improve the documentation

nickgaski (Wed, 07 Jun 2017 14:05:57 GMT):
thanks jason. let me have a read. been looking forward to seeing this sucker in action

dave.enyeart (Wed, 07 Jun 2017 14:08:03 GMT):
agreed, an example in the doc would be great, in addition to this config and config update playback video we've discussed.

jyellick (Wed, 07 Jun 2017 14:09:00 GMT):
For the moment, I'm prioritizing defect resolution over the playback, but it is on my list

nickgaski (Wed, 07 Jun 2017 14:09:16 GMT):
ah damn I was going to ask for a quick demo

dave.enyeart (Wed, 07 Jun 2017 14:09:45 GMT):
ok, let's get off the release channel now :) i'm sure there is more critical release business...

cbf (Wed, 07 Jun 2017 14:36:10 GMT):
@dave.enyeart thanks for the thoroughness

cbf (Wed, 07 Jun 2017 14:36:51 GMT):
not sure we need to worry about configtxlator docs but do want it in the release pkg

dave.enyeart (Wed, 07 Jun 2017 14:41:21 GMT):
after more discussion with @rameshthoomu , he did a pre-release trial yesterday, see June 06 tar file: https://nexus.hyperledger.org/content/repositories/snapshots/org/hyperledger/fabric/fabric-binary/darwin-amd64-1.0.0-alpha3-SNAPSHOT/

dave.enyeart (Wed, 07 Jun 2017 14:41:31 GMT):
and configtxlator is indeed in the /bin directory :)

cbf (Wed, 07 Jun 2017 16:06:31 GMT):
thanks @dave.enyeart

cbf (Wed, 07 Jun 2017 16:10:42 GMT):
@here I hope others are following @dave.enyeart 's lead and testing the release locally

cbf (Wed, 07 Jun 2017 16:12:29 GMT):
while you cannot download the release tarballs yet, testing the e2e here https://gerrit.hyperledger.org/r/#/c/10261/ and following the directions in https://gerrit.hyperledger.org/r/#/c/10247/ would be especially helpful

dave.enyeart (Wed, 07 Jun 2017 16:13:45 GMT):
we've also asked @scottz to organize some folks in the test lab to get platform coverage

cbf (Wed, 07 Jun 2017 16:16:21 GMT):
thanks

cbf (Wed, 07 Jun 2017 16:17:09 GMT):
Windows has (to date) been our predominant downloaded platform, so hopefully we get some coverage for Windows

rameshthoomu (Wed, 07 Jun 2017 16:38:12 GMT):
@cbf @JonathanLevi updated comment on https://gerrit.hyperledger.org/r/#/c/10261/

rameshthoomu (Wed, 07 Jun 2017 16:38:52 GMT):
once we publish tools image to docker hub we need script to pull this image..

cbf (Wed, 07 Jun 2017 16:51:40 GMT):
oh add to download-dockerimages.sh then? ok

rameshthoomu (Wed, 07 Jun 2017 16:52:37 GMT):
also in bootstrap scripts..

JonathanLevi (Wed, 07 Jun 2017 16:56:25 GMT):
Hi, we have removed the *bootstrap.sh*

JonathanLevi (Wed, 07 Jun 2017 16:56:36 GMT):
(or were about to)

lehors (Wed, 07 Jun 2017 16:57:21 GMT):
doesn't getting started need that?

lehors (Wed, 07 Jun 2017 16:57:54 GMT):
@cbf I don't understand what we can test of getting started at this point, without the images

cbf (Wed, 07 Jun 2017 16:58:47 GMT):
scripts/bootstrap-1.0.0-beta.sh

cbf (Wed, 07 Jun 2017 16:59:04 GMT):
we have dedicated version per release

weeds (Wed, 07 Jun 2017 17:02:17 GMT):
what tasks are remaining? what help is needed now?

lehors (Wed, 07 Jun 2017 17:10:43 GMT):
yikes: make release-all does nothing for me :(

lehors (Wed, 07 Jun 2017 17:11:23 GMT):
clean slate with a git clone plus checkout of https://gerrit.hyperledger.org/r/#/c/10261/

cbf (Wed, 07 Jun 2017 17:11:24 GMT):
kick the tires, follow the to-be-updated getting started and docs https://gerrit.hyperledger.org/r/#/c/10247/ (do a local build) and run e2e (excepting the download part, you'd need to build images and binaries locally from https://gerrit.hyperledger.org/r/#/c/10261/ ). Also would benefit from testing ot fabric-ca and sdks similarly

chris.elder (Wed, 07 Jun 2017 17:24:25 GMT):
Has joined the channel.

troyronda (Wed, 07 Jun 2017 17:48:43 GMT):
Sending build context to Docker daemon 47.34 MB Step 1/10 : FROM hyperledger/fabric-buildenv:x86_64-1.0.0-alpha3-snapshot-f87b4abd repository hyperledger/fabric-buildenv not found: does not exist or no pull access make: *** [build/image/testenv/.dummy-x86_64-1.0.0-beta] Error 1

troyronda (Wed, 07 Jun 2017 17:49:08 GMT):
(running make docker on https://gerrit.hyperledger.org/r/#/c/10261)

troyronda (Wed, 07 Jun 2017 17:49:19 GMT):
(after reseting docker to factory)

troyronda (Wed, 07 Jun 2017 17:49:45 GMT):
REPOSITORY TAG IMAGE ID CREATED SIZE hyperledger/fabric-buildenv latest 1db336ef7638 About a minute ago 1.32 GB hyperledger/fabric-buildenv x86_64-1.0.0-beta 1db336ef7638 About a minute ago 1.32 GB

troyronda (Wed, 07 Jun 2017 17:50:45 GMT):
(seems that its looking for alpha3-snapshot instead of beta)

smithbk (Wed, 07 Jun 2017 17:59:14 GMT):
new clone + https://gerrit.hyperledger.org/r/#/c/10261, then "make clean" and "make" and I get the following

smithbk (Wed, 07 Jun 2017 17:59:20 GMT):
Removing intermediate container 9c95bce88e9e Step 8/8 : LABEL org.hyperledger.fabric.version 1.0.0-beta org.hyperledger.fabric.base.version 0.3.1 ---> Running in a59f685db5da ---> d3ed00b968fe Removing intermediate container a59f685db5da Successfully built d3ed00b968fe docker tag hyperledger/fabric-tools hyperledger/fabric-tools:x86_64-1.0.0-beta Checking committed files for SPDX-License-Identifier headers ... grep: examples/e2e_cli/bootstrap.sh: No such file or directory All files have SPDX-License-Identifier headers Checking changed go files for spelling errors ... The following files are have spelling errors: CHANGELOG.md:439:154: "principl" is a misspelling of "principals" CHANGELOG.md:455:147: "runing" is a misspelling of "running" CHANGELOG.md:871:142: "statment" is a misspelling of "statement" CHANGELOG.md:1103:123: "Determinsitic" is a misspelling of "Deterministic" CHANGELOG.md:1155:66: "Interm" is a misspelling of "Interim" CHANGELOG.md:1348:97: "maintainance" is a misspelling of "maintenance" CHANGELOG.md:1609:85: "auxilary" is a misspelling of "auxiliary" CHANGELOG.md:1749:70: "occasionaly" is a misspelling of "occasionally" make: *** [spelling] Error 1

smithbk (Wed, 07 Jun 2017 18:02:44 GMT):
Not seeing where alpha3 would come from for you Troy

smithbk (Wed, 07 Jun 2017 18:02:47 GMT):
$ grep -lrI alpha3 * CHANGELOG.md examples/configtxupdate/README.md

troyronda (Wed, 07 Jun 2017 18:03:12 GMT):
yeh - i'm trying fresh clone & checkout now

lehors (Wed, 07 Jun 2017 18:05:50 GMT):
and on my side, on a Windows 7 box, 1) doing a make release in docker toolbox per the e2e instructions does nothing, 2) doing make release in vagrant gives me this error: Building release/linux-amd64/bin/configtxlator for linux-amd64 mkdir -p release/linux-amd64/bin CGO_CFLAGS=" " GOOS=linux GOARCH=amd64 go build -o /opt/gopath/src/github.com/hyperledger/fabric/release/linux-amd64/bin/configtxlator -tags "nopkcs11" -ldflags "-X github.com/hyperledger/fabric/common/tools/configtxlator/metadata.Version=1.0.0-beta" github.com/hyperledger/fabric/common/tools/configtxlator mkdir -p release/linux-amd64/install cat: release/linux-amd64/install/../../templates/get-docker-images.in: No such file or directory

cbf (Wed, 07 Jun 2017 18:05:55 GMT):
oh crap didn't think of that

cbf (Wed, 07 Jun 2017 18:06:37 GMT):
you can omit the spelling check by just running make unit-test I think @smithbk

cbf (Wed, 07 Jun 2017 18:07:00 GMT):
@lehors the spellcheck needs to omit the changelog

lehors (Wed, 07 Jun 2017 18:07:12 GMT):
we should make the spelling check as non fatal error

cbf (Wed, 07 Jun 2017 18:07:18 GMT):
+1

cbf (Wed, 07 Jun 2017 18:07:33 GMT):
either way, it should skip that

cbf (Wed, 07 Jun 2017 18:12:03 GMT):
actually, I will make an edit to check_spelling.sh in the prepare CRs

lehors (Wed, 07 Jun 2017 18:50:38 GMT):
good news: I was able to get through examples/e2e_cli within Vagrant on Windows, including running "make" to build the docker images and al

lehors (Wed, 07 Jun 2017 18:51:42 GMT):
I still don't know why end-to-end.rst reads as if I should be able to do that on Windows directly (via Docker Toolbox)

lehors (Wed, 07 Jun 2017 18:59:21 GMT):
nor why we have end-to-end and getting-started - they are highly redundant

lehors (Wed, 07 Jun 2017 18:59:51 GMT):
I thought I had seen something about merging the two

cbf (Wed, 07 Jun 2017 19:11:20 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-release?msg=7fnEvcucMcwmdAtTh) @smithbk Keith, I don't get the spelling errors

lehors (Wed, 07 Jun 2017 19:11:40 GMT):
I do

lehors (Wed, 07 Jun 2017 19:11:47 GMT):
I was just trying that out

lehors (Wed, 07 Jun 2017 19:11:52 GMT):
I get a whole load of them

smithbk (Wed, 07 Jun 2017 19:12:07 GMT):
With "make release-all" you don't but with "make" you do

smithbk (Wed, 07 Jun 2017 19:12:17 GMT):
atleast I do

lehors (Wed, 07 Jun 2017 19:12:36 GMT):
I did a simple make spelling

lehors (Wed, 07 Jun 2017 19:12:46 GMT):
The following files are have spelling errors: bddtests/regression/README.md:20:4: "Continous" is a misspelling of "Continuous" bddtests/steps/coverage.py:26:5: "Ouput" is a misspelling of "Output" bddtests/steps/coverage.py:38:5: "Ouput" is a misspelling of "Output" CHANGELOG.md:439:154: "principl" is a misspelling of "principals" CHANGELOG.md:455:147: "runing" is a misspelling of "running" CHANGELOG.md:871:142: "statment" is a misspelling of "statement" CHANGELOG.md:1103:123: "Determinsitic" is a misspelling of "Deterministic" CHANGELOG.md:1155:66: "Interm" is a misspelling of "Interim" CHANGELOG.md:1348:97: "maintainance" is a misspelling of "maintenance" CHANGELOG.md:1609:85: "auxilary" is a misspelling of "auxiliary" CHANGELOG.md:1749:70: "occasionaly" is a misspelling of "occasionally" core/chaincode/chaincodetest.yaml:168:39: "seperation" is a misspelling of "separation" core/chaincode/chaincodetest.yaml:397:53: "specifed" is a misspelling of "specified" core/chaincode/chaincodetest.yaml:426:43: "encompases" is a misspelling of "encompasses" core/chaincode/platforms/util/utils_test.go:228:56: "existant" is a misspelling of "existent" core/chaincode/shim/java/src/main/java/org/hyperledger/fabric/shim/impl/Handler.java:482:38: "Recieved" is a misspelling of "Received" core/common/ccprovider/ccinfocache_test.go:285:46: "cannonical" is a misspelling of "canonical" core/endorser/endorser_test.yaml:164:39: "seperation" is a misspelling of "separation" core/endorser/endorser_test.yaml:402:53: "specifed" is a misspelling of "specified" core/endorser/endorser_test.yaml:421:43: "encompases" is a misspelling of "encompasses" docs/source/dev-setup/build.rst:36:5: "excecute" is a misspelling of "execute" docs/source/msp.rst:130:23: "overriden" is a misspelling of "overridden" docs/source/Setup/logging-control.rst:62:0: "varaibles" is a misspelling of "variables" docs/source/videos.rst:4:32: "libary" is a misspelling of "library" examples/chaincode/go/utxo/README.md:11:42: "avilable" is a misspelling of "available" examples/cluster/config/core.yaml:72:39: "seperation" is a misspelling of "separation" examples/cluster/config/core.yaml:297:95: "configruation" is a misspelling of "configurations" examples/cluster/config/core.yaml:387:43: "encompases" is a misspelling of "encompasses" examples/configtxupdate/README.md:20:3: "Buliding" is a misspelling of "Building" peer/channel/update_test.go:112:48: "existant" is a misspelling of "existent" proposals/r1/Custom-Events-High-level-specification.md:48:106: "commited" is a misspelling of "committed" proposals/r1/Next-Ledger-Architecture-Proposal.md:23:9: "Enginer" is a misspelling of "Engineer" proposals/r1/Next-Ledger-Architecture-Proposal.md:117:106: "enviroment" is a misspelling of "environment" protos/common/policies.pb.go:127:94: "sufficent" is a misspelling of "sufficient" protos/common/policies.proto:47:94: "sufficent" is a misspelling of "sufficient" protos/msp/msp_principal.proto:115:25: "posess" is a misspelling of "possess" protos/msp/msp_principal.pb.go:170:22: "posess" is a misspelling of "possess" protos/peer/chaincode_shim.proto:58:12: "emmited" is a misspelling of "emitted" protos/peer/chaincode_shim.pb.go:99:10: "emmited" is a misspelling of "emitted" protos/peer/proposal.proto:214:44: "extentions" is a misspelling of "extensions" protos/peer/proposal.pb.go:124:44: "extentions" is a misspelling of "extensions" sampleconfig/core.yaml:54:39: "seperation" is a misspelling of "separation" sampleconfig/core.yaml:254:95: "configruation" is a misspelling of "configurations" sampleconfig/core.yaml:349:43: "encompases" is a misspelling of "encompasses" test/tools/PTE/pte-main.js:788:48: "Successfull" is a misspelling of "Successful" Makefile:103: recipe for target 'spelling' failed make: *** [spelling] Error 1

smithbk (Wed, 07 Jun 2017 19:12:47 GMT):
:-) yeh that too

lehors (Wed, 07 Jun 2017 19:13:29 GMT):
sorry, that was a bit much :)

lehors (Wed, 07 Jun 2017 19:14:08 GMT):
these are trivial to fix but don't know that we should touch this stuff at this point

lehors (Wed, 07 Jun 2017 19:14:21 GMT):
otherwise let me know and I'll be happy to submit a CR :)

smithbk (Wed, 07 Jun 2017 19:14:34 GMT):
@lehors What did you do to get past the other error?

smithbk (Wed, 07 Jun 2017 19:14:36 GMT):
cat: release/linux-s390x/install/../../templates/get-docker-images.in: No such file or directory

lehors (Wed, 07 Jun 2017 19:14:52 GMT):
nothing

lehors (Wed, 07 Jun 2017 19:15:12 GMT):
I ignored them and in the end it seems not to have mattered

lehors (Wed, 07 Jun 2017 19:16:00 GMT):
I just made just I had the docker images with a make docker

lehors (Wed, 07 Jun 2017 19:16:00 GMT):
I just made sure I had the docker images with a make docker

lehors (Wed, 07 Jun 2017 19:16:04 GMT):
that part worked

lehors (Wed, 07 Jun 2017 19:16:31 GMT):
so, I'm not saying it is quite all right

lehors (Wed, 07 Jun 2017 19:18:52 GMT):
the spelling errors from CHANGELOG seem to indicate that it would serve well to have a spelling checker hooked onto git commit ;-)

cbf (Wed, 07 Jun 2017 19:19:07 GMT):
@smithbk oh nevermind, I see I changed a file doh!

lehors (Wed, 07 Jun 2017 19:19:47 GMT):
and @cbf the CHANGELOG starts with * [d9a81f03](https://github.com/hyperledger/fabric/commit/d9a81f03) [WIP] [FAB-4380](https://jira.hyperledger.org/browse/FAB-4380) prepare for 1.0.0-beta release

lehors (Wed, 07 Jun 2017 19:20:00 GMT):
I'm guessing you don't want WIP in there

cbf (Wed, 07 Jun 2017 19:27:12 GMT):
done

cbf (Wed, 07 Jun 2017 19:27:14 GMT):
updated CR

cbf (Wed, 07 Jun 2017 19:27:25 GMT):
good catch

cbf (Wed, 07 Jun 2017 19:44:56 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-release?msg=SoBFiBQkwkCefhFCK) @lehors this is a good point, though the end-to-end.rst is more for ppl building from a clone while the GS is for someone downloading the images

lehors (Wed, 07 Jun 2017 19:47:08 GMT):
that's fine but it doesn't work natively on Windows

lehors (Wed, 07 Jun 2017 19:47:29 GMT):
I mean end-to-end

lehors (Wed, 07 Jun 2017 19:47:36 GMT):
so it should imply that it will

lehors (Wed, 07 Jun 2017 19:47:36 GMT):
so it should not imply that it will

cbf (Wed, 07 Jun 2017 19:47:52 GMT):
oh, sorry, missed that point

cbf (Wed, 07 Jun 2017 19:48:07 GMT):
does GS work on Windows?

lehors (Wed, 07 Jun 2017 19:48:37 GMT):
well, I can't test the latest one but I expect it will

lehors (Wed, 07 Jun 2017 19:48:50 GMT):
I made sure it did for alpha2

lehors (Wed, 07 Jun 2017 19:48:59 GMT):
I think it will work for beta as well

lehors (Wed, 07 Jun 2017 19:49:26 GMT):
it's the build with make that doesn't work on Windows

cbf (Wed, 07 Jun 2017 19:49:35 GMT):
what part of end-to-end doesn't work on Windows?

lehors (Wed, 07 Jun 2017 19:50:46 GMT):
make release-all

lehors (Wed, 07 Jun 2017 19:51:03 GMT):
which is what end-to-end tells you to do after cloning the repo

cbf (Wed, 07 Jun 2017 19:51:58 GMT):
what about that fails?

lehors (Wed, 07 Jun 2017 19:52:03 GMT):
I'll try again, maybe I missed something

cbf (Wed, 07 Jun 2017 19:52:26 GMT):
oh well - I think that gari changed that to make release

cbf (Wed, 07 Jun 2017 19:52:48 GMT):
because when you are running local, you only need your os/arch

cbf (Wed, 07 Jun 2017 19:52:55 GMT):
let me double check

lehors (Wed, 07 Jun 2017 19:53:36 GMT):
the two targets exist actually

lehors (Wed, 07 Jun 2017 19:53:49 GMT):
but you're right, for e2e make release should do

cbf (Wed, 07 Jun 2017 19:55:49 GMT):
done

cbf (Wed, 07 Jun 2017 19:56:01 GMT):
good catch again

cbf (Wed, 07 Jun 2017 19:56:11 GMT):
of course, I don't do Windows

lehors (Wed, 07 Jun 2017 19:56:27 GMT):
oh I know :-)

JonathanLevi (Wed, 07 Jun 2017 20:04:34 GMT):
BTW: @lehors, thanks for your round of checking of the LICENSEs

lehors (Wed, 07 Jun 2017 20:05:20 GMT):
yw

JonathanLevi (Wed, 07 Jun 2017 20:05:57 GMT):
@cbf will simply update test/chaincodes/BadImport/main.go Greg Haskins (We'll assign it to @greg.haskins - who can re-assign it if needs be) core/config/config_test.go Anil (which we'll assign to IBM)

JonathanLevi (Wed, 07 Jun 2017 20:05:57 GMT):
Just talked to @cbf who will simply update *test/chaincodes/BadImport/main.go* Greg Haskins (We'll assign it to @greg.haskins - who can re-assign it if needs be) *core/config/config_test.go* Anil (which we'll assign to IBM)

JonathanLevi (Wed, 07 Jun 2017 20:06:11 GMT):
As it is easier at this point to simply update the staged commit.

JonathanLevi (Wed, 07 Jun 2017 20:06:28 GMT):
FYI

lehors (Wed, 07 Jun 2017 20:06:46 GMT):
yes, makes sense to me

JonathanLevi (Wed, 07 Jun 2017 20:07:45 GMT):
---- For the record, IBM and others seem less concerned with JSONs and binaries at this point. We can re-visit if needed. Thanks again @lehors and @tkuhrt

JonathanLevi (Wed, 07 Jun 2017 20:08:06 GMT):
Please, all, reach out if the above presents any issue.

JonathanLevi (Wed, 07 Jun 2017 20:08:06 GMT):
Please, all/everyone/anyone, reach out if the above presents any issue.

lehors (Wed, 07 Jun 2017 20:08:28 GMT):
well, IBM might be but I don't think @tkuhrt feels the same :)

JonathanLevi (Wed, 07 Jun 2017 20:09:07 GMT):
Yes, I understand, which is why I'm checking.

lehors (Wed, 07 Jun 2017 20:10:06 GMT):
I'll let her speak for herself but she's made pretty clear that everything has to have a copyright and license (I assume binaries excluded)

lehors (Wed, 07 Jun 2017 20:12:10 GMT):
there is probably a few exceptions besides binaries though, like CHANGELOG, MAINTAINERS

lehors (Wed, 07 Jun 2017 20:12:18 GMT):
maybe pem files?

lehors (Wed, 07 Jun 2017 20:13:14 GMT):
I took Tracy's point as: everything except when there is a good reason not to

JonathanLevi (Wed, 07 Jun 2017 20:16:41 GMT):
Yes, I remember. I believe we may re-visit some of the above (certainly, on the to the GA). I just didn't want to miss/skip some of the data/info that your scripts provided relating to the Golang files, at this point.

JonathanLevi (Wed, 07 Jun 2017 20:17:26 GMT):
-- Yours, the pragmatic Jon ;-)

lehors (Wed, 07 Jun 2017 20:17:51 GMT):
:)

binhn (Wed, 07 Jun 2017 20:40:10 GMT):
e2e_cli ran fine on my mac with these images

lehors (Wed, 07 Jun 2017 21:02:48 GMT):
well, I'm not sure what's up but I was able to do make release within docker toolbox on windows 7 but that's all

lehors (Wed, 07 Jun 2017 21:03:22 GMT):
and there is something weird with my make command which doesn't work, I have to use cygwin's but we can ignore that for now

lehors (Wed, 07 Jun 2017 21:03:35 GMT):
more importantly make docker fails

lehors (Wed, 07 Jun 2017 21:05:18 GMT):
unfortunately our Makefile has become so sophisticated it's getting hard to find out what's wrong when things go wrong.

lehors (Wed, 07 Jun 2017 21:22:48 GMT):
ok, I think I found the root cause of the error and it seems to be (again) a Docker Toolbox problem

lehors (Wed, 07 Jun 2017 21:23:01 GMT):
grrr

lehors (Wed, 07 Jun 2017 21:25:38 GMT):
a problem with volume mounts (which seems to be an ongoing source of problems)

greg.haskins (Wed, 07 Jun 2017 21:29:49 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-release?msg=2p3pW6YjkQ3naDnKi) @JonathanLevi TLDR, what is the action item you need from me?

greg.haskins (Wed, 07 Jun 2017 21:30:16 GMT):
oh, is this w.r.t. copyright assignments?

greg.haskins (Wed, 07 Jun 2017 21:30:23 GMT):
I took it as JIRA assignments

greg.haskins (Wed, 07 Jun 2017 21:30:31 GMT):
if copyright, sounds good to me

greg.haskins (Wed, 07 Jun 2017 21:31:27 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-release?msg=hru9p3TQ9dHEZwsfQ) @lehors Ill take the blame for that mate: what seems to be the problem?

greg.haskins (Wed, 07 Jun 2017 21:32:09 GMT):
(though in my defense, i think a bunch of things were piled on there that really should have been subdir/Makefiles

greg.haskins (Wed, 07 Jun 2017 21:32:11 GMT):
i digress

lehors (Wed, 07 Jun 2017 21:32:29 GMT):
oh, I know, no worries :)

greg.haskins (Wed, 07 Jun 2017 21:32:37 GMT):
overall, I own the lion share of blame for any complexity there

lehors (Wed, 07 Jun 2017 21:32:43 GMT):
git blame makes that quite clear as a matter of fact ;-)

lehors (Wed, 07 Jun 2017 21:33:14 GMT):
on the copyright point, the question is what the copyright should be for a file you created

lehors (Wed, 07 Jun 2017 21:33:36 GMT):
recently

greg.haskins (Wed, 07 Jun 2017 21:33:46 GMT):
just assign it to me: normally I assign it to whoever signs my paycheck, but our legal dept seems to be ignoring my question

lehors (Wed, 07 Jun 2017 21:33:49 GMT):
older files have a LSE copyright

greg.haskins (Wed, 07 Jun 2017 21:34:18 GMT):
anything since 12/16, def not LSE

greg.haskins (Wed, 07 Jun 2017 21:34:36 GMT):
gregory.haskins@gmail.com is fine

greg.haskins (Wed, 07 Jun 2017 21:34:53 GMT):
if SS ever gets back to me, ill retro-assign it over

lehors (Wed, 07 Jun 2017 21:35:01 GMT):
ok, good to know

lehors (Wed, 07 Jun 2017 21:35:46 GMT):
test/chaincodes/BadImport/main.go is from March so I figured it couldn't be LSE

greg.haskins (Wed, 07 Jun 2017 21:36:28 GMT):
yeah, just assign to me

greg.haskins (Wed, 07 Jun 2017 21:36:35 GMT):
actually thats probably from last week IIRC

greg.haskins (Wed, 07 Jun 2017 21:36:36 GMT):
but either way

greg.haskins (Wed, 07 Jun 2017 21:37:02 GMT):
(im actually surprised I forgot to add one ...oh well

greg.haskins (Wed, 07 Jun 2017 21:37:07 GMT):
fast-n-furious

lehors (Wed, 07 Jun 2017 21:38:32 GMT):
understood

lehors (Wed, 07 Jun 2017 21:39:06 GMT):
otherwise, about the Makefile, I was trying to figure out how the command to build peer-docker is figured out

lehors (Wed, 07 Jun 2017 21:39:26 GMT):
the docker run doesn't work for me

lehors (Wed, 07 Jun 2017 21:39:54 GMT):
and I have now figured that it's because the volume mount into the container doesn't work

lehors (Wed, 07 Jun 2017 21:40:10 GMT):
so the source files are not visible from within the container

lehors (Wed, 07 Jun 2017 21:43:50 GMT):
$ ls /home/lehors/Documents/Projects/Go/src/github.com/hyperledger/fabric '#Makefile#'* bddtests/ CHANGELOG.md* CONTRIBUTING.md* devenv/ docs/ examples/ gotools/ LICENSE* mkdocs.yml* orderer/ proposals/ README.md* sampleconfig/ settings.gradle* unit-test/ bccsp/ build/ common/ core/ docker-env.mk* events/ gossip/ images/ Makefile* msp/ peer/ protos/ release/ scripts/ test/ vendor/

lehors (Wed, 07 Jun 2017 21:44:08 GMT):
$ docker run -i --rm --user=197628 -v /home/lehors/Documents/Projects/Go/src/github.com/hyperledger/fabric:/opt/gopath/src/github.com/hyperledger/fabric -w /opt/gopath/src/github.com/hyperledger/fabric hyperledger/fabri c-baseimage:x86_64-0.3.1 ls build

lehors (Wed, 07 Jun 2017 21:44:20 GMT):
this should be the same

lehors (Wed, 07 Jun 2017 21:46:15 GMT):
@greg.haskins can you please tell me how DRUN is set?

greg.haskins (Wed, 07 Jun 2017 21:46:28 GMT):
look in docker-env.mk

greg.haskins (Wed, 07 Jun 2017 21:46:39 GMT):
that file is included by the top-level Makefile

lehors (Wed, 07 Jun 2017 21:47:12 GMT):
got it

lehors (Wed, 07 Jun 2017 21:47:13 GMT):
thanks

greg.haskins (Wed, 07 Jun 2017 21:47:16 GMT):
np

greg.haskins (Wed, 07 Jun 2017 21:47:29 GMT):
(you arent the first to miss the indirection there)

lehors (Wed, 07 Jun 2017 21:48:03 GMT):
I was looking for an include at the top.. silly me I should have search for it :)

lehors (Wed, 07 Jun 2017 21:48:03 GMT):
I was looking for an include at the top.. silly me I should have searched for it :)

greg.haskins (Wed, 07 Jun 2017 21:48:47 GMT):
that doesnt seem unreasonable...i think I put it at the point that I wanted it to become effective, but i am not sure make even works that way

greg.haskins (Wed, 07 Jun 2017 21:49:24 GMT):
(e.g. I wanted the variables that are declared above it to be in effect when it was loaded, but maybe they would be anyway..i am not sure

lehors (Wed, 07 Jun 2017 21:49:46 GMT):
right, I figured that was why you put it there

lehors (Wed, 07 Jun 2017 21:49:55 GMT):
I don't know either whether this really matters

greg.haskins (Wed, 07 Jun 2017 21:50:07 GMT):
well, for clarity at least

greg.haskins (Wed, 07 Jun 2017 21:50:26 GMT):
a handful of others thought $(DRUN) was magic voodoo until I pointed out the include

greg.haskins (Wed, 07 Jun 2017 21:50:54 GMT):
revealing the wizard behind the curtain

greg.haskins (Wed, 07 Jun 2017 21:50:55 GMT):
heh

lehors (Wed, 07 Jun 2017 21:51:40 GMT):
right, it does seem magic when you can't find the include indeed

lehors (Wed, 07 Jun 2017 21:52:23 GMT):
well, did you see the output I got above?

lehors (Wed, 07 Jun 2017 21:52:34 GMT):
I think there is something very wrong with Docker toolbox

greg.haskins (Wed, 07 Jun 2017 21:52:56 GMT):
i didnt really understand what I was looking at

lehors (Wed, 07 Jun 2017 21:53:04 GMT):
the mount is simply not working

greg.haskins (Wed, 07 Jun 2017 21:53:17 GMT):
but that said, we generally only support "real" docker, and docker-for-mac

greg.haskins (Wed, 07 Jun 2017 21:53:21 GMT):
for other reasons

lehors (Wed, 07 Jun 2017 21:53:48 GMT):
oh, I just do a docker run which does a mount of the fabric src directory and execute ls

lehors (Wed, 07 Jun 2017 21:53:59 GMT):
and it shows the files are not visible

greg.haskins (Wed, 07 Jun 2017 21:54:09 GMT):
not that others cannot work per se, but a) thats how it was tested and b) I know older docker-toolbox on OSX wont work with our compose files

lehors (Wed, 07 Jun 2017 21:54:09 GMT):
which means the mount didn't work

greg.haskins (Wed, 07 Jun 2017 21:54:20 GMT):
is this OSX or windows?

lehors (Wed, 07 Jun 2017 21:54:30 GMT):
Windows 7...

greg.haskins (Wed, 07 Jun 2017 21:54:59 GMT):
ah...i dont know much about the platform, but I can say that older docker-toolbox/docker-machine on OSX was wonky until docker-for-mac came out

greg.haskins (Wed, 07 Jun 2017 21:55:10 GMT):
all kinds of "kind of works, but not really" scenarios

greg.haskins (Wed, 07 Jun 2017 21:55:16 GMT):
like port forwarding for example

greg.haskins (Wed, 07 Jun 2017 21:55:42 GMT):
The nail in the coffin for me was when I tried to surface the dockerd port to the peer

greg.haskins (Wed, 07 Jun 2017 21:56:07 GMT):
docker-machine supported TLS but not UDS, and docker-for-mac supported UDS but not TLS

lehors (Wed, 07 Jun 2017 21:56:17 GMT):
yeah... so we should probably have a warning in the doc and/or the release notes about that

greg.haskins (Wed, 07 Jun 2017 21:56:18 GMT):
so, I picked one (the newer one)

lehors (Wed, 07 Jun 2017 21:56:28 GMT):
@cbf ^^

greg.haskins (Wed, 07 Jun 2017 21:57:00 GMT):
that said, I was not aware of problems in DRUN+volumes on docker-toolbox + win7, but I am not entirely surprised

lehors (Wed, 07 Jun 2017 21:57:30 GMT):
well, for alpha2 we faced a bunch of problems with mount also

greg.haskins (Wed, 07 Jun 2017 21:57:42 GMT):
on toolbox+win7?

greg.haskins (Wed, 07 Jun 2017 21:57:44 GMT):
or in general?

lehors (Wed, 07 Jun 2017 21:57:56 GMT):
on toolbox+win7

greg.haskins (Wed, 07 Jun 2017 21:57:59 GMT):
ok

lehors (Wed, 07 Jun 2017 21:58:13 GMT):
the genesis block file wasn't mounting

lehors (Wed, 07 Jun 2017 21:58:25 GMT):
I changed the name of the file and it worked!?

greg.haskins (Wed, 07 Jun 2017 21:58:28 GMT):
for sanity, it might be more conservative to just say "native docker or docker-for-mac" for now, until we can get to the bottom of it

greg.haskins (Wed, 07 Jun 2017 21:58:44 GMT):
I know those two generally should work (or I want to know about it)

lehors (Wed, 07 Jun 2017 21:58:54 GMT):
right

greg.haskins (Wed, 07 Jun 2017 21:59:13 GMT):
its possible that toolbox+win7 is an easy fix, but I dont know enough about it to say

lehors (Wed, 07 Jun 2017 21:59:37 GMT):
well, I'll investigate further tomorrow

greg.haskins (Wed, 07 Jun 2017 21:59:43 GMT):
ok

lehors (Wed, 07 Jun 2017 22:00:00 GMT):
for now it's midnight and my wife poured some whiskey ;-)

greg.haskins (Wed, 07 Jun 2017 22:00:24 GMT):
as a simple test, you can always do something like "docker run -it --rm -v$(PWD):/opt alpine /bin/sh"

greg.haskins (Wed, 07 Jun 2017 22:00:48 GMT):
ah, well you should go enjoy time with the wife (and whiskey)

lehors (Wed, 07 Jun 2017 22:01:06 GMT):
well, that was a bit what I was doing with my docker run ... ls

greg.haskins (Wed, 07 Jun 2017 22:01:08 GMT):
have a nice night

greg.haskins (Wed, 07 Jun 2017 22:01:14 GMT):
i see

lehors (Wed, 07 Jun 2017 22:01:21 GMT):
thanks

lehors (Wed, 07 Jun 2017 22:01:21 GMT):
take care

greg.haskins (Wed, 07 Jun 2017 22:01:25 GMT):
likewise

weeds (Wed, 07 Jun 2017 22:06:53 GMT):
thank you guys for helping out today

tkuhrt (Wed, 07 Jun 2017 23:08:43 GMT):
So it looks like I was asked for my thoughts on licensing for binaries and JSON files. All files, regardless of type need to have licensing identified. This can be done through a LICENSE file in the directory containing files that cannot contain a comment with the license information. Here is a couple examples of how this can be done: * OPNFV Apex: https://github.com/opnfv/apex/blob/master/LICENSE.rst -- this is an example of explicitly calling out Apache 2.0 for source code and CC-BY-4.0 for docs. * containerd: https://github.com/containerd/containerd/blob/master/README.md -- see notice at bottom. This also calls out the separate Apache / CC-BY-4.0 docs, and explicitly references the "docs" directory. The idea is that we should make sure that all files have a license specified, either by including it in the files where it can be included, or by having a separate file that calls out the license for those where the license cannot be included.

tkuhrt (Wed, 07 Jun 2017 23:09:00 GMT):
@lehors @JonathanLevi ^^

qsmen (Thu, 08 Jun 2017 00:54:56 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-release?msg=5r5L6Ztskikn599Qi) @cbf when the download speed is zero for a period of time, the download will stop. I have to run curl once again. If the new dowloaded part can be added to the part that was downloaded before, it will be better.

cbf (Thu, 08 Jun 2017 09:38:09 GMT):
@qsmen see https://www.cyberciti.biz/faq/curl-command-resume-broken-download/

cbf (Thu, 08 Jun 2017 09:40:11 GMT):
you can see the curl command that is being executed when you run the command from the Getting Started here https://github.com/hyperledger/fabric/blob/master/scripts/bootstrap-1.0.0-alpha2.sh#L35

cbf (Thu, 08 Jun 2017 09:41:11 GMT):
you're going to want to modify that to just write the gzipped tar file to disk (-o option) instead of piping to tar to unzip and then after a successful download, unzip yourself

cbf (Thu, 08 Jun 2017 09:41:45 GMT):
after we get the beta release published, I'll add a troubleshooting the download to provide specific guidance

cbf (Thu, 08 Jun 2017 09:41:57 GMT):
thanks for raising this

cbf (Thu, 08 Jun 2017 09:47:03 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-release?msg=6Bv6QrfviFGzmt93c) @qsmen https://jira.hyperledger.org/browse/FAB-4458

cbf (Thu, 08 Jun 2017 10:31:30 GMT):
https://lists.hyperledger.org/pipermail/hyperledger-fabric/2017-June/001147.html

cbf (Thu, 08 Jun 2017 10:31:44 GMT):
https://lists.hyperledger.org/pipermail/hyperledger-fabric/2017-June/001148.html

cbf (Thu, 08 Jun 2017 10:39:01 GMT):
NOTE: when we tag the release, please do so with the release_notes/v1.0.0-beta.md as the tag comment % git tag \-a v1.0.0-beta \-F release_notes/v1.0.0-beta.md

cbf (Thu, 08 Jun 2017 10:46:12 GMT):
@greg.haskins or @rjones just checking as I wasn't present for the last release, but the tags are created in a local clone and pushed to Gerrit, correct?

cbf (Thu, 08 Jun 2017 10:46:47 GMT):
I don't see a 'create tag' in the Gerrit UX so just want to be sure

cbf (Thu, 08 Jun 2017 11:25:21 GMT):
all battle plans fail to survive the first engagement with the enemy - sigh

cbf (Thu, 08 Jun 2017 11:26:09 GMT):
because the fabric-sdk-java release notes were merged prematurely, we need to create a CR to actually populate the CHANGELOG.md that the release notes reference

cbf (Thu, 08 Jun 2017 11:26:11 GMT):
https://gerrit.hyperledger.org/r/#/c/10327/

greg.haskins (Thu, 08 Jun 2017 12:17:51 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-release?msg=2QBgW98Txp8gFgTaQ) @cbf Thats correct. As far as I can tell, this is the only way to do it with our current setup

cbf (Thu, 08 Jun 2017 12:18:11 GMT):
ok thanks, what I thought

greg.haskins (Thu, 08 Jun 2017 12:18:22 GMT):
I wanted to put together a few of my notes on the release process: what would be a good forum?

greg.haskins (Thu, 08 Jun 2017 12:18:27 GMT):
(wiki, google doc, etc)

cbf (Thu, 08 Jun 2017 12:18:37 GMT):
wiki - I was going to do the same

greg.haskins (Thu, 08 Jun 2017 12:18:47 GMT):
do you have a page started / in mind ?

cbf (Thu, 08 Jun 2017 12:19:01 GMT):
no, please feel free to create off of fabric project page

greg.haskins (Thu, 08 Jun 2017 12:19:05 GMT):
ok

cbf (Thu, 08 Jun 2017 12:19:17 GMT):
thx

greg.haskins (Thu, 08 Jun 2017 12:19:19 GMT):
(have you cut the release yet btw?)

cbf (Thu, 08 Jun 2017 12:19:25 GMT):
in progress

greg.haskins (Thu, 08 Jun 2017 12:19:36 GMT):
ok, dont merge it till we sync

cbf (Thu, 08 Jun 2017 12:19:48 GMT):
it?

greg.haskins (Thu, 08 Jun 2017 12:19:56 GMT):
the release CR

cbf (Thu, 08 Jun 2017 12:19:57 GMT):
haven't pushed any buttons

greg.haskins (Thu, 08 Jun 2017 12:20:04 GMT):
ok..dont till we speak

cbf (Thu, 08 Jun 2017 12:20:08 GMT):
ok

cbf (Thu, 08 Jun 2017 12:20:12 GMT):
won't

greg.haskins (Thu, 08 Jun 2017 12:20:13 GMT):
theres a nuance that I think has been missed in the past

greg.haskins (Thu, 08 Jun 2017 12:20:17 GMT):
want to make sure its understood

cbf (Thu, 08 Jun 2017 12:20:22 GMT):
ok I'll -2 for now

greg.haskins (Thu, 08 Jun 2017 12:20:31 GMT):
ok

greg.haskins (Thu, 08 Jun 2017 12:20:36 GMT):
have a CR link handy, btw?

cbf (Thu, 08 Jun 2017 12:21:27 GMT):
in the email I sent this am

cbf (Thu, 08 Jun 2017 12:21:42 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-release?msg=eoFNChnqvNNSh7uqY) @cbf this one

greg.haskins (Thu, 08 Jun 2017 12:32:05 GMT):

Message Attachments

greg.haskins (Thu, 08 Jun 2017 12:32:16 GMT):
this is the basic problem we have made in the past

greg.haskins (Thu, 08 Jun 2017 12:32:46 GMT):
i.e. we create the release CR early, more changes go in, and then we simply hit the button on the release CR

greg.haskins (Thu, 08 Jun 2017 12:33:01 GMT):
what we should do is some form of "rebase" first

greg.haskins (Thu, 08 Jun 2017 12:33:28 GMT):
that could be literally a rebase of the release+prepare CRs...or perhaps there is an alternate merge strategy we can select in gerrit

greg.haskins (Thu, 08 Jun 2017 12:34:36 GMT):
@cbf @rjones ^^^

cbf (Thu, 08 Jun 2017 12:35:07 GMT):
I just did that for fabric and node and java sdks

greg.haskins (Thu, 08 Jun 2017 12:35:24 GMT):
cool...as long as no more commits are merged, should be sufficient

greg.haskins (Thu, 08 Jun 2017 12:35:34 GMT):
if they are, rinse+repeat

cbf (Thu, 08 Jun 2017 12:36:03 GMT):
I can check fabric-ca to be certain there are none

greg.haskins (Thu, 08 Jun 2017 12:36:22 GMT):
cool...the hint I use is the parent-sha in the UI

cbf (Thu, 08 Jun 2017 12:36:45 GMT):
BTW, I created the wiki page since you were busy

greg.haskins (Thu, 08 Jun 2017 12:36:51 GMT):
(if you want to check rather than smash the rebase through and take the CI hit

cbf (Thu, 08 Jun 2017 12:36:53 GMT):
https://wiki.hyperledger.org/projects/fabric/release_process_notes

greg.haskins (Thu, 08 Jun 2017 12:36:58 GMT):
awesome, thanks

greg.haskins (Thu, 08 Jun 2017 12:37:01 GMT):
ill add my note above

greg.haskins (Thu, 08 Jun 2017 12:37:07 GMT):
(sorry, was off drawing, heh)

cbf (Thu, 08 Jun 2017 12:37:38 GMT):
your point is related to the one I had already added

lehors (Thu, 08 Jun 2017 12:41:54 GMT):
I've been pulling my hair all (european) day trying to get an environment where make peer-docker would successfully run

lehors (Thu, 08 Jun 2017 12:42:02 GMT):
on Windows 7

lehors (Thu, 08 Jun 2017 12:42:09 GMT):
this is a freaking pain

lehors (Thu, 08 Jun 2017 12:45:21 GMT):
so, here is a brief (as much as I can) summary: Docker Toolbox uses the MinGW environment which comes with Git but unfortunately this is missing the make command. And I have not been able to find a make that works. There is one but it generates Windows paths which docker run doesn't understand. And if I try to use cygwin make it generates a path that docker run accepts but fails to mount

lehors (Thu, 08 Jun 2017 12:46:05 GMT):
I tried all sorts of combinations to no avail

lehors (Thu, 08 Jun 2017 12:47:54 GMT):
interestingly, if I fix by hand the filepaths make generates and run the docker run command manually I can emulate make peer-docker all right

lehors (Thu, 08 Jun 2017 12:48:24 GMT):
I mean the go command completes all right

lehors (Thu, 08 Jun 2017 12:48:56 GMT):
so it's really a matter of getting the right make + docker combo

lehors (Thu, 08 Jun 2017 12:50:24 GMT):
I've managed to get Docker Toolbox running with cygwin instead of MinGW so I get the right make command but the mount of docker run still fails

cbf (Thu, 08 Jun 2017 12:50:56 GMT):
@greg.haskins ok. so what we'll need to do then is merge the release_notes CRs and then rebase the release CRs (I really should have combined them)

lehors (Thu, 08 Jun 2017 12:51:12 GMT):
so I think we should have a note somewhere in the release notes or the end to end doc that people shouldn't expect this to work on Windows 7 (at least)

cbf (Thu, 08 Jun 2017 12:51:17 GMT):
hence my note in the wiki

cbf (Thu, 08 Jun 2017 12:51:52 GMT):
@lehors only for people running make - we would not expect users to do that

cbf (Thu, 08 Jun 2017 12:51:52 GMT):
@lehors only for people running make - we should not expect users to do that

lehors (Thu, 08 Jun 2017 12:52:23 GMT):
right, I'm merely talking about end-to-end

lehors (Thu, 08 Jun 2017 12:52:32 GMT):
that's why getting started is better

lehors (Thu, 08 Jun 2017 12:53:05 GMT):
again, my problem is that currently the end-to-end doc implies this can be done on Windows running Docker Toolbox

lehors (Thu, 08 Jun 2017 12:53:54 GMT):
I will create a JIRA to document my findings and submit a CR to add a note to end-to-end.rst

cbf (Thu, 08 Jun 2017 12:54:33 GMT):
thanks

jimthematrix (Thu, 08 Jun 2017 12:56:13 GMT):
@cbf hi Chris, https://gerrit.hyperledger.org/r/#/c/10159 needs two small (but one of them is critical) changes

cbf (Thu, 08 Jun 2017 13:32:02 GMT):
ok, thanks @jimthematrix for the sharp eyes that caught my cut-n-paste error;-)

mastersingh24 (Thu, 08 Jun 2017 13:33:39 GMT):
@cbf - but I assume that we will actually be using the CHANGELOG that will be merged as part of the CR?

jimthematrix (Thu, 08 Jun 2017 13:33:47 GMT):
np had the benefit of quiet morning while waiting for my son to wake up ;-)

cbf (Thu, 08 Jun 2017 13:33:49 GMT):
the following CRs are ready to be merged https://gerrit.hyperledger.org/r/#/c/10159/ https://gerrit.hyperledger.org/r/#/c/10263/ https://gerrit.hyperledger.org/r/#/c/10261/ https://gerrit.hyperledger.org/r/#/c/10327/

cbf (Thu, 08 Jun 2017 13:34:08 GMT):
please review and +2 and I'll push the blue button

jimthematrix (Thu, 08 Jun 2017 13:37:24 GMT):
https://gerrit.hyperledger.org/r/#/c/10159 is good to go

cbf (Thu, 08 Jun 2017 13:37:35 GMT):
thanks!

smithbk (Thu, 08 Jun 2017 13:42:13 GMT):
one comment on https://gerrit.hyperledger.org/r/#/c/10263

muralisr (Thu, 08 Jun 2017 13:44:59 GMT):
@cbf +2ed https://gerrit.hyperledger.org/r/#/c/10159

cbf (Thu, 08 Jun 2017 13:45:12 GMT):
thanks

cbf (Thu, 08 Jun 2017 13:46:39 GMT):
@smithbk done thanks

smithbk (Thu, 08 Jun 2017 13:49:27 GMT):
+2'ed https://gerrit.hyperledger.org/r/#/c/10263

cbf (Thu, 08 Jun 2017 13:55:31 GMT):
ok, so the SDKs are ready to be merged. I cannot merge java, so @rickr or @jimthematrix will need to do that... once they have been merged, you guys can proceed to tagging the node and java SDKs per instructions in the relevant JIRAs FAB-4389 and FAB-4390

s.narayanan (Thu, 08 Jun 2017 13:55:33 GMT):
Has joined the channel.

cbf (Thu, 08 Jun 2017 13:56:33 GMT):
hold off java not right

cbf (Thu, 08 Jun 2017 13:56:38 GMT):
pom.xml needs updating

cbf (Thu, 08 Jun 2017 13:56:48 GMT):
why didn't we catch this yesterday???

rameshthoomu (Thu, 08 Jun 2017 13:57:20 GMT):
@cbf @rickr updated comment on java patch..

cbf (Thu, 08 Jun 2017 13:59:21 GMT):
ok updated

rameshthoomu (Thu, 08 Jun 2017 14:00:04 GMT):
thanks @cbf

rickr (Thu, 08 Jun 2017 14:01:23 GMT):
thx

rickr (Thu, 08 Jun 2017 14:02:59 GMT):
Was not on the that JIRA ... I think I want to update the README.MD too it has an Alpha2 section

rickr (Thu, 08 Jun 2017 14:04:08 GMT):
probably just want to delete that

cbf (Thu, 08 Jun 2017 14:04:25 GMT):
delete the section?

rickr (Thu, 08 Jun 2017 14:04:29 GMT):
y

cbf (Thu, 08 Jun 2017 14:04:33 GMT):
ok, sec

cbf (Thu, 08 Jun 2017 14:06:06 GMT):
what about the valid fabric and fabric-ca commits? that's not right either

cbf (Thu, 08 Jun 2017 14:06:19 GMT):
thinking you would be best just updating after the release

cbf (Thu, 08 Jun 2017 14:06:31 GMT):
unless the README goes to maven or something

rickr (Thu, 08 Jun 2017 14:07:54 GMT):
@cbf src/test/fixture/sdkintegration/.env should have the tag for what beta is going to be

rickr (Thu, 08 Jun 2017 14:09:15 GMT):
IMAGE_TAG_FABRIC=:x86_64-1.0.0-beta IMAGE_TAG_FABRIC_CA=:x86_64-1.0.0-beta

rickr (Thu, 08 Jun 2017 14:10:24 GMT):
People using the beta shouldn't use those ... they should pull from docker images .. that's why the .env file need changing

rickr (Thu, 08 Jun 2017 14:10:50 GMT):
can you do that in the commit ?

rickr (Thu, 08 Jun 2017 14:11:00 GMT):
@cbf ^^

cbf (Thu, 08 Jun 2017 14:11:06 GMT):
y

rickr (Thu, 08 Jun 2017 14:13:02 GMT):
ahh unless those images are published the verify builds will fail .. I would assume the sdk follow the fabric

rickr (Thu, 08 Jun 2017 14:18:12 GMT):
Did we expect an order to the release Fabric/Fabric CA publish then the SDKs ?

cbf (Thu, 08 Jun 2017 14:35:12 GMT):
we should be able to push them out together...

cbf (Thu, 08 Jun 2017 14:35:16 GMT):
I updated the CR

cbf (Thu, 08 Jun 2017 14:37:39 GMT):
@jimthematrix you can tag sdk-node and push the modules to npm https://jira.hyperledger.org/browse/FAB-4389 https://jira.hyperledger.org/browse/FAB-4395

jimthematrix (Thu, 08 Jun 2017 14:38:08 GMT):
https://gerrit.hyperledger.org/r/#/c/10329/

jimthematrix (Thu, 08 Jun 2017 14:38:23 GMT):
but having CI trouble to clear the build

jimthematrix (Thu, 08 Jun 2017 14:38:54 GMT):
(other CRs in fabric-sdk-node suffering same problem since yesterday, already contacted CI team)

jimthematrix (Thu, 08 Jun 2017 14:39:28 GMT):
4395 as it is now is a duplicate of 4387 (both tasks accomplished at once)

jimthematrix (Thu, 08 Jun 2017 14:39:46 GMT):
i'll repurpose it for preparing the repo for rc1 development

cbf (Thu, 08 Jun 2017 14:55:08 GMT):
so, you want to manual verify?

cbf (Thu, 08 Jun 2017 14:55:21 GMT):
is this intermittent?

jimthematrix (Thu, 08 Jun 2017 14:55:22 GMT):
i think it'd safe to do

jimthematrix (Thu, 08 Jun 2017 14:55:35 GMT):
has been intermittent but today it's gotten worse

jimthematrix (Thu, 08 Jun 2017 14:55:40 GMT):
all x86 builds failed

cbf (Thu, 08 Jun 2017 14:55:41 GMT):
ok

jimthematrix (Thu, 08 Jun 2017 14:55:48 GMT):
all s390 builds were fine

jimthematrix (Thu, 08 Jun 2017 14:56:04 GMT):
and also fabric's e2e verify that also runs the node sdk tests ran fine

jimthematrix (Thu, 08 Jun 2017 14:56:21 GMT):
so it must have something to do with those specific VMs for the node sdk verify CI

cbf (Thu, 08 Jun 2017 14:58:01 GMT):
ok

jimthematrix (Thu, 08 Jun 2017 14:58:50 GMT):
please +2 and merge https://gerrit.hyperledger.org/r/#/c/10329

cbf (Thu, 08 Jun 2017 14:59:18 GMT):
I take it this depends on the fabric and ca being merged

jimthematrix (Thu, 08 Jun 2017 14:59:35 GMT):
then I'll manually push the tag to github, then we can merge https://gerrit.hyperledger.org/r/10349

jimthematrix (Thu, 08 Jun 2017 14:59:57 GMT):
yes

cbf (Thu, 08 Jun 2017 15:00:09 GMT):
@greg.haskins do we push the tag to GH or Gerrit... I would have thought Gerrit

jimthematrix (Thu, 08 Jun 2017 15:00:18 GMT):
or at least once the docker hub publish were done

jimthematrix (Thu, 08 Jun 2017 15:00:48 GMT):
I've always been pushing tags directly to github

jimthematrix (Thu, 08 Jun 2017 15:01:08 GMT):
don't think you can do it with Gerrit

cbf (Thu, 08 Jun 2017 15:01:31 GMT):
I didn't think we could push to GH

jimthematrix (Thu, 08 Jun 2017 15:02:20 GMT):
I learned that from @greg.haskins and was also surprised

jimthematrix (Thu, 08 Jun 2017 15:03:04 GMT):
maybe it does: https://stackoverflow.com/questions/17953713/how-to-push-tag-to-specific-branch-in-gerrit

jimthematrix (Thu, 08 Jun 2017 15:03:25 GMT):
I used annotated tags anyway

cbf (Thu, 08 Jun 2017 15:03:32 GMT):
right

cbf (Thu, 08 Jun 2017 15:05:46 GMT):
AFAIU GH is R/O

cbf (Thu, 08 Jun 2017 15:06:00 GMT):
if you tag GH then the tag does not exist in Gerrit

cbf (Thu, 08 Jun 2017 15:06:07 GMT):
(assuming you can)

rickr (Thu, 08 Jun 2017 15:09:53 GMT):
I tried to push like that to gerrit and got the permission issue. Followed jims advise and pushed the tag GH and it was ok showed up under releases

cbf (Thu, 08 Jun 2017 15:22:32 GMT):
@rjones @greg.haskins ^^ I'm a bit confused how tags end up in Gerrit if they are pushed to GH

cbf (Thu, 08 Jun 2017 15:23:40 GMT):
meanwhile https://gerrit.hyperledger.org/r/#/c/10261/ is ready - had to manually verify due to flakey gosssip failure on Z but let's move forward... of course for tags, we need to get that sorted out

cbf (Thu, 08 Jun 2017 15:29:36 GMT):
gee no one around... I guess the release can wait a few more days - holy crap

cbf (Thu, 08 Jun 2017 15:29:36 GMT):
gee no one around... I guess the release can wait a few more days

cbf (Thu, 08 Jun 2017 15:43:24 GMT):
ok, verified that you CAN push tags to Gerrit, which is what we should be doing, I believe

cbf (Thu, 08 Jun 2017 15:43:36 GMT):
must be annotated, but we want that anyway

cbf (Thu, 08 Jun 2017 15:50:13 GMT):
1786 git tag -aF release-notes.md mytag 1787 git tag 1788 git push origin mytag HEAD:refs/heads/master

cbf (Thu, 08 Jun 2017 15:50:53 GMT):
so, I don't know what the issue was previously but we should push tags to Gerrit IMO

cbf (Thu, 08 Jun 2017 15:51:05 GMT):
those should get mirrored to GH

cbf (Thu, 08 Jun 2017 15:53:28 GMT):
@JonathanLevi or @mastersingh24 can one of you please merge 10261 and 10263

cbf (Thu, 08 Jun 2017 15:53:33 GMT):
thanks

mastersingh24 (Thu, 08 Jun 2017 15:55:16 GMT):
I did 10263 but need 1 more +2 on 10261

cbf (Thu, 08 Jun 2017 15:55:35 GMT):
@rickr and @jimthematrix you can merge 10327 and have LF sign and then push to maven

rickr (Thu, 08 Jun 2017 16:01:40 GMT):
@cbf I really think we need to wait for the docker images to be there

rickr (Thu, 08 Jun 2017 16:01:54 GMT):
If I merge that it will fail

rickr (Thu, 08 Jun 2017 16:02:35 GMT):
never mind ... don't understand it passed

rickr (Thu, 08 Jun 2017 16:03:37 GMT):

Message Attachments

rickr (Thu, 08 Jun 2017 16:03:58 GMT):
the beta needs to be on the uncommitted lines

cbf (Thu, 08 Jun 2017 16:14:06 GMT):
?

cbf (Thu, 08 Jun 2017 16:14:17 GMT):
checkout the patch and amend as needed

cbf (Thu, 08 Jun 2017 16:14:42 GMT):
so, apparently you can't use markdown in annotated tags

cbf (Thu, 08 Jun 2017 16:15:18 GMT):
HTML seems to be ok - but for instance lines starting with # are considered comments, not headings (DOH!)

cbf (Thu, 08 Jun 2017 16:15:40 GMT):
so the release notes I added to the various repos aren't very usable

mastersingh24 (Thu, 08 Jun 2017 16:25:03 GMT):
Not sure what you mean here? (https://chat.hyperledger.org/channel/fabric-release?msg=5opgos7t3W5bPLMKe) @cbf

mastersingh24 (Thu, 08 Jun 2017 16:26:36 GMT):
https://github.com/hyperledger/fabric-ca/blob/master/release_notes/v1.0.0-beta.md looks fine to me

cbf (Thu, 08 Jun 2017 16:38:19 GMT):
I used markdown syntax including headings which are '# foobar'

cbf (Thu, 08 Jun 2017 16:38:38 GMT):
and the # is treated as a comment so they were not carried into the tag's annotation

cbf (Thu, 08 Jun 2017 16:39:23 GMT):
so when created the fabric-ca tag (which should be there) I changed to html

cbf (Thu, 08 Jun 2017 16:39:29 GMT):
hope that works;-)

cbf (Thu, 08 Jun 2017 16:40:13 GMT):
and no

cbf (Thu, 08 Jun 2017 16:40:14 GMT):
https://github.com/hyperledger/fabric-ca/releases/tag/v1.0.0-beta

cbf (Thu, 08 Jun 2017 16:40:38 GMT):
it's true that the most common programming language is profanity

LordGoodman (Thu, 08 Jun 2017 16:44:56 GMT):
will it be very different from alpha2 ？

rjones (Thu, 08 Jun 2017 16:48:02 GMT):
@cbf you (and all other fabric committers) should be able to push tags to the fabric project right now. I am rolling that out more generally right now.

cbf (Thu, 08 Jun 2017 16:48:42 GMT):
thanks

cbf (Thu, 08 Jun 2017 16:49:26 GMT):
can I get a maintainer to +2 https://gerrit.hyperledger.org/r/#/c/10261/ please?

rjones (Thu, 08 Jun 2017 16:56:53 GMT):
done - the maintainers of any project in gerrit can now push tags for that project

jimthematrix (Thu, 08 Jun 2017 17:06:29 GMT):
@cbf Chris, I left a comment in https://gerrit.hyperledger.org/r/#/c/10261, it's an optional update. also @lehors had a comment

cbf (Thu, 08 Jun 2017 17:07:36 GMT):
I'm done

cbf (Thu, 08 Jun 2017 17:07:43 GMT):
seriously let's just move on

jimthematrix (Thu, 08 Jun 2017 17:08:10 GMT):
fine by me (it's optional)

cbf (Thu, 08 Jun 2017 17:10:51 GMT):
ok, merged and tagged

cbf (Thu, 08 Jun 2017 17:11:21 GMT):
https://github.com/hyperledger/fabric/releases/tag/v1.0.0-beta

jimthematrix (Thu, 08 Jun 2017 17:16:26 GMT):
now the master branches are back in business again right?

rameshthoomu (Thu, 08 Jun 2017 17:16:53 GMT):
@cbf see this line [5] https://github.com/hyperledger/fabric/blob/master/CHANGELOG.md#v100-beta (dots) are trimmed here

rameshthoomu (Thu, 08 Jun 2017 17:17:06 GMT):
https://github.com/hyperledger/fabric/releases/tag/v1.0.0-beta

cbf (Thu, 08 Jun 2017 17:19:41 GMT):
??

cbf (Thu, 08 Jun 2017 17:20:11 GMT):
@rameshthoomu not sure what you mean

mastersingh24 (Thu, 08 Jun 2017 17:20:23 GMT):
the link works

rameshthoomu (Thu, 08 Jun 2017 17:20:54 GMT):
yes the link works.. but the version number after CHANGELOG.md is showing `v100-beta..`

rameshthoomu (Thu, 08 Jun 2017 17:21:09 GMT):
minor observation..

cbf (Thu, 08 Jun 2017 17:21:54 GMT):
the link in the release notes is https://github.com/hyperledger/fabric/blob/master/CHANGELOG.md#v100-beta which links to the header in the changelog

cbf (Thu, 08 Jun 2017 17:23:06 GMT):
have the images and binary publish jobs triggered

cbf (Thu, 08 Jun 2017 17:23:07 GMT):
?

rameshthoomu (Thu, 08 Jun 2017 17:23:10 GMT):
yes

mastersingh24 (Thu, 08 Jun 2017 17:23:18 GMT):
@cbf - rebase and merge https://gerrit.hyperledger.org/r/#/q/rc1+status:open

cbf (Thu, 08 Jun 2017 17:23:32 GMT):
yes will get to that

cbf (Thu, 08 Jun 2017 17:24:10 GMT):
done

cbf (Thu, 08 Jun 2017 17:26:10 GMT):
@rickr can u merge 10327 please and then work with @jimthematrix and @rjones to get the jar signed and published to maven central?

rjones (Thu, 08 Jun 2017 17:26:30 GMT):
@jwagantall ^^^

rickr (Thu, 08 Jun 2017 17:27:34 GMT):
yes -- but I really want to see it verify

rickr (Thu, 08 Jun 2017 17:28:52 GMT):
@rameshthoomu I thought too that it's still a manual process

cbf (Thu, 08 Jun 2017 17:30:04 GMT):
Rickr also, you neet to convert the release_notes/v1.0.0-beta.md in sdk-java to plan text notes ala what I did for fabric

rameshthoomu (Thu, 08 Jun 2017 17:30:10 GMT):
@cbf Below is the update from CI: 1) fabric-binaries -- `Pushed` https://nexus.hyperledger.org/content/repositories/releases/org/hyperledger/fabric/fabric-binary/ 2) fabric-ca images -- `Pushed` https://hub.docker.com/r/hyperledger/fabric-ca/tags/ 3) fabric docker images -- `Pushed` https://hub.docker.com/r/hyperledger/fabric-peer/tags/ 4) npm modules -- `Pushed` https://www.npmjs.com/package/fabric-ca-client https://www.npmjs.com/package/fabric-client 5) fabric-sdk-java -- `Yet to start`

cbf (Thu, 08 Jun 2017 17:30:13 GMT):
when you create the tag... if you like, I can do

rickr (Thu, 08 Jun 2017 17:31:16 GMT):
sure - if you can

cbf (Thu, 08 Jun 2017 17:31:25 GMT):
ok, LMK when you merge

rameshthoomu (Thu, 08 Jun 2017 17:34:27 GMT):
yes @rickr at least for this release will do manual publish.. will automate this before next release..

rickr (Thu, 08 Jun 2017 17:35:37 GMT):
@rameshthoomu ETA of Fabric docker images ?

rameshthoomu (Thu, 08 Jun 2017 17:36:07 GMT):
it's done..

rickr (Thu, 08 Jun 2017 17:36:18 GMT):
great

mastersingh24 (Thu, 08 Jun 2017 17:55:51 GMT):
Looks like https://gerrit.hyperledger.org/r/#/c/10305/ is ready

rickr (Thu, 08 Jun 2017 17:56:25 GMT):
merged

rjones (Thu, 08 Jun 2017 17:58:31 GMT):
@rickr it still has a -2 from cbf

rjones (Thu, 08 Jun 2017 17:58:37 GMT):
so don't merge

rickr (Thu, 08 Jun 2017 18:00:04 GMT):
10305 ?

rickr (Thu, 08 Jun 2017 18:00:18 GMT):
done did that

rameshthoomu (Thu, 08 Jun 2017 18:10:43 GMT):
@rickr so we are ready to publish java jar.. pom.xml is on right version.. Shall I publish now?

rickr (Thu, 08 Jun 2017 18:11:13 GMT):
sure

rameshthoomu (Thu, 08 Jun 2017 18:15:17 GMT):
testing java e2e tests on beta images before publish.. Will let you know the update

jimthematrix (Thu, 08 Jun 2017 18:15:20 GMT):
``` jimzhang:fabric-sdk-node jimzhang$ npm show fabric-client { name: 'fabric-client', description: 'SDK for writing node.js applications to interact with [Hyperledger Fabric](http://hyperledger-fabric.readthedocs.io/en/latest/).', 'dist-tags': { latest: '1.0.0-beta', unstable: '1.0.0-snapshot.71' }, ... }

jimthematrix (Thu, 08 Jun 2017 18:15:28 GMT):
same for fabric-ca-client

cbf (Thu, 08 Jun 2017 18:38:17 GMT):
well fricking wonderful - e2e downloads but doesn't run because it says it cannot pull images

cbf (Thu, 08 Jun 2017 18:38:50 GMT):
someone needs to look into this ASAP - I am on JPMC call for next 90 mins and cannot chase

cbf (Thu, 08 Jun 2017 18:39:01 GMT):
@here

cbf (Thu, 08 Jun 2017 18:39:04 GMT):
Starting orderer.example.com peer1.org1.example.com is up-to-date Starting peer0.org1.example.com peer1.org2.example.com is up-to-date peer0.org2.example.com is up-to-date ERROR: for peer0.org1.example.com Cannot start service peer0.org1.example.com: driver failed programming external connectivity on endpoint peer0.org1.example.com (7adac87386fb4bf62a6d8e1046d559357f369864e3a346ea402091c0a23bd425): Error starting userland proxy: Bind for 0.0.0.0:7053 failed: port is already allocated ERROR: for orderer.example.com Cannot start service orderer.example.com: driver failed programming external connectivity on endpoint orderer.example.com (c86f07a877f5ae7cb8e4b1f3a244c3b2d1c36d1bf5f487c2f2bbdc17d7f0ccb5): Error starting userland proxy: Bind for 0.0.0.0:7050 failed: port is already allocated ERROR: Encountered errors while bringing up the project. ERROR !!!! Unable to pull the images

muralisr (Thu, 08 Jun 2017 18:40:59 GMT):
@cbf will look into it....( @rameshthoomu available to help ?)

muralisr (Thu, 08 Jun 2017 18:42:17 GMT):
@cbf one thing before going too deep ... `Error starting userland proxy: Bind for 0.0.0.0:7053 failed: port is already allocated`

muralisr (Thu, 08 Jun 2017 18:43:02 GMT):
any reason you can think of why 7050 , 7054 etc may *already* be up ?

rameshthoomu (Thu, 08 Jun 2017 18:44:07 GMT):
tested e2e flow on different machines with beta images and it worked as expected for us..

rameshthoomu (Thu, 08 Jun 2017 18:44:20 GMT):
will this help `./network_setup.sh restart `

cbf (Thu, 08 Jun 2017 18:45:25 GMT):
phew it was my vagrant env still running

cbf (Thu, 08 Jun 2017 18:45:32 GMT):
sigh we really need to LOSE THAT

muralisr (Thu, 08 Jun 2017 18:45:38 GMT):
vagrant ... :-)

cbf (Thu, 08 Jun 2017 18:45:55 GMT):
next error

cbf (Thu, 08 Jun 2017 18:45:56 GMT):
Caused by: x509: certificate signed by unknown authority (possibly because of "x509: ECDSA verification failure" while trying to verify candidate authority certificate "ca.org1.example.com") Usage: peer channel join [flags] Global Flags: -b, --blockpath string Path to file containing genesis block --cafile string Path to file containing PEM-encoded trusted certificate(s) for the ordering endpoint -c, --chain string In case of a newChain command, the chain ID to create. -f, --file string Configuration transaction file generated by a tool such as configtxgen for submitting to orderer --logging-level string Default logging level and overrides, see core.yaml for full syntax -o, --orderer string Ordering service endpoint --test.coverprofile string Done (default "coverage.cov") -t, --timeout int Channel creation timeout (default 5) --tls Use TLS when communicating with the orderer endpoint -v, --version Display current version of fabric peer server !!!!!!!!!!!!!!! After 5 attempts, PEER1 has failed to Join the Channel !!!!!!!!!!!!!!!! ================== ERROR !!! FAILED to execute End-2-End Scenario ==================

markparz (Thu, 08 Jun 2017 18:46:09 GMT):
we know you love vagrant

muralisr (Thu, 08 Jun 2017 18:50:22 GMT):
;-)

muralisr (Thu, 08 Jun 2017 18:51:17 GMT):
@cbf trying to recreate (1) scripts/bootstrap-1.0.0-beta.sh and (2) cd examples/e2e_cli && ./network_setup.sh up

muralisr (Thu, 08 Jun 2017 18:51:33 GMT):
(cleaned up the env and pulled latest )

cbf (Thu, 08 Jun 2017 18:51:48 GMT):
thx

nickgaski (Thu, 08 Jun 2017 18:56:42 GMT):
hunky dory on my machine

muralisr (Thu, 08 Jun 2017 18:58:27 GMT):
@cbf worked on Mac host... will try vagrant now

cbf (Thu, 08 Jun 2017 19:06:03 GMT):
ok, did a clean run and it worked for me as well

cbf (Thu, 08 Jun 2017 19:06:19 GMT):
must have been some leftover partial success

muralisr (Thu, 08 Jun 2017 19:09:40 GMT):
and worked under vagrant as well

muralisr (Thu, 08 Jun 2017 19:09:40 GMT):
and worked under vagrant as well @cbf

lehors (Thu, 08 Jun 2017 19:23:53 GMT):
as I had indicated the getting-started curl command doesn't work on Windows 7 + Docker Toolbox

lehors (Thu, 08 Jun 2017 19:24:16 GMT):
for some reason the curl doesn't follow the redirect

lehors (Thu, 08 Jun 2017 19:24:35 GMT):
we would have been better off sticking with the true URL...

lehors (Thu, 08 Jun 2017 19:27:12 GMT):
AND not use a compact command that doesn't let the user know what happened

muralisr (Thu, 08 Jun 2017 19:30:39 GMT):
@lehors that's ... a bit worrying

muralisr (Thu, 08 Jun 2017 19:31:22 GMT):
would be nice to play well in windows env

muralisr (Thu, 08 Jun 2017 19:32:35 GMT):
something we can work on post beta perhaps worstcase and doc for now ?

lehors (Thu, 08 Jun 2017 19:33:02 GMT):
I'm trying but I get the feeling of being a bit ignored...

muralisr (Thu, 08 Jun 2017 19:33:26 GMT):
I can help...what can I do ?

jimthematrix (Thu, 08 Jun 2017 19:33:48 GMT):
successfully test fabric-sdk-node/examples/balance-transfer sample web app that pulls down the beta images from docker hub, runs the network, runs the web app and test the REST APIs to drive create/join channel, install/instantiate chaincode, invoke/query chaincode

jimthematrix (Thu, 08 Jun 2017 19:33:48 GMT):
successfully tested fabric-sdk-node/examples/balance-transfer sample web app that pulls down the beta images from docker hub, runs the network, runs the web app and test the REST APIs to drive create/join channel, install/instantiate chaincode, invoke/query chaincode

lehors (Thu, 08 Jun 2017 19:34:12 GMT):
minor nit: the getting started doc doesn't say to change directory to release/xxx before running ./network_setup.sh up

lehors (Thu, 08 Jun 2017 19:34:54 GMT):
otherwise, passed those hurdles I'm happy to say that the script completed

lehors (Thu, 08 Jun 2017 19:34:54 GMT):
otherwise, passed those hurdles I'm happy to say that the script completed successfully

lehors (Thu, 08 Jun 2017 19:35:22 GMT):
I will try a build on vagrant now

lehors (Thu, 08 Jun 2017 19:36:18 GMT):
I'll even rebuild my vagrant env for that matter

rameshthoomu (Thu, 08 Jun 2017 19:36:27 GMT):
@harrijk tested this on windows 7

harrijk (Thu, 08 Jun 2017 19:37:38 GMT):
I ran inside a Docker Quickstart Terminal

harrijk (Thu, 08 Jun 2017 19:37:47 GMT):
on Windows 7

lehors (Thu, 08 Jun 2017 19:37:50 GMT):
what?

mastersingh24 (Thu, 08 Jun 2017 19:37:54 GMT):
@lehors - I had the same issue as you

mastersingh24 (Thu, 08 Jun 2017 19:38:24 GMT):
I then installed curl natively on Windows and updated my PATH in the quickstart terminal

mastersingh24 (Thu, 08 Jun 2017 19:38:46 GMT):
But it does not seem to work at all on Windows 7 with Docker Toolbox

mastersingh24 (Thu, 08 Jun 2017 19:38:53 GMT):
at least the latest version

mastersingh24 (Thu, 08 Jun 2017 19:39:00 GMT):
it can't mount any of the volumes

lehors (Thu, 08 Jun 2017 19:39:44 GMT):
yeah, the env you get with Docket Toolbox is a mini MinGW which actually comes with Windows Git and is very limited

lehors (Thu, 08 Jun 2017 19:39:44 GMT):
yeah, the env you get with Docker Toolbox is a mini MinGW which actually comes with Windows Git and is very limited

lehors (Thu, 08 Jun 2017 19:41:00 GMT):
it doesn't even have make

mastersingh24 (Thu, 08 Jun 2017 19:41:09 GMT):
I'm about to try Windows 10 and Docker for Windows

lehors (Thu, 08 Jun 2017 19:41:25 GMT):
@harrijk what is it that you ran in Docker Quickstart Terminal?

lehors (Thu, 08 Jun 2017 19:41:42 GMT):
I ran the getting started in Docker Quickstart Terminal

harrijk (Thu, 08 Jun 2017 19:42:22 GMT):
Well ... it was a bit of a hack... the curl command couldn't handle the redirect, so i issued curl using the redirected url.

harrijk (Thu, 08 Jun 2017 19:42:31 GMT):
This downloaded all of the x86_64 images

harrijk (Thu, 08 Jun 2017 19:42:43 GMT):
I then went into release/windows...

harrijk (Thu, 08 Jun 2017 19:43:07 GMT):
ran network_setup.sh up beta 10

harrijk (Thu, 08 Jun 2017 19:43:14 GMT):
all tests ran successfully

lehors (Thu, 08 Jun 2017 19:43:47 GMT):
@mastersingh24 indeed, using cygwin curl works

harrijk (Thu, 08 Jun 2017 19:44:06 GMT):
I can also confirm that

lehors (Thu, 08 Jun 2017 19:44:21 GMT):
ok, so we did the same

lehors (Thu, 08 Jun 2017 19:44:30 GMT):
it's not quite out of the box yet

harrijk (Thu, 08 Jun 2017 19:44:38 GMT):
almost there...

lehors (Thu, 08 Jun 2017 19:45:23 GMT):
the short URL isn't worth the trouble

mastersingh24 (Thu, 08 Jun 2017 19:45:23 GMT):
@harrijk - Windows 7?

mastersingh24 (Thu, 08 Jun 2017 19:45:33 GMT):
What does `docker version` show for you

harrijk (Thu, 08 Jun 2017 19:45:37 GMT):
@mastersingh24 Yes, Windows 7

mastersingh24 (Thu, 08 Jun 2017 19:45:44 GMT):
and what folder did you install in?

mastersingh24 (Thu, 08 Jun 2017 19:45:51 GMT):
root of the quickstart terminal?

harrijk (Thu, 08 Jun 2017 19:46:08 GMT):
yes, i installed in the root of the qt term

cbf (Thu, 08 Jun 2017 19:46:14 GMT):
so back from my cust call

cbf (Thu, 08 Jun 2017 19:46:24 GMT):
it works here on mac, I saw a couple windows

harrijk (Thu, 08 Jun 2017 19:46:27 GMT):
Docker version is 1.12.0

lehors (Thu, 08 Jun 2017 19:46:33 GMT):
I did not, I installed into a different dir

silliman (Thu, 08 Jun 2017 19:46:45 GMT):
Has left the channel.

cbf (Thu, 08 Jun 2017 19:46:59 GMT):
@lehors don't understand your concern with the short url

cbf (Thu, 08 Jun 2017 19:47:09 GMT):
we do want to track downloads

lehors (Thu, 08 Jun 2017 19:47:33 GMT):
it doesn't work with the curl one gets with Docker Toolbox

cbf (Thu, 08 Jun 2017 19:47:36 GMT):
we can add troubleshooting to the doc

lehors (Thu, 08 Jun 2017 19:47:49 GMT):
sure

cbf (Thu, 08 Jun 2017 19:47:57 GMT):
for windows?

lehors (Thu, 08 Jun 2017 19:48:04 GMT):
yes

cbf (Thu, 08 Jun 2017 19:48:05 GMT):
what about it doesn't work

lehors (Thu, 08 Jun 2017 19:48:14 GMT):
I've been saying it for 2 days :)

lehors (Thu, 08 Jun 2017 19:48:26 GMT):
it doesn't follow the redirect

cbf (Thu, 08 Jun 2017 19:48:39 GMT):
ok

cbf (Thu, 08 Jun 2017 19:48:44 GMT):
that blows

lehors (Thu, 08 Jun 2017 19:49:04 GMT):
so that's what people will see:

lehors (Thu, 08 Jun 2017 19:49:05 GMT):
$ curl -sSL https://goo.gl/LQkuoh|bash bash: line 1: syntax error near unexpected token `newline' bash: line 1: `'

cbf (Thu, 08 Jun 2017 19:49:08 GMT):
have you tried installing a more recent version?

mastersingh24 (Thu, 08 Jun 2017 19:49:09 GMT):
yep

lehors (Thu, 08 Jun 2017 19:49:17 GMT):
because it feeds the html to bash

lehors (Thu, 08 Jun 2017 19:49:34 GMT):
yes, I installed the latest this morning

mastersingh24 (Thu, 08 Jun 2017 19:49:34 GMT):
@lehors - what does `docker version` show for you?

lehors (Thu, 08 Jun 2017 19:49:45 GMT):
$ docker version Client: Version: 17.05.0-ce API version: 1.29 Go version: go1.7.5 Git commit: 89658be Built: Fri May 5 15:36:11 2017 OS/Arch: windows/amd64 Server: Version: 17.05.0-ce API version: 1.29 (minimum version 1.12) Go version: go1.7.5 Git commit: 89658be Built: Thu May 4 21:43:09 2017 OS/Arch: linux/amd64

cbf (Thu, 08 Jun 2017 19:50:17 GMT):
cbf$ curl --version curl 7.51.0 (x86_64-apple-darwin16.0) libcurl/7.51.0 SecureTransport zlib/1.2.8 Protocols: dict file ftp ftps gopher http https imap imaps ldap ldaps pop3 pop3s rtsp smb smbs smtp smtps telnet tftp Features: AsynchDNS IPv6 Largefile GSS-API Kerberos SPNEGO NTLM NTLM_WB SSL libz UnixSockets

lehors (Thu, 08 Jun 2017 19:50:46 GMT):
$ curl --version curl 7.49.1 (x86_64-w64-mingw32) libcurl/7.49.1 OpenSSL/1.0.2h zlib/1.2.8 libidn /1.32 libssh2/1.7.0 nghttp2/1.11.1 librtmp/2.3 Protocols: dict file ftp ftps gopher http https imap imaps ldap ldaps pop3 pop3s rtmp rtsp scp sftp smtp smtps telnet tftp Features: IDN IPv6 Largefile SSPI Kerberos SPNEGO NTLM SSL libz TLS-SRP HTTP2 Me talink

lehors (Thu, 08 Jun 2017 19:51:04 GMT):
that's the problem

harrijk (Thu, 08 Jun 2017 19:51:06 GMT):
@lehors same thing with me

lehors (Thu, 08 Jun 2017 19:51:18 GMT):
but that's what one gets with Docker Toolbox...

lehors (Thu, 08 Jun 2017 19:52:16 GMT):
on cygwin I have curl 7.52.1 and that works

mastersingh24 (Thu, 08 Jun 2017 19:52:18 GMT):
@lehors - so once you replace curl and download the images, does it work? I don't think it will. I think it works with Docker Toolbox 1.12

cbf (Thu, 08 Jun 2017 19:52:21 GMT):
can u please try to d/l a more current version? https://curl.haxx.se/download.html

mastersingh24 (Thu, 08 Jun 2017 19:52:31 GMT):
We know that works @cbf

lehors (Thu, 08 Jun 2017 19:52:35 GMT):
@mastersingh24 yes, it does

lehors (Thu, 08 Jun 2017 19:52:46 GMT):
so it's not so bad

mastersingh24 (Thu, 08 Jun 2017 19:52:50 GMT):
So e2e worked for you?

cbf (Thu, 08 Jun 2017 19:52:54 GMT):
so, we need guidance to have ppl update to a more recent curl

lehors (Thu, 08 Jun 2017 19:52:56 GMT):
yes

mastersingh24 (Thu, 08 Jun 2017 19:52:59 GMT):
hmm

mastersingh24 (Thu, 08 Jun 2017 19:53:15 GMT):
I was on an earlier rev of Docker Toolbox

mastersingh24 (Thu, 08 Jun 2017 19:53:19 GMT):
let me upgrade

mastersingh24 (Thu, 08 Jun 2017 19:53:25 GMT):
17.03

lehors (Thu, 08 Jun 2017 19:53:26 GMT):
cbf, yes but it's not so easy to do unfortunately

cbf (Thu, 08 Jun 2017 19:53:34 GMT):
do tell

lehors (Thu, 08 Jun 2017 19:54:01 GMT):
because we aren't using the standard Windows commands

lehors (Thu, 08 Jun 2017 19:54:10 GMT):
we use MinGW

lehors (Thu, 08 Jun 2017 19:54:16 GMT):
which is a bit like cygwin

lehors (Thu, 08 Jun 2017 19:54:25 GMT):
it gives a Minimal GNU Windows env

lehors (Thu, 08 Jun 2017 19:54:41 GMT):
but it's not even the standard MinGW

lehors (Thu, 08 Jun 2017 19:54:52 GMT):
so when you try to update it it's a freaking mess

mastersingh24 (Thu, 08 Jun 2017 19:55:05 GMT):
yeah - but it is likely based on one of the later versions of mingw as well

lehors (Thu, 08 Jun 2017 19:55:09 GMT):
I spent the day trying to update it to get a make command that works

lehors (Thu, 08 Jun 2017 19:55:15 GMT):
and couldn't figure it out

mastersingh24 (Thu, 08 Jun 2017 19:55:24 GMT):
it's kinda silly that we need to run Unix emulation for Windows

lehors (Thu, 08 Jun 2017 19:55:25 GMT):
@mastersingh24 yes

cbf (Thu, 08 Jun 2017 19:55:39 GMT):
yeah

mastersingh24 (Thu, 08 Jun 2017 19:55:40 GMT):
I don't even like piping to bash

lehors (Thu, 08 Jun 2017 19:55:45 GMT):
well, it's not silly, it's the only way to survive on Windows! ;-)

mastersingh24 (Thu, 08 Jun 2017 19:55:52 GMT):
we could just have a BAT file

cbf (Thu, 08 Jun 2017 19:55:55 GMT):
get a mac

lehors (Thu, 08 Jun 2017 19:56:00 GMT):
lol

mastersingh24 (Thu, 08 Jun 2017 19:56:06 GMT):
you can run docker and docker-compose from Windows cmd prompt

lehors (Thu, 08 Jun 2017 19:57:15 GMT):
@cbf is that what you're going to tell all the devs out there stuck with Wndows?

cbf (Thu, 08 Jun 2017 19:57:17 GMT):
so, lehors, can you please submit a CR to add windows troubleshooting to the GS

lehors (Thu, 08 Jun 2017 19:57:30 GMT):
ok

cbf (Thu, 08 Jun 2017 19:58:05 GMT):
and at the end, it can say they can simply curl the tarfile and unzip and execute themselves but leave that for last

lehors (Thu, 08 Jun 2017 19:58:22 GMT):
as noted in one my JIRA comments the piping to bash makes things worse

mastersingh24 (Thu, 08 Jun 2017 19:58:24 GMT):
I was unable to get it to work with Docker Toolbox 17.03.0-ce

lehors (Thu, 08 Jun 2017 19:58:34 GMT):
because when it fails you're left with nothing to investigate

mastersingh24 (Thu, 08 Jun 2017 19:58:43 GMT):
upgrading to 17.05.0.-ce

mastersingh24 (Thu, 08 Jun 2017 19:58:43 GMT):
upgrading to 17.05.0-ce

lehors (Thu, 08 Jun 2017 19:59:19 GMT):
if at least we did something like curl xxx > bootstrap.sh && bash < boostrap.sh one could look what's in bootstrap.sh

mastersingh24 (Thu, 08 Jun 2017 20:00:55 GMT):
why can't we just download the script and/or the zip file and then run the script?

lehors (Thu, 08 Jun 2017 20:01:15 GMT):
you tell me!

mastersingh24 (Thu, 08 Jun 2017 20:02:08 GMT):
because someone likes the `curl ... | bash` concept

mastersingh24 (Thu, 08 Jun 2017 20:02:10 GMT):
;)

lehors (Thu, 08 Jun 2017 20:03:02 GMT):
I guess so :)

lehors (Thu, 08 Jun 2017 20:03:31 GMT):
I figured feeding the file to bash is to avoid problem with the file not being executable

lehors (Thu, 08 Jun 2017 20:03:55 GMT):
which is reasonable

lehors (Thu, 08 Jun 2017 20:04:26 GMT):
but piping directly the curl output is too optimistic

mastersingh24 (Thu, 08 Jun 2017 20:06:25 GMT):
@lehors - I assume your username on Windows has no spaces in it?

lehors (Thu, 08 Jun 2017 20:06:36 GMT):
correct

lehors (Thu, 08 Jun 2017 20:06:39 GMT):
it's lehors

mastersingh24 (Thu, 08 Jun 2017 20:07:06 GMT):
Mine is "Gari Singh" - so artifacts failing to generate

lehors (Thu, 08 Jun 2017 20:07:58 GMT):
ah...

lehors (Thu, 08 Jun 2017 20:08:30 GMT):
now I have vagrant failing because it doesn't support my newer version of docker. Oh joy!

troyronda (Thu, 08 Jun 2017 20:09:54 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-release?msg=Npr6kdS7Ff777rb6r) btw - you really need to trust the docs https://goo.gl/LQkuoh isn't going to damage your machine when you just pipe to bash ;)

troyronda (Thu, 08 Jun 2017 20:09:54 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-release?msg=Npr6kdS7Ff777rb6r) btw - you really need to trust the docs that https://goo.gl/LQkuoh isn't going to damage your machine when you just pipe to bash ;)

lehors (Thu, 08 Jun 2017 20:10:16 GMT):
good point!

cbf (Thu, 08 Jun 2017 20:15:37 GMT):
you people

lehors (Thu, 08 Jun 2017 20:56:53 GMT):
for what it's worth, this is where I commented on the curl not working: https://gerrit.hyperledger.org/r/#/c/10247

lehors (Thu, 08 Jun 2017 20:58:06 GMT):
that was yesterday

cbf (Thu, 08 Jun 2017 21:42:40 GMT):
So, I think we're done - it was not as smooth as I might have liked, but we've captured some good feedback here https://wiki.hyperledger.org/projects/fabric/release_process_notes and of course others are welcome to share their feedback as well

cbf (Thu, 08 Jun 2017 21:42:59 GMT):
@here ^^

cbf (Thu, 08 Jun 2017 21:43:19 GMT):
so THANK YOU to all who helped us pull this off

lehors (Thu, 08 Jun 2017 21:44:05 GMT):
and thank you for driving it all with a mighty force

cbf (Thu, 08 Jun 2017 21:59:24 GMT):
@here https://twitter.com/christo4ferris/status/872935969426681857 please amplify

troyronda (Thu, 08 Jun 2017 22:09:38 GMT):
yay!

binhn (Thu, 08 Jun 2017 22:30:24 GMT):
@cbf don't we need to merge this one https://gerrit.hyperledger.org/r/#/c/10301/ ?

cbf (Thu, 08 Jun 2017 22:35:08 GMT):
@binhn yes I was waiting for a clean CI but screw it... let's merge - please +2

cbf (Thu, 08 Jun 2017 22:35:28 GMT):
once we do, we ca resume regular review/merge process

binhn (Thu, 08 Jun 2017 22:35:37 GMT):
ok

cbf (Thu, 08 Jun 2017 22:37:22 GMT):
thx

jtrayfield (Thu, 08 Jun 2017 22:56:10 GMT):
Has joined the channel.

JohnWhitton (Thu, 08 Jun 2017 22:56:14 GMT):
Has joined the channel.

farhan3 (Thu, 08 Jun 2017 22:57:01 GMT):
Has joined the channel.

dwakeman (Thu, 08 Jun 2017 23:04:15 GMT):
Has joined the channel.

sidrmsh (Thu, 08 Jun 2017 23:07:55 GMT):
Has joined the channel.

grapebaba (Fri, 09 Jun 2017 01:15:22 GMT):
Has joined the channel.

qsmen (Fri, 09 Jun 2017 01:36:22 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-release?msg=XB6FjCyev7fwtW2eP) @cbf Thanks. That guideline is useful.

butch.g (Fri, 09 Jun 2017 02:03:37 GMT):
Has joined the channel.

weeds (Fri, 09 Jun 2017 11:21:00 GMT):
Thanks Chris and Jonathan for leading the release effort- lots of hard work got put in,.. and appreciate it!

sqwerrels (Fri, 09 Jun 2017 14:19:44 GMT):
Has joined the channel.

cbf (Fri, 09 Jun 2017 19:14:07 GMT):
@greg.haskins @rameshthoomu https://gerrit.hyperledger.org/r/#/c/10413/ - I have added a target(s) to create a tar file for the release binaries and given it a flatter structure. The intention is also to keep separate from the e2e sample so that the release binaries can be used by installers like homebrew.

cbf (Fri, 09 Jun 2017 19:14:45 GMT):
next step will be to package up the e2e_cli

rameshthoomu (Fri, 09 Jun 2017 19:28:13 GMT):
ok so now `make dist-all` generated tar file per platform.. I have to publish two artificats (tar files and e2e_cli package tar) to nexus ??

rameshthoomu (Fri, 09 Jun 2017 19:28:13 GMT):
ok so now `make dist-all` generated tar file per platform.. CI script have to publish two artificats ( release binaries tar files and e2e_cli package tar) to nexus ??

rameshthoomu (Fri, 09 Jun 2017 19:28:13 GMT):
ok so now `make dist-all` generated tar file per platform.. CI script has to publish two artificats ( release binaries tar files and e2e_cli package tar) to nexus ??

rameshthoomu (Fri, 09 Jun 2017 19:31:29 GMT):
Will update comments to this FAB item https://jira.hyperledger.org/browse/FAB-4152

cbf (Fri, 09 Jun 2017 20:28:39 GMT):
yes, I am working on the e2e part next

cbf (Fri, 09 Jun 2017 20:28:46 GMT):
@rameshthoomu ^^

rameshthoomu (Fri, 09 Jun 2017 20:29:18 GMT):
ok

cbf (Sat, 10 Jun 2017 00:21:58 GMT):
teed up for next week's release https://jira.hyperledger.org/browse/FAB-4518

cbf (Sat, 10 Jun 2017 12:31:44 GMT):
https://wiki.hyperledger.org/projects/fabric/release_process_notes?&#weekly_release_cadence_-_cbf

cbf (Sat, 10 Jun 2017 12:31:57 GMT):
proposed process for weekly releases

dave.enyeart (Sat, 10 Jun 2017 13:33:05 GMT):
@rameshthoomu @cbf Concerning making the tar into a 'flatter structure'... I thought @rameshthoomu had a specific reason for the prior tar structure in alpha2 timeframe, if my memory is right it had something to do with ensuring the e2e had access to the other chaincodes like marbles02. May not be important, but just wanted to ensure @rameshthoomu takes a good look at the new structure relative to the structure that was put in place for alpha2, and confirm that we are ok.

dave.enyeart (Sat, 10 Jun 2017 13:34:20 GMT):
Speaking of structure, given weekly releases nexus is going to get busy given the flat structure. May be better to have a directory per /release/platform in nexus?

cbf (Sat, 10 Jun 2017 15:24:35 GMT):
@dave.enyeart what's in the tarfile has nothing to do with the fabric repo structure - and conflating the two is what makes what we deliver unnecessarily complex

cbf (Sat, 10 Jun 2017 15:25:40 GMT):
we need to be able to deliver binaries and images independent of samples, whether e2e or the new "writing your first app" especially so that we can leverage the likes of NuGet and Homebrew to have legit installers for our tools

JonathanLevi (Mon, 12 Jun 2017 20:12:27 GMT):
----- Good morning/afternoon/evening/night: https://www.hyperledger.org/blog/2017/06/12/hyperledger-fabric-v1-0-0-beta-is-now-available-for-testing -----

lehors (Mon, 12 Jun 2017 21:42:11 GMT):
@JonathanLevi this first paragraph got to have been written by Chris...

lehors (Mon, 12 Jun 2017 21:42:23 GMT):
he always puts links on "here"

lehors (Mon, 12 Jun 2017 21:44:08 GMT):
You can read all about it here and dive into the documentation here. -> You can read all about it in the _Release Notes_ and dive into the _documentation_.

lehors (Mon, 12 Jun 2017 21:44:19 GMT):
I think Chris will never learn though :)

lehors (Mon, 12 Jun 2017 21:45:42 GMT):
For more details on this, see: http://lehors.wordpress.com/2009/01/29/linking-the-proper-way/

JonathanLevi (Mon, 12 Jun 2017 21:54:40 GMT):
OMG. This link is so 2009 !

JonathanLevi (Mon, 12 Jun 2017 21:55:24 GMT):
Why can not simply put everything on a blockchain and start using the Merkel root instead?

cbf (Mon, 12 Jun 2017 22:59:53 GMT):
you people

JonathanLevi (Mon, 12 Jun 2017 23:16:57 GMT):
:-)

JonathanLevi (Mon, 12 Jun 2017 23:17:04 GMT):
BTW: @troyronda: https://jira.hyperledger.org/browse/FAB-2946

troyronda (Mon, 12 Jun 2017 23:29:03 GMT):
i was mainly asking due to the 1.0 label

troyronda (Mon, 12 Jun 2017 23:29:54 GMT):
(at the time - i see its updated now)

JonathanLevi (Mon, 12 Jun 2017 23:45:56 GMT):
Sure thing, thank you!

JonathanLevi (Mon, 12 Jun 2017 23:45:56 GMT):
Sure thing, thank you! Yes, I should have removed the v1.0 label from it much earlier on. Thanks for checking and pointing this out @troyronda

dwakeman (Tue, 13 Jun 2017 00:37:34 GMT):
Has left the channel.

JonathanLevi (Tue, 13 Jun 2017 07:03:17 GMT):
BTW: Unless anyone follows up on the below https://jira.hyperledger.org/browse/FAB-4256 this ticket is likely to get closed tomorrow.

odowdaibm (Tue, 13 Jun 2017 15:45:34 GMT):
Anyone seen issues with peer instantiate getting the following type of errors on beta 1```017-06-13 15:40:24.082 UTC [grpc] Printf -> DEBU 010 transport: http2Client.notifyError got notified that the client transport was broken unexpected EOF.```

odowdaibm (Tue, 13 Jun 2017 15:46:05 GMT):
seems like connection to orderer is broken

yacovm (Tue, 13 Jun 2017 16:15:08 GMT):
what do the orderer logs tell you?

yacovm (Tue, 13 Jun 2017 16:15:23 GMT):
also this isn't related to #fabric-release , let's take it to another channel please? :)

yacovm (Tue, 13 Jun 2017 16:15:23 GMT):
also this isn't related to #fabric-release (this is a more channel), let's take it to another channel please? :)

paapighoda (Wed, 14 Jun 2017 10:56:15 GMT):
Has joined the channel.

alexliu (Thu, 15 Jun 2017 03:26:12 GMT):
Has joined the channel.

dselman (Thu, 15 Jun 2017 20:13:38 GMT):
We released Composer v0.8 today -- which now supports HLFv1beta1 (as well as v0.6). Thanks for all your hard work guys -- we appreciate it. We are seeing people downloading and using within minutes of release!

dselman (Thu, 15 Jun 2017 20:14:32 GMT):
Release notes: https://github.com/hyperledger/composer/releases/tag/v0.8.0

feici02 (Fri, 16 Jun 2017 01:31:50 GMT):
Has joined the channel.

catbus (Fri, 16 Jun 2017 16:02:28 GMT):
Has joined the channel.

sfukazu (Mon, 19 Jun 2017 06:36:28 GMT):
Has joined the channel.

roj (Mon, 19 Jun 2017 10:46:26 GMT):
Has joined the channel.

dongqi (Tue, 20 Jun 2017 08:37:41 GMT):
Has joined the channel.

arner (Tue, 20 Jun 2017 13:36:40 GMT):
Has joined the channel.

weeds (Tue, 20 Jun 2017 16:37:33 GMT):
@scottz posted this on another channel so copying here- Please take a look at the updated Hyperledger-Fabric System Verification Test (SVT) report for v1.0, available @here : https://docs.google.com/spreadsheets/d/1E3-PXchMOWm6DC5xq6RN-NT2YmngKNcG_zQqW0ireY4/edit?usp=sharing It shows the system test summary on first tab, plus a breakdown by "Test Area" in the following tabs which contain individual testcases. We even created Jira tasks to describe each testcase. This report does NOT include everything such as Unit Tests or other manual tests done by various community members, but hopefully it satisfies questions about system test coverage.

JonathanLevi (Tue, 20 Jun 2017 16:38:31 GMT):
@scottz , @weeds : 1. Thank you. 2. Can we email it to the (fabric) mailing list as well?

JonathanLevi (Tue, 20 Jun 2017 16:39:02 GMT):
It's a great report @scottz , thank you!

scottz (Tue, 20 Jun 2017 16:40:31 GMT):
yes, was planning to email it out after giving maintainers a preview :)

JonathanLevi (Tue, 20 Jun 2017 16:41:31 GMT):
BTW: If you want to share stuff with the maintainers, the recommended way is to have one of the maintainers' putting it forward on the maintainers channel, on your behalf.

JonathanLevi (Tue, 20 Jun 2017 16:42:12 GMT):
It's true for PRs, prioritization, discussions, and of course for sharing docs, reports, or sharing info amongst them.

lehors (Tue, 20 Jun 2017 16:44:19 GMT):
@JonathanLevi I know people don't necessarily pay attention to it but I think it would make sense to expand no the info attached to the #release channel to make the policy clear

lehors (Tue, 20 Jun 2017 16:44:19 GMT):
@JonathanLevi I know people don't necessarily pay attention to it but I think it would make sense to expand on the info attached to the #release channel to make the policy clear

lehors (Tue, 20 Jun 2017 16:45:23 GMT):
even though it says it is meant for internal discussion among the maintainers, you could make it clearer that non maintainers should not post there

JonathanLevi (Tue, 20 Jun 2017 16:45:33 GMT):
OK, when I have some time later on today, I can formulate an email or so.

JonathanLevi (Tue, 20 Jun 2017 16:46:00 GMT):
Good point @lehors , I know that people are not doing it "on purpose".

lehors (Tue, 20 Jun 2017 16:46:27 GMT):
email wouldn't hurt but I'm talking about the description of the channel

lehors (Tue, 20 Jun 2017 16:46:54 GMT):
you know the stuff that gets displayed when you hit the little i

lehors (Tue, 20 Jun 2017 16:47:57 GMT):
set it to something like: "DO NOT POST HERE unless you're a maintainer" :)

lehors (Tue, 20 Jun 2017 16:48:25 GMT):
otherwise it looks like a channel where one should go to talk to the maintainers

JonathanLevi (Tue, 20 Jun 2017 16:48:43 GMT):
Oh, I see....

JonathanLevi (Tue, 20 Jun 2017 16:49:16 GMT):
Yes, "we really don't want to make people believe that they should talk to the maintainers " <---- I'm joking

lehors (Tue, 20 Jun 2017 16:49:26 GMT):
lol

JonathanLevi (Tue, 20 Jun 2017 16:50:23 GMT):
OK, let me update it. It should be really a "read only" thing for non-maintainers/community managers.

JonathanLevi (Tue, 20 Jun 2017 16:50:53 GMT):
So that we have these in the open. Of course we could (have) close(d) that channel, but that would defy the whole point.

lehors (Tue, 20 Jun 2017 16:51:13 GMT):
of course to respect the #fabric-maintainers policy I polluted this channel now ;-)

mastersingh24 (Tue, 20 Jun 2017 17:21:30 GMT):
@lehors - you pollute all channels - so it's ok ;)

mastersingh24 (Tue, 20 Jun 2017 17:21:46 GMT):
we've come to expect it from you

lehors (Tue, 20 Jun 2017 17:21:51 GMT):
lol

lehors (Tue, 20 Jun 2017 17:22:14 GMT):
good day to you as well! ;-)

mastersingh24 (Tue, 20 Jun 2017 17:23:04 GMT):
:wave:

JonathanLevi (Tue, 20 Jun 2017 17:30:41 GMT):
Oh, sorry, I was too direct.

JonathanLevi (Tue, 20 Jun 2017 17:30:56 GMT):
@lehors how *is* your day?

JonathanLevi (Tue, 20 Jun 2017 17:30:58 GMT):
How are you?

lehors (Tue, 20 Jun 2017 17:31:29 GMT):
:)

JonathanLevi (Tue, 20 Jun 2017 17:31:30 GMT):
Please, by all means.

lehors (Tue, 20 Jun 2017 17:31:46 GMT):
I'm actually in Beijing where it's 1:31am

JonathanLevi (Tue, 20 Jun 2017 17:31:48 GMT):
If not here, then where would I ask? ;-)

JonathanLevi (Tue, 20 Jun 2017 17:32:08 GMT):
OMG. So you are still still pumped-up from the energy of the talks?

lehors (Tue, 20 Jun 2017 17:32:22 GMT):
lol

lehors (Tue, 20 Jun 2017 17:32:30 GMT):
I'm afraid this is merely called jetlag :)

JonathanLevi (Tue, 20 Jun 2017 17:32:36 GMT):
ha ha.

JonathanLevi (Tue, 20 Jun 2017 17:32:51 GMT):
BTW (and sorry I'm talking about "work"): seems like we are getting a lot more interest/exposure in China these days.

JonathanLevi (Tue, 20 Jun 2017 17:33:20 GMT):
Several people have contacted (me), or through the mailing list, asking if they should use fabric.

lehors (Tue, 20 Jun 2017 17:33:46 GMT):
seems reasonable for the #fabric-release channel

lehors (Tue, 20 Jun 2017 17:34:05 GMT):
but now I'm no longer responsible for polluting it! :-P

JonathanLevi (Tue, 20 Jun 2017 17:34:17 GMT):
I should have warned them about @lehor being on every fabric channel, of course, the main concern was regarding "how ready" it is.

JonathanLevi (Tue, 20 Jun 2017 17:34:17 GMT):
I should have warned them about @lehors being on every fabric channel, of course, the main concern was regarding "how ready" it is.

JonathanLevi (Tue, 20 Jun 2017 17:34:17 GMT):
I should have warned them about @lehors being on every fabric channel, of course, but the main concern seems to be around "how ready" it is.

JonathanLevi (Tue, 20 Jun 2017 17:36:03 GMT):
We should "show off" with how quiet the release channel has been (meaning, no issues), but then again that was before @lehors ' jetlag kicked in.

lehors (Tue, 20 Jun 2017 17:36:35 GMT):
lol

JonathanLevi (Tue, 20 Jun 2017 17:37:20 GMT):
Have a good night. (I"m still trying to figure out what [to propose] that we should do with the maintainers' channel). Catch up later.

JonathanLevi (Tue, 20 Jun 2017 17:37:20 GMT):
Have a good night. (I"m still trying to figure out what [to propose that] we should do with the maintainers' channel). Catch up later.

mastersingh24 (Tue, 20 Jun 2017 17:39:39 GMT):
sounds good

weeds (Tue, 20 Jun 2017 21:33:56 GMT):
@JonathanLevi I saw Barry Mosakowski already post to email. Although there seemed to be a delay- but yes posted to email

jeffgarratt (Tue, 20 Jun 2017 22:53:30 GMT):
any one here seeing issue with gerrit? Specifically bad gateway from nginx?

simsc (Tue, 20 Jun 2017 23:10:44 GMT):
The static security scan and analysis has been uploaded to Jira 4547

rjones (Tue, 20 Jun 2017 23:48:01 GMT):
@jeffgarratt there was a reboot to apply emergency patches

jeffgarratt (Wed, 21 Jun 2017 00:29:17 GMT):
@rjones good deal!! Thnx so much!!

mastersingh24 (Wed, 21 Jun 2017 10:18:25 GMT):
@cbf @nickgaski - Why don't we use versions with RTD?

cbf (Wed, 21 Jun 2017 10:19:13 GMT):
I'd have to double check, but I think that it wants branches

cbf (Wed, 21 Jun 2017 10:19:30 GMT):
post 1.0, we definitely need to look into this

cbf (Wed, 21 Jun 2017 10:19:50 GMT):
btw, I am reworking the configtxlator doc

mastersingh24 (Wed, 21 Jun 2017 10:21:12 GMT):
Ah - I thought it might support tags

cbf (Wed, 21 Jun 2017 10:28:22 GMT):
don't think it is that sophisticated

cbf (Wed, 21 Jun 2017 10:56:27 GMT):
ugh

cbf (Wed, 21 Jun 2017 10:56:34 GMT):
running orderer native is all messed

cbf (Wed, 21 Jun 2017 10:57:06 GMT):
why is it looking for fabric/sampleconfig???

cbf (Wed, 21 Jun 2017 10:57:46 GMT):
ORDERER_GENERAL_LOGLEVEL=debug ORDERER_GENERAL_GENESISMETHOD=file ORDERER_GENERAL_GENESISFILE=config/twoorgs.genesis.block ORDERER_GENERAL_LOCALMSPID=OrdererMSP ORDERER_GENERAL_LOCALMSPDIR=crypto-config/ordererOrganizations/example.com/orderers/orderer.example.com ../bin/orderer 2017-06-21 18:55:03.809 HKT [orderer/main] main -> INFO 001 Starting orderer: Version: development build Go version: go1.8.1 OS/Arch: darwin/amd64 2017-06-21 18:55:03.813 HKT [bccsp_sw] createKeyStoreIfNotExists -> DEBU 002 KeyStore path [/Users/cbf/dev/go/src/github.com/hyperledger/fabric/sampleconfig/crypto-config/ordererOrganizations/example.com/orderers/orderer.example.com/keystore] missing [true]: [] 2017-06-21 18:55:03.814 HKT [bccsp_sw] createKeyStore -> DEBU 003 Creating KeyStore at [/Users/cbf/dev/go/src/github.com/hyperledger/fabric/sampleconfig/crypto-config/ordererOrganizations/example.com/orderers/orderer.example.com/keystore]... 2017-06-21 18:55:03.814 HKT [bccsp_sw] createKeyStore -> DEBU 004 KeyStore created at [/Users/cbf/dev/go/src/github.com/hyperledger/fabric/sampleconfig/crypto-config/ordererOrganizations/example.com/orderers/orderer.example.com/keystore]. 2017-06-21 18:55:03.814 HKT [bccsp_sw] openKeyStore -> DEBU 005 KeyStore opened at [/Users/cbf/dev/go/src/github.com/hyperledger/fabric/sampleconfig/crypto-config/ordererOrganizations/example.com/orderers/orderer.example.com/keystore]...done 2017-06-21 18:55:03.814 HKT [bccsp] initBCCSP -> DEBU 006 Initialize BCCSP [SW] 2017-06-21 18:55:03.815 HKT [msp] getPemMaterialFromDir -> DEBU 007 Reading directory /Users/cbf/dev/go/src/github.com/hyperledger/fabric/sampleconfig/crypto-config/ordererOrganizations/example.com/orderers/orderer.example.com/signcerts 2017-06-21 18:55:03.815 HKT [orderer/main] initializeLocalMsp -> CRIT 008 Failed to initialize local MSP: Could not load a valid signer certificate from directory /Users/cbf/dev/go/src/github.com/hyperledger/fabric/sampleconfig/crypto-config/ordererOrganizations/example.com/orderers/orderer.example.com/signcerts, err stat /Users/cbf/dev/go/src/github.com/hyperledger/fabric/sampleconfig/crypto-config/ordererOrganizations/example.com/orderers/orderer.example.com/signcerts: no such file or directory

mastersingh24 (Wed, 21 Jun 2017 13:10:22 GMT):
@cbf - what directory are you running in?

mastersingh24 (Wed, 21 Jun 2017 13:10:58 GMT):
and `ORDERER_GENERAL_LOCALMSPDIR=crypto-config/ordererOrganizations/example.com/orderers/orderer.example.com` should be `ORDERER_GENERAL_LOCALMSPDIR=crypto-config/ordererOrganizations/example.com/orderers/orderer.example.com/msp`

dave.enyeart (Wed, 21 Jun 2017 13:29:40 GMT):
@cbf I'm attempting byfn. Built release binaries and docker images local on mac. Trying `./byfn.sh -m up`

dave.enyeart (Wed, 21 Jun 2017 13:30:21 GMT):
It fails at chaincode instantiate step:

dave.enyeart (Wed, 21 Jun 2017 13:30:23 GMT):
Error: Error endorsing chaincode: rpc error: code = Unknown desc = Error starting container: API error (404): {"message":"network byfn_default not found"}

dave.enyeart (Wed, 21 Jun 2017 13:30:23 GMT):
```Error: Error endorsing chaincode: rpc error: code = Unknown desc = Error starting container: API error (404): {"message":"network byfn_default not found"}```

mastersingh24 (Wed, 21 Jun 2017 13:31:02 GMT):
@cbf - the root of your issue is the env variable I posted above - you are missing `msp` at the end of localmspdir

mastersingh24 (Wed, 21 Jun 2017 13:31:42 GMT):
I'll assume that you are actually running in the `/Users/cbf/dev/go/src/github.com/hyperledger/fabric/sampleconfig` directory

cbf (Wed, 21 Jun 2017 13:31:58 GMT):
ah thanks

cbf (Wed, 21 Jun 2017 13:32:12 GMT):
well, no

cbf (Wed, 21 Jun 2017 13:32:37 GMT):
actually, was running from somewhere nowhere near the fabric repo

mastersingh24 (Wed, 21 Jun 2017 13:33:06 GMT):
GOPATH=/Users/cbf/dev/go/ ?

cbf (Wed, 21 Jun 2017 13:33:15 GMT):
yes

cbf (Wed, 21 Jun 2017 13:33:58 GMT):
does it look for sampleconfig if it cannot find the msp directory?

mastersingh24 (Wed, 21 Jun 2017 13:34:50 GMT):
when it cannot find your MSP, it tries to create one (well bccsp does). Since you used a relative path, it picks something relative to config path (core/config package)

mastersingh24 (Wed, 21 Jun 2017 13:35:10 GMT):
I usually just set FABRIC_CFG_PATH to be safe

mastersingh24 (Wed, 21 Jun 2017 13:35:28 GMT):
but it all stemmed from not finding the MSP

rameshthoomu (Wed, 21 Jun 2017 13:36:49 GMT):
@dave.enyeart you have to replace **byfn** with **current working dir** name in https://github.com/hyperledger/fabric-samples/blob/master/first-network/base/peer-base.yaml#L15

rameshthoomu (Wed, 21 Jun 2017 13:37:58 GMT):
before replace you have to trim the current dir name..

dave.enyeart (Wed, 21 Jun 2017 13:38:18 GMT):
is this in the instructions?

rameshthoomu (Wed, 21 Jun 2017 13:38:23 GMT):
it should be like this `firstnetwork`

dave.enyeart (Wed, 21 Jun 2017 14:11:58 GMT):
@rameshthoomu Setting the peer-base.yaml CORE_VM_DOCKER_HOSTCONFIG_NETWORKMODE got me further, but i'm hitting another error during chaincode instantiate now:

dave.enyeart (Wed, 21 Jun 2017 14:12:07 GMT):
```Error: Error endorsing chaincode: rpc error: code = Unknown desc = Timeout expired while starting chaincode mycc:1.0(networkid:dev,peerid:peer0.org2.example.com,tx:97827cb0da367eeb9aa37482fceaea5736751567a2836680e2691ccf4b057f07)```

rameshthoomu (Wed, 21 Jun 2017 14:15:11 GMT):
could you please clear the network and try again please..

wlahti (Wed, 21 Jun 2017 14:25:42 GMT):
Has joined the channel.

cbf (Wed, 21 Jun 2017 14:28:09 GMT):
@rameshthoomu why is the CORE_VM_DOCKER_HOSTCONFIG_NETWORKMODE tied to the CWD?

cbf (Wed, 21 Jun 2017 14:28:15 GMT):
that makes no sense

cbf (Wed, 21 Jun 2017 14:28:38 GMT):
that means that the compose file isn't portable?

rameshthoomu (Wed, 21 Jun 2017 14:46:28 GMT):
I am not quite sure why it is tied to CWD but that's how it is working.. I see network mode is not specified in docker-compose file.. @mastersingh24 could you please provide your inputs please..

cbf (Wed, 21 Jun 2017 14:50:21 GMT):
maybe that should be removed?

rameshthoomu (Wed, 21 Jun 2017 14:50:53 GMT):
Will try that

cbf (Wed, 21 Jun 2017 14:57:47 GMT):
didn't work for me

cbf (Wed, 21 Jun 2017 14:58:52 GMT):
@dave.enyeart I got all the way through with the firstnetwork_default value

rameshthoomu (Wed, 21 Jun 2017 14:59:09 GMT):
same for me

cbf (Wed, 21 Jun 2017 15:02:26 GMT):
https://gerrit.hyperledger.org/r/#/c/10913/

dave.enyeart (Wed, 21 Jun 2017 15:04:28 GMT):
after setting FABRIC_CFG_PATH and updating firstnetwork_default value, it works for me as well

rameshthoomu (Wed, 21 Jun 2017 15:05:10 GMT):
@cbf Will abandon this patch https://gerrit.hyperledger.org/r/#/c/10907/

dave.enyeart (Wed, 21 Jun 2017 15:05:22 GMT):
is FABRIC_CFG_PATH needed? if so, it should be documented at the beginning

mastersingh24 (Wed, 21 Jun 2017 15:10:45 GMT):
Sorry - was distracted with something else

cbf (Wed, 21 Jun 2017 15:11:13 GMT):
@rameshthoomu oh sorry did not see that

mastersingh24 (Wed, 21 Jun 2017 15:11:20 GMT):
So here's the network "issue"

cbf (Wed, 21 Jun 2017 15:11:26 GMT):
besides, had to update the basic-network one as well

mastersingh24 (Wed, 21 Jun 2017 15:11:32 GMT):
But it's not actually hard to solve

mastersingh24 (Wed, 21 Jun 2017 15:14:50 GMT):
So by default, when you run Docker Compose, it will create a bridge network. By default, the nae of the network is the *name of the current folder* plus *_default* - so assuming the compose file is in a directory called *firstnetwork*, the Docker network created will be called *firstnetwork_default*

mastersingh24 (Wed, 21 Jun 2017 15:14:50 GMT):
So by default, when you run Docker Compose, it will create a bridge network. By default, the nae of the network is the *name of the current folder* plus *"_default"* - so assuming the compose file is in a directory called *firstnetwork*, the Docker network created will be called *firstnetwork_default*

mastersingh24 (Wed, 21 Jun 2017 15:16:59 GMT):
Normally, one would not care at all about this. The reason we need to care is because when the peer launches chaincode, we need the chaincode container to be able to talk to the peer (and when you use TLS we need the hostname the chaincode uses to access the peer to match the CN/SAN in the TLS certificate used by the peer).

mastersingh24 (Wed, 21 Jun 2017 15:17:35 GMT):
So in order to solve this, we need to connect the chaincode containers to the same bridge network as the peer(s) is (are) running on

mastersingh24 (Wed, 21 Jun 2017 15:17:35 GMT):
So in order to solve this, we need to connect the chaincode containers to the same bridge network as the peer(s) is (are) running on so we leverage `CORE_VM_DOCKER_HOSTCONFIG_NETWORKMODE` which allows you to specify the bridge network the container should join

cbf (Wed, 21 Jun 2017 15:21:12 GMT):
so, we should make that a varianle

cbf (Wed, 21 Jun 2017 15:21:12 GMT):
so, we should make that a variable

mastersingh24 (Wed, 21 Jun 2017 15:21:55 GMT):
If we truly want to make the compose files portable across directories (not sure we really want to take this on now), we can do a few things: 1) require that people pass the `--project-name=firstnetwork` and keep `CORE_VM_DOCKER_HOSTCONFIG_NETWORKMODE=firstnetwork_default` 2) we can leverage the `COMPOSE_PROJECT_NAME` environment variable

mastersingh24 (Wed, 21 Jun 2017 15:22:24 GMT):
But honestly, how much do we want to try to explain to people?

mastersingh24 (Wed, 21 Jun 2017 15:23:02 GMT):
I don't think we should do anything for rc1 though

cbf (Wed, 21 Jun 2017 15:26:06 GMT):
why not just CORE_VM_DOCKER_HOSTCONFIG_NETWORKMODE=$COMPOSE_PROJECT_NAME ?

cbf (Wed, 21 Jun 2017 15:26:15 GMT):
is that what you meant?

mastersingh24 (Wed, 21 Jun 2017 15:46:33 GMT):
We would have to set COMPOSE_PROJECT_NAME is a .env file though

dave.enyeart (Wed, 21 Jun 2017 15:55:31 GMT):
@cbf do we want the release binaries ( /bin directory) within /first-network or as a peer directory? The automated byfn assumes the latter, the manual byfn instructions assumes the former. e.g.:

dave.enyeart (Wed, 21 Jun 2017 15:55:35 GMT):
`./bin/cryptogen generate --config=./crypto-config.yaml`

JonathanLevi (Wed, 21 Jun 2017 16:49:00 GMT):
@binhn & other friends: https://jira.hyperledger.org/browse/FAB-4910

JonathanLevi (Wed, 21 Jun 2017 16:49:42 GMT):
If you have suggestions/additions that you believe we should consider/add to the release notes (of any version)... by all means.

JonathanLevi (Wed, 21 Jun 2017 16:49:47 GMT):
Thanks again

binhn (Wed, 21 Jun 2017 17:25:00 GMT):
thank Jonathan

rameshthoomu (Wed, 21 Jun 2017 17:52:25 GMT):
@mastersingh24 I have updated patch https://gerrit.hyperledger.org/r/#/c/10913/ with your suggested changes.. @cbf

cbf (Wed, 21 Jun 2017 18:57:26 GMT):
@dave.enyeart there are other samples that need them... the way they get installed should be in the root of fabric-samples and invoked ../bin/peer etc

dave.enyeart (Wed, 21 Jun 2017 18:57:36 GMT):
@cbf I’ve run through the complete Build Your First Network. A few minor issues: 1) The network name issue - already being worked: https://gerrit.hyperledger.org/r/#/c/10913 2) The byfn.sh assumes /bin is in a peer directory to /first-network, while the manual instructions assume that /bin is in a subdirectory of /first-network. Which one is correct? 3) The Using CouchDB section uses marbles02 chaincode (JSON based), however the marbles02 chaincode is not available as an example within /first-network. Do we want to copy marbles02 into fabric-samples? (I don’t like having multiple copies in source, ‘fabric' and 'fabric-samples', due to dual maintenance concerns. I assume we’ll eventually remove them from ‘fabric’?) 4) In the doc the manual instructions still reference -p during chaincode instantiate. -p has been removed. This causes an error. 5) In the doc there are some old section name references, which do not exist after the doc refactor - can be fixed together with (4)

cbf (Wed, 21 Jun 2017 18:57:44 GMT):
@rameshthoomu thx

cbf (Wed, 21 Jun 2017 19:16:38 GMT):
@dave.enyeart thanks for the thorough review... will address

dave.enyeart (Wed, 21 Jun 2017 19:16:54 GMT):
ok, let me know if you'd like help on any...

cbf (Wed, 21 Jun 2017 19:22:26 GMT):
will want some eyes on review in a few

cbf (Wed, 21 Jun 2017 19:59:19 GMT):
@dave.enyeart on the -p in instantiate... what lines of the build_network.rst??? I cannot find anything

cbf (Wed, 21 Jun 2017 20:02:36 GMT):
nevermind, found it

cbf (Wed, 21 Jun 2017 20:07:38 GMT):
https://gerrit.hyperledger.org/r/#/c/10947/ https://gerrit.hyperledger.org/r/#/c/10957/

paapighoda (Thu, 22 Jun 2017 09:15:21 GMT):
Has left the channel.

troyronda (Thu, 22 Jun 2017 14:44:47 GMT):
hi @cbf, @JonathanLevi - any updates on the plans for the next release?

weeds (Thu, 22 Jun 2017 16:26:53 GMT):
Chris is traveling so doubt he will respond...

weeds (Thu, 22 Jun 2017 16:27:04 GMT):
ie probably sleeping on some plane from China

cbf (Thu, 22 Jun 2017 22:42:52 GMT):
I'll need to review where we are with @JonathanLevi when I get home late tonight

cbf (Thu, 22 Jun 2017 22:43:17 GMT):
was looking like RC1 tomorrow when I left

cbf (Thu, 22 Jun 2017 22:43:48 GMT):
@mastersingh24 what's the latest from today's testing?

cbf (Thu, 22 Jun 2017 22:44:14 GMT):
I'm just about to board my final leg home

mastersingh24 (Thu, 22 Jun 2017 22:51:53 GMT):
@cbf - so far so good

cbf (Thu, 22 Jun 2017 22:52:09 GMT):
cool

mastersingh24 (Thu, 22 Jun 2017 22:52:17 GMT):
my vote is to get everything ready tomorrow and actually release on Monday

mastersingh24 (Thu, 22 Jun 2017 22:52:33 GMT):
but I can be convinced other wise

cbf (Thu, 22 Jun 2017 22:52:38 GMT):
I have JPMC thing Monday

cbf (Thu, 22 Jun 2017 22:53:25 GMT):
everything should be ready... I have CRs teed up... they just need rebase and regenerate changelig

JonathanLevi (Fri, 23 Jun 2017 00:09:03 GMT):
Yes, let's take another look tonight at where we are...

mastersingh24 (Fri, 23 Jun 2017 02:25:01 GMT):
this fixes byfn in fabric-samples: https://gerrit.hyperledger.org/r/#/c/11043/

mastersingh24 (Fri, 23 Jun 2017 02:25:07 GMT):
needs some love

mastersingh24 (Fri, 23 Jun 2017 02:34:13 GMT):
https://gerrit.hyperledger.org/r/#/c/11043 https://gerrit.hyperledger.org/r/#/c/11027/ https://gerrit.hyperledger.org/r/#/c/9263/

weeds (Fri, 23 Jun 2017 11:52:05 GMT):
@mastersingh24 @cbf @JonathanLevi Mastersingh24 says we should get everything ready.. what help is needed? I know cbf/Jonathan always helps us orchestrate, and I know several of us want to chip in.. so let us know what you need us to do and how you want things done today to get ready.

JonathanLevi (Fri, 23 Jun 2017 11:53:11 GMT):
There is a lot that's still in the making... but reviewing some of the latest docs, is never a bad idea (in retrospect)

JonathanLevi (Fri, 23 Jun 2017 11:53:25 GMT):
We still have stuff that is yet to be committed.

cbf (Fri, 23 Jun 2017 11:53:30 GMT):
https://jira.hyperledger.org/browse/FAB-4518

cbf (Fri, 23 Jun 2017 11:53:37 GMT):
still has 2 open blockers

cbf (Fri, 23 Jun 2017 11:53:46 GMT):
WYFA and WYFCC are not merged

JonathanLevi (Fri, 23 Jun 2017 11:53:50 GMT):
Oh, good morning!

cbf (Fri, 23 Jun 2017 11:54:13 GMT):
also, I should add that there's a potential licensing issue with the PKCS11 dependency

cbf (Fri, 23 Jun 2017 11:54:54 GMT):
it wasn't clear, but apparently they don't want us releasing a RC until we resolve it - I am working on a call with the legal team at LF

cbf (Fri, 23 Jun 2017 11:55:23 GMT):
and I am working with Gari to see if we can just omit PKCS11 dependency and people can add it themselves if they want to use it

cbf (Fri, 23 Jun 2017 11:55:58 GMT):
also, there are two High defects open

weeds (Fri, 23 Jun 2017 11:56:07 GMT):
for FAB-4518, it looks like fab 4430 is the blocker yes? or did I miss something else?

cbf (Fri, 23 Jun 2017 11:56:24 GMT):
open the full list

cbf (Fri, 23 Jun 2017 11:56:48 GMT):
FAB-2291 (actually has 2 CRs

cbf (Fri, 23 Jun 2017 11:56:48 GMT):
FAB-2291 (actually has 2 CRs)

cbf (Fri, 23 Jun 2017 11:57:29 GMT):
we need to get at least https://gerrit.hyperledger.org/r/#/c/9263/ merged

cbf (Fri, 23 Jun 2017 11:57:38 GMT):
I have to respond to Binh's comments

weeds (Fri, 23 Jun 2017 11:57:39 GMT):
ah missed that- thanks cbf

weeds (Fri, 23 Jun 2017 11:57:56 GMT):
clearly i need my coffee today ;-) not sure how you do it

greg.haskins (Fri, 23 Jun 2017 12:25:58 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-release?msg=C2qBsAzRnq34DmiLx) @cbf I haven't been following along, but my general thought on PKCS11 support is it should be off by default

greg.haskins (Fri, 23 Jun 2017 12:26:06 GMT):
not sure that helps the legal issue

cbf (Fri, 23 Jun 2017 12:26:30 GMT):
well, as the quality of my work on Weds shows, everyone has limits of sleep depravation before their work suffers

greg.haskins (Fri, 23 Jun 2017 12:26:31 GMT):
I am envisioning its turned on a) when the user asks, or b) by the packager (when appropriate)

cbf (Fri, 23 Jun 2017 12:27:05 GMT):
turning on or off is not the problem @greg.haskins

cbf (Fri, 23 Jun 2017 12:27:13 GMT):
by default it is off, yes

greg.haskins (Fri, 23 Jun 2017 12:27:14 GMT):
("user" above is someone building from source)

greg.haskins (Fri, 23 Jun 2017 12:27:43 GMT):
to be clear, i mean the default build should be "GOTAGS = -pkcs11"

greg.haskins (Fri, 23 Jun 2017 12:27:57 GMT):
only only +pkcs11 on demand

greg.haskins (Fri, 23 Jun 2017 12:28:00 GMT):
(IMO)

greg.haskins (Fri, 23 Jun 2017 12:28:35 GMT):
so, dont even link it in to the build unless the tag explicitly turned it on

cbf (Fri, 23 Jun 2017 12:29:05 GMT):
right now, they want it removed from source

cbf (Fri, 23 Jun 2017 12:29:21 GMT):
which IMNSHO is silly

greg.haskins (Fri, 23 Jun 2017 12:29:23 GMT):
my argument is: it makes 0 sense to do +pkcs11 in a docker container, and its painful for people to need to deal with libtool-dev when they dont care

greg.haskins (Fri, 23 Jun 2017 12:30:19 GMT):
ok, well, ill leave the lawyers to make silly requests ;) but I wouldn't mind if it became opt-in

muralisr (Fri, 23 Jun 2017 13:15:26 GMT):
https://chat.hyperledger.org/channel/fabric-release?msg=FWR38TygiNbv2oM3t

muralisr (Fri, 23 Jun 2017 13:16:16 GMT):
@cbf will focus on the chaincode tutorials today

cbf (Fri, 23 Jun 2017 13:16:47 GMT):
about to post the fixes per binh and nick's feedback

cbf (Fri, 23 Jun 2017 13:16:55 GMT):
@muralisr ^^

muralisr (Fri, 23 Jun 2017 13:17:18 GMT):
ok

cbf (Fri, 23 Jun 2017 13:23:39 GMT):
https://gerrit.hyperledger.org/r/#/c/10869/

cbf (Fri, 23 Jun 2017 13:25:19 GMT):
https://gerrit.hyperledger.org/r/#/c/9263/

binhn (Fri, 23 Jun 2017 13:27:11 GMT):
thanks @cbf , i'll take another pass https://gerrit.hyperledger.org/r/#/c/9263/

mastersingh24 (Fri, 23 Jun 2017 13:34:48 GMT):
https://gerrit.hyperledger.org/r/#/c/11047/ - easy one

dave.enyeart (Fri, 23 Jun 2017 13:44:06 GMT):
merged

binhn (Fri, 23 Jun 2017 13:46:25 GMT):
@cbf @JonathanLevi We have 1 high defect reported yesterday https://jira.hyperledger.org/browse/FAB-4924, but our tests run fine and we can't recreate. Requested the reporter to provide more info but no response yet, so I propose we lower priority to medium. Advise?

mastersingh24 (Fri, 23 Jun 2017 13:56:49 GMT):
set to unverified and mark as medium IMHO until we hear back

mastersingh24 (Fri, 23 Jun 2017 13:57:02 GMT):
the initial report is cryptic IMHO

mastersingh24 (Fri, 23 Jun 2017 13:57:18 GMT):
That's my vote FWIW

weeds (Fri, 23 Jun 2017 14:02:40 GMT):
thanks

lehors (Fri, 23 Jun 2017 14:42:34 GMT):
fyi: e2e successfully completed on Windows 7 with vagrant

lehors (Fri, 23 Jun 2017 14:43:19 GMT):
I also have a patch to do the same without vagrant but I don't know whether you guys care to merge that or not

lehors (Fri, 23 Jun 2017 14:43:29 GMT):
I can push it if there is interest

ashutosh_kumar (Fri, 23 Jun 2017 14:59:06 GMT):
Has joined the channel.

mastersingh24 (Fri, 23 Jun 2017 15:06:06 GMT):
What's the "patch"?

mastersingh24 (Fri, 23 Jun 2017 15:06:52 GMT):
BTW - @lehors - are you trying https://github.com/hyperledger/fabric-samples/tree/master/first-network ?

binhn (Fri, 23 Jun 2017 16:00:50 GMT):
@rameshthoomu @cbf do we need this https://gerrit.hyperledger.org/r/#/c/11057 ?

rameshthoomu (Fri, 23 Jun 2017 16:03:20 GMT):
yes @binhn

binhn (Fri, 23 Jun 2017 16:06:29 GMT):
ok

dave.enyeart (Fri, 23 Jun 2017 16:35:02 GMT):
@cbf The recent updates to byfn look good and work. Had to make one more fix to the manual instructions for the recent tls ca cert change though:

dave.enyeart (Fri, 23 Jun 2017 16:35:04 GMT):
https://gerrit.hyperledger.org/r/#/c/11065/

weeds (Fri, 23 Jun 2017 16:50:09 GMT):
Just to keep coordinated here it looks like we have https://gerrit.hyperledger.org/r/#/c/10869 and https://gerrit.hyperledger.org/r/#/c/9263

weeds (Fri, 23 Jun 2017 16:50:18 GMT):
right? anything else that I'm missing?

cbf (Fri, 23 Jun 2017 16:52:36 GMT):
think that those are the last two

lehors (Fri, 23 Jun 2017 16:55:23 GMT):
@mastersingh24 I will push my patch - it's a bit involved, I had to use a side script to work around a make limitation/bug - and you can have a look

lehors (Fri, 23 Jun 2017 16:55:33 GMT):
I will look at the first-network next

weeds (Fri, 23 Jun 2017 17:09:10 GMT):
what is the patch number @lehors?

mastersingh24 (Fri, 23 Jun 2017 17:11:41 GMT):
[ Ah - cool. Forgot to read the directions ](https://chat.hyperledger.org/channel/fabric-release?msg=GEoHTqYRiJqYbvPPm) @dave.enyeart

weeds (Fri, 23 Jun 2017 17:12:19 GMT):
looks like people since this AM were reviewing 10869 and 9263- they are now merged

mastersingh24 (Fri, 23 Jun 2017 17:23:39 GMT):
https://gerrit.hyperledger.org/r/10975

mastersingh24 (Fri, 23 Jun 2017 17:25:40 GMT):
@cbf - merge it? ^^^^

cbf (Fri, 23 Jun 2017 17:26:04 GMT):
yep

cbf (Fri, 23 Jun 2017 17:27:14 GMT):
ok @JonathanLevi last remaining thing is the OASIS headers

cbf (Fri, 23 Jun 2017 17:27:24 GMT):
trying to get a call with LF legal

mastersingh24 (Fri, 23 Jun 2017 17:27:44 GMT):
I think my logic on the OASIS thing is sound ;)

cbf (Fri, 23 Jun 2017 17:27:47 GMT):
@here let's lock down any changes please

JonathanLevi (Fri, 23 Jun 2017 17:27:52 GMT):
Yup!

mastersingh24 (Fri, 23 Jun 2017 17:27:58 GMT):
Anything left for docs?

mastersingh24 (Fri, 23 Jun 2017 17:28:13 GMT):
or we go with what we have for now and roll out anything else when it's ready?

cbf (Fri, 23 Jun 2017 17:28:18 GMT):
MORATORIUM on merging to fabric, fabric-ca, fabric-sdk-node, fabric-sdk-java

mastersingh24 (Fri, 23 Jun 2017 17:28:18 GMT):
docs that is

cbf (Fri, 23 Jun 2017 17:28:38 GMT):
I have rebased and updated all the CRs for the release

cbf (Fri, 23 Jun 2017 17:28:53 GMT):
please review them

cbf (Fri, 23 Jun 2017 17:29:05 GMT):
https://gerrit.hyperledger.org/r/#/c/10827/

cbf (Fri, 23 Jun 2017 17:29:15 GMT):
https://gerrit.hyperledger.org/r/#/c/10829/

cbf (Fri, 23 Jun 2017 17:29:24 GMT):
https://gerrit.hyperledger.org/r/#/c/10963/

cbf (Fri, 23 Jun 2017 17:29:57 GMT):
https://gerrit.hyperledger.org/r/#/c/10965/

mastersingh24 (Fri, 23 Jun 2017 17:30:54 GMT):
@cbf - do you also want to create the follow-up CRs so we can immediately merge them as well?

binhn (Fri, 23 Jun 2017 17:36:18 GMT):
can we get 1 more changes in on first app doc https://gerrit.hyperledger.org/r/#/c/11069/ ?

cbf (Fri, 23 Jun 2017 17:36:25 GMT):
I will create them shortly

mastersingh24 (Fri, 23 Jun 2017 17:36:39 GMT):
OK - because we should merge them at the same time

cbf (Fri, 23 Jun 2017 17:36:45 GMT):
@binhn ugh

cbf (Fri, 23 Jun 2017 17:36:47 GMT):
yes

cbf (Fri, 23 Jun 2017 17:36:57 GMT):
but we can't do anything until I talk to LF legal

cbf (Fri, 23 Jun 2017 17:37:01 GMT):
waiting for a call

binhn (Fri, 23 Jun 2017 17:37:11 GMT):
@cbf thank you a million

cbf (Fri, 23 Jun 2017 17:38:05 GMT):
let me know ehen it is merged so I can update the CR for the release

cbf (Fri, 23 Jun 2017 17:38:11 GMT):
@binhn ^^

binhn (Fri, 23 Jun 2017 17:43:44 GMT):
@cbf done

cbf (Fri, 23 Jun 2017 17:45:18 GMT):
thx

weeds (Fri, 23 Jun 2017 17:45:20 GMT):
@binhn @muralisr - can you look at the 4 CR's chris posted to make sure they are ok?

rameshthoomu (Fri, 23 Jun 2017 17:50:10 GMT):
@cbf I have a small change coming in Makefile https://github.com/hyperledger/fabric/blob/master/scripts/bootstrap-1.0.0-rc1.sh#L35

rameshthoomu (Fri, 23 Jun 2017 17:50:10 GMT):
@cbf I have a small change coming in bootstrap script https://github.com/hyperledger/fabric/blob/master/scripts/bootstrap-1.0.0-rc1.sh#L35

binhn (Fri, 23 Jun 2017 17:53:27 GMT):
@weeds looking

binhn (Fri, 23 Jun 2017 17:55:19 GMT):
@rameshthoomu `curl https://nexus.hyperledger.org/content/repositories/releases/org/hyperledger/fabric/fabric-binary/${ARCH}-${VERSION}/hyperledger-fabric-${ARCH}.${VERSION}.tar.gz | tar xz` ?

lehors (Fri, 23 Jun 2017 17:56:52 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-release?msg=nRSTTjCYCRybDjzCs) @weeds sorry I don't have one yet - will post here when I od

lehors (Fri, 23 Jun 2017 17:56:52 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-release?msg=nRSTTjCYCRybDjzCs) @weeds sorry I don't have one yet - will post here when I do

rameshthoomu (Fri, 23 Jun 2017 17:58:03 GMT):
@binhn @cbf https://gerrit.hyperledger.org/r/#/c/11081/1/scripts/bootstrap-1.0.0-rc1.sh

rameshthoomu (Fri, 23 Jun 2017 17:59:10 GMT):
maven is not able identify the hyperledger-fabric-${ARCH}.${VERSION}.tar.gz.. it's always referring fabric-binary

rameshthoomu (Fri, 23 Jun 2017 17:59:10 GMT):
maven is not able identify the hyperledger-fabric-${ARCH}.${VERSION}.tar.gz.. it's always referring fabric-binary-${ARCH}.${VERSION}.tar.gz

binhn (Fri, 23 Jun 2017 18:09:53 GMT):
@rameshthoomu merged

binhn (Fri, 23 Jun 2017 18:10:17 GMT):
@cbf 1 comment/question on https://gerrit.hyperledger.org/r/#/c/10827

JonathanLevi (Fri, 23 Jun 2017 18:14:12 GMT):
@binhn:, Chris and I will add it ourselves, when we finalize the announcement.

JonathanLevi (Fri, 23 Jun 2017 18:14:20 GMT):
(including the formatting, etc...)

binhn (Fri, 23 Jun 2017 18:14:43 GMT):
ah good, thanks

JonathanLevi (Fri, 23 Jun 2017 18:16:37 GMT):
Free service, provided by the devoted, HTML-formatting, release managers ;-)

smithbk (Fri, 23 Jun 2017 18:39:53 GMT):
@cbf Chris, see https://gerrit.hyperledger.org/r/#/c/10829 comment

smithbk (Fri, 23 Jun 2017 18:39:53 GMT):
@cbf Chris, see https://gerrit.hyperledger.org/r/#/c/10829 ... I'll go ahead and fix unless I hear otherwise

cbf (Fri, 23 Jun 2017 18:49:49 GMT):
@smithbk done

smithbk (Fri, 23 Jun 2017 18:53:19 GMT):
@cbf I pushed but looks like script still left SDK node commits in?

cbf (Fri, 23 Jun 2017 18:55:56 GMT):
oh crap

cbf (Fri, 23 Jun 2017 18:57:19 GMT):
I pushed and seems like maybe you clobbered my change?

smithbk (Fri, 23 Jun 2017 18:58:00 GMT):
i guess pushing at same time

smithbk (Fri, 23 Jun 2017 18:58:18 GMT):
I'll leave it to you :-)

bretharrison (Fri, 23 Jun 2017 19:00:06 GMT):
For the NodeSDK, do we change the NPM package version now

lehors (Fri, 23 Jun 2017 19:03:35 GMT):
@mastersingh24 if you want to have a look, my patch is https://gerrit.hyperledger.org/r/#/c/11093/ but I don't think this should be applied for this release - it's still a bit too rough for my taste and I don't see the need to rush this in

lehors (Fri, 23 Jun 2017 19:03:48 GMT):
I will check the samples now

dave.enyeart (Fri, 23 Jun 2017 19:06:03 GMT):
pretty bad formatting issue in BYFN:

dave.enyeart (Fri, 23 Jun 2017 19:06:08 GMT):

Message Attachments

dave.enyeart (Fri, 23 Jun 2017 19:06:21 GMT):
fix is ready: https://gerrit.hyperledger.org/r/#/c/11089/

nickgaski (Fri, 23 Jun 2017 19:13:12 GMT):
and we still have getting started content out there that is really just a duplicate of BYFN. Need getting_started.rst to reflect the content in this patch from Chris - https://gerrit.hyperledger.org/r/#/c/10507/. I think we overlooked this because we restored getting started

nickgaski (Fri, 23 Jun 2017 19:14:56 GMT):
also the link to the application in that piece should be :doc:`write_first_app` not :doc:`write`

cbf (Fri, 23 Jun 2017 19:17:59 GMT):
the fix can go in after

cbf (Fri, 23 Jun 2017 19:18:11 GMT):
I am done rebasing the release CRs

smithbk (Fri, 23 Jun 2017 19:21:12 GMT):
+2'ed https://gerrit.hyperledger.org/r/#/c/10829

nickgaski (Fri, 23 Jun 2017 19:38:29 GMT):
are changing this URL `https://goo.gl/LQkuoh` or the backend script to pull rc1 rather than beta?

nickgaski (Fri, 23 Jun 2017 19:38:29 GMT):
are we changing this URL `https://goo.gl/LQkuoh` or the backend script to pull rc1 rather than beta?

nickgaski (Fri, 23 Jun 2017 19:43:40 GMT):
here's the GS patch - https://gerrit.hyperledger.org/r/#/c/11099/

mastersingh24 (Fri, 23 Jun 2017 19:46:29 GMT):
@nickgaski - I think this is already in the release CR which has been staged: https://gerrit.hyperledger.org/r/#/c/10827/6/docs/source/getting_started.rst

nickgaski (Fri, 23 Jun 2017 19:48:27 GMT):
cool ty. will abandon. I see my URL question is addressed in that patch set too. All gravy

lehors (Fri, 23 Jun 2017 19:58:25 GMT):
cool: first-network worked on my Windows 7 box

lehors (Fri, 23 Jun 2017 19:59:03 GMT):
using the latest docker images I built from master on Windows 7 :)

lehors (Fri, 23 Jun 2017 20:02:02 GMT):
speaking of whether to change the URL or the script behind it when we cut a new release, we also need to learn to keep the old versions of the doc in place

mastersingh24 (Fri, 23 Jun 2017 20:02:20 GMT):
I mentioned that as well the other day @lehors

mastersingh24 (Fri, 23 Jun 2017 20:02:30 GMT):
We are on the same page. Who would have thought ;)

lehors (Fri, 23 Jun 2017 20:02:43 GMT):
I don't believe it! :-)

mastersingh24 (Fri, 23 Jun 2017 20:04:06 GMT):
RTD supports tagged versions as I recall

lehors (Fri, 23 Jun 2017 20:04:25 GMT):
indeed

lehors (Fri, 23 Jun 2017 20:04:45 GMT):
we just haven't made the effort to use it, since 0.6

cbf (Fri, 23 Jun 2017 20:34:18 GMT):
@here spoke with @tkuhrt and LF legal about the OASIS copyrighted headers in our vendored dependency

cbf (Fri, 23 Jun 2017 20:34:52 GMT):
I need to chase a few things down, but suffice to say we can proceed with rc1

mastersingh24 (Fri, 23 Jun 2017 20:43:38 GMT):
@lehors - http://hyperledger-fabric.readthedocs.io/en/stable/ - stable points at some old docs for sure

mastersingh24 (Fri, 23 Jun 2017 20:43:50 GMT):
Who controls the RTD account for fabric?

cbf (Fri, 23 Jun 2017 20:45:13 GMT):
@mastersingh24 I think @rjones but I think that @rameshthoomu has access

cbf (Fri, 23 Jun 2017 20:45:37 GMT):
@JonathanLevi and I are about to cut the release - stay tuned

cbf (Fri, 23 Jun 2017 20:46:41 GMT):
well... check that

cbf (Fri, 23 Jun 2017 20:46:46 GMT):
CI seems b0rked

cbf (Fri, 23 Jun 2017 20:56:10 GMT):
@mastersingh24 https://gerrit.hyperledger.org/r/#/c/10827/ I addressed in the follow-on CR as it was less rebasing madness involved

bretharrison (Fri, 23 Jun 2017 20:56:12 GMT):
@cbf @mastersingh24 When should we change the NodeSDK version number, once test gives the OK tomorrow or when we declare the release GA. If we do it tomorrow then should the version number be 1.0.0-rc1 only to be replaced again with 1.0.0 when we are GA ?

cbf (Fri, 23 Jun 2017 20:56:47 GMT):
@bretharrison where is that done?

cbf (Fri, 23 Jun 2017 20:56:55 GMT):
the version should be 1.0.0-rc1

bretharrison (Fri, 23 Jun 2017 20:57:38 GMT):
There are files called package.json under both fabric-client and fabric-ca-client

cbf (Fri, 23 Jun 2017 21:00:35 GMT):
so those need to be changed now?

bretharrison (Fri, 23 Jun 2017 21:01:06 GMT):
if they get changed now then this will cause a publish to NPM

bretharrison (Fri, 23 Jun 2017 21:01:48 GMT):
so I would think once we are happy , then make that change to cause the publish

rjones (Fri, 23 Jun 2017 21:03:41 GMT):
@cbf @mastersingh24 I might not own every single RTD splinter. the lack of namespace control in RTD is painful

rjones (Fri, 23 Jun 2017 21:05:06 GMT):
I don't own http://hyperledger-fabric.readthedocs.io/en/stable/

rjones (Fri, 23 Jun 2017 21:06:15 GMT):
I own: http://hyperledger-fabric-docs.readthedocs.io/en/latest/

rjones (Fri, 23 Jun 2017 21:06:36 GMT):
s/I/LF, as well as Ramesh,/

mastersingh24 (Fri, 23 Jun 2017 21:07:06 GMT):
@bretharrison @cbf the package.json change should be in the release CR just like we change the Makefile in fabric

cbf (Fri, 23 Jun 2017 21:07:27 GMT):
I updated the release CR and added a post release CR

cbf (Fri, 23 Jun 2017 21:07:48 GMT):
https://gerrit.hyperledger.org/r/#/c/11105/

cbf (Fri, 23 Jun 2017 21:08:07 GMT):
https://gerrit.hyperledger.org/r/#/c/11107/

rjones (Fri, 23 Jun 2017 21:08:58 GMT):

Message Attachments

rjones (Fri, 23 Jun 2017 21:10:30 GMT):
@rameshthoomu please add me as an admin for https://readthedocs.org/projects/hyperledger-fabric/

rameshthoomu (Fri, 23 Jun 2017 21:19:54 GMT):
@rjones done

rjones (Fri, 23 Jun 2017 21:22:30 GMT):
@rameshthoomu I triggered builds for master and 1.0.0-beta (which I think you can see): https://readthedocs.org/projects/hyperledger-fabric/builds/

rameshthoomu (Fri, 23 Jun 2017 21:22:49 GMT):
yes

rjones (Fri, 23 Jun 2017 21:29:04 GMT):
@cbf @mastersingh24 I see that "latest" always points at master. to choose the version of the docs you see you need to click this glyph in the UI:

rjones (Fri, 23 Jun 2017 21:29:46 GMT):

Message Attachments

rjones (Fri, 23 Jun 2017 21:30:09 GMT):

Message Attachments

rameshthoomu (Fri, 23 Jun 2017 21:31:05 GMT):
same for 1.0.0-rc1 ?

rameshthoomu (Fri, 23 Jun 2017 21:31:17 GMT):
once release is done.

rjones (Fri, 23 Jun 2017 21:32:05 GMT):
We'll need to manually add the tags and make them public

rjones (Fri, 23 Jun 2017 21:32:19 GMT):
RTD is less than optimal

rameshthoomu (Fri, 23 Jun 2017 21:36:52 GMT):
@cbf updated comment on https://gerrit.hyperledger.org/r/#/c/10963/

cbf (Fri, 23 Jun 2017 21:54:30 GMT):
it isn't clear to me that we need specific beta/rc1 versions of the docs until post 1.0 when we want to maintain a 1.0errata and 1.1 development

mastersingh24 (Fri, 23 Jun 2017 21:59:42 GMT):
We need to get rid of old version then

mastersingh24 (Fri, 23 Jun 2017 21:59:46 GMT):
other than 0.6

cbf (Fri, 23 Jun 2017 22:06:35 GMT):
fabric and fabric-ca have been tagged and bagged

cbf (Fri, 23 Jun 2017 22:06:51 GMT):
fabric-sdk-node will be done soon as CI completes

cbf (Fri, 23 Jun 2017 22:07:14 GMT):
fabric-sdk-java needs rick - I don't have merge privs

weeds (Fri, 23 Jun 2017 22:09:31 GMT):
@bretharrison @rickr need some help here

cbf (Fri, 23 Jun 2017 22:10:14 GMT):
no for node I am good @weeds

cbf (Fri, 23 Jun 2017 22:10:25 GMT):
java is the one I don't have commit bit

mastersingh24 (Fri, 23 Jun 2017 22:13:47 GMT):
We are not going to be able to commit the Java one until we get a +1 from a maintainer other than Rick

cbf (Fri, 23 Jun 2017 22:20:49 GMT):
ok fabric, fabric-ca and fabric-sdk-node are tagged and bagged

cbf (Fri, 23 Jun 2017 22:22:05 GMT):
let the testing commence

dwakeman (Fri, 23 Jun 2017 22:22:59 GMT):
Has joined the channel.

weeds (Fri, 23 Jun 2017 22:23:31 GMT):
for everyone watching the release channel @bmos299 has a few people who will be testing- they will post if anything urgent comes up on fabric release channel- and also post their sniff test results sometime tomorrow afternoon

simsc (Fri, 23 Jun 2017 22:25:01 GMT):
i left msgs with rick cell and text.

weeds (Fri, 23 Jun 2017 22:26:55 GMT):
@jimthematrix if you are still occasionally looking please see this chat as well as I think needs you and Rick

rickr (Fri, 23 Jun 2017 22:26:56 GMT):
README.md needs updating for release candidate 1

rickr (Fri, 23 Jun 2017 22:27:42 GMT):
https://gerrit.hyperledger.org/r/#/c/10965/

rameshthoomu (Fri, 23 Jun 2017 22:30:52 GMT):
Seems curl is failed to pull correct url... Seems artificat ID is messed in nexus..

weeds (Fri, 23 Jun 2017 22:35:33 GMT):
who can help with that @rameshthoomu

cbf (Fri, 23 Jun 2017 22:40:24 GMT):
ok, RTD has not built the release content

cbf (Fri, 23 Jun 2017 22:40:39 GMT):
I hope that whatever was going on there has not screwed things up

rameshthoomu (Fri, 23 Jun 2017 22:40:58 GMT):
@cbf seems this link is broken https://github.com/hyperledger/fabric/blob/master/scripts/bootstrap-1.0.0-rc1.sh#L35...

cbf (Fri, 23 Jun 2017 22:41:52 GMT):
hmmm... must have been stale cache

cbf (Fri, 23 Jun 2017 22:41:56 GMT):
I seem to have it now

cbf (Fri, 23 Jun 2017 22:47:27 GMT):
@rameshthoomu I thought we merged that change

rameshthoomu (Fri, 23 Jun 2017 22:48:08 GMT):
hyperledger-fabric-${ARCH}.${VERSION}.tar.gz .. Problem is with the `.` before the VERSION..

rameshthoomu (Fri, 23 Jun 2017 22:48:27 GMT):
it should be `-`..

cbf (Fri, 23 Jun 2017 22:48:43 GMT):
ok

rameshthoomu (Fri, 23 Jun 2017 22:49:18 GMT):
that has to change here https://github.com/hyperledger/fabric/blob/master/scripts/bootstrap-1.0.0-rc1.sh#L35

cbf (Fri, 23 Jun 2017 22:54:59 GMT):
https://gerrit.hyperledger.org/r/#/c/11111/

cbf (Fri, 23 Jun 2017 23:16:15 GMT):
ok, so aside from the binary download location, and fabric-sdk-java I think we are good to resume merging to fabric, fabric-ca and fabric-sdk-node

cbf (Fri, 23 Jun 2017 23:16:21 GMT):
@JonathanLevi agree?

JonathanLevi (Sat, 24 Jun 2017 00:09:21 GMT):
_jonathan suggests to not lift the merge freeze, in the meantime_ ;-)

cbf (Sat, 24 Jun 2017 01:20:52 GMT):
https://gerrit.hyperledger.org/r/#/c/11111/3 is read to merge

muralisr (Sat, 24 Jun 2017 01:23:08 GMT):
@cbf ^^^ +2ed... need one more

JonathanLevi (Sat, 24 Jun 2017 01:23:40 GMT):
Merged. Happy to lift up the merge freeze. @cbf ?

JonathanLevi (Sat, 24 Jun 2017 01:23:43 GMT):
Let's do it.

cbf (Sat, 24 Jun 2017 01:24:47 GMT):
yay!

rameshthoomu (Sat, 24 Jun 2017 01:36:05 GMT):
Below is the update on **1.0.0-rc1** 1) fabric-binaries -- Pushed https://nexus.hyperledger.org/content/repositories/releases/org/hyperledger/fabric/hyperledger-fabric/ 2) fabric-ca image -- Pushed https://hub.docker.com/r/hyperledger/fabric-ca/tags/ 3) fabric images -- Pushed https://hub.docker.com/r/hyperledger/fabric-peer/tags/ 4) npm modules -- READY https://www.npmjs.com/package/fabric-client https://www.npmjs.com/package/fabric-ca-client 5) fabric-sdk-java - Manual Push (Jessica) Release Yet to Cut.. **on Hold** 6) Release testing (Ramesh) -- In-Progress

rameshthoomu (Sat, 24 Jun 2017 01:36:05 GMT):
Below is the update on **1.0.0-rc1** 1) fabric-binaries -- **Pushed** https://nexus.hyperledger.org/content/repositories/releases/org/hyperledger/fabric/hyperledger-fabric/ 2) fabric-ca image -- **Pushed** https://hub.docker.com/r/hyperledger/fabric-ca/tags/ 3) fabric images -- **Pushed** https://hub.docker.com/r/hyperledger/fabric-peer/tags/ 4) npm modules -- **Pushed** https://www.npmjs.com/package/fabric-client https://www.npmjs.com/package/fabric-ca-client 5) fabric-sdk-java - Manual Push (Jessica) Release Yet to Cut.. **on Hold** 6) Release testing (Ramesh) -- In-Progress

rameshthoomu (Sat, 24 Jun 2017 01:36:05 GMT):
Below is the update on **1.0.0-rc1** 1) fabric-binaries -- **Pushed** https://nexus.hyperledger.org/content/repositories/releases/org/hyperledger/fabric/hyperledger-fabric/ 2) fabric-ca image -- **Pushed** https://hub.docker.com/r/hyperledger/fabric-ca/tags/ 3) fabric images -- **Pushed** https://hub.docker.com/r/hyperledger/fabric-peer/tags/ 4) npm modules -- **Pushed** https://www.npmjs.com/package/fabric-client https://www.npmjs.com/package/fabric-ca-client 5) fabric-sdk-java - Manual Push **published** https://mvnrepository.com/artifact/org.hyperledger.fabric-sdk-java/fabric-sdk-java 6) Release testing -- Done

weeds (Sat, 24 Jun 2017 13:59:50 GMT):
i got the following early this morning- All looks pretty good. Ratnakar found https://jira.hyperledger.org/browse/FAB-4988 and submitted patch set https://gerrit.hyperledger.org/r/#/c/11119 with some changes from FAB-4904. ...nothing major so far has been found

weeds (Sat, 24 Jun 2017 14:00:28 GMT):
looks like this was to fix the sample for write your first app (thank you Ratnkar for finding this)

weeds (Sat, 24 Jun 2017 14:00:28 GMT):
looks like this was to fix the sample for write your first app (thank you @Ratnakar for finding this)

JonathanLevi (Sat, 24 Jun 2017 14:19:07 GMT):
Good morning. Yes, thanks a lot @Ratnakar - appreciated. We'll merge it once the build/tests are complete.

JonathanLevi (Sat, 24 Jun 2017 14:19:07 GMT):
Good morning. Yes, thanks a lot @Ratnakar - appreciated. We'll merge it once the build/tests are complete. UPDATE: https://gerrit.hyperledger.org/r/#/c/11119 is merged.

JonathanLevi (Sat, 24 Jun 2017 14:19:54 GMT):
Everybody, by all means, please can you spend some time today and tomorrow and try things out. Starting from the samples/guides, etc.

JonathanLevi (Sat, 24 Jun 2017 14:20:47 GMT):
We would like to make a Big Announcement [TM] and call for others to test this with us, so anything/the more we can tackle this weekend - the bettter.

simsc (Sat, 24 Jun 2017 14:22:12 GMT):
i have been playing with byfn. i got a timeout instanciating chain code once in several times.. but as discussed with ramesh barry probably a docker networking thing.

JonathanLevi (Sat, 24 Jun 2017 14:23:57 GMT):
Thanks @simsc. Does anyone else experience something similar to this ^^^

JonathanLevi (Sat, 24 Jun 2017 14:24:49 GMT):
We log anything that's suspicious - but yes, when it doubt, we can "pair" and check that issues are reproducible/consistent/etc.

JonathanLevi (Sat, 24 Jun 2017 14:26:11 GMT):
Do we think that the "docker networking thing" being a configuration/set up issue? *Feel free to file/issue/log things*. We can close issues if/when others chime in.

weeds (Sat, 24 Jun 2017 15:01:49 GMT):
@simsc you are testing on mac yes?

JonathanLevi (Sat, 24 Jun 2017 15:04:05 GMT):
Yes, we need info. System, O/S, environment, and how to repro. This way, others can help in verifying.

simsc (Sat, 24 Jun 2017 15:14:31 GMT):
yep, i spent some time with ramesh Thursday in the lab, he felt sure it was a docker related item.

simsc (Sat, 24 Jun 2017 15:14:49 GMT):
i can't seem to repro it now

rameshthoomu (Sat, 24 Jun 2017 15:16:32 GMT):
@simsc we have cleared all the docker containers, images and did `./byfn -m generate` and `./byfn -m up` it worked.. Also, we observed network is too slow on your machine.

rameshthoomu (Sat, 24 Jun 2017 15:16:32 GMT):
@simsc we have cleared all the docker containers, images and did `./byfn.sh -m generate` and `./byfn.sh -m up` it worked.. Also, we observed network is too slow on your machine.

weeds (Sat, 24 Jun 2017 15:17:43 GMT):
@rameshthoomu so you guys have tested out on windows? linux?...

rameshthoomu (Sat, 24 Jun 2017 15:19:33 GMT):
I don't have windows environment to test .. I have asked @harrijk to test on windows 7

rameshthoomu (Sat, 24 Jun 2017 15:20:14 GMT):
and I have bunch of release jobs triggered from sandbox to test on `x`, `p` and `z` platforms

rameshthoomu (Sat, 24 Jun 2017 15:20:14 GMT):
and I have bunch of release testing (e2e tests) jobs triggered from sandbox to test on `x`, `p` and `z` platforms

weeds (Sat, 24 Jun 2017 15:20:56 GMT):
i think @lehors is helping out also on windows

simsc (Sat, 24 Jun 2017 15:21:27 GMT):
yes, i did all that again this morning. stopping/restarting docker. also ./byfn.sh - m restart. can't seem to capture it again. i will keep playing

muralisr (Sat, 24 Jun 2017 15:37:27 GMT):
ran "write your first" app

muralisr (Sat, 24 Jun 2017 15:37:27 GMT):
ran "write your first" app ..worked

muralisr (Sat, 24 Jun 2017 15:37:27 GMT):
ran "write your first" app on mac ..worked

yacovm (Sat, 24 Jun 2017 15:39:20 GMT):
FWIW my https://github.com/yacovm/fabricDeployment seems to be still working with the latest master branch

JonathanLevi (Sat, 24 Jun 2017 15:39:43 GMT):
Oh man, I should be watching that repo of yours ;-)

JonathanLevi (Sat, 24 Jun 2017 15:39:53 GMT):
[ Amiably ]

JonathanLevi (Sat, 24 Jun 2017 15:40:32 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-release?msg=eSYXAur8AKswdjq9J) Cool!

yacovm (Sat, 24 Jun 2017 15:48:23 GMT):
https://github.com/hyperledger/fabric/blob/master/docs/source/getting_started.rst#id5 the `:doc:`write_first_app` and :doc:`samples` links don't work here, but I guess that's a known problem?

yacovm (Sat, 24 Jun 2017 15:48:23 GMT):
https://github.com/hyperledger/fabric/blob/master/docs/source/getting_started.rst#id5 the `write_first_app` and `samples` links don't work here, but I guess that's a known problem?

dave.enyeart (Sat, 24 Jun 2017 15:55:52 GMT):
yes, that's ok @yacovm , the links are designed to work in readthedocs, and they do work:

dave.enyeart (Sat, 24 Jun 2017 15:55:53 GMT):
https://hyperledger-fabric.readthedocs.io/en/latest/getting_started.html

yacovm (Sat, 24 Jun 2017 15:56:26 GMT):
ah, thanks. I had a suspicion I'm not looking at the right place

yacovm (Sat, 24 Jun 2017 15:57:11 GMT):
Makes sense too, after all markdown != RST

dave.enyeart (Sat, 24 Jun 2017 15:57:27 GMT):
I've tested byfn on mac using download script and readthedocs instructions, everything works fine with both leveldb and couchdb containers

weeds (Sat, 24 Jun 2017 15:57:46 GMT):
Thank you Dave, Yacov, Murali, Clayton

weeds (Sat, 24 Jun 2017 15:58:02 GMT):
and Ramesh

muralisr (Sat, 24 Jun 2017 16:07:05 GMT):
devmode sample in works on mac

simsc (Sat, 24 Jun 2017 16:33:41 GMT):
'write your first app' works for me

simsc (Sat, 24 Jun 2017 16:43:44 GMT):
I see the following in the doc Choosing a Location for the Code If you haven’t been doing programming in Go, you may want to make sure that you have :ref:_Golang installed and your system properly configured.

simsc (Sat, 24 Jun 2017 16:44:07 GMT):
"ref:Golang"

bmos299 (Sat, 24 Jun 2017 17:26:07 GMT):
The quality team has successfully performed some general testing on the release candidate images. The testing covered areas to include, - end-to-end flows driven with the node and java SDKs as well as the cli - various chaincdoes driven through the cli - stressing the orderer - gossip (taking peers up and down) - running through the 'Building Your First Network' and 'Writing Your First Application' from the documentation - ensuring all 'make' commands succeed - the node SDK is published to npm (and tested) and the java sdk will be published to maven once FAB-4522 (https://gerrit.hyperledger.org/r/#/c/10965 ) is merged Over the next week the quality team will ensure the system testing is performed against the release candidate images. The system tests to be performed are all described in the https://docs.google.com/spreadsheets/d/1E3-PXchMOWm6DC5xq6RN-NT2YmngKNcG_zQqW0ireY4/edit#gid=1852797754.

weeds (Sat, 24 Jun 2017 17:27:18 GMT):
I"m in the Glossary. when i click on links such as configuration block which was in green or gossip which was in gossip protocol- the color turns to grey (the other words still remain green). is this intended?

weeds (Sat, 24 Jun 2017 17:28:16 GMT):
Thanks @bmos299 and to the quality team- really appreciate your help on a weekend and for all the work/sniff testing.

cbf (Sat, 24 Jun 2017 17:45:17 GMT):
visited links change color

Sandeep (Sat, 24 Jun 2017 18:24:37 GMT):
Has joined the channel.

JonathanLevi (Sat, 24 Jun 2017 18:25:34 GMT):
:-)

nickgaski (Sat, 24 Jun 2017 18:26:08 GMT):
I imagine we could mess with the css and make them stay green if the grayed out color change seems like an issue

JonathanLevi (Sat, 24 Jun 2017 18:26:38 GMT):
Sure, but by all means, let's prioritize.

nickgaski (Sat, 24 Jun 2017 18:26:57 GMT):
amen

JonathanLevi (Sat, 24 Jun 2017 18:27:20 GMT):
Can someone open a JIRA ticket with the formatting/CSS of links... just so that we have it somewhere.

JonathanLevi (Sat, 24 Jun 2017 18:27:49 GMT):
We really need to check that we pass all possible sanity-checks (that we can carry these 2 days)

lehors (Sat, 24 Jun 2017 20:02:57 GMT):
please, don't screw up with the way links are represented

lehors (Sat, 24 Jun 2017 20:03:24 GMT):
these should always be left to the browser

lehors (Sat, 24 Jun 2017 20:04:41 GMT):
I have successfully ran first network on a windows 7 box, pulling the artifacts with the curl command

lehors (Sat, 24 Jun 2017 20:04:41 GMT):
I have successfully run first network on a windows 7 box, pulling the artifacts with the curl command

lehors (Sat, 24 Jun 2017 20:06:44 GMT):
it's no big deal but I wonder what the rationale for asking confirmation for the user is

lehors (Sat, 24 Jun 2017 20:06:44 GMT):
it's no big deal but I wonder what the rationale for asking confirmation from the user is when running the script

lehors (Sat, 24 Jun 2017 20:15:51 GMT):
not so lucky with first app though

lehors (Sat, 24 Jun 2017 20:16:41 GMT):
npm install seemed to go through fine but node query.js fails

lehors (Sat, 24 Jun 2017 20:17:09 GMT):
note that this may be a node installation problem as I've never used it before on this machine

lehors (Sat, 24 Jun 2017 20:18:03 GMT):
but this is what it looks like:

lehors (Sat, 24 Jun 2017 20:18:04 GMT):
$ node query.js Create a client and set the wallet location Set wallet path, and associate user PeerAdmin with application Check user is enrolled, and set a query URL in the network Make query Assigning transaction_id: 3ab88cbad468edc24dcad6be26cdbc796bca2858eff0af81c3da1 1f9c860d48f error: [client-utils.js]: sendPeersProposal - Promise is rejected: Error: Connec t Failed at C:\Users\lehors\Documents\Projects\Go\src\github.com\hyperledger\fabric-s amples\fabcar\node_modules\grpc\src\node\src\client.js:434:17 returned from query Query result count = 1 error from query = { Error: Connect Failed at C:\Users\lehors\Documents\Projects\Go\src\github.com\hyperledger\fabric-s amples\fabcar\node_modules\grpc\src\node\src\client.js:434:17 code: 14, metadata : Metadata { _internal_repr: {} } } Response is Error: Connect Failed

lehors (Sat, 24 Jun 2017 20:18:04 GMT):
$ node query.js Create a client and set the wallet location Set wallet path, and associate user PeerAdmin with application Check user is enrolled, and set a query URL in the network Make query Assigning transaction_id: 3ab88cbad468edc24dcad6be26cdbc796bca2858eff0af81c3da1 1f9c860d48f error: [client-utils.js]: sendPeersProposal - Promise is rejected: Error: Connect Failed at C:\Users\lehors\Documents\Projects\Go\src\github.com\hyperledger\fabric-samples\fabcar\node_modules\grpc\src\node\src\client.js:434:17 returned from query Query result count = 1 error from query = { Error: Connect Failed at C:\Users\lehors\Documents\Projects\Go\src\github.com\hyperledger\fabric-samples\fabcar\node_modules\grpc\src\node\src\client.js:434:17 code: 14, metadata: Metadata { _internal_repr: {} } } Response is Error: Connect Failed

binhn (Sat, 24 Jun 2017 20:31:06 GMT):
@lehors not on Windows, so just a guess here -- could be some docker ps left over from previous run; try to clean all ps and connections; ie `docker rm ` and `docker network prune`

lehors (Sat, 24 Jun 2017 20:31:49 GMT):
no, not that easy I'm afraid

lehors (Sat, 24 Jun 2017 20:32:03 GMT):
I've restarted with a totally clean slate

lehors (Sat, 24 Jun 2017 20:33:21 GMT):
for the sake of the exercise I even removed *every* image I had on that machine

binhn (Sat, 24 Jun 2017 20:35:39 GMT):
ok, maybe try to debug with CLI by doing the same query to see if you can connect to the peer

lehors (Sat, 24 Jun 2017 20:36:03 GMT):
yep, I'm going to start digging to see what I can find

mastersingh24 (Sat, 24 Jun 2017 20:37:53 GMT):
The issue is that localhost will not work on Windows (https://chat.hyperledger.org/channel/fabric-release?msg=hAfgeyXpAnowKzEwN) @lehors

mastersingh24 (Sat, 24 Jun 2017 20:38:17 GMT):
You need to replace it with the IP that Docker Quickstart terminal prints out

lehors (Sat, 24 Jun 2017 20:38:58 GMT):
ok, why doesn't localhost work?

mastersingh24 (Sat, 24 Jun 2017 20:40:43 GMT):
Because Docker Toolbox uses Virtual box and it only sets it up on a bridge network

mastersingh24 (Sat, 24 Jun 2017 20:41:13 GMT):
so when Docker exposes a port, it exposes it on the Virtual Box network which is only bound to the brige network

mastersingh24 (Sat, 24 Jun 2017 20:41:13 GMT):
so when Docker exposes a port, it exposes it on the Virtual Box network which is only bound to the bridge network

lehors (Sat, 24 Jun 2017 20:42:36 GMT):
I see - another case where Docker Toolbox loses :-(

mastersingh24 (Sat, 24 Jun 2017 20:42:42 GMT):
Recall that in the Vagrant dev environment we specifically expose ports on the host system but if you tried to run Docker even in the dev Vagrant image and used a different port you would not see it on localhost

mastersingh24 (Sat, 24 Jun 2017 20:43:37 GMT):
anyway - that's my theory as to why it's not working

mastersingh24 (Sat, 24 Jun 2017 20:43:46 GMT):
The localhost part is 100% correct though

mastersingh24 (Sat, 24 Jun 2017 20:43:47 GMT):
;)

lehors (Sat, 24 Jun 2017 20:44:03 GMT):
:)

lehors (Sat, 24 Jun 2017 20:44:22 GMT):
ok, thanks for the tip

jyellick (Sat, 24 Jun 2017 21:06:46 GMT):
Just ran through "Writing your first application" on Linux, with Node 7.10 (which I know is not officially supported), but encountered no errors. Not a showstopper, but `query.js` seems to use a mix of spaces and tabs which makes it look pretty ugly depending on your tab width.

jyellick (Sat, 24 Jun 2017 21:06:46 GMT):
Just ran through "Writing your first application" on Linux, with Node 7.10 (which I know is not officially supported, but seemed like something users are going to accidentally try), but encountered no errors. Not a showstopper, but `query.js` seems to use a mix of spaces and tabs which makes it look pretty ugly depending on your tab width.

mastersingh24 (Sat, 24 Jun 2017 21:32:48 GMT):
@jyellick - https://gerrit.hyperledger.org/r/11131

mrshah-ibm (Sun, 25 Jun 2017 03:04:13 GMT):
Has joined the channel.

nickgaski (Sun, 25 Jun 2017 14:13:56 GMT):
@lehors - FYI, this is from David. ```for windows 7. `npm install` will fail w/o an OpenSSL dll you can get from installing `Win64 OpenSSL v1.0.2k```

lehors (Sun, 25 Jun 2017 15:26:37 GMT):
Yeah, thanks, but I think in passed that point

lehors (Sun, 25 Jun 2017 15:26:37 GMT):
Yeah, thanks, but I think I'm passed that point

elli-androulaki (Sun, 25 Jun 2017 16:17:00 GMT):
Hi, I went over the two tutorials (https://hyperledger-fabric.readthedocs.io/en/latest/getting_started.html#tutorials) and applied the instructions step by step. It worked like a charm. I have one (minor) comment: The user is prompted to go over “Writing your own application” tutorial first (https://hyperledger-fabric.readthedocs.io/en/latest/write_first_app.html) and then for the “Building your first network” (https://hyperledger-fabric.readthedocs.io/en/latest/build_network.html). If one tries to do them in this order, then the first part of the second tutorial would output an error (some containers already exist from the previous tutoria). Perhaps some link to how to clean up your setup at the end of the second tutorial or the begining of the second would be helpful for the beginners.

elli-androulaki (Sun, 25 Jun 2017 16:17:00 GMT):
Hi, I went over the two tutorials (https://hyperledger-fabric.readthedocs.io/en/latest/getting_started.html#tutorials) and applied the instructions step by step. It worked like a charm. I have one (minor) comment: The user is prompted to go over “Writing your own application” tutorial first (https://hyperledger-fabric.readthedocs.io/en/latest/write_first_app.html) and then for the “Building your first network” (https://hyperledger-fabric.readthedocs.io/en/latest/build_network.html). If one tries to do them in this order, then the first part of the second tutorial would output an error (some containers already exist/are in use as a result of the completion of the first tutorial). Perhaps a link to how to clean up your setup (at the end of the second tutorial or the beginning of the second) would be helpful for the beginners.

cbf (Sun, 25 Jun 2017 19:40:39 GMT):
writing your first app should be refactored to use basic-network which has a teardown script that woukd avoid this.

latitiah (Sun, 25 Jun 2017 20:27:53 GMT):
Has joined the channel.

yacovm (Sun, 25 Jun 2017 21:18:20 GMT):
I'm sure it's known but in case it isn't - it looks like the `-e` flag in `writing your first app` isn't supported in earlier docker versions (i.e 1.12.5), in the `Prerequisites` page it is said that ` Docker v1.12 or greater is required.` but I have `1.12.5` and the `-e` flag didn't work for me and also isn't present in the `docker exec --help` list: ``` Usage: docker exec [OPTIONS] CONTAINER COMMAND [ARG...] Run a command in a running container -d, --detach Detached mode: run command in the background --detach-keys Override the key sequence for detaching a container --help Print usage -i, --interactive Keep STDIN open even if not attached --privileged Give extended privileges to the command -t, --tty Allocate a pseudo-TTY -u, --user Username or UID (format: [:]) ``` Perhaps we should re-write the script to not use the `-e` flag?

yacovm (Sun, 25 Jun 2017 21:18:20 GMT):
I'm sure it's known but in case it isn't - it looks like the `-e` flag in `writing your first app` isn't supported in earlier docker versions (i.e 1.12.5), in the `Prerequisites` page it is said that ` Docker v1.12 or greater is required.` but I have `1.12.5` in one of my VMs and the `-e` flag didn't work for me and also isn't present in the `docker exec --help` list: ``` Usage: docker exec [OPTIONS] CONTAINER COMMAND [ARG...] Run a command in a running container -d, --detach Detached mode: run command in the background --detach-keys Override the key sequence for detaching a container --help Print usage -i, --interactive Keep STDIN open even if not attached --privileged Give extended privileges to the command -t, --tty Allocate a pseudo-TTY -u, --user Username or UID (format: [:]) ``` Perhaps we should re-write the script to not use the `-e` flag?

cbf (Sun, 25 Jun 2017 21:54:30 GMT):
hmmm, searching the release notes does not reveal any useful hint as to when it was added @yacovm

cbf (Sun, 25 Jun 2017 21:54:53 GMT):
I would suggest a more recent version of Docker, frankly

mastersingh24 (Sun, 25 Jun 2017 21:56:47 GMT):
yeah - we should recommend the latest CE version when we publish 1.0.0

mastersingh24 (Sun, 25 Jun 2017 21:56:53 GMT):
But -e has been around for a long time

mastersingh24 (Sun, 25 Jun 2017 21:56:59 GMT):
Since way before 1.12

mastersingh24 (Sun, 25 Jun 2017 21:57:14 GMT):
oh - maybe not for exec

mastersingh24 (Sun, 25 Jun 2017 21:57:15 GMT):
I see

mastersingh24 (Sun, 25 Jun 2017 21:57:23 GMT):
my bad

cbf (Sun, 25 Jun 2017 21:59:03 GMT):
which version are we testing with?

cbf (Sun, 25 Jun 2017 22:27:32 GMT):
yeah, I looked through the release notes and didn't find a mention

cbf (Sun, 25 Jun 2017 22:28:23 GMT):
agree we should probably recommend latest... at the very least we should update prerequisites to indicare which version we are tasting

yacovm (Mon, 26 Jun 2017 10:27:41 GMT):
Why update the prerequisites just because of this `-e` flag though? all our scripts in fabric work with docker 12.5. Maybe just update the script to not use `-e` ?

cbf (Mon, 26 Jun 2017 11:11:48 GMT):
well, we are not testing against versions that old for starters - we shouldn't be making claims we cannot really defend

yacovm (Mon, 26 Jun 2017 11:13:11 GMT):
ok, well in that case I guess we need to crank up the minimum version

simsc (Mon, 26 Jun 2017 12:50:48 GMT):
yes, I saw the same thing elli mentioned above

xixuejia (Mon, 26 Jun 2017 14:53:42 GMT):
Has joined the channel.

joe-alewine (Mon, 26 Jun 2017 15:12:35 GMT):
If I could just urge any maintainer -- other than Chris, who has already obliged -- to give a +2 to https://gerrit.hyperledger.org/r/#/c/10971/ All that's been done here is to update images (and remove some others) to conform to our current image styles. As it is this doc looks very out of sync with the new Writing Your First App doc These images will change again soon -- the design team pushed these out to help improve the look of the doc but is working on finalized versions -- but even this intermediary step would help make the docs look more organized and professional. Thank you

joe-alewine (Mon, 26 Jun 2017 15:12:35 GMT):
If I could just urge any maintainer -- other than Chris, who has already obliged -- to give a +2 to https://gerrit.hyperledger.org/r/#/c/10971/ All that's been done here is to update images (and remove some others) to conform to our current image styles. Without a merge this doc looks very out of sync with the new Writing Your First App doc. These images will change again soon -- the design team pushed these out to help improve the look of the doc but is working on finalized versions -- but even this intermediary step would help make the docs look more organized and professional. Thank you.

rameshthoomu (Mon, 26 Jun 2017 15:21:15 GMT):
@joe-alewine please post this in #fabric-pr-review channel

mrshah-ibm (Mon, 26 Jun 2017 15:44:14 GMT):
looks like it was added in https://github.com/docker/docker-ce/commit/bf1e1cd730647e933fdc349a6d5b3d46d2e760a2

holocron (Mon, 26 Jun 2017 15:55:32 GMT):
Has joined the channel.

JonathanLevi (Mon, 26 Jun 2017 19:15:10 GMT):
Congrats, everyone!

JonathanLevi (Mon, 26 Jun 2017 19:15:11 GMT):
https://lists.hyperledger.org/pipermail/hyperledger-announce/2017-June/000010.html

scottz (Mon, 26 Jun 2017 21:57:05 GMT):
Some exit criteria are listed here: https://wiki.hyperledger.org/projects/fabric/release_exit_criteria . Is there anyone planning to create a subpage for each release (v1.0, v2.0...), to permanently post artifacts such as: the crypto export compliance audit results, the jira bug report summary showing no high/highest bugs, scan result showing no license violations, results of security scans (static and dynamic), etc. etc.

scottz (Mon, 26 Jun 2017 21:57:13 GMT):
Ramesh and I were thinking that would be a good possible home for the final code coverage report for the actual v1.0 release, and a snapshot of the summary page (or more) of SVT test results, rather than creating multple links on that main fabric wiki page to subpages for each item.

scottz (Mon, 26 Jun 2017 21:57:13 GMT):
Ramesh and I were thinking that would be a good possible home for the final code coverage report for the actual v1.0 release, and a snapshot of the summary page (or more) of SVT test results, rather than creating several links tfor a variety of artifacts under the "Releases" header on the main fabric wiki page to subpages for each item.

scottz (Mon, 26 Jun 2017 21:57:13 GMT):
Ramesh and I were thinking that would be a good possible home for the final code coverage report for the actual v1.0 release, and a snapshot of the summary page (or more) of SVT test results, rather than creating several links to subpages for a variety of artifacts under the "Releases" header on the main fabric wiki page https://wiki.hyperledger.org/projects/fabric.

scottz (Mon, 26 Jun 2017 22:06:08 GMT):
@JonathanLevi I don't see that wiki mentioned in your email to the distribution list, so maybe it is not a good formal place for those items; do you have another ideas if those things should be collected or where they could be stored?

JonathanLevi (Mon, 26 Jun 2017 22:07:23 GMT):
Which things specifically?

JonathanLevi (Mon, 26 Jun 2017 22:07:34 GMT):
1. "final code coverage report"

JonathanLevi (Mon, 26 Jun 2017 22:07:48 GMT):
2. "SVT test results"

JonathanLevi (Mon, 26 Jun 2017 22:07:55 GMT):
...

JonathanLevi (Mon, 26 Jun 2017 22:08:37 GMT):
Please list them out explicitly and we'll work to find a good place and a way to evaluate/share.

JonathanLevi (Mon, 26 Jun 2017 22:08:58 GMT):
Some tests (/results) can be part of the CI

JonathanLevi (Mon, 26 Jun 2017 22:10:21 GMT):
... Please be a bit more specific @scottz - so that I don't give the wrong answer in case I didn't understand or a "blank check" over things that I will need to run by all the fellow maintainers. THanks.

ynamiki (Tue, 27 Jun 2017 00:09:14 GMT):
Has joined the channel.

DeutscheBahn-BlockchainDev (Tue, 27 Jun 2017 08:38:24 GMT):
Has joined the channel.

cbf (Tue, 27 Jun 2017 13:18:08 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-release?msg=J6HLYPHaxvD8pi5ud) @scottz I don't think we need to do that...

cbf (Tue, 27 Jun 2017 13:18:42 GMT):
also the release criteria is just that, criteria - not a page to post other stuff

simsc (Tue, 27 Jun 2017 13:53:55 GMT):
At one point we discussed adding a QA section to the wiki. The section could be an overview of test coverage describing UT coverage including links to jenkins unit tests and svt coverage with links pointing to svt doc, etc, etc.

simsc (Tue, 27 Jun 2017 13:54:44 GMT):
This would not be tied so much to release criteria, but a describe test coverage in general

cbf (Tue, 27 Jun 2017 13:56:20 GMT):
that's fine

cbf (Tue, 27 Jun 2017 13:56:32 GMT):
I just don't want the release criteria page cluttered

elli-androulaki (Tue, 27 Jun 2017 13:57:24 GMT):
Hi, a CR on updating documentation to indicate non-support of RSA https://gerrit.hyperledger.org/r/#/c/11189/

cbf (Tue, 27 Jun 2017 13:58:48 GMT):
@elli-androulaki just a nit

cbf (Tue, 27 Jun 2017 13:59:08 GMT):
having version info in the docs is just adding technical debt

scottz (Tue, 27 Jun 2017 13:59:52 GMT):
I am looking under "Releases" heading on wiki https://wiki.hyperledger.org/projects/fabric . There are links to v1.0.0-alpha* content and release testing (which is a descriptive doc). I am suggesting to declutter, because I agree we do not want to add several beta links and several RC links here. I imagined a link to a subpage for release v1.0.0, which could contain/describe any materials.

scottz (Tue, 27 Jun 2017 14:00:51 GMT):
I figured we would have to store artifacts showing we met the release criteria. If not, then we could get rid of these alpha links.

scottz (Tue, 27 Jun 2017 14:01:37 GMT):
And the FAQ that Clayton mentioned could contain a link to test info or a troubleshooting/debugging page or whatever.

scottz (Tue, 27 Jun 2017 14:01:37 GMT):
And in that case, the FAQ that Clayton mentioned could contain a link to test info or a troubleshooting/debugging page or whatever.

elli-androulaki (Tue, 27 Jun 2017 14:01:53 GMT):
@cbf, thanks! addressed

cbf (Tue, 27 Jun 2017 14:02:00 GMT):
thanks!

weeds (Tue, 27 Jun 2017 15:31:46 GMT):
Today- i got 2 questions from 2 different people trying to use the latest release candidate- they indicated that it was hard to find https://hub.docker.com/r/hyperledger/ link in the documentation to figure out how to quickly pull the images. Maybe we need to make it more prominent?

weeds (Tue, 27 Jun 2017 15:32:17 GMT):
I don't personally have suggestions where to put it myself

weeds (Tue, 27 Jun 2017 15:33:12 GMT):
These particular people were not looking for walking through write your first app,etc,.. as they already had experience with the fabric at v1.0 prior releases (ie beta,etc,.)

cbf (Tue, 27 Jun 2017 15:35:31 GMT):
here http://hyperledger-fabric.readthedocs.io/en/latest/samples.html#download-platform-specific-binaries

cbf (Tue, 27 Jun 2017 15:35:42 GMT):
it could be clearer that this is how you get the binaries and images

weeds (Tue, 27 Jun 2017 15:36:12 GMT):
right- i found it- but i don't know how to make it "easier to find"

weeds (Tue, 27 Jun 2017 15:37:42 GMT):
maybe we just have to change the "main" title?

cbf (Tue, 27 Jun 2017 15:52:19 GMT):
https://gerrit.hyperledger.org/r/11197

nickgaski (Tue, 27 Jun 2017 16:07:21 GMT):
thanks sharon. looks like it is addressed very simply with Chris' CR

clessor (Tue, 27 Jun 2017 17:16:38 GMT):
Has joined the channel.

tkuhrt (Wed, 28 Jun 2017 18:06:58 GMT):
As part of the 1.0 release, one of the things that has been requested is an FAQ. I believe that we can use the following document for this purpose: https://wiki.hyperledger.org/projects/fabric/welcome. One thing that I see missing from this document is something that highlights the differences between v0.6 and v1.0. Is this documented somewhere that we can pull into the FAQ (even if just as a link)?

JonathanLevi (Thu, 29 Jun 2017 12:35:24 GMT):
Good morning. @tkuhrt This is a very good idea/point. Back in the day, we tried to post answers to FAQuestions on Stackover flow... but, yes, we can certainly add that.

JonathanLevi (Thu, 29 Jun 2017 12:36:11 GMT):
I will quickly open a JIRA ticket to track (and can quickly add some basic info, off the top of my head, regarding the diff between 0.6 and 1.0)

JonathanLevi (Thu, 29 Jun 2017 12:37:06 GMT):
The request for the diff between 0.6 and 1.0 has been, and being popping up very often. So often that I assumed that it was handled a long time ago.

JonathanLevi (Thu, 29 Jun 2017 12:37:06 GMT):
The request for the diff between 0.6 and 1.0 has been popping up very often. So often that I assumed that it was handled a long, long time ago!

JonathanLevi (Thu, 29 Jun 2017 12:37:48 GMT):
I will quickly open a JIRA ticket to track (and can quickly add some basic info, off the top of my head, regarding the diff between 0.6 and 1.0)... that others can extend/amend/improve/enhance/update/...

JonathanLevi (Thu, 29 Jun 2017 12:37:48 GMT):
I have quickly opened a JIRA ticket to track (and can quickly add some basic info, off the top of my head, regarding the diff between 0.6 and 1.0)... that others can extend/amend/improve/enhance/update/... https://jira.hyperledger.org/browse/FAB-5102

JonathanLevi (Thu, 29 Jun 2017 12:38:44 GMT):
--- BTW: https://chat.hyperledger.org/channel/fabric?msg=HxPLMNWaNvAjGhzKZ

JonathanLevi (Thu, 29 Jun 2017 12:38:54 GMT):
FYI ^^^

tkuhrt (Thu, 29 Jun 2017 15:10:00 GMT):
Thanks, @JonathanLevi, for the Jira issue

Michal Malka (Wed, 05 Jul 2017 07:24:37 GMT):
Has joined the channel.

JonathanLevi (Wed, 05 Jul 2017 09:10:51 GMT):
Hello

JonathanLevi (Wed, 05 Jul 2017 09:10:57 GMT):
Is the e2e test broken?

JonathanLevi (Wed, 05 Jul 2017 09:11:25 GMT):
Is the e2e test broken/failing?

yacovm (Wed, 05 Jul 2017 09:24:48 GMT):
I don't think so

mastersingh24 (Wed, 05 Jul 2017 09:59:27 GMT):
@JonathanLevi - what issue are you seeing?

yacovm (Wed, 05 Jul 2017 10:03:04 GMT):
I believe he means https://chat.hyperledger.org/channel/fabric-maintainers?msg=3JeRysLQSbMdAqgGd

JonathanLevi (Wed, 05 Jul 2017 11:11:31 GMT):
Yes, the integration tests failures on the CI. @mastersingh24

JonathanLevi (Wed, 05 Jul 2017 11:11:52 GMT):
---- @ "here": any (more) feedback about this? https://jira.hyperledger.org/browse/FAB-5177

JonathanLevi (Wed, 05 Jul 2017 11:11:52 GMT):
---- @ "here": any (more) feedback on/regarding this? https://jira.hyperledger.org/browse/FAB-5177

JonathanLevi (Wed, 05 Jul 2017 11:12:08 GMT):
Too big/too important to skip/too unimportant to risk, etc...

rameshthoomu (Wed, 05 Jul 2017 13:11:54 GMT):
@JonathanLevi I have re-triggered e2e job on latest commit and it worked as expected.. https://jenkins.hyperledger.org/view/fabric/job/fabric-merge-end-2-end-x86_64/

rameshthoomu (Wed, 05 Jul 2017 13:13:25 GMT):
I see couple of failures with java e2e tests.. it seems orderer timeout issues causing these failures.. Will check with @rickr and create a JIRA item for the intermittent failures

JonathanLevi (Wed, 05 Jul 2017 13:18:51 GMT):
1. Thanks. 2. Please take a look at the commit logs: Success Build #932 (Jul 5, 2017 11:44:00 AM) Failed Build #931 (Jul 5, 2017 10:30:00 AM) Failed Build #930 (Jul 4, 2017 7:29:33 PM)

JonathanLevi (Wed, 05 Jul 2017 13:19:11 GMT):
We had a failure at #930

JonathanLevi (Wed, 05 Jul 2017 13:19:32 GMT):
I have re-triggered #931 and not it passes at #932

JonathanLevi (Wed, 05 Jul 2017 13:19:42 GMT):
I have re-triggered #931 and now it passes at #932

JonathanLevi (Wed, 05 Jul 2017 13:19:53 GMT):
@rameshthoomu

JonathanLevi (Wed, 05 Jul 2017 13:20:31 GMT):
Why are these tests so brittle...? ( <--- forwarding a question that I have just been asked)

rameshthoomu (Wed, 05 Jul 2017 13:22:34 GMT):
Below are the reason for the failures (#930, #931) #931 00:19:03.932 End2endIT.setup:209 Send transactions failed. Reason: timeout #930 00:23:55.218 End2endIT.setup:209 Send transactions failed. Reason: timeout

rameshthoomu (Wed, 05 Jul 2017 13:23:28 GMT):
Will work with @rickr to increase the time to avoid these timeout issues..

JonathanLevi (Wed, 05 Jul 2017 13:33:16 GMT):
Yes, please. Thank you @rameshthoomu and @rickr !

seanbarclay (Fri, 07 Jul 2017 01:32:19 GMT):
Has joined the channel.

tkuhrt (Fri, 07 Jul 2017 17:24:40 GMT):
@jyellick asked me to put this here : https://chat.hyperledger.org/channel/fabric-maintainers?msg=cHdQcDWxbCuBnXZw7

shimos (Fri, 07 Jul 2017 17:41:40 GMT):
Has joined the channel.

JonathanLevi (Fri, 07 Jul 2017 19:52:27 GMT):
https://chat.hyperledger.org/channel/fabric-maintainers?msg=tEMjdpciYC94X9u4S

JonathanLevi (Fri, 07 Jul 2017 19:52:46 GMT):
*MERGE FREEZE* / *CODE FREEZE - BEGIN*

JonathanLevi (Fri, 07 Jul 2017 19:53:59 GMT):
To clarify, nothing's going to happen this weekend. The maintainers will reconvene on Monday to evaluate the state of everything and assess whether our next cut will be "rc2" or the final "1.0.0"

tkuhrt (Fri, 07 Jul 2017 19:54:40 GMT):
Thanks, @JonathanLevi

dave.enyeart (Mon, 10 Jul 2017 17:44:24 GMT):
https://jira.hyperledger.org/browse/FAB-5107 is a high bug against samples. It wasn't previously tagged as 1.0.0. I've fixed the tagging, so it may show up in bug reports now. Does anybody know if this is being actively worked?

dave.enyeart (Mon, 10 Jul 2017 18:24:45 GMT):
Since it is a sample docker compose issue and not a fabric runtime bug, I have reduced to Medium.

yoheiueda (Tue, 11 Jul 2017 09:18:29 GMT):
Has joined the channel.

mrkiouak (Tue, 11 Jul 2017 16:14:28 GMT):
does https://www.nytimes.com/reuters/2017/07/11/technology/11reuters-blockchain-hyperledger.html indicate a release was cut?

lehors (Tue, 11 Jul 2017 16:24:09 GMT):
Yes, it's actually being pushed out now

lehors (Tue, 11 Jul 2017 16:24:48 GMT):
The news is slightly ahead but we're getting there

binhn (Tue, 11 Jul 2017 17:24:03 GMT):
when do we fix up the docs to remore rc1? ``` Look at the names for each image; these are the components that will ultimately comprise our Hyperledger Fabric network. You will also notice that you have two instances of the same image ID - one tagged as “x86_64-1.0.0-rc1” and one tagged as “latest”. ```

troyronda (Tue, 11 Jul 2017 17:27:04 GMT):
Is there a download location for pre-built binaries such as configtx-gen?

troyronda (Tue, 11 Jul 2017 17:27:04 GMT):
Is there a download location for pre-built binaries such as configtxgen?

nickgaski (Tue, 11 Jul 2017 17:28:11 GMT):
I'll push CRs today to remove rc1

troyronda (Tue, 11 Jul 2017 17:35:21 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-release?msg=d2DfrojSWHo3b6Nb4) @troyronda Answering my own question: https://nexus.hyperledger.org/content/repositories/releases/org/hyperledger/fabric/hyperledger-fabric/

dave.enyeart (Tue, 11 Jul 2017 19:16:14 GMT):
@troyronda That's correct. The Getting Started instructions has a link that downloads the binaries and docker images: https://hyperledger-fabric.readthedocs.io/en/latest/getting_started.html

lehors (Tue, 11 Jul 2017 22:12:15 GMT):
Following up on https://chat.hyperledger.org/channel/fabric-maintainers?msg=9jMTkWeh6PxD39FNF ...

lehors (Tue, 11 Jul 2017 22:12:49 GMT):
this is tricky because it apparently depends on the git program used

lehors (Tue, 11 Jul 2017 22:13:34 GMT):
unfortunately on Windows 7, the git that comes with Docker Toolbox does exhibit the problem and this is what we tell people to use...

lehors (Tue, 11 Jul 2017 22:13:56 GMT):
git clone https://github.com/hyperledger/fabric-samples.git fails

lehors (Tue, 11 Jul 2017 22:14:14 GMT):
but if I use cygwin's git it succeeds

JonathanLevi (Tue, 11 Jul 2017 22:23:42 GMT):
@lehors (Un?)fortunately, I don't use Windows

JonathanLevi (Tue, 11 Jul 2017 22:23:56 GMT):
But when I used to... we had something like: *git config core.longpaths true*

JonathanLevi (Tue, 11 Jul 2017 22:24:00 GMT):
Can you please try?

JonathanLevi (Tue, 11 Jul 2017 22:24:12 GMT):
It may be an obsolete thing...

JonathanLevi (Tue, 11 Jul 2017 22:24:24 GMT):
Risking me showing my age here ;-)

lehors (Tue, 11 Jul 2017 22:31:40 GMT):
nice!

lehors (Tue, 11 Jul 2017 22:31:44 GMT):
it seems to work

lehors (Tue, 11 Jul 2017 22:31:54 GMT):
so, then the easy fix is to add that to the doc

lehors (Tue, 11 Jul 2017 22:32:09 GMT):
I'll create the JIRA and submit a CR

lehors (Tue, 11 Jul 2017 22:33:54 GMT):
you have to wonder why this isn't the default!

JonathanLevi (Tue, 11 Jul 2017 22:37:23 GMT):
Yes, please. Thank you.

naohide (Wed, 12 Jul 2017 01:36:05 GMT):
Has joined the channel.

weeds (Wed, 12 Jul 2017 02:03:51 GMT):
Jonathan- i don't have all the specifics, but throughout the day on Tuesday there was not just the 3 hour testing that you are aware of but various testing that the team did

weeds (Wed, 12 Jul 2017 02:04:19 GMT):
I will have to ask the various people that reached out to me to post more specifics but this is some of the information i received:

weeds (Wed, 12 Jul 2017 02:06:01 GMT):
@elli-androulaki indicated to me that her, Angelo, Ale tested the network overall, but also tested security components across the fabric.

weeds (Wed, 12 Jul 2017 02:07:26 GMT):
@dave.enyeart tested basic network, basic ledger updates and queries on leveldb and couchdb as well as some deeper ledger testing.

weeds (Wed, 12 Jul 2017 02:08:10 GMT):
@yacovm tested the basics of fabric and also did very deep and thorough testing of gossip.

weeds (Wed, 12 Jul 2017 02:09:48 GMT):
@jimthematrix tested fabric builds and node.js and java SDK sniff tested and did deeper testing.. he tested manually some of the sample apps

weeds (Wed, 12 Jul 2017 02:10:56 GMT):
@muralisr did some testing on chaincode, some of the vendoring pieces, and then went a bit deeper on chaincode elements.

weeds (Wed, 12 Jul 2017 02:11:59 GMT):
@jyellick did do quite a bit of consensus specific testing - ran through the paces and hit a bit deeper

weeds (Wed, 12 Jul 2017 02:12:34 GMT):
@lehors helped us with the windows environment specifically (he always is the master of finding things in windows others do not- seems to look good)

weeds (Wed, 12 Jul 2017 02:13:14 GMT):
@smithbk did quite a bit of testing on the CA

weeds (Wed, 12 Jul 2017 02:13:45 GMT):
AGain, as you know we have a lot of automated tests that were run that cover these areas... but several people had wanted to do some manual testing "just because"

weeds (Wed, 12 Jul 2017 02:14:14 GMT):
I would ask all those that are tagged here post a bit more specifically what they tested if it would help you, but I do want to thank you for leading today.

weeds (Wed, 12 Jul 2017 02:15:16 GMT):
You also are aware that we did a lot of security testing with outside firms that was shared with our security maven for Hyperledger and the maintainers and security auditing.

weeds (Wed, 12 Jul 2017 02:15:41 GMT):
@binhn personally did testing as well-

weeds (Wed, 12 Jul 2017 02:16:38 GMT):
I'm sure there are others that I'm not highlighting here-- I know that there were a whole team of people that @scottz had running both automated and manual testing throughout the day to check the release across all areas.

weeds (Wed, 12 Jul 2017 02:17:08 GMT):
In any case, I would ask that those on this list that I have mentioned - posting a little more detail for Jonathan might be helpful.

weeds (Wed, 12 Jul 2017 02:17:12 GMT):
Thank you Jonathan

weeds (Wed, 12 Jul 2017 02:18:57 GMT):
@JonathanLevi ^^

weeds (Wed, 12 Jul 2017 02:23:05 GMT):
I did leave out one bit- I know several people walked through the documentation with the release as well and followed the steps to make sure they worked with the new release- and they did

weeds (Wed, 12 Jul 2017 02:23:25 GMT):
@nickgaski can probably add his work as well in this space

dave.enyeart (Wed, 12 Jul 2017 02:25:12 GMT):
I re-tested the readthedocs samples including Build Your First Network and Writing Your First App on mac. Doc content looks good (after a couple minor fixes that were pushed). BYFN automated and manual steps worked flawlessly on both leveldb and couchdb. WYFA had one issue in the SDK sample which is fixed by https://gerrit.hyperledger.org/r/#/c/11205. Tested the various ledger functions/queries including rich query, history queries, and the query system chaincode functions.

dave.enyeart (Wed, 12 Jul 2017 02:25:12 GMT):
I re-tested the readthedocs samples including Build Your First Network and Writing Your First App on mac. Doc content looks good (after a couple minor fixes that were pushed). BYFN all-in-one and manual steps worked flawlessly on both leveldb and couchdb. WYFA had one issue in the SDK sample which is fixed by https://gerrit.hyperledger.org/r/#/c/11205. Tested the various ledger functions/queries including rich query, history queries, and the query system chaincode functions.

jyellick (Wed, 12 Jul 2017 03:12:46 GMT):
I retested the dev mode instructions, especially for non-admin channel creation. I also ran some stress tests with some performance tooling I have been working on, hitting the orderer with 200 concurrent connections driving traffic as fast as possible and everything seems stable and correct.

paapighoda (Wed, 12 Jul 2017 09:47:20 GMT):
Has joined the channel.

yacovm (Wed, 12 Jul 2017 10:57:16 GMT):
I tested fabric deployment on VMs with https://github.com/yacovm/fabricDeployment that tests gossip block dissemination (single leader per org) and also used https://github.com/sandp125/FabricNodeAPI_V1 which also adds a new organization to a channel, and I analyzed the gossip logs in it to ensure that peers of the new added org eventually communicate properly with gossip.

yacovm (Wed, 12 Jul 2017 11:10:44 GMT):
Also I have done performance benchmarking of gossip in small networks (8 peers) and it seems that the gossip network can withstand bursts of hundreds of blocks per second (blocks are 100KB of size, and the hosts each have 4 CPUs)

scottz (Wed, 12 Jul 2017 13:03:30 GMT):
Ramesh ran all our daily test suite automated tests, touching many areas, which are now part of a releaseTestSuite (and will publish a jenkins job report after rerun today). This suite now includes many additional tests including "make" commands, e2e tests, BYFN, and other tests using sdks too - over and beyond the UT and behave tests that are run with every submission. Plus we put some manual focus on the areas touched by fixes merged since RC1 (orderer, gossip, vendoring) and ran some chaincode integration tests and some system integration tests using PTE. Furthermore we manually verified the v1.0.0 images, binaries & node-moduels using the following samples 1. BYFN (fabric-samples / first network) 2. Balance-transfer 3. fabcar

scottz (Wed, 12 Jul 2017 13:12:00 GMT):
And we also looked through all the files for mentions of "rc1", fixed some, and confirmed the rest were all fixed by Nick and others by late afternoon.

jiangyaoguo (Thu, 13 Jul 2017 02:02:26 GMT):
Has joined the channel.

paapighoda (Thu, 13 Jul 2017 05:48:12 GMT):
Has left the channel.

pschnap (Thu, 13 Jul 2017 13:12:54 GMT):
Has joined the channel.

JonathanLevi (Fri, 14 Jul 2017 22:35:17 GMT):
Hello everyone, and thanks again for all the help here.

JonathanLevi (Fri, 14 Jul 2017 22:36:18 GMT):
Really appreciate all your/the assistance... wrote back to most of your directly, but I'm sure I have missed a few.

JonathanLevi (Fri, 14 Jul 2017 22:36:18 GMT):
Really appreciate all your/the assistance... wrote back to most of you directly, but I'm sure I have missed a few.

JonathanLevi (Fri, 14 Jul 2017 22:36:48 GMT):
https://lists.hyperledger.org/pipermail/hyperledger-fabric/2017-July/001308.html

JonathanLevi (Fri, 14 Jul 2017 22:36:48 GMT):
https://lists.hyperledger.org/pipermail/hyperledger-fabric/2017-July/001309.html

qingdu (Tue, 18 Jul 2017 08:25:21 GMT):
Has joined the channel.

colinGrahms (Wed, 19 Jul 2017 09:07:22 GMT):
Has joined the channel.

uber.twin (Tue, 25 Jul 2017 12:02:02 GMT):
Has joined the channel.

uber.twin (Tue, 25 Jul 2017 12:14:44 GMT):
@scottz hi, are there any estimates for when to expect the features specified at https://github.com/hyperledger/fabric/blob/master/proposals/r1/Next-Ledger-Architecture-Proposal.md?

scottz (Tue, 25 Jul 2017 13:36:44 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-release?msg=fk5JH2KrkXKkXcL4h) @uber.twin Much of that content is provided with version v1.0, released earlier this month. If you have a question about specific capability, please post it and an architect or release manager should be able to answer with more information. Right now they are planning for v1.1.

uber.twin (Tue, 25 Jul 2017 13:46:18 GMT):
@scottz thanks, I'd like to know what options are there to restrict access for certain assets to their respective owners and I thought a feature or two listed in there may help, such as "The complete ledger may not reside on all committers". As an alternative, might there be an option to encrypt the ledger and the world state?

uber.twin (Tue, 25 Jul 2017 13:51:49 GMT):
@scottz the reason would be related to the requirement that when two parties are transacting an asset, they might like to keep that transaction secret

scottz (Tue, 25 Jul 2017 14:05:46 GMT):
You are askinga about client private data. There is some work being done in this area now; take a look at FAB-1151, and ask @dave.enyeart . As for whether the entire ledger could be encrypted, I am not sure about that.

uber.twin (Tue, 25 Jul 2017 14:09:59 GMT):
alright, thank you

dave.enyeart (Tue, 25 Jul 2017 14:43:33 GMT):
@uber.twin The first answer for private data between participants is to use separate 'channels'. A channel provides private communication and ledger between a subset of network participants.

dave.enyeart (Tue, 25 Jul 2017 14:43:35 GMT):
http://hyperledger-fabric-docs.readthedocs.io/en/latest/channels.html

dave.enyeart (Tue, 25 Jul 2017 14:47:33 GMT):
Channels work well for many scenarios. But in some scenarios you need everybody in the network to have visibility to some public global data, while some of the transaction data should stay private. In these scenarios a hash of the data can go on the chain and the private data is saved 'on the side' by authorized peers. That's where FAB-1151 comes in, it will be targeted to a future release.

dave.enyeart (Tue, 25 Jul 2017 14:47:33 GMT):
Channels work well for many scenarios. But in some scenarios you need everybody in the network to have visibility to some public global data, while some of the transaction data should stay private, with dependencies between the two. In these scenarios a hash of the data can go on the chain and the private data can be saved 'on the side' by authorized peers. That's where FAB-1151 comes in, it will be targeted for a future release.

uber.twin (Tue, 25 Jul 2017 14:58:58 GMT):
@dave.enyeart but even with a separate channel, the couchdb databases seem to be unprotected

uber.twin (Tue, 25 Jul 2017 15:02:14 GMT):
anybody with access in the docker network gets full open access to any couchdb isn't it?

dave.enyeart (Tue, 25 Jul 2017 15:06:35 GMT):
@uber.twin If somebody hacks into the peer or peer docker network, all bets are off. only the peer public APIs should be exposed. You must protect everything behind the peer public APIs.

dave.enyeart (Tue, 25 Jul 2017 15:07:28 GMT):
even with LevelDB somebody that hacked into peer could mount a program to read the data

uber.twin (Tue, 25 Jul 2017 15:09:33 GMT):
but isn't each peer suppose to be administrated by its owner?

uber.twin (Tue, 25 Jul 2017 15:10:24 GMT):
and whoever can access a peer's cuchdb, can access the other peers couch db as well, isn't it

uber.twin (Tue, 25 Jul 2017 15:10:24 GMT):
and whoever can access a peer's couchdb, can access the other peers couchdb as well, isn't it

uber.twin (Tue, 25 Jul 2017 15:14:34 GMT):
or the business entities should not have administrative privileges over their own peers?

uber.twin (Tue, 25 Jul 2017 15:18:39 GMT):
FAB-1151 sounds good

scottz (Tue, 25 Jul 2017 15:41:28 GMT):
@uber.twin you are talking about deployment strategies, and network security between business entities within an organization. Fabric developers do not dictate how to use it. The Fabric is flexible and can be used in many ways by the network architect who must decide how to configure and permission their network gateways, peers, and servers that run the client applicaiton code. Explore the use of channels and consortiums first, to do what you want, and then FAB-1151.

dave.enyeart (Tue, 25 Jul 2017 16:55:21 GMT):
the peer owner/administrator is authorized to see all data on their peer. they cannot access other peers or other peer's couchdb.

noyonthe1 (Wed, 26 Jul 2017 18:23:35 GMT):
Has joined the channel.

Asara (Wed, 26 Jul 2017 18:58:55 GMT):
Has joined the channel.

Asara (Wed, 26 Jul 2017 18:59:09 GMT):
Hey all, is there a fabric ca-server binary?

Asara (Wed, 26 Jul 2017 19:01:42 GMT):
And if not, is that on the roadmap by any chance?

jyellick (Wed, 26 Jul 2017 19:12:40 GMT):
@JonathanLevi @greg.haskins ^

jyellick (Wed, 26 Jul 2017 19:13:24 GMT):
We have the release binaries here for fabric https://nexus.hyperledger.org/content/repositories/releases/org/hyperledger/fabric/hyperledger-fabric/linux-amd64-1.0.0/ which seems quite useful, but the lack of parity for the other components is surprising

BhavishaDawda (Wed, 26 Jul 2017 19:28:13 GMT):
Has joined the channel.

rameshthoomu (Wed, 26 Jul 2017 19:31:38 GMT):
@jyellick we have fabric-chaintool binary is here https://nexus.hyperledger.org/content/repositories/releases/org/hyperledger/fabric/hyperledger-fabric/chaintool-1.0.0/

rameshthoomu (Wed, 26 Jul 2017 19:32:14 GMT):
we did this recently (1 week ago)

jyellick (Wed, 26 Jul 2017 19:32:52 GMT):
@rameshthoomu I think @Asara was more interested in the fabric-ca, is this in plan?

rameshthoomu (Wed, 26 Jul 2017 19:33:18 GMT):
@jyellick I am not sure on that..

Asara (Wed, 26 Jul 2017 19:33:29 GMT):
Yeap, specifically talking about fabric-ca here.

bobbiejc (Wed, 26 Jul 2017 20:56:05 GMT):
Has joined the channel.

xinpei8 (Wed, 26 Jul 2017 22:06:46 GMT):
Has joined the channel.

jimthematrix (Fri, 28 Jul 2017 14:37:42 GMT):
@mastersingh24 for cutting 1.0.1 the fabric-sdk-node and fabric-sdk-java repos can just be tagged at the master HEAD. would you like Rick and I to do the necessary steps for CI triggering and tagging? or are you handling them all?

mastersingh24 (Fri, 28 Jul 2017 16:37:20 GMT):
Hey Jim - I'm going through them all. We are only taking bug fixes

mastersingh24 (Fri, 28 Jul 2017 16:37:40 GMT):
Here's the work for Fabric 1.0.1 as an example - https://gerrit.hyperledger.org/r/#/c/12019/

muralisr (Fri, 28 Jul 2017 17:03:03 GMT):
@mastersingh24 can we submit CRs now ?

mastersingh24 (Fri, 28 Jul 2017 17:03:28 GMT):
You've always been able to submit CRs ;)

mastersingh24 (Fri, 28 Jul 2017 17:04:08 GMT):
Luckily this time the bug fixes did not conflict with any "new" stuff

mastersingh24 (Fri, 28 Jul 2017 17:04:47 GMT):
cherry-picking was straightforward and I was able to lay down the bug fixes in order with no issue ;)

rjones (Fri, 28 Jul 2017 17:05:13 GMT):
_agitates for `git merge -s --no-ff` in this channel as well :)_

mastersingh24 (Fri, 28 Jul 2017 17:07:21 GMT):
I went with `git rebase -i HEAD~28` based on some practices I saw from other projects. But I hear you on the sign of the actual merge commit, although it did an additional signed-off by to each commit listed in the commit msg

rjones (Fri, 28 Jul 2017 17:08:56 GMT):
I _feel_ losing `git bisect` and no longer having 1:1 commits is a heavy price to pay for future debugging.

rjones (Fri, 28 Jul 2017 17:09:27 GMT):
regardless - I'm glad to see this process is moving along

mastersingh24 (Fri, 28 Jul 2017 17:15:28 GMT):
Sure - I'm with you. But I felt that we still have the full history on the master branch - but I hear you

rickr (Fri, 28 Jul 2017 17:35:10 GMT):
JSDK is already done. Just waiting for fabric to publish v1.0.1 docker images to see if passes then. https://gerrit.hyperledger.org/r/#/c/12013/

jyellick (Fri, 28 Jul 2017 20:33:16 GMT):
Can we get the v1.0.2 version put into JIRA? Would be nice to able to start tagging items which did not make v1.0.1 but are candidates for the next point release

rjones (Fri, 28 Jul 2017 20:38:01 GMT):
@jyellick added https://jira.hyperledger.org/projects/FAB/versions/10606

jyellick (Fri, 28 Jul 2017 20:38:21 GMT):
Thanks @rjones!

rjones (Fri, 28 Jul 2017 20:39:34 GMT):
I think, possibly, we should have a `future point release` version and create new versions with numbers when the decision is made to roll forward with a new release, but let's cross that bridge in the future

mastersingh24 (Fri, 28 Jul 2017 20:40:58 GMT):
I like using `1.0.X` ;)

mastersingh24 (Fri, 28 Jul 2017 20:41:10 GMT):
or `1.0.P`

lehors (Sat, 29 Jul 2017 14:54:08 GMT):
hi there, what's the status for the release?

weeds (Mon, 31 Jul 2017 14:33:09 GMT):
my understanding from early this morning (might have changed) is that most of the work is done- and they are working through CI possibly

JanRzepecki (Mon, 31 Jul 2017 14:48:23 GMT):
Has joined the channel.

jimthematrix (Mon, 31 Jul 2017 16:53:41 GMT):
@mastersingh24 I'm not seeing a CR for fabric-sdk-node triggering a release CI, as described here https://jira.hyperledger.org/browse/FAB-2802, I assume you are planning to do that after the fabric has been built first?

Eric.Bui (Thu, 03 Aug 2017 16:59:50 GMT):
Has joined the channel.

mastersingh24 (Thu, 03 Aug 2017 18:04:18 GMT):
right

eacoeytaux (Fri, 04 Aug 2017 19:55:17 GMT):
Has joined the channel.

mastersingh24 (Sun, 06 Aug 2017 11:45:46 GMT):
@ddhulla http://hyperledger-fabric.readthedocs.io/en/latest/dev-setup/devenv.html#note-to-windows-users (https://chat.hyperledger.org/channel/general?msg=ML8dsmicrTCFS3Fa4)

ddhulla (Sun, 06 Aug 2017 11:45:46 GMT):
Has joined the channel.

rickr (Tue, 08 Aug 2017 11:58:43 GMT):
Any ETA on Fabric v1.0.1 published to Docker Hub ?

cbf (Tue, 08 Aug 2017 12:53:39 GMT):
it still needs some +2 love

cbf (Tue, 08 Aug 2017 12:53:58 GMT):
https://gerrit.hyperledger.org/r/c/12047/ in particular and then fabric and fabric-ca ready

jimthematrix (Wed, 09 Aug 2017 19:45:22 GMT):
squash commit of fabric-sdk-node 1.0.1 content: https://gerrit.hyperledger.org/r/#/c/12299/ @cbf @mastersingh24

jimthematrix (Wed, 09 Aug 2017 20:08:26 GMT):
releasing v1.0.1 fabric-sdk-node: https://gerrit.hyperledger.org/r/#/c/12301/

mastersingh24 (Thu, 10 Aug 2017 11:55:34 GMT):
Thanks @jimthematrix - will take a look if not done already

mastersingh24 (Thu, 10 Aug 2017 11:55:43 GMT):
1.0.1 images have been published

Jonny (Tue, 15 Aug 2017 14:11:08 GMT):
Has joined the channel.

genggjh (Wed, 16 Aug 2017 00:14:25 GMT):
Has joined the channel.

tskzh (Thu, 17 Aug 2017 16:13:14 GMT):
Has joined the channel.

Asara (Thu, 17 Aug 2017 16:55:19 GMT):
Hey all, is there a plan to include a release of the CA as a binary? And if it is already available, could someone point me in the right direction?

JonathanLevi (Wed, 23 Aug 2017 22:18:29 GMT):
Do we have an estimated deadline for the Hyperledger Fabric 1.2 release?

JonathanLevi (Wed, 23 Aug 2017 22:19:50 GMT):
We are prioritizing items for v1.1 (and moving stuff that "won't fit" to 1.2)....while the v1.2 planning is ongoing, we can/should discuss initial plans. Thoughts, suggestions?

JonathanLevi (Wed, 23 Aug 2017 22:20:13 GMT):
We are prioritizing items for v1.1 (and moving stuff that "won't make it" to 1.2)....while the v1.2 planning is ongoing, we can/should discuss initial plans. Thoughts, suggestions?

JonathanLevi (Wed, 23 Aug 2017 22:20:32 GMT):
We are prioritizing items for v1.1 (and moving stuff that "won't make it to v1.1" to 1.2)....while the v1.2 planning is ongoing, we can/should discuss initial plans. Thoughts, suggestions?

JonathanLevi (Wed, 23 Aug 2017 22:21:30 GMT):
There is always the tradeoff between two short a cycle vs. a few months gap between releases. Everybody is welcome to "chime in"...

dayubian (Thu, 24 Aug 2017 00:38:37 GMT):
Has joined the channel.

mastersingh24 (Thu, 24 Aug 2017 12:29:30 GMT):
It would be good if we can attempt to do quarterly releases - at least "minor" releases

harsha (Thu, 24 Aug 2017 12:58:36 GMT):
Is there a ETA on adoption of go1.8.3 ?

harsha (Thu, 24 Aug 2017 12:58:36 GMT):
w.r.t FAB-2945 .Is there a ETA on adoption of go1.8.3 ?

mastersingh24 (Thu, 24 Aug 2017 14:07:28 GMT):
I think we actually want to skip to 1.9

mastersingh24 (Thu, 24 Aug 2017 14:07:59 GMT):
https://jira.hyperledger.org/browse/FAB-5461

troyronda (Thu, 24 Aug 2017 14:34:43 GMT):
good idea :)

troyronda (Thu, 24 Aug 2017 14:35:06 GMT):
might want to think about dep for vendoring

troyronda (Thu, 24 Aug 2017 14:35:06 GMT):
might want to think about supporting dep for vendoring

troyronda (Thu, 24 Aug 2017 14:36:13 GMT):
(https://github.com/golang/dep)

aleksandar.likic (Thu, 24 Aug 2017 20:19:20 GMT):
Has joined the channel.

troyronda (Fri, 25 Aug 2017 03:25:21 GMT):
https://blog.golang.org/go1.9 :)

troyronda (Sat, 26 Aug 2017 15:48:32 GMT):
Posted some thoughts on why FAB-5460/FAB-5682 (https://gerrit.hyperledger.org/r/#/c/12435/) is useful in a business blockchain network: https://jira.hyperledger.org/browse/FAB-5460?focusedCommentId=30235&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-30235

troyronda (Sat, 26 Aug 2017 15:48:32 GMT):
Posted some thoughts to Jira on why FAB-5460/FAB-5682 (https://gerrit.hyperledger.org/r/#/c/12435/) is useful in a business blockchain network at https://jira.hyperledger.org/browse/FAB-5460?focusedCommentId=30235&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-30235

troyronda (Sat, 26 Aug 2017 16:03:16 GMT):
(btw - with the maintainers chatroom set to read-only, it isn't entirely clear where to post this discussion).

troyronda (Sat, 26 Aug 2017 16:03:16 GMT):
btw - with the maintainers chatroom set to read-only, it isn't entirely clear where to launch this discussion...

mastersingh24 (Mon, 28 Aug 2017 10:25:30 GMT):
Folks - planning on cutting fabric and fabric-ca 1.0.2 releases this week

ArnabChatterjee (Wed, 30 Aug 2017 08:51:49 GMT):
Has joined the channel.

jyellick (Wed, 30 Aug 2017 20:51:02 GMT):
It looks like people are having problems because the v1.0.1 release did not regenerate the artifacts in the samples? Does this sound right to anyone more familiar? https://jira.hyperledger.org/browse/FAB-5309?focusedCommentId=30354&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-30354

mastersingh24 (Thu, 31 Aug 2017 08:32:56 GMT):
@jyellick - yeah - I'll address this morning as part of https://jira.hyperledger.org/browse/FAB-5995

mastersingh24 (Thu, 31 Aug 2017 14:38:51 GMT):
^^^ fixed basic-network, fabcar and updated first-network

mastersingh24 (Thu, 31 Aug 2017 14:38:57 GMT):
working on the rest

mastersingh24 (Fri, 01 Sep 2017 22:56:38 GMT):
Fabric and Fabric CA 1.0.2 have both been tagged and released. I'll check for the Docker builds later. 4 tasks left: - make sure everything works - need to merge my change to fabric-samples - https://gerrit.hyperledger.org/r/#/c/13069/ - need to merge fabric-samples master and release branches - update the link in the docs on master branch

mastersingh24 (Fri, 01 Sep 2017 23:24:39 GMT):
1.0.2 images are now on Dockerhub

sstone1 (Tue, 05 Sep 2017 08:49:01 GMT):
will the Node.js SDK for 1.0.2 be released soon? @jimthematrix

Colonel_HLE (Tue, 05 Sep 2017 11:55:40 GMT):
Has joined the channel.

jimthematrix (Tue, 05 Sep 2017 18:38:08 GMT):
@sstone1 based on our discussions earlier today, I'll work on a 1.0.2 release for 1) grpc upgrade, 2) nodeJS 8 support

dragon82 (Wed, 06 Sep 2017 08:58:08 GMT):
Has joined the channel.

SimonOberzan (Thu, 07 Sep 2017 09:30:46 GMT):
Has joined the channel.

troyronda (Fri, 08 Sep 2017 17:09:20 GMT):
I see https://gerrit.hyperledger.org/r/#/c/13219/ has been merged - what's the trigger for the push to Dockerhub?

rjones (Fri, 08 Sep 2017 17:20:57 GMT):
@greg.haskins @troyronda should I manually trigger https://jenkins.hyperledger.org/view/fabric-baseimage/job/fabric-baseimage-release-trigger/ for refs/changes/19/13219/1 ?

greg.haskins (Fri, 08 Sep 2017 17:42:58 GMT):
i need to push a tag

greg.haskins (Fri, 08 Sep 2017 17:43:06 GMT):
let me do that

greg.haskins (Fri, 08 Sep 2017 17:45:11 GMT):
done: https://github.com/hyperledger/fabric-baseimage/releases/tag/v0.4.0

greg.haskins (Fri, 08 Sep 2017 17:45:20 GMT):
that should trigger the CI job to eventually push

greg.haskins (Fri, 08 Sep 2017 17:45:32 GMT):
give it 30+ minutes, the baseimage job is typically slow

greg.haskins (Fri, 08 Sep 2017 17:46:09 GMT):
@rjones: whatever happened with my inability to push tags recently, it seems to have been resolved

rjones (Fri, 08 Sep 2017 17:46:28 GMT):
OK, glad to hear

weeds (Tue, 12 Sep 2017 14:40:20 GMT):
FYI- https://wiki.hyperledger.org/projects/fabric/proposedv1_1

weeds (Tue, 12 Sep 2017 14:41:01 GMT):
This is still work in process thanks to a lot of the maintainers and contributors- if you see something that has to get added please contact @Clayton Sims as I'm sure it still needs work

MRobinson (Wed, 13 Sep 2017 11:24:03 GMT):
Has joined the channel.

s.narayanan (Wed, 13 Sep 2017 18:36:43 GMT):
Are the IBM certified docker images in https://hub.docker.com/u/ibmblockchain/ release 1.0.1?

s.narayanan (Wed, 13 Sep 2017 18:36:43 GMT):
Are the IBM certified docker images in https://hub.docker.com/u/ibmblockchain/ release 1.0.1? It is not clear from documentation if it is 1.0 or 1.0.1

ericmvaughn (Thu, 14 Sep 2017 23:02:40 GMT):
Has joined the channel.

weeds (Fri, 15 Sep 2017 14:17:23 GMT):
i wanted to share some information here that I've asked @scottz to share on email for hyperledger as I don't know that everyone has this information, but I thought it was a great summary

weeds (Fri, 15 Sep 2017 14:19:35 GMT):
Several people in community that Scott has been leading have created new repo "fabric-test" at end of July, with testers as maintainers. This has allowed people who have more automation development test skills to move forward much more quickly. And tools are getting merged that have been utilized to test the various releases. And the tests are intended to continue to get integrated into the CI. Ledger Traffic Engine (LTE) merged 8/10, 1400 lines functional and performance testing of APIs for ledger component NetworkLauncher (NL)--> intent here is to ultimately move to Cello merged 8/29, 2500 lines used on command-line or invoked by other tools; internally uses cryptogen, configtxgen, creates and uses docker-compose files; launches configurable network on a single host Performance Traffic Engine (PTE) merged 9/08, 7000 lines system testing traffic engine configurable with a command-line interface and test configuration files Behave major framework merged 8/07 - 9/12, 4500 lines, plus 1100 lines of growing feature test files user-friendly language for network operators and users Still TO DO is below: merge tools infrastructure into fabric-test repo: Add Behave functions for more tests as needed Orderer Traffic Engine (OTE) target date to complete merging 09/29 -- unblocks 30 tests configurable test engine for orderer service component: multiple orderers, kafka brokers, channels; drives broadcast and deliver clients and verifies all traffic msg counts Cello - fabric network deployment tool target date to complete merges 09/29 -- unblocks 10 tests, plus more planned cannot yet obtain cloud machines from LF; backup plan (being tested) is to utilize vLaunch machines in cloud

weeds (Fri, 15 Sep 2017 14:20:17 GMT):
--------------

weeds (Fri, 15 Sep 2017 14:21:11 GMT):
Linux Foundation helping with servers and assistance to set up reserved pool for automation jobs - required to install and use new tool Cello (Fabric-Deploy) tool as a standard community tool - before converting all the tests to use Cello. @tongli is working with LF to acquire and configure servers and help people with Cello and getting the automation into the ci.

tongli (Fri, 15 Sep 2017 14:21:11 GMT):
Has joined the channel.

weeds (Fri, 15 Sep 2017 14:21:24 GMT):
---------

weeds (Fri, 15 Sep 2017 14:22:19 GMT):
There are tremendous amount of tests that are "system related" (this is beyond the basic already automated unit/function test) that we are trying to get automated into the CI ultimately. So if anyone is interested in helping with that effort of getting it moved over I suggest to reach out to @scottz

weeds (Fri, 15 Sep 2017 14:23:31 GMT):
the key thing is we do have quite a bit automated but not in CI, which is the real goal.

weeds (Fri, 15 Sep 2017 14:51:03 GMT):
@s.narayanan the IBM certified images are version 1.0.1, and they are working to release 1.02 out soon

s.narayanan (Fri, 15 Sep 2017 14:51:14 GMT):
Thansk @weeds

s.narayanan (Fri, 15 Sep 2017 14:51:14 GMT):
Thanks @weeds

manish-sethi (Fri, 15 Sep 2017 15:45:27 GMT):
Has joined the channel.

jyellick (Mon, 18 Sep 2017 19:18:55 GMT):
``` $ docker pull hyperledger/fabric-orderer Using default tag: latest Error response from daemon: manifest for hyperledger/fabric-orderer:latest not found ``` Anyone know what happened to the `latest` tagged docker images?

SubbaBachina (Mon, 18 Sep 2017 19:20:02 GMT):
Has joined the channel.

jrosmith (Mon, 18 Sep 2017 19:20:12 GMT):
Has joined the channel.

jyellick (Mon, 18 Sep 2017 19:20:47 GMT):
@JonathanLevi @greg.haskins @mastersingh24 ^

greg.haskins (Mon, 18 Sep 2017 19:21:54 GMT):
@jyellick we have (intentionally) never published them to dockerhub....they exist purely as a construct of developer convenience and are generated when you build locally

greg.haskins (Mon, 18 Sep 2017 19:23:02 GMT):
everything that is on dockerhub is designed to work with like-tagged images

jyellick (Mon, 18 Sep 2017 19:23:02 GMT):
Ah, thanks Greg, does our CI push anything to dockerhub on merge to master?

rameshthoomu (Mon, 18 Sep 2017 19:23:18 GMT):
@jyellick no

greg.haskins (Mon, 18 Sep 2017 19:23:39 GMT):
as far as official releases, def not...i wasnt clear on intermediate states but it seems Ramesh has answered that one too

rameshthoomu (Mon, 18 Sep 2017 19:23:51 GMT):
only after release tag is created

greg.haskins (Mon, 18 Sep 2017 19:24:22 GMT):
@jyellick if you dig in, you will see docker image tags fall into two categories

greg.haskins (Mon, 18 Sep 2017 19:24:46 GMT):
1) those which are strongly versioned and linked to each other, and 2) those which assume the developer context of :latest

greg.haskins (Mon, 18 Sep 2017 19:25:23 GMT):
most of the primary components fall into (1)...things like behave scripts often rely on (2) out of convenience with the premise that wouldnt be used outside of development/CI context

greg.haskins (Mon, 18 Sep 2017 19:25:59 GMT):
e.g. its a PITA to pass "x86_64-snapshot-e4a5b3" to the behave setup, so it uses :latest

jyellick (Mon, 18 Sep 2017 19:26:19 GMT):
Got it, thanks for the additional explanation @greg.haskins !

greg.haskins (Mon, 18 Sep 2017 19:26:52 GMT):
any time

vu3mmg (Tue, 19 Sep 2017 02:16:56 GMT):
Has joined the channel.

mastersingh24 (Tue, 19 Sep 2017 13:57:05 GMT):
You'll also notice that the Makefile will also tag images as latest and you'll notice that the download script for the binaries from the getting started also retags images as latest as well

mastersingh24 (Tue, 19 Sep 2017 13:58:07 GMT):
We also had to deal with the lack of multi-arch support in the past as well. We actually need to start leveraging that capability of Dockerhub now so we can get rid of the arch in the tags

Asara (Tue, 19 Sep 2017 20:38:35 GMT):
Quick question guys, is fabric-ca still only distributed as a docker image (or compiled by the user)? Are there any binaries provided for the CA yet?

Jacky_Sheng (Wed, 20 Sep 2017 03:22:05 GMT):
Has joined the channel.

cbf (Wed, 20 Sep 2017 15:20:52 GMT):
not yet, no

weeds (Wed, 20 Sep 2017 17:37:17 GMT):
btw, i sent clayton to the hyperledger hacfkest as i needed to be in nyc on friday

toriaezunama (Mon, 25 Sep 2017 12:20:19 GMT):
Has joined the channel.

yushan (Tue, 26 Sep 2017 09:17:17 GMT):
Has joined the channel.

jyellick (Fri, 29 Sep 2017 16:05:56 GMT):
Noticed by @jworthington, it looks like the `orderer` binary in the v1.0.2 release artifacts reports its version as `development version` rather than as `v1.0.2` like all the other binaries in the release.

jworthington (Fri, 29 Sep 2017 16:05:56 GMT):
Has joined the channel.

mastersingh24 (Fri, 29 Sep 2017 17:36:32 GMT):
Hmm - is their a JIRA for this @jyellick? Going to put together 1.0.3 this weekend so will try to remember to check this

jyellick (Fri, 29 Sep 2017 17:37:30 GMT):
@mastersingh24 No JIRA to my knowledge, wanted to double check here first

yacovm (Fri, 29 Sep 2017 18:10:16 GMT):
@mastersingh24 is the gRPC upgrade going to release?

mastersingh24 (Fri, 29 Sep 2017 18:15:35 GMT):
Not for 1.0.3

mastersingh24 (Fri, 29 Sep 2017 18:23:17 GMT):
[there's a bug ](https://chat.hyperledger.org/channel/fabric-release?msg=zihYb67HbDcbSKmHX) @jyellick

mastersingh24 (Fri, 29 Sep 2017 18:23:17 GMT):
[there is a bug ](https://chat.hyperledger.org/channel/fabric-release?msg=zihYb67HbDcbSKmHX) @jyellick

mastersingh24 (Fri, 29 Sep 2017 18:25:05 GMT):
I'll create a JIRA and fix :(

mastersingh24 (Fri, 29 Sep 2017 18:27:52 GMT):
https://jira.hyperledger.org/browse/FAB-6351 ^^^^

mastersingh24 (Fri, 29 Sep 2017 20:04:00 GMT):
^^^^^ https://gerrit.hyperledger.org/r/#/c/13983/

mastersingh24 (Fri, 29 Sep 2017 20:04:00 GMT):
^^^^^ https://gerrit.hyperledger.org/r/#/c/13983/ https://gerrit.hyperledger.org/r/#/c/13985/

mastersingh24 (Fri, 29 Sep 2017 20:04:00 GMT):
^^^^^ https://gerrit.hyperledger.org/r/#/c/13983/ https://gerrit.hyperledger.org/r/#/c/13989/

fredbi (Tue, 03 Oct 2017 08:34:00 GMT):
Has joined the channel.

mastersingh24 (Wed, 04 Oct 2017 13:55:46 GMT):
Hyperledger Fabric v1.0.3 and Hyperledger Fabric CA v1.0.3 are now available!

mastersingh24 (Wed, 04 Oct 2017 13:55:49 GMT):
Enjoy!

dave.enyeart (Wed, 04 Oct 2017 21:00:52 GMT):
Two proposals for your consideration: *1) Jira enhancements* - With current Jira setup, it is difficult to get a good view into release content. I would propose enhancing Jira Features as follows - split current Description into Overview/Motivation, Internal Design, and Usage sections. Then add fields for Status (one line free text summary), Design Reviewed (no, yes (or reviewer names)), SDK Impact (unset, no, yes), Doc Required (unset, no, yes), New System Test Required (unset, no, yes). For any yes, feature must have respective subtasks completed prior to marking Done. *2) 1.1 Alpha content* - Without good release visibility in Jira, for now I’ve summarized proposed 1.1 release content and 1.1 alpha highlight areas in a google sheet. An alpha highlight area is a 1.1 feature that is complete enough to warrant requesting early feedback on in the short term. These are focus areas for Doc and System Test leading up to an alpha release sometime in October. Please take a look and either comment inline or here with thoughts. As always, you can up vote a feature in Jira. https://docs.google.com/spreadsheets/d/1TswRWap0MO-CVSLWbGnBzUPQp4SaWUeflRgkxZFh1t0/edit#gid=0

yacovm (Wed, 04 Oct 2017 21:08:09 GMT):
Is there an example for (1) ?

yacovm (Wed, 04 Oct 2017 21:09:34 GMT):
do you mean to split the description _ always_ or can it be opt-in ? because if one doesn't fill all the fields won't that leave the JIRA with lots of blank fields when you browse it?

dave.enyeart (Wed, 04 Oct 2017 21:18:30 GMT):
I believe it is possible to pre-populate Jira fields with templated values... assuming that is the case I'd suggest keep current Description field and upon work item creation populate it with Overview/Motivation, Internal Design, and Usage sections. With recommendation for people to fill out as many of them as feasible. We'd like all this information collected for new features. Reviewers care about Internal Design, while users and documenters care about Usage.

dave.enyeart (Wed, 04 Oct 2017 21:20:10 GMT):
As today, a link to a google doc can be included if the content is lengthy.

JonathanLevi (Wed, 04 Oct 2017 23:39:22 GMT):
A great initiative @dave.enyeart

JonathanLevi (Wed, 04 Oct 2017 23:39:52 GMT):
In HACERA, we deal with these parts using JIRA's dependencies and components

JonathanLevi (Wed, 04 Oct 2017 23:40:06 GMT):

Message Attachments

JonathanLevi (Wed, 04 Oct 2017 23:40:45 GMT):
Having Epics and then we break it down to the sub-components (in this case, they'd be the NodeJS, Go, etc...)

JonathanLevi (Wed, 04 Oct 2017 23:41:16 GMT):
I think that the Design should be at the Epic level

JonathanLevi (Wed, 04 Oct 2017 23:41:59 GMT):
Internal designs that are closely related to the implementations (and may vary between implementations) can act like "special" derivations

JonathanLevi (Wed, 04 Oct 2017 23:42:46 GMT):
---

JonathanLevi (Wed, 04 Oct 2017 23:44:44 GMT):
While at it (and I fully agree that these need organization) - what will (also?) be key is our ability to use ETAs along with these dependencies. I feel that this could use some improvements, as it's difficult at times to figure out the ripple effect of a key feature not getting done on time / as planned, how how it directly or indirectly affects some deadlines and milestones.

JonathanLevi (Wed, 04 Oct 2017 23:45:19 GMT):
Back in the day, I do remember many many reports that stated that everything green, but many things didn't work.

JonathanLevi (Wed, 04 Oct 2017 23:45:52 GMT):
Back in the day, I do remember many many reports that stated that everything green, while many things didn't work - and it was not reflected.

JonathanLevi (Wed, 04 Oct 2017 23:47:19 GMT):
___ We should certainly have a much better JIRA state of the *1.1 Release* (alpha or otherwise)

pradeeppadmarajaiah (Thu, 05 Oct 2017 04:27:37 GMT):
Has joined the channel.

cotofei (Thu, 05 Oct 2017 06:31:53 GMT):
Has joined the channel.

mastersingh24 (Thu, 05 Oct 2017 08:55:58 GMT):
@dave.enyeart - I am not opposed to adding fields, but I don't think we need to (at least not to start with). What we need to do is actually add "release" discipline and provide prescriptive guidance on the usage of types, etc

dave.enyeart (Thu, 05 Oct 2017 09:36:41 GMT):
@mastersingh24 Exactly... the prescriptive guidance and discipline will make all the difference. The additional fields is just some structure to nudge the discipline in the right direction, plus they would enable interesting reports to more easily get a thumbnail view of a release (similar to the google sheet)

dave.enyeart (Thu, 05 Oct 2017 09:36:41 GMT):
@mastersingh24 Exactly... the prescriptive guidance and discipline will make all the difference. I am going to create a wiki page with the prescriptive guidance. The additional fields is just some structure to nudge the discipline in the right direction, plus they would enable interesting reports to more easily get a thumbnail view of a release (similar to the google sheet)

mastersingh24 (Thu, 05 Oct 2017 10:24:51 GMT):
I personally prefer the use of "New Feature" and "Improvement" versus "Story". For some odd reason, "story points" does not show up for either of these. We also need people to get into the habit of using "Tasks" under any of these. Tasks can be used to include docs, etc.

mastersingh24 (Thu, 05 Oct 2017 10:25:27 GMT):
I also like this view: https://jira.hyperledger.org/secure/ReleaseNote.jspa?projectId=10002&version=10702

mastersingh24 (Thu, 05 Oct 2017 10:26:50 GMT):
Sadly, we can't quite use these as our release notes because we have multiple projects under one JIRA project, but I like this view because it gives you a perspective on describing a release

mastersingh24 (Thu, 05 Oct 2017 10:27:08 GMT):
In the end, this all comes down to proper planning of release content

mastersingh24 (Thu, 05 Oct 2017 10:30:53 GMT):
BTW - as part of trying to clean things up, we now have both "v1.1" and "v1.1-experimental" available for "fix version"

mastersingh24 (Thu, 05 Oct 2017 10:32:37 GMT):
Also added v1.2 as well

dave.enyeart (Thu, 05 Oct 2017 13:34:06 GMT):
link to google sheet: https://docs.google.com/spreadsheets/d/1TswRWap0MO-CVSLWbGnBzUPQp4SaWUeflRgkxZFh1t0/edit?usp=sharing

cbf (Thu, 05 Oct 2017 15:08:30 GMT):
I have asked @dhuseby to request some JIRA ninja consulting, because we could sorely use some;-)

cbf (Thu, 05 Oct 2017 15:09:52 GMT):
the absence of story points on features and enhancements seems arbitrary... I would hope we could add them

cbf (Thu, 05 Oct 2017 15:11:07 GMT):
because (and I was recommending this with @simsc and @weeds way back) we need to be more rigorous about planning. It isn't enough to just put a JIRA up with a title and nothing else.

cbf (Thu, 05 Oct 2017 15:13:09 GMT):
then we need to be doing planning... again, I have suggested this multiple times that before we jump into coding, we need to a) agree as maintainers what our priorities are and b) we need to assess whether there is resource to actually do the work we prioritize and map that to a release cadence

cbf (Thu, 05 Oct 2017 15:16:08 GMT):
so, I support template that Dave proposed... the missing piece in all of this is that we need to be a lot more brutal in how we manage code being merged

cbf (Thu, 05 Oct 2017 15:17:21 GMT):
IMO, if we require voting of all New Feature and Improvement JIRAs or else related CRs are rejected, that might get people into the habit of playing ball

cbf (Thu, 05 Oct 2017 15:18:20 GMT):
eg only planned and approved JIRAs can get merged (bug fixes and small performance tweaks or new tests should obviously be exempt from this).

cbf (Thu, 05 Oct 2017 15:20:46 GMT):
as to release 1.1 visibility, I actually worked on a new gadget for the dashboard that captures what was posted in the wiki (and aligned the two)

cbf (Thu, 05 Oct 2017 15:20:53 GMT):
see the upper left hand gadget

cbf (Thu, 05 Oct 2017 15:21:24 GMT):
I would prefer that we not create yet another place where our plan of record is maintained

cbf (Thu, 05 Oct 2017 15:21:59 GMT):
while JIRA is not in an ideal configuration - we should just work with the tools we have and not scatter information to more places for it to become out of sync

dhuseby (Thu, 05 Oct 2017 15:23:56 GMT):
I’m talking with @tkuhrt about adding a JIRA consultant to the budget request.

dhuseby (Thu, 05 Oct 2017 15:24:33 GMT):
I’ll be gathering requirements over the short term so that I can get a handle on what everybody needs from JIRA

cbf (Thu, 05 Oct 2017 15:25:24 GMT):
well, I think that this is one of those situations where we could throw out a bunch of requirements but that would suggest a solution

dhuseby (Thu, 05 Oct 2017 15:25:38 GMT):
To @cbf’s point, most large open source projects require demonstration of an “intent to implement” discussion before any code will get merged.

cbf (Thu, 05 Oct 2017 15:26:06 GMT):
what we want to be able to do in the simplest case is plan out what new features are going to be in a release and plan as to whether it is likely to make it in time

dhuseby (Thu, 05 Oct 2017 15:26:33 GMT):
Who is “we”?

dhuseby (Thu, 05 Oct 2017 15:26:38 GMT):
That’s important

cbf (Thu, 05 Oct 2017 15:26:42 GMT):
ok ME

cbf (Thu, 05 Oct 2017 15:26:43 GMT):
lol

dhuseby (Thu, 05 Oct 2017 15:26:48 GMT):
Bingo!!

dhuseby (Thu, 05 Oct 2017 15:26:50 GMT):
: )

dhuseby (Thu, 05 Oct 2017 15:27:18 GMT):
If it’s the maintainers, then I would suggest doing an email process:

dhuseby (Thu, 05 Oct 2017 15:27:40 GMT):
1) send a list of features do 1.1 to the list and ask for others?

dhuseby (Thu, 05 Oct 2017 15:28:38 GMT):
2) once you have a list, then make moodle where people are allowed to select their top 5 or so.

dhuseby (Thu, 05 Oct 2017 15:28:54 GMT):
3) that creates a ranking of features based on community consensus.

dhuseby (Thu, 05 Oct 2017 15:29:22 GMT):
Then you figure out how many of the top priorities can make it into the next release.

tkuhrt (Thu, 05 Oct 2017 15:29:55 GMT):
Important that planning is done in the open to ensure that anyone can contribute.

simsc (Thu, 05 Oct 2017 15:30:00 GMT):
just as fyi and a bit of history. i sent out link to proposed content (in our wiki )asking for feedback more than once. this was an attempt to 'socialize'. gari also presented this at hackfest. so folks should be more than aware of proposed content. there was zero feedback so far.

simsc (Thu, 05 Oct 2017 15:31:05 GMT):
btw - i agree with having a prescriptive process for defining content. the above was fyi

dhuseby (Thu, 05 Oct 2017 15:31:49 GMT):
@simsc silence is acceptance

dhuseby (Thu, 05 Oct 2017 15:32:33 GMT):
It’s normal in open source that you will only get feedback when people have a problem with what you’re doing.

simsc (Thu, 05 Oct 2017 15:33:22 GMT):
good to know - because i only hear 'crickets chirping' :)

cbf (Thu, 05 Oct 2017 15:35:21 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-release?msg=gEi7wHAPbrBNSa7ee) @dhuseby I disagree

simsc (Thu, 05 Oct 2017 15:35:27 GMT):
should we just send the list one more time (explaining its already be sent a couple times). explain this will be the content unless there is feedback

dhuseby (Thu, 05 Oct 2017 15:39:53 GMT):
@simsc so you might double check that your communicating where people can hear you. But @cbf if you gate on trying to force people to reply, lots of stuff will get stuck.

dhuseby (Thu, 05 Oct 2017 15:40:17 GMT):
Check that you’re* communicating...

dhuseby (Thu, 05 Oct 2017 15:41:36 GMT):
@cbf I’m curious what your disagreement is.

cbf (Thu, 05 Oct 2017 15:42:19 GMT):
silence is not assent, it is apathy

cbf (Thu, 05 Oct 2017 15:42:33 GMT):
yes, it is important not to be a tree in the forest

dhuseby (Thu, 05 Oct 2017 15:42:43 GMT):
(BTW, pushing ownership and maintainership to the engineers who wrote/maintain pieces, you make it more likely that there will be a discussion because the focus of each maintainer is narrowed sufficiently)

simsc (Thu, 05 Oct 2017 15:42:51 GMT):
0) its posted in wiki where all the release content has been historically posted 1) sent email to hyperledger community 2) posted it in fabric-scrum rocket channel more than once 3) gari presented and showed wiki with content at hackfest.

dhuseby (Thu, 05 Oct 2017 15:42:57 GMT):
Apathy is fine.

mastersingh24 (Thu, 05 Oct 2017 15:43:00 GMT):
JIRA is not hard - frankly I could set it up with the right access

cbf (Thu, 05 Oct 2017 15:43:31 GMT):
@rjones ^^

mastersingh24 (Thu, 05 Oct 2017 15:45:25 GMT):
BTW - IMHO the ship has sailed for 1.1 other than dropping stuff. For right or wrong, that's where things are. For 1.2, we can get cracking an put the right process in place.

mastersingh24 (Thu, 05 Oct 2017 15:46:24 GMT):
And I just want to state that every open source project has a core group of people who do set the direction / priority for the project. Of course you need feedback, etc and should do this in the open, but I don't want people thinking this becomes a free for all

mastersingh24 (Thu, 05 Oct 2017 15:46:58 GMT):
I really don't see why this is so hard to be honest. ;)

jljordan_bcgov (Thu, 05 Oct 2017 15:47:02 GMT):
Has left the channel.

rjones (Thu, 05 Oct 2017 16:06:34 GMT):
I'm pro-putting-project-in-charge-of-jira. What hamstrings me is there isn't a division between "can manage user facing parts of JIRA" and "has admin access to the whole thing". If you recall I gave you admin access, @cbf, and I got spanked for doing that.

rjones (Thu, 05 Oct 2017 16:07:21 GMT):
The best I could do is something like "screenshare with @mastersingh24 and let him drive" or something, which is pretty wonky

mastersingh24 (Thu, 05 Oct 2017 16:49:53 GMT):
@rjones - so even being part of the `JIRA Administrators` group (as opposed to the `JIRA System Administrators` ) is out of the question? Even if only for say a week or so? ;)

agrimberg (Thu, 05 Oct 2017 16:51:36 GMT):
Has joined the channel.

agrimberg (Thu, 05 Oct 2017 16:52:41 GMT):
We don't grant systems level administration access to anything that we manage. We'll grant _project_ admin to the committers of a project or their requested proxies. But not global rights like that

mastersingh24 (Thu, 05 Oct 2017 16:55:38 GMT):
That's problematic because unfortunately as @rjones pointed out you can't do anything useful to customize JIRA as a project admin

agrimberg (Thu, 05 Oct 2017 16:56:39 GMT):
Give us clear requests via ticket and we'll make changes

agrimberg (Thu, 05 Oct 2017 16:57:19 GMT):
We've had far too many projects request such powers and then cause problems for their entire community to allow it to happen anymore

dhuseby (Thu, 05 Oct 2017 22:37:02 GMT):
@agrimberg I think a lot of the problem comes from the fact that a lot of us are chafing with JIRA and want some changes but we're not sure of exactly what we want. I think I'm getting a sense that we want somebody who is an expert in deploying/customizing JIRA for organizations that can come in and gather requirements and tell us what they know would work for most, if not all of our requirements and then set it up for us.

jrosmith (Fri, 06 Oct 2017 14:06:34 GMT):
hey all, i know v1.0.3 is out but I saw on npm that fabric-client and fabric-ca-client are both still at v1.0.2. will there be a v1.03 release for the node sdk or is v1.0.2 compatible?

mastersingh24 (Fri, 06 Oct 2017 14:22:00 GMT):
v1.0.2 compatible

mastersingh24 (Fri, 06 Oct 2017 14:22:00 GMT):
v1.0.2 is compatible

mastersingh24 (Fri, 06 Oct 2017 14:23:15 GMT):
``` Friends and family, The Hyperledger Fabric maintainers are happy to announce the v1.0.3 release of both Hyperledger Fabric and Hyperledger Fabric CA. The binaries / Docker images are available for download here: http://hyperledger-fabric.readthedocs.io/en/latest/samples.html#binaries The release notes can be found here: https://github.com/hyperledger/fabric/releases/tag/v1.0.3 https://github.com/hyperledger/fabric-ca/releases/tag/v1.0.3 Please note that none of the SDKs released a v1.0.3. The existing SDKs will continue to work with v1.0.3. Enjoy! -- G ```

jrosmith (Fri, 06 Oct 2017 15:04:47 GMT):
ahh i see. in the future i'll read the release notes...

mastersingh24 (Fri, 06 Oct 2017 15:27:29 GMT):
no worries.

grice_32 (Fri, 06 Oct 2017 21:00:51 GMT):
Has joined the channel.

julian (Mon, 09 Oct 2017 17:10:49 GMT):
Has joined the channel.

lmars (Tue, 10 Oct 2017 15:51:58 GMT):
Has joined the channel.

rjones (Tue, 10 Oct 2017 16:31:25 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-release?msg=AHn9BNbwoJW9BvL4Z) @dhuseby agreed

luomin (Thu, 12 Oct 2017 01:18:41 GMT):
Has joined the channel.

weeds (Thu, 12 Oct 2017 09:11:23 GMT):
@dhuseby Just to add on- Sometimes it is a little hard to determine how progress is going in the dashboards, because "done" number for Jira does not really go up. But if you look at overall subtasks, you see quite a bit of work by so many developers across community. I"m not sure if there is a better way to show some of this, but that can sometimes be a challenge. And, I always wonder what impression it leaves community in terms of progressing projects.

weeds (Thu, 12 Oct 2017 18:30:39 GMT):
Also on comments up above from Clayton- we honestly did put in rocket chat several times, the email forum several times and had Gari present at hackfest- is there something else we are missing> I just worry we bring up these topics and we don't have a "true" resolution in terms of what we are not doing right- people do want to do the right thing, but it is honestly frustrating when we are told to do one thing and then given different direction- we need to be consistent

Asara (Thu, 12 Oct 2017 18:49:58 GMT):
Is the fabric-ca released as a binary eyt?

Asara (Thu, 12 Oct 2017 18:49:58 GMT):
Is the fabric-ca released as a binary yet?

Asara (Thu, 12 Oct 2017 18:50:08 GMT):
And is there any plan for that?

mastersingh24 (Thu, 12 Oct 2017 18:50:10 GMT):
@Asara - no

mastersingh24 (Thu, 12 Oct 2017 18:50:10 GMT):
@Asara - no - we don't publish binaries. And yes - we should publish a binary of the fabric-ca-client. Should happen in the 1.1 timeframe (although we can look to see if we can do it earlier)

Asara (Thu, 12 Oct 2017 18:52:29 GMT):
Thanks @mastersingh24

Asara (Thu, 12 Oct 2017 19:58:13 GMT):
@mastersingh24 Is there a binary for the fabric-client-ca?

Asara (Thu, 12 Oct 2017 20:00:21 GMT):
I ask because if not that is the only thing you need to install golang in compile/use.

Asara (Thu, 12 Oct 2017 20:10:49 GMT):
Woops I misread what you wrote. I meant to ask about the fabric-ca-server not client :)

mastersingh24 (Thu, 12 Oct 2017 20:21:45 GMT):
We really don't publish binaries of the runtimes. We stick with Docker images

Asara (Thu, 12 Oct 2017 20:22:39 GMT):
I mean the peer/orderer are released as binaries. Any reason that isn't the case for the ca?

mastersingh24 (Thu, 12 Oct 2017 20:30:51 GMT):
We did the peer becuase unfortunately the peer can also be used as a CLI. Not sure why we did the orderer actually

Asara (Thu, 12 Oct 2017 20:32:03 GMT):
Why so against providing binaries?

mastersingh24 (Thu, 12 Oct 2017 20:38:32 GMT):
because then we get into platform support issues

Asara (Thu, 12 Oct 2017 20:41:21 GMT):
Makes sense.

KristofSajdak (Wed, 18 Oct 2017 10:00:06 GMT):
Has joined the channel.

sachikoy (Tue, 24 Oct 2017 09:51:46 GMT):
Hi, I have a question. What is the planned schedule of v1.1 release?

dave.enyeart (Tue, 24 Oct 2017 10:08:34 GMT):
@sachikoy 1.1 alpha is targeted by end of year. 1.1 GA date will be driven by community, in part based on alpha/beta feedback.

dave.enyeart (Tue, 24 Oct 2017 10:08:34 GMT):
@sachikoy 1.1 'preview' is targeted soon and 1.1 'alpha' is targeted by end of year. 1.1 GA date will be driven by community, in part based on alpha/beta feedback. For definitions of these releases, see https://wiki.hyperledger.org/community/release_taxonomy.

sachikoy (Tue, 24 Oct 2017 10:09:04 GMT):
@dave.enyeart thank you very much for your prompt reply.

weeds (Tue, 24 Oct 2017 16:31:28 GMT):
@sachikoy we do have regular updates of version 1.0 for any bugs or security fixes required-- we have released up to version 1.0.3 at this point

knagware9 (Tue, 24 Oct 2017 18:42:58 GMT):
Has joined the channel.

sachikoy (Tue, 24 Oct 2017 20:57:05 GMT):
@weeds will performance improvement (e.g., https://jira.hyperledger.org/browse/FAB-5932 ) be included in 1.0.x anytime soon?

dave.enyeart (Tue, 24 Oct 2017 21:08:20 GMT):
@sachikoy No, that perf improvement is under the Epic "Performance and scale improvements for 1.1" https://jira.hyperledger.org/browse/FAB-6421. In general only bug fixes are ported to 1.0.x, while features and improvements will go into 1.1.

dave.enyeart (Tue, 24 Oct 2017 21:09:12 GMT):
That perf improvements is in current master and will therefore be included in the 1.1 'preview' in coming weeks.

dave.enyeart (Tue, 24 Oct 2017 21:09:12 GMT):
That perf improvement is in current master and will therefore be included in the 1.1 'preview' in coming weeks.

dave.enyeart (Wed, 25 Oct 2017 11:54:07 GMT):
-------

dave.enyeart (Wed, 25 Oct 2017 11:54:10 GMT):
Things are shaping up for a 1.1 ‘preview’ release, as early as next week. For the definition of a ‘preview’ release, see https://wiki.hyperledger.org/community/release_taxonomy.

dave.enyeart (Wed, 25 Oct 2017 11:54:18 GMT):
Features in 1.1 that will be ready to try out in the preview include:

dave.enyeart (Wed, 25 Oct 2017 11:54:26 GMT):
https://jira.hyperledger.org/browse/FAB-2331- Node.js Chaincode https://jira.hyperledger.org/browse/FAB-5363 - Node.js SDK Connection Profile https://jira.hyperledger.org/browse/FAB-830 - Encryption library for chaincode https://jira.hyperledger.org/browse/FAB-5346 - Attribute-based Access Control https://jira.hyperledger.org/browse/FAB-6089 - Chaincode APIs to retrieve creator cert info https://jira.hyperledger.org/browse/FAB-6421 - Performance improvements

dave.enyeart (Wed, 25 Oct 2017 11:54:32 GMT):
Each of these have had some level of early success, through a combination of community trials, system test, and Composer test.

dave.enyeart (Wed, 25 Oct 2017 11:54:46 GMT):
A few TODOs before the ‘preview’ release: - There is a todo to simplify the encryption library and example: https://jira.hyperledger.org/browse/FAB-6751 I’ve discussed with @aso. - I think we will want to publish images that are built without experimental tag @rameshthoomu - I have looked at all highest and high defects, all the ones that I’d like to get into preview are IN REVIEW already. I’m highlighting reviewer name here:

dave.enyeart (Wed, 25 Oct 2017 11:54:46 GMT):
A few TODOs before the ‘preview’ release: - There is a todo to simplify the encryption library and example: https://jira.hyperledger.org/browse/FAB-6751 I’ve discussed with @aso . - I think we will want to publish images that are built without experimental tag @rameshthoomu - I have looked at all highest and high defects, all the ones that I’d like to get into preview are IN REVIEW already. I’m highlighting reviewer name here:

dave.enyeart (Wed, 25 Oct 2017 11:54:55 GMT):
https://jira.hyperledger.org/browse/FAB-6679 IN REVIEW @jimthematrix https://jira.hyperledger.org/browse/FAB-6707 IN REVIEW @jimthematrix https://jira.hyperledger.org/browse/FAB-6706 IN REVIEW @jimthematrix https://jira.hyperledger.org/browse/FAB-6709 IN REVIEW @jimthematrix https://jira.hyperledger.org/browse/FAB-6738 IN REVIEW @manish-sethi

dave.enyeart (Wed, 25 Oct 2017 11:54:55 GMT):
https://jira.hyperledger.org/browse/FAB-6679 IN REVIEW @jimthematrix https://jira.hyperledger.org/browse/FAB-6707 IN REVIEW @jimthematrix https://jira.hyperledger.org/browse/FAB-6706 IN REVIEW @jimthematrix https://jira.hyperledger.org/browse/FAB-6709 IN REVIEW @jimthematrix ~https://jira.hyperledger.org/browse/FAB-6738 IN REVIEW @manish-sethi ~

dave.enyeart (Wed, 25 Oct 2017 11:54:55 GMT):
~https://jira.hyperledger.org/browse/FAB-6679 IN REVIEW @jimthematrix~ https://jira.hyperledger.org/browse/FAB-6707 IN REVIEW @jimthematrix ~https://jira.hyperledger.org/browse/FAB-6706 IN REVIEW @jimthematrix~ https://jira.hyperledger.org/browse/FAB-6709 IN REVIEW @jimthematrix ~https://jira.hyperledger.org/browse/FAB-6738 IN REVIEW @manish-sethi ~

dave.enyeart (Wed, 25 Oct 2017 11:54:55 GMT):
~https://jira.hyperledger.org/browse/FAB-6679 IN REVIEW @jimthematrix~ ~https://jira.hyperledger.org/browse/FAB-6707 IN REVIEW @jimthematrix~ ~https://jira.hyperledger.org/browse/FAB-6706 IN REVIEW @jimthematrix~ https://jira.hyperledger.org/browse/FAB-6709 IN REVIEW @jimthematrix ~https://jira.hyperledger.org/browse/FAB-6738 IN REVIEW @manish-sethi ~

dave.enyeart (Wed, 25 Oct 2017 11:55:02 GMT):
Please reply if there are other defects that you think are important to get into the preview.

dave.enyeart (Wed, 25 Oct 2017 11:55:08 GMT):
-------

troyronda (Wed, 25 Oct 2017 13:43:07 GMT):
@dave.enyeart will there also be a published image with the experimental tag enabled... so the community can start more easily using FAB-1151 - private channel data, and provide feedback?

jimthematrix (Wed, 25 Oct 2017 17:57:58 GMT):
@dave.enyeart the list of 4 CRs tagged to me are all reviewed, pending a minor change to 14723 (for F.A.B-6679) and the rest are queued up behind it

lmars (Thu, 26 Oct 2017 02:10:43 GMT):
@dave.enyeart, @troyronda, are you planning to support Java Chaincode in 1.1? As I know if you build 1.1 preview with experimental tag it will be there.

shanlusun (Thu, 26 Oct 2017 02:19:38 GMT):
Has joined the channel.

dave.enyeart (Thu, 26 Oct 2017 02:36:50 GMT):
@troyronda @lmars FAB-1151 private channel data has changes coming later in 1.1 and is therefore not a highlight area for 1.1 preview. An experimental image with FAB-1151 is not intended for 1.1 preview. I do not think Java Chaincode will be a production feature in 1.1. Maintainers will meet closer to 1.1 ship date to determine which of the features are production ready versus which features need to be hidden behind experimental tag.

lmars (Thu, 26 Oct 2017 02:52:42 GMT):
@dave.enyeart, This is weird that Java Chaincode isn't supported.

firas.qutishat (Fri, 27 Oct 2017 19:29:42 GMT):
Has joined the channel.

aviralwal (Sat, 28 Oct 2017 17:36:51 GMT):
Has joined the channel.

Solaire (Mon, 30 Oct 2017 12:49:36 GMT):
Has joined the channel.

cbf (Tue, 31 Oct 2017 14:01:08 GMT):
@lmars it is a matter of resource - we would warmly welcome someone to pick up and bring across the finish line.

dave.enyeart (Tue, 31 Oct 2017 14:29:20 GMT):
@rameshthoomu are you prepared to start cutting a 1.1 preview release in the next day? I wanted to check on the status of https://jira.hyperledger.org/browse/FAB-6801

cbf (Tue, 31 Oct 2017 14:39:08 GMT):
@dave.enyeart @mastersingh24 assume that we are omitting fabric-sdk-java from 1.1.0-preview

cbf (Tue, 31 Oct 2017 14:39:11 GMT):
yes?

cbf (Tue, 31 Oct 2017 14:39:28 GMT):
my understanding is it isn't ready with connection profiles

rameshthoomu (Tue, 31 Oct 2017 15:13:05 GMT):
@dave.enyeart yes. Will update the status

dave.enyeart (Tue, 31 Oct 2017 15:18:13 GMT):
@cbf Right, I'm not seeing any reason to cut a fabric-sdk-java for 1.1.0-preview. Although I have a question out to @rickr in case he wants to showcase anything new.

rickr (Tue, 31 Oct 2017 15:39:08 GMT):
Not planning to. I'm currently not really aware of anything that's needed from an SDK for _1.1.0-preview_ to support Fabric/ca The JSDK has also SNAPSHOTs being published that can get the very latest commited code if desired.

cbf (Tue, 31 Oct 2017 15:43:21 GMT):
ok, just confirming my belief thanks!

realhuyi (Wed, 01 Nov 2017 06:17:24 GMT):
Has joined the channel.

cbf (Wed, 01 Nov 2017 14:40:17 GMT):
@dave.enyeart @rameshthoomu it occurs to me that we have never released fabric-chaincode-node repo... we need to push to NPM I suspect but I also need to add release_notes and changelog.sh script to prepare

cbf (Wed, 01 Nov 2017 14:40:42 GMT):
Ramesh, can you please check to make sure we are prepared for this?

cbf (Wed, 01 Nov 2017 14:40:47 GMT):
@jimthematrix ^^

rameshthoomu (Wed, 01 Nov 2017 14:44:19 GMT):
From CI, we have published to npm from fabric-chaincode-node https://www.npmjs.com/package/fabric-shim

rameshthoomu (Wed, 01 Nov 2017 14:44:43 GMT):
I will check this again..

dave.enyeart (Wed, 01 Nov 2017 15:06:55 GMT):
@cbf I got the green light from @scottz and @rameshthoomu that the overnight tests on master are clean, or at least as clean as they ever are :)

dave.enyeart (Wed, 01 Nov 2017 15:07:29 GMT):
The 1.1.0-preview release process can start. I see you've got some CRs out there already.

cbf (Wed, 01 Nov 2017 15:07:57 GMT):
yep almost there!

rameshthoomu (Wed, 01 Nov 2017 15:11:08 GMT):
@cbf added comment in fabric-chaincode-node patch.

rameshthoomu (Wed, 01 Nov 2017 15:39:12 GMT):
@harrijk Could you please run byfn tests on windows machine after 1.1.0-preview release

harrijk (Wed, 01 Nov 2017 15:39:43 GMT):
@rameshthoomu Will do

cbf (Wed, 01 Nov 2017 16:01:11 GMT):
@rameshthoomu @rjones or @jwagantall jenkins having a bad day

cbf (Wed, 01 Nov 2017 16:01:35 GMT):
there are tests failing apparently to do scut work post the actual test execution

cbf (Wed, 01 Nov 2017 16:01:53 GMT):
e.g. https://jenkins.hyperledger.org/job/fabric-chaincode-node-verify-s390x/23/console

rameshthoomu (Wed, 01 Nov 2017 16:05:16 GMT):
yes.. delay is causing some of the build failures.. I will re-trigger them.

cbf (Wed, 01 Nov 2017 16:08:34 GMT):
sigh

rjones (Wed, 01 Nov 2017 16:16:42 GMT):
what delay?

rameshthoomu (Wed, 01 Nov 2017 16:18:49 GMT):
I see failures in behave tests (like channel creation taking couple of sec's extra than the specified timeout value etc..) docker containers are not coming up in specified time..

rjones (Wed, 01 Nov 2017 16:19:00 GMT):
```15:55:03 [11:55:03] Starting 'docker-cli-ready'... 15:55:03 Creating network "basicnetwork_basic" with the default driver 15:55:03 Pulling orderer.example.com (hyperledger/fabric-orderer:latest)... 15:55:04 manifest for hyperledger/fabric-orderer:latest not found 15:55:04 [11:55:04] 'docker-cli-ready' errored after 865 ms 15:55:04 [11:55:04] Error in plugin 'gulp-shell' 15:55:04 Message: 15:55:04 Command `docker-compose -f /tmp/fabric-shim/basic-network/docker-compose.yml up -d cli` failed with exit code 1 15:55:04 Build step 'Execute shell' marked build as failure``` doesn't look like a post-build step failure

rameshthoomu (Wed, 01 Nov 2017 16:20:28 GMT):
not a post build failures.. seems orderer images is unavailable or not didn't find this before it try to trigger from dockerhub..

rjones (Wed, 01 Nov 2017 16:21:52 GMT):
ok. I don't think there is much I can do.

cbf (Wed, 01 Nov 2017 17:45:34 GMT):
the orderer images missing is actually a flaw in the approach of using the "PREV_VERSION" to select the image tag

cbf (Wed, 01 Nov 2017 17:45:56 GMT):
I manually verified the fabric-ca CRs that were failing

cbf (Wed, 01 Nov 2017 17:46:42 GMT):
but what this highlights is that we NEED to be saving interim image builds in Nexus's Docker registry so we can pull them for adjacent builds

rameshthoomu (Wed, 01 Nov 2017 17:54:04 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-release?msg=9XGPHDNNxeQwqx6LL) @cbf referring to this build failure.. I see orderer image failed to build because of this error ``` 00:02:45.103 curl: (18) transfer closed with 1583478 bytes remaining to read 00:02:45.105 00:02:45.105 gzip: stdin: unexpected end of file 00:02:45.105 tar: Unexpected EOF in archive 00:02:45.105 tar: Unexpected EOF in archive 00:02:45.105 tar: Error is not recoverable: exiting now ```

rameshthoomu (Wed, 01 Nov 2017 17:56:12 GMT):
checking for any mirror links available

cbf (Wed, 01 Nov 2017 19:26:03 GMT):
@jimthematrix I need you to tag fabric-chaincode-node

cbf (Wed, 01 Nov 2017 19:26:07 GMT):
I don't have privs

cbf (Wed, 01 Nov 2017 19:26:10 GMT):
git checkout master git pull git tag -a v1.0.0-preview d47625b -F release_notes/v1.0.0-preview.txt git push origin v1.0.0-preview HEAD:refs/heads/master

dave.enyeart (Wed, 01 Nov 2017 19:26:57 GMT):
fabric-chaincode-node and fabric-ca are failing CI due to same reason as before - can't find the 1.0.0-preview orderer and peer images

cbf (Wed, 01 Nov 2017 19:26:59 GMT):
@here the 1.1.0-preview is complete except for validating stuff works as expected

cbf (Wed, 01 Nov 2017 19:27:14 GMT):
weird

vdods (Wed, 01 Nov 2017 19:27:27 GMT):
:)

cbf (Wed, 01 Nov 2017 19:27:46 GMT):
but I think it is because they are looking for a tag x86_64-v1.1.0-preview whcih doesn't exist yet

dave.enyeart (Wed, 01 Nov 2017 19:28:22 GMT):
is the push to dockerhub in progress?

cbf (Wed, 01 Nov 2017 19:28:36 GMT):
I was just about to ask @rameshthoomu

cbf (Wed, 01 Nov 2017 19:28:50 GMT):
pushing the tag should have triggered

dave.enyeart (Wed, 01 Nov 2017 19:30:17 GMT):
fabric-chaincode-node needs to redo their two: https://gerrit.hyperledger.org/r/#/c/15085/ and https://gerrit.hyperledger.org/r/#/c/15087/ , since the wrong package.json was updated the first time around

dave.enyeart (Wed, 01 Nov 2017 19:30:34 GMT):
they were worried about CI failure

dave.enyeart (Wed, 01 Nov 2017 19:30:53 GMT):
but i think they can manually verify (CI failure due to cant find the other images)

dave.enyeart (Wed, 01 Nov 2017 19:31:25 GMT):
so i'll ask @jimthematrix to merge those two, and THEN tag the new commit

rameshthoomu (Wed, 01 Nov 2017 19:33:50 GMT):
yes I all triggered..

rameshthoomu (Wed, 01 Nov 2017 19:33:50 GMT):
yes all release jobs triggered..

cbf (Wed, 01 Nov 2017 19:33:57 GMT):
thanks

rameshthoomu (Wed, 01 Nov 2017 19:34:13 GMT):
I see fabric-ca release jobs are failed..

rameshthoomu (Wed, 01 Nov 2017 19:34:33 GMT):
Once the fabric orderer, tools and peer images are published will re-trigger these jobs..

dave.enyeart (Wed, 01 Nov 2017 19:35:22 GMT):
@jimthematrix says that for fabric-sdk-node and fabric-chaincode-node the push is triggered by the merge CI, rather than the tagging. So those will likely fail.

cbf (Wed, 01 Nov 2017 19:36:07 GMT):
the tag is created on the merge?

cbf (Wed, 01 Nov 2017 19:36:12 GMT):
i don't think so

cbf (Wed, 01 Nov 2017 19:36:19 GMT):
the NPM publish may be

cbf (Wed, 01 Nov 2017 19:36:29 GMT):
but then the repo isn't tagged

rameshthoomu (Wed, 01 Nov 2017 19:36:59 GMT):
yes npm publish works on merge job based on the release version..

cbf (Wed, 01 Nov 2017 19:37:07 GMT):
this is definitely an area we need to synch up because it is unnecessary complexity to have things behave arbitrarily differently

rameshthoomu (Wed, 01 Nov 2017 19:38:02 GMT):
we publish `unstable` npm modules if it is snapshot

dave.enyeart (Wed, 01 Nov 2017 19:38:20 GMT):
@rameshthoomu fabric-chaincode-node has version 1.0.0-preview while fabric is 1.1.0-preview. Will that cause a problem?

cbf (Wed, 01 Nov 2017 19:38:26 GMT):
we should publish those to Nexus

cbf (Wed, 01 Nov 2017 19:38:30 GMT):
not NPM

cbf (Wed, 01 Nov 2017 19:38:49 GMT):
@dave.enyeart yeah, that was my observation earlier

cbf (Wed, 01 Nov 2017 19:38:51 GMT):
I went with it

cbf (Wed, 01 Nov 2017 19:38:58 GMT):
either way it seems weird

cbf (Wed, 01 Nov 2017 19:39:16 GMT):
eg first release is 1.1 or it is inconsistent with fabric releases

dave.enyeart (Wed, 01 Nov 2017 19:39:49 GMT):
yeah, it is weird but i'm asking @rameshthoomu if it will actually break any assumptions in the scripts?

rameshthoomu (Wed, 01 Nov 2017 19:40:54 GMT):
no.. @dave.enyeart

dave.enyeart (Wed, 01 Nov 2017 19:41:05 GMT):
ok, so it is weird but acceptable

dave.enyeart (Wed, 01 Nov 2017 19:41:05 GMT):
ok, so it is weird but workable

rameshthoomu (Wed, 01 Nov 2017 19:41:47 GMT):
fabric-chaincode-node merge builds are failed because we have an issue in building fabric-ca-orderer etc.. images

cbf (Wed, 01 Nov 2017 19:47:19 GMT):
ok images starting to get posted

cbf (Wed, 01 Nov 2017 19:47:45 GMT):
retrigger the build

cbf (Wed, 01 Nov 2017 19:47:56 GMT):
https://hub.docker.com/r/hyperledger/fabric-orderer/tags/

cbf (Wed, 01 Nov 2017 19:47:59 GMT):
tag is there now

cbf (Wed, 01 Nov 2017 19:48:23 GMT):
brb walking dogs

dave.enyeart (Wed, 01 Nov 2017 20:16:51 GMT):
@rameshthoomu for fabric-ca only 2 of 3 got published: https://hub.docker.com/r/hyperledger/fabric-ca/tags/

rameshthoomu (Wed, 01 Nov 2017 20:17:32 GMT):
yes.. Triggered s390x now..

rameshthoomu (Wed, 01 Nov 2017 20:19:34 GMT):
done.. 3/3

dave.enyeart (Wed, 01 Nov 2017 20:20:56 GMT):
@rameshthoomu I see it now

dave.enyeart (Wed, 01 Nov 2017 20:21:09 GMT):
go ahead and retrigger fabric-sdk-node

dave.enyeart (Wed, 01 Nov 2017 20:25:21 GMT):
SUCCESS

dave.enyeart (Wed, 01 Nov 2017 20:25:21 GMT):
SUCCESS on Mac :white_check_mark:

dave.enyeart (Wed, 01 Nov 2017 20:25:54 GMT):
cloned updated samples and pulled 1.1.0-preview binaries and images using instructions: http://hyperledger-fabric.readthedocs.io/en/latest/samples.html

dave.enyeart (Wed, 01 Nov 2017 20:26:22 GMT):
successfully ran byfn using instructions: http://hyperledger-fabric.readthedocs.io/en/latest/build_network.html

cbf (Wed, 01 Nov 2017 20:32:54 GMT):
I had success on mac as well

cbf (Wed, 01 Nov 2017 20:33:03 GMT):
@dave.enyeart here's a draft of the note

cbf (Wed, 01 Nov 2017 20:33:04 GMT):
https://jira.hyperledger.org/browse/FAB-6862

cbf (Wed, 01 Nov 2017 20:33:19 GMT):
if you approve, I will send it out

dave.enyeart (Wed, 01 Nov 2017 20:33:54 GMT):
I'm make a few edits (including spelling of my name) :)

cbf (Wed, 01 Nov 2017 20:34:02 GMT):
lol apologies

dave.enyeart (Wed, 01 Nov 2017 20:34:38 GMT):
you have to leave soon right?

dave.enyeart (Wed, 01 Nov 2017 20:34:49 GMT):
i think we'll want to get some more testing done before emailing

dave.enyeart (Wed, 01 Nov 2017 20:35:14 GMT):
sdk, node.js chaincode, platforms

davidkel (Wed, 01 Nov 2017 20:35:48 GMT):
Currently testing the preview with node.js container support with composer. It's looking good so far

davidkel (Wed, 01 Nov 2017 20:36:26 GMT):
@dave.enyeart did some couchdb performance improvements go in very recently ?

dave.enyeart (Wed, 01 Nov 2017 20:37:02 GMT):
couchdb perf improvements have been in for a month or two

davidkel (Wed, 01 Nov 2017 20:38:25 GMT):
thought I had a more recent level of the source code when testing today before the preview. Just running against the preview our query system tests went through at such a rate I thought they may not be working

dave.enyeart (Wed, 01 Nov 2017 20:39:16 GMT):
did you have indexes in place for couchdb? that makes all the difference.

dave.enyeart (Wed, 01 Nov 2017 20:39:16 GMT):
did you have indexes in place for couchdb queries? that makes all the difference.

davidkel (Wed, 01 Nov 2017 20:39:26 GMT):
No, no indexes

dave.enyeart (Wed, 01 Nov 2017 20:39:57 GMT):
if you have any volume of data, you'll need indexes to get good performance on rich queries

davidkel (Wed, 01 Nov 2017 20:41:02 GMT):
In this case the volume is low as these as automated system tests which set up a few assets and participants to query. but before each test took a few seconds to run. Now The whole batch took just a few seconds to run

dave.enyeart (Wed, 01 Nov 2017 20:41:30 GMT):
i'll take it

davidkel (Wed, 01 Nov 2017 20:42:43 GMT):
Will investigate more tomorrow but it is looking good from a composer (via node.js chaincode) point of view.

dave.enyeart (Wed, 01 Nov 2017 20:47:36 GMT):
@davidkel are you using sdk connection profile as well?

davidkel (Wed, 01 Nov 2017 20:48:53 GMT):
@dave.enyeart No the branch I have is just dedicated to the node.js chaincode support. We have another branch for the connection profile stuff but that works fine against 1.0.x still

cbf (Wed, 01 Nov 2017 20:53:24 GMT):
@dave.enyeart feel free to send the email after you edit - I need to bug out to head down to Ft lauderdale

cbf (Wed, 01 Nov 2017 20:53:32 GMT):
or I can send later this evening

mastersingh24 (Wed, 01 Nov 2017 22:02:51 GMT):
@dave.enyeart - do you also want to include an announcement for v1.0.4 as well?

dave.enyeart (Wed, 01 Nov 2017 22:09:36 GMT):
@mastersingh24 I'd suggest keep them separate, go ahead and announce 1.0.4

rameshthoomu (Wed, 01 Nov 2017 22:14:02 GMT):
FYI: ``` published fabric images to dockerhub -- done https://hub.docker.com/r/hyperledger/fabric-peer/tags/ published fabric-ca images to dockerhub -- done https://hub.docker.com/r/hyperledger/fabric-ca/tags/ published fabric binaries to nexus repository -- done https://nexus.hyperledger.org/content/repositories/releases/org/hyperledger/fabric/hyperledger-fabric/ published fabric-sdk-node modules (fabric-client & fabric-ca-client) to npm -- done https://www.npmjs.com/package/fabric-client & https://www.npmjs.com/package/fabric-ca-client published fabric-chaincode-node (fabric-shim) to npm -- done https://www.npmjs.com/package/fabric-shim ```

rameshthoomu (Wed, 01 Nov 2017 22:15:09 GMT):
byfn tests worked on `x86_64`, `s390x` and `ppc64le`.. @harrijk testing on windows (stuck with mount issue)

rameshthoomu (Wed, 01 Nov 2017 22:15:09 GMT):
**byfn** tests worked on `x86_64`, `s390x` and `ppc64le`.. @harrijk testing on windows (stuck with mount issue)

dave.enyeart (Wed, 01 Nov 2017 22:49:21 GMT):
and for me byfn and fabcar (go and node.js chaincode) worked on mac

harrijk (Wed, 01 Nov 2017 23:07:40 GMT):
I managed to get a clean e2e test on Windows, but had to make the following changes... 1. Edit fabric-samples/first-network/docker-compose-cli.yaml and change ... ``` - ./crypto-config:/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/ - ./scripts:/opt/gopath/src/github.com/hyperledger/fabric/peer/scripts/ - ./channel-artifacts:/opt/gopath/src/github.com/hyperledger/fabric/peer/channel-artifacts ``` to ... ``` - ./crypto-config/:/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/ - ./scripts/:/opt/gopath/src/github.com/hyperledger/fabric/peer/scripts/ - ./channel-artifacts/:/opt/gopath/src/github.com/hyperledger/fabric/peer/channel-artifacts ``` 2. Remove the carriage return characters (^M) in fabric-samples/scripts/script.sh by issuing `dos2unix.exe fabric-samples/scripts/script.sh`

dave.enyeart (Thu, 02 Nov 2017 00:57:41 GMT):
Thanks @harrijk . Could you or @lehors submit a change to fabric-samples?

dave.enyeart (Thu, 02 Nov 2017 00:58:50 GMT):
Note that in the v1.1.0-preview docs we have people clone the master branch of fabric-samples, so we'll be able to make enhancements after today's v1.1.0-preview release

dave.enyeart (Thu, 02 Nov 2017 01:01:17 GMT):
------------------------------------------------------------------

dave.enyeart (Thu, 02 Nov 2017 01:01:17 GMT):
-----------------------------------------------------------------------------------------------

dave.enyeart (Thu, 02 Nov 2017 01:01:42 GMT):
--- Hyperledger Fabric v1.1.0-preview has been announced ---

dave.enyeart (Thu, 02 Nov 2017 01:01:48 GMT):
--- https://lists.hyperledger.org/pipermail/hyperledger-fabric/2017-November/002036.html ---

dave.enyeart (Thu, 02 Nov 2017 01:02:00 GMT):
-----------------------------------------------------------------------------------------------

dave.enyeart (Thu, 02 Nov 2017 01:09:25 GMT):
@jimthematrix @bretharrison Need you to tag the fabric-chaincode-node repository with v1.0.0-preview. This is the last of the repositories to be tagged for the preview. As we get closer to alpha, we'll need to make a decision of whether to promote it to v1.1.0 to be aligned with the other components.

dave.enyeart (Thu, 02 Nov 2017 01:11:30 GMT):
```git checkout master git pull git tag -a v1.0.0-preview 6a2a696 -F release_notes/v1.0.0-preview.txt git push origin v1.0.0-preview HEAD:refs/heads/master```

rickr (Fri, 03 Nov 2017 00:46:34 GMT):
Is there published anywhere the release targets dates for 1.1.0-alpha and 1.1.0 ?

dave.enyeart (Fri, 03 Nov 2017 02:19:27 GMT):
@rickr Given remaining work items and velocity, my best guess is alpha in December and release in Q1.

Amitchandra (Fri, 03 Nov 2017 07:24:53 GMT):
Has joined the channel.

bennettneale (Fri, 03 Nov 2017 16:16:07 GMT):
Has joined the channel.

weeds (Fri, 03 Nov 2017 19:22:31 GMT):
this is all up to community but the hope is beta in jan and release in feb... but it depends on velocity of course and how well we do with defect backlog, testing,etc,.

weeds (Fri, 03 Nov 2017 19:22:47 GMT):
so that's just a "guess"

weeds (Fri, 03 Nov 2017 19:23:17 GMT):
and of course did the features get done to make alpha in December since the list has been identified as to what had to be done by community

PreetCS (Mon, 06 Nov 2017 05:23:20 GMT):
Hi all,

PreetCS (Mon, 06 Nov 2017 05:23:51 GMT):
how to write, run and deploy chaincode in ibm bluemix ?

mastersingh24 (Mon, 06 Nov 2017 10:16:51 GMT):
@PreetCS - I'd suggest posting your question here: https://developer.ibm.com/answers/topics/blockchain/?smartspace=bluemix

rickr (Mon, 06 Nov 2017 13:44:52 GMT):
Is cryptogen not producing TLS certs for the client /peer/order et al ?

mastersingh24 (Mon, 06 Nov 2017 14:38:57 GMT):
@rickr - not sure if you are asking about producing client certificates for mutual TLS? If that's the question, then the answer is no. I've slowly been working all of the mutual TLS tasks and will likely add TLS certs for the clients generated by cryptogen. No need to do that for the orderer and the peer actually uses the same cert for both server and client TLS

rickr (Mon, 06 Nov 2017 14:53:03 GMT):
So the plan for mutual TLS is just to use the peer's server TLS certs for the client?

mastersingh24 (Mon, 06 Nov 2017 15:57:35 GMT):
Sorry - not - the peer

mastersingh24 (Mon, 06 Nov 2017 15:57:35 GMT):
Sorry - no - the peer's will use their server certificate and their client certificate for communicating with other peers and the ordering nodes. I'll update cryptogen to generate some client certificates for the sample clients. But I need to think a bit more about exactly what we want to do for integration tests first

lehors (Mon, 06 Nov 2017 17:21:42 GMT):
In an effort to fulfill a long overdue action on my part I created https://jira.hyperledger.org/browse/FAB-6897 "The list of supported OS is not documented". I'd like to invite @cbf @mastersingh24 @rameshthoomu @bmos299 and anyone else interested to chime in

mastersingh24 (Mon, 06 Nov 2017 17:25:03 GMT):
"It's supported unless it doesn't work" ;)

lehors (Mon, 06 Nov 2017 17:31:39 GMT):
oh, I know that part too well! :)

cbf (Wed, 08 Nov 2017 08:37:43 GMT):
I guess that means Windows 7 is RIGHT OUT! LOL @lehors @mastersingh24

mastersingh24 (Wed, 08 Nov 2017 09:16:22 GMT):
Actually, I use Windows 7 and Windows 10 occasionally and I get it to work ;)

shkhssn (Wed, 08 Nov 2017 09:32:14 GMT):
Has joined the channel.

ascatox (Wed, 08 Nov 2017 14:24:12 GMT):
Has joined the channel.

lehors (Wed, 08 Nov 2017 15:29:33 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-release?msg=bnW4yJKXpcZgEj8o7) @mastersingh24 the question is what is "it" in your statement? Some things definitely work (thankfully) but not everything does

mastersingh24 (Wed, 08 Nov 2017 17:36:48 GMT):
I run it all in Docker most of the time

divyank (Thu, 09 Nov 2017 13:31:15 GMT):
Has joined the channel.

divyank (Thu, 09 Nov 2017 13:34:19 GMT):
Hello, I'm trying to tag a fabric-baseimage release to complete FAB-6778

divyank (Thu, 09 Nov 2017 13:34:36 GMT):
Does anyone know how I can go about doing this? https://gerrit.hyperledger.org/r/c/15143/

simsc (Thu, 09 Nov 2017 14:27:36 GMT):
As a community, it would be helpful to establish a cadence and schedule for playbacks. Playbacks are intended to allow contributors to present a proposal or provide progress on a particular feature, to get feedback from the community. There will be a best effort to hold this on Monday and Tuesday at 10:00 - 11:00 EST to accommodate different geos and work week schedules. Weekly scrums are a great place to propose topics and get on the agenda. #fabric-scrum Here is a place on the wiki to help track and manage the playbacks https://wiki.hyperledger.org/projects/fabric/playbacks Please look for web conference information in the #fabric-playbacks channel prior to meeting starting. Lets try and see how it goes!

rameshthoomu (Thu, 09 Nov 2017 14:42:49 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-release?msg=f8NDXqMy7MDLSCZaP) @divyank added comment

divyank (Mon, 13 Nov 2017 20:58:22 GMT):
Hi @rameshthoomu , I addressed your comments on https://gerrit.hyperledger.org/r/c/15143 . Can we go ahead with tagging the base image release?

rameshthoomu (Mon, 13 Nov 2017 20:59:16 GMT):
someone has to approve and merge..

rameshthoomu (Mon, 13 Nov 2017 20:59:37 GMT):
may be #fabric-pr-review is the better place to ask

Chandraamit (Tue, 14 Nov 2017 16:15:40 GMT):
Has joined the channel.

Cryptobuster (Tue, 14 Nov 2017 23:06:16 GMT):
Has joined the channel.

rickr (Wed, 15 Nov 2017 15:41:44 GMT):
https://jira.hyperledger.org/browse/FAB-6042 is any part of this in a garrit CR ? Can the client/sdk get the resource config from the peer ? Are the exact details of this new Resource tree defined and confident we're settled on it ? Are protopuf changes still pending (ID object some protobuf artifact) ? Would it be possible to have a _concrete_ example of chaincode in this resource tree. What type of hash is required ? Over what ?

rickr (Wed, 15 Nov 2017 15:42:10 GMT):
@jyellick @mastersingh24 ^^ ?

yacovm (Wed, 15 Nov 2017 15:48:44 GMT):
@rickr there is https://gerrit.hyperledger.org/r/#/c/15479/ from @aambati and I'm working on the peer CLI side of it, I hope to release a functional working change set by end of tomorrow if that is any help

rickr (Wed, 15 Nov 2017 15:54:38 GMT):
I have the code that calculates the Configupdate from new to updated block. The next big step would be knowing *exactly* how the Resource tree needs to be modified to get updated block.

yacovm (Wed, 15 Nov 2017 15:55:53 GMT):
I guess maybe you can look at https://gerrit.hyperledger.org/r/#/c/15461/7/peer/chaincode/resources.go

rickr (Wed, 15 Nov 2017 15:55:55 GMT):
Getting the existing resource block and then doing those modification

yacovm (Wed, 15 Nov 2017 15:56:03 GMT):
I have the code here and I _ hope _ it's correct

yacovm (Wed, 15 Nov 2017 15:56:09 GMT):
but only @jyellick can verify

rickr (Wed, 15 Nov 2017 15:57:49 GMT):
I think it would be helpful for all sdks if a more concrete example of the Resource tree would be provided in the JIRA

cbf (Mon, 20 Nov 2017 12:46:46 GMT):
@rickr what's stopping you? :-)

philviana (Tue, 21 Nov 2017 06:15:04 GMT):
Has joined the channel.

jackeyliliang (Fri, 24 Nov 2017 03:01:20 GMT):
Has joined the channel.

baoyangc (Sun, 26 Nov 2017 16:41:41 GMT):
Has joined the channel.

rickr (Mon, 27 Nov 2017 15:22:11 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-release?msg=3AQDkj4HiGg8PbSXv) If I have to reverse engineer from source I'll be too far behind getting this function in the sdk to document what other will need to know ?

bretharrison (Tue, 28 Nov 2017 17:23:39 GMT):
@jyellick @rickr Will this new `Resources` config tree have any values that are bytes, and if so will the name be used as in the channel config to indicate how to decode those bytes?

jyellick (Tue, 28 Nov 2017 17:27:00 GMT):
@bretharrison Yes and yes, config values are always encoded as bytes, and we follow the same naming scheme. The protos have already been merged, if you take a look at https://github.com/hyperledger/fabric/blob/master/protos/peer/resources.proto

rickr (Tue, 28 Nov 2017 17:37:16 GMT):
Ok -- good to hear. Bret and I are planning to have a utility that follows that pattern so given the `name` it's a simple lookup to determine what it's to be decoded as. I hope the name will be unique anywhere in the tree ?

egeek (Wed, 29 Nov 2017 11:17:23 GMT):
Has joined the channel.

mastersingh24 (Fri, 01 Dec 2017 09:18:56 GMT):
FYI: ETA for v1.0.5 is 12/4 (Mon)

rameshthoomu (Fri, 01 Dec 2017 15:12:49 GMT):
@cbf could you please check this FAB-7244

cbf (Fri, 01 Dec 2017 15:40:35 GMT):
comment left

rameshthoomu (Fri, 01 Dec 2017 17:59:38 GMT):
Thanks Chris.. Once the tag is confirmed for dependent images, will publish to docker hub

Kayad (Mon, 04 Dec 2017 02:49:24 GMT):
Has joined the channel.

ttandale (Mon, 04 Dec 2017 12:26:49 GMT):
Has joined the channel.

ttandale (Mon, 04 Dec 2017 12:28:01 GMT):
hii, I want to create multiple channel, can anyone ple help me??

kostas (Mon, 04 Dec 2017 13:02:35 GMT):
@ttandale: Let's do this in #fabric

lvdh (Tue, 05 Dec 2017 13:42:29 GMT):
Has joined the channel.

rickr (Tue, 05 Dec 2017 15:27:07 GMT):
Hi @sanchezl I know _officially_ Node CC should be supported in 1.1 ( I think with out doing any changes at all ) What's the story for Java CC ? Same level of support active by default ? Still need to change code to enable ?

sanchezl (Tue, 05 Dec 2017 15:27:07 GMT):
Has joined the channel.

dave.enyeart (Tue, 05 Dec 2017 15:57:15 GMT):
Java CC is already hidden behind experimental build tag, meaning it will not be in 1.1, but people can build in experimental mode if they want to play with it.

rickr (Tue, 05 Dec 2017 17:21:37 GMT):
I treat `experimental` as not supported.

rickr (Tue, 05 Dec 2017 17:22:15 GMT):
I suppose the Node CC is not `experimental` and is enabled by default ?

dave.enyeart (Tue, 05 Dec 2017 18:03:43 GMT):
Correct

samwood (Tue, 05 Dec 2017 20:10:47 GMT):
is there an updated ETA for v1.0.5?

mastersingh24 (Thu, 07 Dec 2017 07:24:59 GMT):
@samwood - it has been released

Percival Lucena (Thu, 07 Dec 2017 19:25:11 GMT):
Has joined the channel.

blreay (Fri, 08 Dec 2017 02:07:56 GMT):
Has joined the channel.

blreay (Fri, 08 Dec 2017 02:09:25 GMT):
Hi, can anybody tell me the ETA for v1.1.0, Thanks a lot.

dave.enyeart (Fri, 08 Dec 2017 10:22:37 GMT):
@blreay Q1... exact timing depends on community feedback on the upcoming Alpha release

cbf (Fri, 08 Dec 2017 11:41:26 GMT):
@here @mastersingh24 sent out the 1.0.5 release announce last night. Thanks, Gari! https://twitter.com/christo4ferris/status/939091680866729984 has the same text

gdinhof (Fri, 08 Dec 2017 17:03:32 GMT):
Has joined the channel.

alvaradojl (Sun, 10 Dec 2017 11:04:47 GMT):
Has joined the channel.

baoyangc (Mon, 11 Dec 2017 02:01:34 GMT):
when will the Alpha release come?

nasht00 (Mon, 11 Dec 2017 08:16:31 GMT):
Has joined the channel.

nasht00 (Mon, 11 Dec 2017 08:20:03 GMT):
If I start a new project now, do you recommend developing under 1.1-preview or 1.0.5? Meaning, is the preview stable enough for development purposes?

nasht00 (Mon, 11 Dec 2017 08:20:31 GMT):
On a related note, if I chose 1.0.5, how hard will the 1.1 migration be?

dave.enyeart (Mon, 11 Dec 2017 11:55:59 GMT):
1.1.0-preview has gone through a full round of system testing, it is certainly stable enough for development purpose. 1.0.5 and 1.1 are compatible so the eventual migration would not be a problem either.

guolidong (Tue, 12 Dec 2017 05:58:47 GMT):
Has joined the channel.

baoyangc (Thu, 14 Dec 2017 03:14:49 GMT):
@dave.enyeart , does the version 1.0.5 include the features in the version 1.1-preview?

dave.enyeart (Thu, 14 Dec 2017 03:16:00 GMT):
No, 3rd digit releases include bug fixes only. New features come in 2nd digit releases like 1.1.

valleylord (Fri, 15 Dec 2017 06:51:17 GMT):
Has joined the channel.

troyronda (Fri, 15 Dec 2017 13:17:59 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-release?msg=JWLicvryfjh6opwa2) does anyone know the eta for the next baseimage tag?

thiago-moreira (Fri, 15 Dec 2017 18:56:24 GMT):
Has joined the channel.

Dau (Sat, 16 Dec 2017 13:59:24 GMT):
Has joined the channel.

rickr (Mon, 18 Dec 2017 15:58:43 GMT):
I'm seeing a lot of changes for the alpha release still in flight. Namely filter blocks and chaincode life cycle. So any thoughts on the alpha's eta announce ?

yacovm (Mon, 18 Dec 2017 16:22:04 GMT):
@dave.enyeart ^

rickr (Mon, 18 Dec 2017 16:32:38 GMT):
just caught this https://chat.hyperledger.org/channel/fabric-scrum?msg=LjZzFENEEXv4fkghT

janbols (Thu, 21 Dec 2017 12:33:51 GMT):
Has joined the channel.

peter.li (Wed, 27 Dec 2017 06:29:33 GMT):
Has joined the channel.

rambsuthar (Tue, 02 Jan 2018 20:26:38 GMT):
Has joined the channel.

elias_p (Tue, 02 Jan 2018 22:57:07 GMT):
Has joined the channel.

gurel (Wed, 03 Jan 2018 17:47:15 GMT):
Has joined the channel.

cbf (Thu, 04 Jan 2018 12:43:41 GMT):
@here please see https://chat.hyperledger.org/channel/fabric-maintainers?msg=ZjBJqwCfomcsRTLHm for info about proposed FEATURE FREEZE

weeds (Thu, 04 Jan 2018 15:40:54 GMT):
https://jira.hyperledger.org/secure/Dashboard.jspa?selectPageId=10104 when I look at the dashboard- the one titled fabric dashboard, there are 6 in progress and 1 in review I mention as we really need to make sure we are clear to the path to get to alpha if that is indeed code cutoff and features required- areall of these are really going to make the alpha?... and what has to do to move them to done done done if so.

aceyin (Tue, 09 Jan 2018 03:34:17 GMT):
Has joined the channel.

aceyin (Tue, 09 Jan 2018 03:36:37 GMT):
the nexus artifact in get-byfn.sh is invalid here is the content of 'get-byfn.sh': ``` VERSION=1.0.4 echo "===> Downloading Build Your First Network sample application" curl https://nexus.hyperledger.org/content/repositories/releases/org/hyperledger/fabric/examples/hyperledger-fabric-byfn-$(VERSION).tar.gz | tar xz ``` the artifact directory: *https://nexus.hyperledger.org/content/repositories/releases/org/hyperledger/fabric/examples* is invalid.

simsc (Thu, 11 Jan 2018 16:56:33 GMT):
Here is a dashboard for remaining development items for feature freeze. Bugs, ID, and QA will continue past Jan 12.

simsc (Thu, 11 Jan 2018 16:56:36 GMT):
https://jira.hyperledger.org/secure/Dashboard.jspa?selectPageId=10701

cbf (Thu, 11 Jan 2018 20:13:21 GMT):
thanks @simsc

dave.enyeart (Mon, 15 Jan 2018 20:16:37 GMT):
@here Besides the few remainders listed in the 1.1 dashboard https://jira.hyperledger.org/secure/Dashboard.jspa?selectPageId=10701, we have achieved FEATURE FREEZE for 1.1. Maintainers will not merge other features/improvements through the remainder of the release. Bug fixes, doc updates, samples, and system test are the priority this week, with expectation that alpha is cut next week.

dave.enyeart (Mon, 15 Jan 2018 20:16:37 GMT):
@here Besides the few In-Review and SDK remainders listed in the 1.1 dashboard https://jira.hyperledger.org/secure/Dashboard.jspa?selectPageId=10701, we have achieved FEATURE FREEZE for 1.1. Maintainers will not merge other features/improvements through the remainder of the release. Bug fixes, doc updates, samples, and system test are the priority this week, with expectation that alpha is cut next week.

cbf (Wed, 17 Jan 2018 18:11:35 GMT):
@greg.haskins @dave.enyeart @rameshthoomu just merged the (I believe) last change to baseimage repo for the update of couchdb release... I think that we should be ready to cut a baseimage release so that we can start testing with the integration testing for 1.1

cbf (Wed, 17 Jan 2018 18:11:44 GMT):
@greg.haskins are you on board?

cbf (Wed, 17 Jan 2018 18:11:56 GMT):
Shall I submit a CR?

greg.haskins (Wed, 17 Jan 2018 22:57:43 GMT):
Hey chris, I didnt see the recent activity, but if its related to our last conversation (simultaneous release of the third-party artifacts with the same version number for now, and then looking at independent streams for the third party stuff going forward, sounds good to me

greg.haskins (Wed, 17 Jan 2018 22:58:49 GMT):
(and sorry ive been so distracted guys...trying to get some plumbing done so I can come back and actually play in fabric-land again

greg.haskins (Wed, 17 Jan 2018 22:58:52 GMT):
hopefully soon

cbf (Wed, 17 Jan 2018 23:00:21 GMT):
ok thx

cbf (Wed, 17 Jan 2018 23:12:04 GMT):
@greg.haskins I am a bit confused

greg.haskins (Wed, 17 Jan 2018 23:12:18 GMT):
@cbf: im sure its me

greg.haskins (Wed, 17 Jan 2018 23:12:19 GMT):
heh

cbf (Wed, 17 Jan 2018 23:12:34 GMT):
fabric-baseimage Makefile has: VERSION ?= 0.4.3 IS_RELEASE=true

cbf (Wed, 17 Jan 2018 23:12:49 GMT):
yet current release published is 0.4.2

cbf (Wed, 17 Jan 2018 23:13:06 GMT):
I guess we need to trigger with a tag?

greg.haskins (Wed, 17 Jan 2018 23:13:19 GMT):
yes, the tag is what actually kicks the pipeline

cbf (Wed, 17 Jan 2018 23:13:33 GMT):
ok

cbf (Wed, 17 Jan 2018 23:13:44 GMT):
do you want to do?

greg.haskins (Wed, 17 Jan 2018 23:13:54 GMT):
the IS_RELEASE variable only serves to direct the artifacts versioning

greg.haskins (Wed, 17 Jan 2018 23:14:00 GMT):
sure, standby

cbf (Wed, 17 Jan 2018 23:14:06 GMT):
thx

greg.haskins (Wed, 17 Jan 2018 23:15:31 GMT):
ah, looks like the version was committed wrong

greg.haskins (Wed, 17 Jan 2018 23:15:33 GMT):
let me investigate

greg.haskins (Wed, 17 Jan 2018 23:17:01 GMT):
ok, it only happened one commit ago

greg.haskins (Wed, 17 Jan 2018 23:17:52 GMT):
the _most_ convervative thing to do would be to bump the version one more time (v0.4.4)

greg.haskins (Wed, 17 Jan 2018 23:17:55 GMT):
any objections to that?

greg.haskins (Wed, 17 Jan 2018 23:18:10 GMT):
otherwise, i can cut a v0.4.3 but theres an impurity in the process

greg.haskins (Wed, 17 Jan 2018 23:18:15 GMT):
its not a huge deal either way

greg.haskins (Wed, 17 Jan 2018 23:33:00 GMT):
@cbf: is there a release CR to reference?

rameshthoomu (Wed, 17 Jan 2018 23:42:55 GMT):
@greg.haskins consider latest commit is the release CR. made IS_RELEASE=true in the previous commit assuming bumping nodejs version will go with that but that didn't go through

rameshthoomu (Wed, 17 Jan 2018 23:43:49 GMT):
in latest commit I have added couchdb change keeping IS_RELEASE=true..

greg.haskins (Wed, 17 Jan 2018 23:43:58 GMT):
understood, but that isnt how I designed it nor recommend it to be used

greg.haskins (Wed, 17 Jan 2018 23:44:38 GMT):
what I recommend is 1) a discrete commit that sets ONLY IS_RELEASE=true and a subsequent commit that unsets IS_RELEASE=true and bumps the version

greg.haskins (Wed, 17 Jan 2018 23:44:43 GMT):
and then we target the tag at the first

greg.haskins (Wed, 17 Jan 2018 23:45:16 GMT):
that way, you already know that the CI passes before the IS_RELEASE is set and you have one and only one commit that generates a release artifact

greg.haskins (Wed, 17 Jan 2018 23:45:42 GMT):
if we have to, we can push it through as is, but I would recommend we just do it right

greg.haskins (Wed, 17 Jan 2018 23:46:21 GMT):
its not a huge deal in this case, but I want to having ambiguity if there is a bisect

greg.haskins (Wed, 17 Jan 2018 23:46:21 GMT):
its not a huge deal in this case, but I want to avoid having ambiguity if there is a bisect

rameshthoomu (Wed, 17 Jan 2018 23:46:32 GMT):
agree..

greg.haskins (Wed, 17 Jan 2018 23:49:43 GMT):
how shall we proceed >?

greg.haskins (Wed, 17 Jan 2018 23:49:43 GMT):
how shall we proceed?

rameshthoomu (Wed, 17 Jan 2018 23:57:51 GMT):
Will continue as is otherwise we have to submit two CR's 1) make it "false" 2) release CR to make it "True"

cbf (Thu, 18 Jan 2018 00:21:33 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-release?msg=sarFmcvFCJu2SZ5Hs) @greg.haskins https://jira.hyperledger.org/browse/FAB-7797

greg.haskins (Thu, 18 Jan 2018 03:13:55 GMT):
@cbf: thank you

greg.haskins (Thu, 18 Jan 2018 03:14:05 GMT):
i think correcting it is the right thing to do: I pushed three CRs

greg.haskins (Thu, 18 Jan 2018 03:14:06 GMT):
https://gerrit.hyperledger.org/r/c/16923/

greg.haskins (Thu, 18 Jan 2018 03:14:15 GMT):
https://gerrit.hyperledger.org/r/c/16925/

greg.haskins (Thu, 18 Jan 2018 03:14:28 GMT):
https://gerrit.hyperledger.org/r/c/16927/

greg.haskins (Thu, 18 Jan 2018 03:14:50 GMT):
once those are merged, ill push a tag to 16925 and that should push the artifact

yingmsky (Thu, 18 Jan 2018 03:24:21 GMT):
Has joined the channel.

Manish.Sharma (Thu, 18 Jan 2018 09:13:52 GMT):
Has joined the channel.

mastersingh24 (Thu, 18 Jan 2018 10:38:56 GMT):
Bug fix for Node SDK (both master and release): https://gerrit.hyperledger.org/r/#/q/owner:gari.r.singh%2540gmail.com+status:open

rickr (Thu, 18 Jan 2018 16:11:40 GMT):
Features for alpha are *locked down*. Is then _ 1.1 alpha _ feature complete ? No more features for 1.1 ?

dave.enyeart (Thu, 18 Jan 2018 19:15:49 GMT):
@rickr That's correct. If there items that are a gray area we can ask the maintainers for their opinion of whether it should go in, this is done by using a jira label of `review-needed`.

dave.enyeart (Thu, 18 Jan 2018 19:22:44 GMT):
@mastersingh24 There is a request from @mlishok to backport these node-sdk-fixes to 1.0.x:

mlishok (Thu, 18 Jan 2018 19:22:44 GMT):
Has joined the channel.

dave.enyeart (Thu, 18 Jan 2018 19:22:51 GMT):
https://gerrit.hyperledger.org/r/#/c/15719/

dave.enyeart (Thu, 18 Jan 2018 19:22:56 GMT):
https://gerrit.hyperledger.org/r/#/c/16237/

dave.enyeart (Thu, 18 Jan 2018 19:23:16 GMT):
what is the official process to request this? open a jira bug against 1.0.x?

greg.haskins (Thu, 18 Jan 2018 19:43:32 GMT):
@cbf: need one more +2 https://gerrit.hyperledger.org/r/c/16927/

greg.haskins (Thu, 18 Jan 2018 19:43:36 GMT):
and then someone to fire the stack in

dave.enyeart (Thu, 18 Jan 2018 19:59:00 GMT):
@greg.haskins I've +2ed all three. Go ahead and submit/tag.

cbf (Thu, 18 Jan 2018 22:04:12 GMT):
@greg.haskins they are all ready to go... want me to push the blue button?

cbf (Thu, 18 Jan 2018 22:04:57 GMT):
boom

cbf (Thu, 18 Jan 2018 22:05:03 GMT):
ready to tag

greg.haskins (Fri, 19 Jan 2018 02:47:36 GMT):
cool, ill push it out now

greg.haskins (Fri, 19 Jan 2018 02:49:07 GMT):
done

greg.haskins (Fri, 19 Jan 2018 02:49:57 GMT):
https://github.com/hyperledger/fabric-baseimage/releases/tag/v0.4.4

rameshthoomu (Fri, 19 Jan 2018 20:47:20 GMT):
baseimage & thirdparty images have been pushed with tag 0.4.4

Brucepark (Sat, 20 Jan 2018 06:16:09 GMT):
Has joined the channel.

dave.enyeart (Sat, 20 Jan 2018 07:55:03 GMT):
Thanks @rameshthoomu !

dave.enyeart (Sat, 20 Jan 2018 07:55:23 GMT):
I assume the next step is to make fabric use 0.4.4... I see https://gerrit.hyperledger.org/r/#/c/17001/

dave.enyeart (Sat, 20 Jan 2018 07:55:32 GMT):
I assume that is required before alpha

dave.enyeart (Sat, 20 Jan 2018 07:55:49 GMT):
Can you explain the current failure and next steps?

mastersingh24 (Sat, 20 Jan 2018 10:04:47 GMT):
@dave.enyeart - one of those is the backport to the release branch. We have just not pushed any patch releases for the Node SDK in a few cycles (https://chat.hyperledger.org/channel/fabric-release?msg=CSppcTH6FcaFZMJFj)

rameshthoomu (Sat, 20 Jan 2018 15:39:36 GMT):
@dave.enyeart issue is with kafka version 0.9.0.1.. I think next steps are release one more version with kafka version 0.10.2.0.. Issues has been created for this and see Jason comments https://jira.hyperledger.org/browse/FAB-7825

dave.enyeart (Sat, 20 Jan 2018 16:16:15 GMT):
Thanks @rameshthoomu . Are you driving that? Or we need to work chris/greg?

rameshthoomu (Sat, 20 Jan 2018 16:56:04 GMT):
testing e2e, node sdk and chaincode jobs in sandbox with kafka version 0.10.2.0 and once all tests are passed will submit patch in baseimage

rameshthoomu (Sat, 20 Jan 2018 16:56:04 GMT):
testing e2e, node sdk and node chaincode jobs in sandbox with kafka version 0.10.2.0 and once all tests are passed will submit patch in baseimage

scottz (Mon, 22 Jan 2018 02:33:56 GMT):
@rameshthoomu And then that will be picked up automatically by all the UT and the fabric-test daily jobs, which we will monitor closely. And we will need to make sure everyone gets the newer baseimage for future testing.

rameshthoomu (Mon, 22 Jan 2018 13:19:11 GMT):
yes @scottz once this patch (https://gerrit.hyperledger.org/r/#/c/17041/) is merged, will request to create a release tag 0.4.5 and then update this patch https://gerrit.hyperledger.org/r/#/c/17001/

dave.enyeart (Mon, 22 Jan 2018 17:08:40 GMT):
@rameshthoomu did you see kosta's request to bump kafka to 0.10.2.1? Do you want to make that change before releasing 0.4.5?

dave.enyeart (Mon, 22 Jan 2018 17:08:40 GMT):
@rameshthoomu did you see @kostas request to bump kafka to 0.10.2.1? Do you want to make that change before releasing 0.4.5?

rameshthoomu (Mon, 22 Jan 2018 17:24:35 GMT):
yes.. I have pushed this change to my personal dockerhub account and testing this change in sandbox.. (rameshthoomu/fabric-kafka:x86_64-0.4.5) https://jenkins.hyperledger.org/sandbox/

rameshthoomu (Mon, 22 Jan 2018 23:17:22 GMT):
Submitted Release CR's ( bump release tag to 0.4.5) https://gerrit.hyperledger.org/r/#/c/17079/ https://gerrit.hyperledger.org/r/#/c/17081/

rameshthoomu (Tue, 23 Jan 2018 16:33:20 GMT):
@dave.enyeart @greg.haskins @cbf : Could you please create 0.4.5 release tag in fabric-baseimage..

greg.haskins (Tue, 23 Jan 2018 16:46:18 GMT):
@rameshthoomu i can queue that

greg.haskins (Tue, 23 Jan 2018 16:46:24 GMT):
based on HEAD I presume?

greg.haskins (Tue, 23 Jan 2018 16:46:32 GMT):
and is there a JIRA?

greg.haskins (Tue, 23 Jan 2018 16:47:00 GMT):
oh, i see, already have the CRs

greg.haskins (Tue, 23 Jan 2018 16:47:03 GMT):
ill push the tag

greg.haskins (Tue, 23 Jan 2018 16:48:47 GMT):
https://github.com/hyperledger/fabric-baseimage/releases/tag/v0.4.5

harsha (Wed, 24 Jan 2018 01:44:44 GMT):
@rameshthoomu Looks like 0.4.5 for p isn't published.

rameshthoomu (Wed, 24 Jan 2018 01:50:48 GMT):
Build timeout caused that. Will re trigger

harsha (Wed, 24 Jan 2018 02:33:26 GMT):
I see the image is published now, Thank you 11

rickr (Thu, 25 Jan 2018 16:20:58 GMT):
@rameshthoomu @mastersingh24 Getting the JSDK ready for v1.1 alpha setting docker-compose-yaml to pull the right images from docker-hub I assume they'll be tagged with : hyperledger/fabric-ca:x86_64-1.1.0-alpha hyperledger/fabric:x86_64-1.1.0-alpha

rameshthoomu (Thu, 25 Jan 2018 16:24:10 GMT):
yes @rickr

george.skrbic (Thu, 25 Jan 2018 21:02:04 GMT):
Has joined the channel.

dave.enyeart (Thu, 25 Jan 2018 21:02:19 GMT):
Alpha release update - Need to close out the bootstrap.sh discussion. I think what @rameshthoomu has in https://gerrit.hyperledger.org/r/#/c/17181/ is workable for alpha, but will likely need to change post-alpha. - Upgrade doc will be pushed soon from @joe-alewine . TLS doc is hopeful for later this afternoon, but we won’t necessarily wait for it. - @wlahti has just pushed a couple edits to the event example readme https://gerrit.hyperledger.org/r/#/c/16919/ . Please review/merge. - Besides the above, we are in MERGE FREEZE for Fabric. - A couple final SDK CRs coming in tonight. - Can likely start cutting Fabric alpha tonight, and then finish out SDKs tomorrow.

dave.enyeart (Fri, 26 Jan 2018 13:26:23 GMT):
The above tasks are under control now. We are ready to cut alpha 1.1 today.

cbf (Fri, 26 Jan 2018 15:35:30 GMT):
release cutting is commencing - please DO NOT MERGE anything but release CRs

dave.enyeart (Sat, 27 Jan 2018 01:43:02 GMT):
@here Hyperledger Fabric v1.1.0-alpha is now available! See the mailing list announcement for all the details: https://lists.hyperledger.org/pipermail/hyperledger-fabric/2018-January/002732.html

cbf (Sat, 27 Jan 2018 12:58:22 GMT):
https://jira.hyperledger.org/browse/FAB-7780?focusedCommentId=39220&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-39220 feel free to pile on

knagware9 (Sat, 27 Jan 2018 13:52:46 GMT):
Hi,,when the fabric 1.1 is coming and what additional features will be in it..??

dave.enyeart (Sat, 27 Jan 2018 14:28:00 GMT):
@knagware9 Please see the release announcement above for feature detals. "The alpha release includes all features and APIs that will be released with 1.1. ... Hyperledger Fabric 1.1 will become Generally Available once the exit criteria is achieved (test coverage, defect arrivals, etc)." Typically this takes a couple months, but may be quicker depending on community assistance and findings.

dave.enyeart (Sat, 27 Jan 2018 14:28:00 GMT):
@knagware9 Please see the release announcement above for feature details. "The alpha release includes all features and APIs that will be released with 1.1. ... Hyperledger Fabric 1.1 will become Generally Available once the exit criteria is achieved (test coverage, defect arrivals, etc)." Typically this takes a couple months, but may be quicker depending on community assistance and findings.

knagware9 (Sat, 27 Jan 2018 14:28:51 GMT):
@dave.enyeart Thank you :)

Dan (Sun, 28 Jan 2018 19:33:20 GMT):
Has left the channel.

nhrishi (Tue, 30 Jan 2018 12:33:58 GMT):
@dave.enyeart I'm looking forward to SideDB -Private Data channel enhancement. Would like to know which release its planned for.

dave.enyeart (Tue, 30 Jan 2018 12:38:36 GMT):
@nhrishi Private channel data is an experimental feature in 1.1 and is targeted for 1.2 as a production feature. There will be an announcement about experimental features, but in a nutshell you can enable them by building Fabric with environment variable EXPERIMENTAL=true.

nhrishi (Tue, 30 Jan 2018 12:40:19 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-release?msg=487s4Jh8hiroR8GCX) @dave.enyeart Ok sure. That's great. Would really like to experiment it.

dave.enyeart (Tue, 30 Jan 2018 12:41:29 GMT):
It is there already as experimental feature. For details see the charts at https://jira.hyperledger.org/browse/FAB-1151 and see the example at https://gerrit.hyperledger.org/r/#/c/14769/

nhrishi (Tue, 30 Jan 2018 13:22:23 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-release?msg=4LNSrkpbk387r42en) @dave.enyeart Great Thanks!

nhrishi (Tue, 30 Jan 2018 13:24:51 GMT):
Hi, We're trying to download fabric-1.1.0-preview binaries from this location (https://nexus.hyperledger.org/content/repositories/releases/org/hyperledger/fabric/hyperledger-fabric/linux-amd64-1.1.0-preview/hyperledger-fabric-linux-amd64-1.1.0-preview.tar.gz) However, these binaries are with version 1.0.5. Can you pls advise. Thanks. ```configtxgen --version configtxgen: Version: 1.0.5 Go version: go1.7.5 OS/Arch: linux/amd64 ```

rameshthoomu (Tue, 30 Jan 2018 16:06:11 GMT):
@nhrishi I see the correct version in 1.1.0-preview configtxgen binary.. see the below ``` ubuntu@ubuntu-xenial:~$ tar -xvf hyperledger-fabric-linux-amd64-1.1.0-preview.tar.gz bin/ bin/orderer bin/configtxgen bin/get-docker-images.sh bin/peer bin/configtxlator bin/cryptogen ubuntu@ubuntu-xenial:~$ clear ubuntu@ubuntu-xenial:~$ cd bin/ ubuntu@ubuntu-xenial:~/bin$ ./configtxgen -version configtxgen: Version: 1.1.0-preview Go version: go1.9 OS/Arch: linux/amd64 ubuntu@ubuntu-xenial:~/bin$ ```

Roger (Wed, 31 Jan 2018 05:45:37 GMT):
Has joined the channel.

nhrishi (Wed, 31 Jan 2018 07:22:56 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-release?msg=Z9CSJteGzS4KziMX6) @rameshthoomu Thanks. Sorry my bad. I got it now.

NagatoPeinI1 (Wed, 31 Jan 2018 09:59:06 GMT):
Has joined the channel.

NagatoPeinI1 (Wed, 31 Jan 2018 10:01:12 GMT):
I'm trying to add new organization (org4) with 2 peers in a channel of 3 organizations (org1, org2 and org3 respectively) having 2 peers each. While doing that using configtxlator tool in docker cli container I'm getting this error while getting signature from 3rd organization (org3): Error: got unexpected status: BAD_REQUEST -- Error authorizing update: Error validating ReadSet: Readset expected key [Groups] /Channel/Application at version 1, but got version 2

NagatoPeinI1 (Wed, 31 Jan 2018 10:02:00 GMT):
and after that wheni'm trying to add one more organization it is giving this error: Error: got unexpected status: BAD_REQUEST -- Error authorizing update: Error validating DeltaSet: Policy for [Groups] /Channel/Application not satisfied: Failed to reach implicit threshold of 3 sub-policies, required 1 remaining

dave.enyeart (Wed, 31 Jan 2018 12:20:46 GMT):
@NagatoPeinI1 Please reserve this channel for release information. I've copied your question into #fabric-orderer where the folks that maintain this tool and config hang out.

guoger (Fri, 02 Feb 2018 05:25:48 GMT):
@odowdaibm I think Doc WG meeting A should be *1400 China Standard Time*, instead of *1300* in the mail you sent out...

guoger (Fri, 02 Feb 2018 05:27:10 GMT):
I couldn't participate in the meeting today due to conflict, but I do have a few questions regarding v1.1 docs, as we (TWG China) are getting prepared to translate them once it's stable.

guoger (Fri, 02 Feb 2018 05:28:14 GMT):
So could you also publish the WebEx call-in number and meeting code? I'll join the meeting B later today.

gen_el (Fri, 02 Feb 2018 09:34:58 GMT):
Has joined the channel.

Sahas 2 (Fri, 02 Feb 2018 13:47:53 GMT):
Has joined the channel.

wlahti (Mon, 05 Feb 2018 17:16:18 GMT):
Is anyone aware of any issues with the hosting site for the platform specific binaries for 1.1-alpha? http://hyperledger-fabric.readthedocs.io/en/v1.1.0-alpha/samples.html#download-platform-specific-binaries . When I attempt the `curl` command it just sits and never seems to download.

wlahti (Mon, 05 Feb 2018 17:25:12 GMT):
I'm able to download the 1.1.0-preview binaries but not the 1.1.0-alpha binaries

rameshthoomu (Mon, 05 Feb 2018 17:28:18 GMT):
I see the binaries are available for 1.1.0-alpha.. but it's taking time to download..

rameshthoomu (Mon, 05 Feb 2018 17:28:28 GMT):
https://nexus.hyperledger.org/content/repositories/releases/org/hyperledger/fabric/hyperledger-fabric/linux-amd64-1.1.0-alpha/

wlahti (Mon, 05 Feb 2018 17:28:54 GMT):
modifying the command to search for `v1.1.0-alpha` instead of `1.1.0-alpha` seems to work

wlahti (Mon, 05 Feb 2018 17:28:54 GMT):
modifying the command in the documentation to search for `v1.1.0-alpha` instead of `1.1.0-alpha` seems to work: `curl -sSL https://goo.gl/6wtTN5 | bash -s v1.1.0-alpha` instead of `curl -sSL https://goo.gl/6wtTN5 | bash -s 1.1.0-alpha`

rameshthoomu (Mon, 05 Feb 2018 17:31:41 GMT):
@wlahti I don't see any version with v1.1.0-alpha.. Could be network issue

rameshthoomu (Mon, 05 Feb 2018 17:32:36 GMT):
I just tried, failed at first attempt but 2nd attempt worked

wlahti (Mon, 05 Feb 2018 17:33:01 GMT):
not sure what happened but the command is working with 1.1.0-alpha again. odd.

rameshthoomu (Mon, 05 Feb 2018 17:33:42 GMT):
Could be network issue.. It didn't work for me too..

wlahti (Mon, 05 Feb 2018 17:34:07 GMT):
good enough for now. I'll keep my eyes out for anything else unusual. :)

wlahti (Mon, 05 Feb 2018 17:34:25 GMT):
thanks for taking a look, @rameshthoomu

lbniuqlm (Wed, 07 Feb 2018 06:52:41 GMT):
Has joined the channel.

inatatsu (Wed, 07 Feb 2018 09:12:32 GMT):
Has joined the channel.

inatatsu (Wed, 07 Feb 2018 09:12:41 GMT):
Can zookeeper and kafka images be also tagged with v1.1.0-alpha for orthogonal naming?

inatatsu (Wed, 07 Feb 2018 09:12:41 GMT):
Can zookeeper and kafka images on DockerHub be also tagged with `v1.1.0-alpha` for orthogonal naming?

dave.enyeart (Wed, 07 Feb 2018 15:41:52 GMT):
A few updates to share on the release: - Release 1.1 is on target for Q1. - We do not expect a 1.1 beta is required, as no significant updates since 1.1 alpha have been needed. - We will proceed to 1.1 release candidate, once quality objectives are met. - As such, I encourage everybody to try out v1.1.0-alpha and provide any feedback, either via this mailing list, JIRA ( https://jira.hyperledger.org/ ) or RocketChat ( https://chat.hyperledger.org/ ). - The intent is to release quarterly going forward. - Proposed themes for upcoming releases will be posted for community discussion. Stay tuned for details.

dave.enyeart (Wed, 07 Feb 2018 15:42:02 GMT):
v1.1.0 alpha and updated samples can be found here: http://hyperledger-fabric.readthedocs.io/en/master/samples.html .

yacovm (Wed, 07 Feb 2018 16:54:37 GMT):
@dave.enyeart @joe-alewine do we have documentation that is related for deployment? Some random stackoverflow user that uses docker-swarm upgraded to v1.1 and his chaincode no longer instantiates because he needed to put: CORE_PEER_CHAINCODEADDRESS=peer0.org1.example.com:7052 CORE_PEER_CHAINCODELISTENADDRESS=0.0.0.0:7052 because of docker-swarm ip address resolution confuses the peer address detection logic in case of several interfaces. Is there a place in the documentation that we can write such stuff so people could (hopefully) read and not make these innocent but frustrating mis-configurations ?

joe-alewine (Wed, 07 Feb 2018 17:03:17 GMT):
@yacovm @dave.enyeart Forgive my ignorance here but is this a shim issue? Because that's part of the upgrade/update documentation

yacovm (Wed, 07 Feb 2018 17:03:30 GMT):
this is not an "issue"

yacovm (Wed, 07 Feb 2018 17:04:02 GMT):
it's just that for v1.1, the chaincode server has more configuration combinations

yacovm (Wed, 07 Feb 2018 17:04:02 GMT):
it's just that for v1.1, the chaincode server has more configuration combinations (I think, because it worked in v1.0 for that user)

yacovm (Wed, 07 Feb 2018 17:04:06 GMT):
than in v1.0

yacovm (Wed, 07 Feb 2018 17:04:53 GMT):
I just want that "tip" to be written somewhere :(

yacovm (Wed, 07 Feb 2018 17:09:23 GMT):
for example, things like this https://stackoverflow.com/questions/48657671/hyperledger-fabric-not-working-with-docker-swarm Is there a place to write how to configure the docker-compose file to someone that is brave enough to deploy a chaincode on his own and doesn't use our samples?

yacovm (Wed, 07 Feb 2018 18:20:15 GMT):
@joe-alewine @nickgaski ^

dave.enyeart (Wed, 07 Feb 2018 21:22:10 GMT):
@joe-alewine let's reserve this channel for release discussions. #fabric or #fabric-documentation seems like a better place for this discussion.

dave.enyeart (Wed, 07 Feb 2018 21:22:26 GMT):
@yacovm if you have a specific tip to recommend, could you open a Jira item for that? And then I will help @joe-alewine find the correct place in documentation.

yacovm (Wed, 07 Feb 2018 21:38:56 GMT):
FAB-8125

Glen (Thu, 08 Feb 2018 00:57:44 GMT):
Has joined the channel.

yash-ibm (Thu, 08 Feb 2018 06:34:06 GMT):
Has joined the channel.

dpadev (Thu, 08 Feb 2018 17:00:51 GMT):
Has joined the channel.

rameshthoomu (Mon, 12 Feb 2018 20:08:20 GMT):
@dave.enyeart FAB-8224 FAB-8225

rameshthoomu (Mon, 12 Feb 2018 20:09:02 GMT):
FYI next baseimage update has to go with these changes.

rameshthoomu (Mon, 12 Feb 2018 20:09:02 GMT):
FYI next baseimage update has to go with these changes as well

sheehan (Tue, 13 Feb 2018 23:25:02 GMT):
Is there an existing 1.2 dashboard in Jira?

dave.enyeart (Wed, 14 Feb 2018 01:52:28 GMT):
I know @mastersingh24 was working on that

dave.enyeart (Wed, 14 Feb 2018 10:50:59 GMT):
@rameshthoomu Jira to release baseimage 0.4.6: https://jira.hyperledger.org/browse/FAB-8266

dave.enyeart (Wed, 14 Feb 2018 10:51:34 GMT):
That will update kafka to 1.0.0, along with some other minor updates.

dave.enyeart (Wed, 14 Feb 2018 10:51:34 GMT):
That will update kafka to 1.0.0, along with some other minor updates mentioned in the Jira

dave.enyeart (Wed, 14 Feb 2018 10:53:04 GMT):
baseimage 0.4.6 will be used for v1.1.0-rc1

KGiou (Thu, 15 Feb 2018 10:43:45 GMT):
Has joined the channel.

Ryan2 (Fri, 16 Feb 2018 07:21:08 GMT):
Has joined the channel.

rickr (Fri, 16 Feb 2018 13:32:35 GMT):
Would it be possible to tag in Docker a release alias that always is updated to the latest in the release, be it alpha, rc1, rc2, v1.1.0 etc v1.1.1 something like v1.1-latest ? SDKs and anyone that just wants the latest in 1.1 release stream could use that.

rickr (Fri, 16 Feb 2018 13:32:35 GMT):
Would it be possible to tag in Docker hub a release alias that always is updated to the latest in the release, be it alpha, rc1, rc2, v1.1.0 etc v1.1.1 something like v1.1-latest ? SDKs and anyone that just wants the latest in 1.1 release stream could use that.

dave.enyeart (Fri, 16 Feb 2018 14:45:40 GMT):
To get baseimage 0.4.6 moving which will include kafka 1.0.0, we need +2s on these: https://gerrit.hyperledger.org/r/#/c/17905 https://gerrit.hyperledger.org/r/#/c/17907 @cbf @greg.haskins

dave.enyeart (Fri, 16 Feb 2018 15:09:10 GMT):
Ok, the former is merged. The latter has merge conflict. @rameshthoomu I thought we typically did those CRs on top of each other to ensure the dependency order. Anyways, I think we prefer to tag the branch prior to merging the 'prepare for next' CR.

dave.enyeart (Fri, 16 Feb 2018 15:10:06 GMT):
@greg.haskins I believe you have been our baseimage tagger, I think you can go ahead (although I'm not sure if that is out of habit or if there was a reason for that?)

cbf (Fri, 16 Feb 2018 17:19:37 GMT):
sorry, been on calls all am

cbf (Fri, 16 Feb 2018 17:20:07 GMT):
Greg usually tags, but that is mainly historical since he was the driving force behind the baseimage

rameshthoomu (Sat, 17 Feb 2018 00:51:03 GMT):
@dave.enyeart fabric-baseimage 0.4.6 is released https://hub.docker.com/r/hyperledger/fabric-baseimage/tags/

rameshthoomu (Sat, 17 Feb 2018 00:51:03 GMT):
fabric-baseimage 0.4.6 version is released https://hub.docker.com/r/hyperledger/fabric-baseimage/tags/

rameshthoomu (Sat, 17 Feb 2018 00:51:03 GMT):
fabric-baseimage & thirdparty images are released with version 0.4.6 https://hub.docker.com/r/hyperledger/fabric-baseimage/tags/

dave.enyeart (Sat, 17 Feb 2018 00:53:06 GMT):
@rameshthoomu thanks. Do you want to proceed with the component CRs to start using 0.4.6?

rameshthoomu (Sat, 17 Feb 2018 00:58:13 GMT):
yes sure..

nhrishi (Sun, 18 Feb 2018 05:42:16 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-release?msg=487s4Jh8hiroR8GCX) @dave.enyeart Hi Dave, sorry this might not be the right channel to post this question/issues. I'm tried to compile v1.1.0-alpha code with experimental features in Ubuntu Box. However, i'm getting below error for a peer - ```build/bin/peer CGO_CFLAGS=" " GOBIN=/usr/local/go/src/github.com/hyperledger/fabric/build/bin go install -tags "" -ldflags "-X github.com/hyperledger/fabric/common/metadata.Version=1.1.0-preview -X github.com/hyperledger/fabric/common/metadata.BaseVersion=0.4.2 -X github.com/hyperledger/fabric/common/metadata.BaseDockerLabel=org.hyperledger.fabric -X github.com/hyperledger/fabric/common/metadata.DockerNamespace=hyperledger -X github.com/hyperledger/fabric/common/metadata.BaseDockerNamespace=hyperledger -X github.com/hyperledger/fabric/common/metadata.Experimental=false" github.com/hyperledger/fabric/peer import cycle not allowed package github.com/hyperledger/fabric/peer imports fmt imports errors imports runtime imports runtime/internal/atomic imports unsafe imports runtime import cycle not allowed package github.com/hyperledger/fabric/peer imports github.com/hyperledger/fabric/common/flogging imports github.com/op/go-logging imports log/syslog imports net imports runtime/cgo imports runtime/cgo Makefile:233: recipe for target 'build/bin/peer' failed make: *** [build/bin/peer] Error 1 ```.

dave.enyeart (Sun, 18 Feb 2018 15:10:50 GMT):
@nhrishi First of all it looks like your Experimental is false. You need to set env variable EXPERIMENTAL=true. That is the default in the Fabric Makefile. I've tried master with and without experimental, and I get no import cycles. Please try with latest master.

mastersingh24 (Sun, 18 Feb 2018 16:55:22 GMT):
Fabric and Fabric CA v1.0.6 Releases: https://gerrit.hyperledger.org/r/#/q/status:open+branch:release+topic:release-1.0.6

rickr (Sun, 18 Feb 2018 17:40:31 GMT):
Just making sure not missed something. From the SDKs /API perspective there's nothing that really changes if v1.1 capabilities are turned on or not from what I've seen.

niteshsolanki (Mon, 19 Feb 2018 04:13:44 GMT):
Has joined the channel.

nhrishi (Mon, 19 Feb 2018 10:54:01 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-release?msg=tZdipuE5rsz9FmbC4) @dave.enyeart Okay, I did set the env variable in the Makefile. Will try to pull latest master and try it again. Thanks much.

nhrishi (Mon, 19 Feb 2018 10:54:01 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-release?msg=tZdipuE5rsz9FmbC4) @dave.enyeart Okay, I think last compilation somehow i missed setting the env variable in the Makefile. But I got an error with true value as well. Will try to pull latest master and try it again. Thanks much.

nhrishi (Mon, 19 Feb 2018 10:54:01 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-release?msg=tZdipuE5rsz9FmbC4) @dave.enyeart Okay, I think, during last compilation, somehow i missed setting the env variable in the Makefile. But I got an error with true value as well. Will try to pull latest master and try it again. Thanks much.

b39647 (Mon, 19 Feb 2018 20:13:52 GMT):
Has joined the channel.

mastersingh24 (Tue, 20 Feb 2018 00:01:12 GMT):
Hyperledger Fabric and Fabric CA v1.0.6 are now available!

nhrishi (Wed, 21 Feb 2018 09:39:19 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-release?msg=tZdipuE5rsz9FmbC4) @dave.enyeart I tried again, not sure what am I missing, here are details and steps - ```# OS VERSION ----------------------------- ubuntu@ip-$ uname -a Linux ip-172-31-25-43 4.4.0-1050-aws #59-Ubuntu SMP Tue Jan 30 19:57:10 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux # GO VERSION ----------------------------- ubuntu@ip-$ go version go version go1.9.3 linux/amd64 # DOCKER VERSION ------------------------- ubuntu@ip-$ docker version Client: Version: 17.06.0-ce API version: 1.30 Go version: go1.8.3 Git commit: 02c1d87 Built: Fri Jun 23 21:23:31 2017 OS/Arch: linux/amd64 Server: Version: 17.06.0-ce API version: 1.30 (minimum version 1.12) Go version: go1.8.3 Git commit: 02c1d87 Built: Fri Jun 23 21:19:04 2017 OS/Arch: linux/amd64 Experimental: false # GIT CLONE ------------------------- git clone https://github.com/hyperledger/fabric.git --branch master --single-branch # MAKE ------------------------- make dist-clean all # LOG ----------------------- CGO_CFLAGS=" " GOBIN=/usr/local/go/src/github.com/hyperledger/fabric/build/bin go install -tags "experimental" -ldflags "-X github.com/hyperledger/fabric/common/metadata.Version=1.1.0-beta-snapshot-eeafa9f -X github.com/hyperledger/fabric/common/metadata.BaseVersion=0.4.6 -X github.com/hyperledger/fabric/common/metadata.BaseDockerLabel=org.hyperledger.fabric -X github.com/hyperledger/fabric/common/metadata.DockerNamespace=hyperledger -X github.com/hyperledger/fabric/common/metadata.BaseDockerNamespace=hyperledger -X github.com/hyperledger/fabric/common/metadata.Experimental=true" github.com/hyperledger/fabric/peer import cycle not allowed package github.com/hyperledger/fabric/peer imports fmt imports errors imports runtime imports runtime/internal/atomic imports unsafe imports runtime import cycle not allowed package github.com/hyperledger/fabric/peer imports github.com/hyperledger/fabric/common/flogging imports github.com/op/go-logging imports log/syslog imports net imports runtime/cgo imports runtime/cgo Makefile:258: recipe for target 'build/bin/peer' failed make: *** [build/bin/peer] Error 1 ```

nycycr (Thu, 22 Feb 2018 21:05:01 GMT):
Has joined the channel.

rameshthoomu (Fri, 23 Feb 2018 19:36:43 GMT):
@mastersingh24 could you please comment on FAB-8483

dave.enyeart (Sun, 25 Feb 2018 13:03:33 GMT):
@rameshthoomu @mastersingh24 I agree to update to 1.9.2 across the board, to match the baseimage version 1.9.2.

dave.enyeart (Thu, 01 Mar 2018 17:16:28 GMT):
Starting release process for v1.1.0-rc1.

cbf (Thu, 01 Mar 2018 19:16:36 GMT):
@rameshthoomu @dave.enyeart fabric-ca failing:

cbf (Thu, 01 Mar 2018 19:16:37 GMT):
00:02:40.745 Makefile:137: recipe for target 'build/image/fabric-ca-orderer/.dummy-s390x-1.1.0-rc1' failed 00:02:40.745 make: *** [build/image/fabric-ca-orderer/.dummy-s390x-1.1.0-rc1] Error 1

cbf (Thu, 01 Mar 2018 19:17:45 GMT):
same for x86

cbf (Thu, 01 Mar 2018 19:18:21 GMT):
looks like it is depending on finding a fabric-orderer image with the 1.1.0-rc1 tag?

dave.enyeart (Thu, 01 Mar 2018 19:20:00 GMT):
yes, we found that last time, fabric has to be published before fabric-ca can verify. @mastersingh24 dug in and found the reason, and thinks we could remove that dependency in the future (but not right now)

dave.enyeart (Thu, 01 Mar 2018 19:20:00 GMT):
yes, we found that last time, fabric has to be published to dockerhub before fabric-ca can verify. @mastersingh24 dug in and found the reason, and thinks we could remove that dependency in the future (but not right now)

cbf (Thu, 01 Mar 2018 19:26:25 GMT):
we need to fix this

cbf (Thu, 01 Mar 2018 19:26:38 GMT):
as far as I am concerned, this is fundamentally broken

dave.enyeart (Thu, 01 Mar 2018 19:51:57 GMT):
@cbf @rameshthoomu fabric v1.1.0-rc1 tagged

dave.enyeart (Thu, 01 Mar 2018 20:38:13 GMT):
Fabric v1.1.0-rc1 binaries and images are published

dave.enyeart (Thu, 01 Mar 2018 20:38:36 GMT):
The readthedocs is not yet updates, but you can download with this command:

dave.enyeart (Thu, 01 Mar 2018 20:38:36 GMT):
The readthedocs is not yet updated, but you can download with this command:

dave.enyeart (Thu, 01 Mar 2018 20:38:42 GMT):
`curl -sSL https://goo.gl/6wtTN5 | bash -s 1.1.0-rc1`

dave.enyeart (Thu, 01 Mar 2018 20:39:42 GMT):
Fabric CA is build and will be pushed next

dave.enyeart (Thu, 01 Mar 2018 20:39:42 GMT):
Fabric CA is built and will be pushed next

dave.enyeart (Thu, 01 Mar 2018 20:39:42 GMT):
Fabric CA is built and will be published next

dave.enyeart (Thu, 01 Mar 2018 20:39:42 GMT):
Fabric CA is building and will be published next

rameshthoomu (Thu, 01 Mar 2018 20:41:08 GMT):
doc update will take some time.. having some trouble in building docs in RTD. `Whoa! The build queue is 477 tasks long, new builds may take a while. `

cbf (Thu, 01 Mar 2018 20:44:15 GMT):
lol

dave.enyeart (Thu, 01 Mar 2018 21:10:47 GMT):
master docs are published for v1.1.0-rc1 instructions:

dave.enyeart (Thu, 01 Mar 2018 21:10:48 GMT):
http://hyperledger-fabric.readthedocs.io/en/master/samples.html#download-platform-specific-binaries

cbf (Thu, 01 Mar 2018 21:11:01 GMT):
fabric, fabric-ca and fabric-samples tagged and bagged

dave.enyeart (Thu, 01 Mar 2018 21:11:21 GMT):
Fabric CA available on dockerhub

cbf (Thu, 01 Mar 2018 21:11:29 GMT):
please test a bit and we'll get the note prepared

Ratnakar (Thu, 01 Mar 2018 21:20:14 GMT):
Tested the following samples on `1.1.0-rc1` and all works well :) - *first-network* with several combinations (node.js chiancode, couchdb , couchdb indexing, custom channel name etc.,) Also Update (*eyfn*) and upgrades using *upgrading tutorial* - *fabcar* - *balance-transfer*

Ratnakar (Thu, 01 Mar 2018 21:20:14 GMT):
Tested the following samples on `1.1.0-rc1` and all works well :) - *first-network* with several combinations (node.js chiancode, couchdb , couchdb indexing, custom channel name etc.,) Also Update ( *eyfn* ) and upgrades using *upgrading tutorial* - *fabcar* - *balance-transfer*

Asara (Thu, 01 Mar 2018 21:21:01 GMT):
Is there an upgrade path available for 1.0.X -> 1.1?

dave.enyeart (Thu, 01 Mar 2018 21:21:16 GMT):
http://hyperledger-fabric.readthedocs.io/en/master/upgrade_to_one_point_one.html

Asara (Thu, 01 Mar 2018 21:28:22 GMT):
Thanks @dave.enyeart

rohitadivi (Thu, 01 Mar 2018 22:20:45 GMT):
Has joined the channel.

rohitadivi (Thu, 01 Mar 2018 22:25:18 GMT):
Tested the following samples on `1.1.0-rc1` - *first-network* and adding an org to a channel (*eyfn*) - Upgrading from v1.0.x All of them are working well :)

dave.enyeart (Thu, 01 Mar 2018 23:46:40 GMT):
@here

dave.enyeart (Thu, 01 Mar 2018 23:46:41 GMT):
-------------------------------------------------------------------------------------- ANNOUNCING HYPERLEDGER FABRIC V1.1 - RELEASE CANDIDATE 1 https://lists.hyperledger.org/pipermail/hyperledger-fabric/2018-March/002934.html --------------------------------------------------------------------------------------

bjwswang (Fri, 02 Mar 2018 05:45:44 GMT):
Has joined the channel.

sstone1 (Fri, 02 Mar 2018 10:59:48 GMT):
@dave.enyeart why is there no published Node.js SDK for RC1? looks like there's a bunch of changes that have got in since the alpha... seems like it would be sensible to validate those before publishing the GA? https://github.com/hyperledger/fabric-sdk-node/compare/v1.1.0-alpha...master

sstone1 (Fri, 02 Mar 2018 11:02:46 GMT):
there's also no published Node.js chaincode for RC1? again, more changes that should get validated: https://github.com/hyperledger/fabric-chaincode-node/compare/v1.1.0-alpha...master

nkl199 (Fri, 02 Mar 2018 11:48:32 GMT):
Has joined the channel.

cbf (Fri, 02 Mar 2018 13:37:45 GMT):
@sstone1 everything is oriented to pulling latest from NPM etc so you will get the latest stable images

cbf (Fri, 02 Mar 2018 13:37:55 GMT):
or modules as the case may be

sstone1 (Fri, 02 Mar 2018 13:39:11 GMT):
not sure i follow - for `fabric-client`, the tags are: `'dist-tags': { latest: '1.0.4', unstable: '1.1.0-snapshot.83' }` how do i target my node.js app to use the RC1 version of the `fabric-client` package?

sstone1 (Fri, 02 Mar 2018 13:42:27 GMT):
we want to update composer to use RC1 but at the moment we can only pull in the RC1 docker images for the peer/orderer/etc, we cannot get hold of the RC1 fabric-client or fabric-shim modules from npm so it's a weird mix of RC1 and alpha code

dave.enyeart (Fri, 02 Mar 2018 13:42:57 GMT):
`unstable` has the latest fixes since alpha

sstone1 (Fri, 02 Mar 2018 13:43:32 GMT):
why can't we have a nice rc1 tag?

dave.enyeart (Fri, 02 Mar 2018 13:43:52 GMT):
some node projects do tags like that, some don't

dave.enyeart (Fri, 02 Mar 2018 13:44:28 GMT):
the samples all use `unstable` to get the latest

dave.enyeart (Fri, 02 Mar 2018 13:45:33 GMT):
for the sdks, there were some known fixes coming, so there isnt really a release candidate yet

sstone1 (Fri, 02 Mar 2018 13:45:55 GMT):
it's what you guys did for 1.0.0 ;)

sstone1 (Fri, 02 Mar 2018 13:46:00 GMT):
okay, maybe we should just hold out for those fixes

dave.enyeart (Fri, 02 Mar 2018 13:46:47 GMT):
please do tests with `unstable` lots of improvements since alpha

sstone1 (Fri, 02 Mar 2018 13:49:04 GMT):
will do!

cbf (Fri, 02 Mar 2018 14:25:36 GMT):
FWIW, I retagged the fabric-samples to pull in Keith's fix

cbf (Fri, 02 Mar 2018 14:26:42 GMT):
https://gerrit.hyperledger.org/r/c/18673/

rameshthoomu (Fri, 02 Mar 2018 14:44:59 GMT):
@sstone1 rc1 fabric-ca-client binary is available here https://nexus.hyperledger.org/content/repositories/releases/org/hyperledger/fabric-ca/hyperledger-fabric-ca/ use below commands to get the rc1 fabric-ca-client binary ``` export ARCH=$(echo "$(uname -s|tr '[:upper:]' '[:lower:]'|sed 's/mingw64_nt.*/windows/')-$(uname -m | sed 's/x86_64/amd64/g')" | awk '{print tolower($0)}') VERSION=1.1.0-rc1 curl https://nexus.hyperledger.org/content/repositories/releases/org/hyperledger/fabric-ca/hyperledger-fabric-ca/${ARCH}-${VERSION}/hyperledger-fabric-ca-${ARCH}-${VERSION}.tar.gz | tar xz ```

sstone1 (Fri, 02 Mar 2018 14:45:23 GMT):
cool, thanks @rameshthoomu !

sstone1 (Sat, 03 Mar 2018 18:16:00 GMT):
@dave.enyeart have picked up and integrated the latest fabric-shim (snapshot.12), fabric-ca-client (snapshot.83), and fabric-client (snapshot.85) - all looking good from a composer point of view :+1:

sstone1 (Sat, 03 Mar 2018 18:16:58 GMT):
had to track down a reproducible SIGSEGV when starting chaincode but it turned out that we had pinned grpc a while back, unpinning it and picking up the latest version fixed the problem... just FYI incase anyone else hits a similar problem

rjones (Tue, 06 Mar 2018 02:16:23 GMT):
Has left the channel.

frankz (Tue, 06 Mar 2018 10:54:36 GMT):
Has joined the channel.

weeds (Tue, 06 Mar 2018 14:54:05 GMT):
nice -thanks Simon

aatkddny (Tue, 06 Mar 2018 16:23:06 GMT):
Has joined the channel.

aatkddny (Tue, 06 Mar 2018 16:24:07 GMT):
Has anyone tested standing up a simple couchdb container instance with RC1?

rjones (Tue, 06 Mar 2018 16:55:02 GMT):
dave.enyeart

rjones (Tue, 06 Mar 2018 16:55:31 GMT):
mastersingh24

rjones (Tue, 06 Mar 2018 16:55:38 GMT):
cbf

rjones (Tue, 06 Mar 2018 16:55:41 GMT):
dave.enyeart

rjones (Tue, 06 Mar 2018 16:59:08 GMT):
Has joined the channel.

rjones (Tue, 06 Mar 2018 17:00:20 GMT):
if you feel you should have moderator permissions (the ability to use at-here, really) please ask a channel _owner_ for it.

rjones (Tue, 06 Mar 2018 17:01:05 GMT):
Has left the channel.

Baha-sk (Wed, 07 Mar 2018 19:17:14 GMT):
Has joined the channel.

Baha-sk (Wed, 07 Mar 2018 19:18:06 GMT):
hi all, any plans to support Go 1.10 in Fabric?

Baha-sk (Wed, 07 Mar 2018 20:30:00 GMT):
with reference to the above question.. the below packages need to be updated in Fabric to support Go 1.10.. name = "github.com/google/certificate-transparency-go" name = "github.com/miekg/pkcs11"

dave.enyeart (Wed, 07 Mar 2018 21:34:07 GMT):
@Baha-sk Yes, see https://jira.hyperledger.org/browse/FAB-8060

Baha-sk (Wed, 07 Mar 2018 21:38:51 GMT):
thanks @dave.enyeart

Baha-sk (Wed, 07 Mar 2018 21:39:20 GMT):
do you know the timeframe for this release?

dave.enyeart (Wed, 07 Mar 2018 21:39:38 GMT):
1.2 is the Q2 release (june timeframe)

dave.enyeart (Wed, 07 Mar 2018 21:39:38 GMT):
1.2 is targeted as Q2 release (june timeframe)

Baha-sk (Wed, 07 Mar 2018 21:40:12 GMT):
ok, not far ahead.. I'll stay posted as we need to update the Go SDK

liuhaifeng (Thu, 08 Mar 2018 05:05:58 GMT):
Has joined the channel.

raphaelbenoit (Thu, 08 Mar 2018 10:59:59 GMT):
Has joined the channel.

kiranarshakota (Thu, 08 Mar 2018 11:45:35 GMT):
Has joined the channel.

kiranarshakota (Thu, 08 Mar 2018 11:47:24 GMT):
When is 1.1 release planned

dave.enyeart (Thu, 08 Mar 2018 11:50:26 GMT):
@kiranarshakota 1.1 release candidate 1 is already out. If no major issues are reported against it, 1.1 will be released within 2 weeks

kiranarshakota (Thu, 08 Mar 2018 11:57:46 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-release?msg=cB4pAjmKRiyzjXpBy) @dave.enyeart Thanks for the information

aatkddny (Thu, 08 Mar 2018 13:52:58 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-release?msg=W7rPRTL5Z7Hb8N563) [ ](https://chat.hyperledger.org/channel/fabric-release?msg=LwMnhKko2dcqyaApZ) [ ](https://chat.hyperledger.org/channel/fabric-release?msg=LwMnhKko2dcqyaApZ) Suggest you recheck the couchdb version. Look at the logs for any of the couchdb instances.

aatkddny (Thu, 08 Mar 2018 13:52:58 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-release?msg=LwMnhKko2dcqyaApZ) Suggest you recheck the couchdb version. Look at the logs for any of the couchdb instances.

aatkddny (Thu, 08 Mar 2018 13:52:58 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-release?msg=nJwTAGC9nPGXsHKit) Suggest you recheck the couchdb version. Look at the logs for any of the couchdb instances.

aatkddny (Thu, 08 Mar 2018 14:11:46 GMT):

Screen Shot 2018-03-08 at 9.04.40 AM.png

Ratnakar (Thu, 08 Mar 2018 14:23:46 GMT):
@aatkddny I had a successful run using couchdb as state DB. I confirmed this by checking the couchdb indexes. hence I don't see a problem. Can you please confirm if you have used the command as following ? (make sure you pass the tag name with *option -i* ) `./byfn.sh -m up -s couchdb -i 1.1.0-rc1`

Ratnakar (Thu, 08 Mar 2018 14:24:03 GMT):

Clipboard - March 8, 2018 9:23 AM

Ratnakar (Thu, 08 Mar 2018 14:24:43 GMT):

Clipboard - March 8, 2018 9:24 AM

Ratnakar (Thu, 08 Mar 2018 14:26:41 GMT):
@aatkddny Also there is an issue, please take a look at this https://jira.hyperledger.org/browse/FAB-8630

aatkddny (Thu, 08 Mar 2018 14:31:17 GMT):
That's a totally different problem. That's composer not waiting until something has finished before firing up a "depends_on" container. This is a new couchdb instance erroring out all over the place.

aatkddny (Thu, 08 Mar 2018 14:35:32 GMT):

Screen Shot 2018-03-08 at 9.34.47 AM.png

Ratnakar (Thu, 08 Mar 2018 14:41:37 GMT):
@aatkddny I don't think this is the right channel, could we take the discussion in #fabric-quality channel

dave.enyeart (Thu, 08 Mar 2018 14:50:47 GMT):
@aatkddny Please open a Jira item so that the issue is tracked: https://jira.hyperledger.org

aatkddny (Thu, 08 Mar 2018 15:06:35 GMT):
need an account to do that. all i get is a contact site administrators panel.

aatkddny (Thu, 08 Mar 2018 15:06:35 GMT):
need an account to do that. all i get is a contact site administrators panel. And when I try to do that I get this: Your JIRA administrator has not yet configured this contact form.

dave.enyeart (Thu, 08 Mar 2018 15:19:30 GMT):
@aatkddny Hyperledger Jira uses the same linux foundation id/pw as this Hyperledger rocket.chat. If you have access to one, you have access to the other.

aatkddny (Thu, 08 Mar 2018 15:43:27 GMT):
Ok I logged a bug. https://jira.hyperledger.org/browse/FAB-8722

dave.enyeart (Thu, 08 Mar 2018 16:03:41 GMT):
thanks @aatkddny added my comments to https://jira.hyperledger.org/browse/FAB-8722

hayato (Fri, 09 Mar 2018 03:34:27 GMT):
Has joined the channel.

zhangguiping (Fri, 09 Mar 2018 06:09:13 GMT):
Has joined the channel.

sstone1 (Fri, 09 Mar 2018 08:43:45 GMT):
@rameshthoomu the fabric-ca-client binary is good for me - how can we get it added to the one line installer? i mean whatever runs when this command is executed: `curl -sSL https://goo.gl/6wtTN5 | bash -s 1.1.0-rc1`

eramitg (Fri, 09 Mar 2018 09:35:59 GMT):
Has joined the channel.

eramitg (Fri, 09 Mar 2018 09:36:04 GMT):
HI

mastersingh24 (Fri, 09 Mar 2018 09:47:05 GMT):
@sstone1 - we are not going to do that (https://chat.hyperledger.org/channel/fabric-release?msg=wDSmB5XtHSy9w2w57)

rameshthoomu (Fri, 09 Mar 2018 13:50:52 GMT):
We can include `curl` command to download fabric-ca-client binary.. Will test and submit patch by EOD today..

sambhavdutt (Fri, 09 Mar 2018 14:03:17 GMT):
Has joined the channel.

dave.enyeart (Fri, 09 Mar 2018 14:05:47 GMT):
@rameshthoomu To clarify, you mean fabric-ca-client would be in the /bin directory of the release binary tar, right?

rameshthoomu (Fri, 09 Mar 2018 14:06:39 GMT):
yes it is..

dave.enyeart (Fri, 09 Mar 2018 14:07:03 GMT):
you mean it was for rc1? or you will make that change for 1.1?

rameshthoomu (Fri, 09 Mar 2018 14:08:43 GMT):
it is in fabric-ca-client binary tar.. but @sstone1 is asking to include that in fabric bootstrap.sh script `curl -sSL https://goo.gl/6wtTN5 | bash -s 1.1.0-rc1`

dave.enyeart (Fri, 09 Mar 2018 14:09:52 GMT):
understood, and the curl script downloads a binaries tar and extracts it. just confirming that's where fabric-ca-client will go

dave.enyeart (Fri, 09 Mar 2018 14:10:39 GMT):
so after the curl command is run, we'll see fabric-ca-client in the /bin directory

rameshthoomu (Fri, 09 Mar 2018 14:14:06 GMT):
let me test this

rameshthoomu (Fri, 09 Mar 2018 14:14:06 GMT):
yes we can see fabric-ca-client in bin dir...```(hyp) rameshs-mbp:bin thoomu@us.ibm.com$ ls configtxgen configtxlator cryptogen fabric-ca-client get-docker-images.sh orderer peer (```

dave.enyeart (Fri, 09 Mar 2018 14:19:35 GMT):
perfect htx

dave.enyeart (Fri, 09 Mar 2018 14:19:35 GMT):
perfect thx

dave.enyeart (Fri, 09 Mar 2018 14:20:03 GMT):
it wasnt there in rc1, so was just confirming.

rameshthoomu (Fri, 09 Mar 2018 14:20:31 GMT):
yes

mrtrantuan (Sat, 10 Mar 2018 02:35:58 GMT):
Has joined the channel.

lvzewen (Sat, 10 Mar 2018 07:12:37 GMT):
Has joined the channel.

ShereenSallam (Sat, 10 Mar 2018 12:23:41 GMT):
Has joined the channel.

ShereenSallam (Sat, 10 Mar 2018 12:23:54 GMT):
User User_1 added by ShereenSallam.

ShereenSallam (Sat, 10 Mar 2018 12:23:54 GMT):
User User_2 added by ShereenSallam.

sstone1 (Sun, 11 Mar 2018 14:28:37 GMT):
@rameshthoomu thanks for updating the script, just tried it and works great :+1:

sambhavdutt (Sun, 11 Mar 2018 16:52:03 GMT):
Is this ok, I have not included the Project check yet but otherwise will this script work ``` #!/bin/bash -eu ################################################# #Publish npm module as unstable after merge commit #npm publish --tag unstable #Run this "npm dist-tags ls $pkgs then look for #unstable versions ################################################# set -o pipefail npmPublish() { if [ $RELEASE = "snapshot" ]; then echo UNSTABLE_VER=$(npm dist-tags ls "$1" | awk '/unstable/{ ver=$NF sub(/.*\./,"",rel) sub(/\.[[:digit:]]+$/,"",ver) print ver}') echo "===> UNSTABLE VERSION --> $UNSTABLE_VER" UNSTABLE_INCREMENT=$(npm dist-tags ls "$1" | awk '/unstable/{ ver=$NF rel=$NF sub(/.*\./,"",rel) sub(/\.[[:digit:]]+$/,"",ver) print ver"."rel+1}') echo "===> Incremented UNSTABLE VERSION --> $UNSTABLE_INCREMENT" if [ "$UNSTABLE_VER" = "$CURRENT_RELEASE" ]; then # Replace existing version with Incremented $UNSTABLE_VERSION sed -i 's/$.*\"version\"\: \"$$.*$/\1'$UNSTABLE_INCREMENT\"\,'/' package.json npm publish --tag unstable else # Replace existing version with $CURRENT_RELEASE sed -i 's/$.*\"version\"\: \"$$.*$/\1'$CURRENT_RELEASE\"\,'/' package.json npm publish --tag unstable fi fi } npmstablePublish() { if [[ "$RELEASE" =~ alpha*|preview*|beta*|rc*|^[0-9].[0-9].[0-9]$ ]]; then echo "===> PUBLISH --> $RELEASE" npm publish else echo "$RELEASE: No such release." exit 1 fi } versions() { CURRENT_RELEASE=$(cat package.json | grep version | awk -F\" '{ print $4 }') echo "===> Current Version --> $CURRENT_RELEASE" RELEASE=$(cat package.json | grep version | awk -F\" '{ print $4 }' | cut -d "-" -f 2) echo "===> Current Release --> $RELEASE" } cd $WORKSPACE/gopath/src/github.com/hyperledger/fabric-sdk-node npm config set //registry.npmjs.org/:_authToken=$NPM_TOKEN if [ "GERRIT_EVENT_TYPE=change-merged"]; then cd fabric-ca-client versions npmPublish fabric-ca-client cd ../fabric-client versions npmPublish fabric-client elif [ "GERRIT_EVENT_TYPE=ref-updated"] cd fabric-ca-client versions npmstablePublish fabric-ca-client cd ../fabric-client versions npmstablePublish fabric-client fi ```

PrashantS (Mon, 12 Mar 2018 04:55:39 GMT):
Has joined the channel.

cbf (Mon, 12 Mar 2018 13:23:45 GMT):
@here we're seeing pretty good results from the 1.1.0-rc1 release, and so hopefully we can ship 1.1 later this week. I'll be pulling together a blog post for the Hyperledger blog and would love to reference some of the early adopters (e.g. projects that are planning to upgrade or have been in the process of upgrading from 1.0.x to 1.1.0. Please DM me and we can discuss how we get a quote

eramitg (Mon, 12 Mar 2018 13:24:31 GMT):
Hi cbf

eramitg (Mon, 12 Mar 2018 13:24:55 GMT):
i am new researcher from India doing academic research as well as

eramitg (Mon, 12 Mar 2018 13:25:02 GMT):
i am rnning IT Comany

eramitg (Mon, 12 Mar 2018 13:25:26 GMT):
in india please guide us to whom make hyperledger research adavnced project work me

eramitg (Mon, 12 Mar 2018 13:25:58 GMT):
as part of your research so that i can contribute my best for this hyperledger research

cbf (Mon, 12 Mar 2018 13:27:02 GMT):
If I understand correctly, you are asking with whom you can share results of your research?

cbf (Mon, 12 Mar 2018 13:27:36 GMT):
I would think that the mailing list is the most appropriate way of doing so: hyperledger-fabric@lists.hyperledger.org

eramitg (Mon, 12 Mar 2018 13:27:37 GMT):
yes ...i have gone through edx courses ...also i am abm partner so used there fabric resources..

eramitg (Mon, 12 Mar 2018 13:28:06 GMT):
i joined recently thanks for your suggestion

CaryMa (Mon, 12 Mar 2018 13:33:11 GMT):
Has joined the channel.

davidkhala (Tue, 13 Mar 2018 01:30:13 GMT):
Has joined the channel.

snowy13 (Tue, 13 Mar 2018 02:28:01 GMT):
Has joined the channel.

divudivyansh (Tue, 13 Mar 2018 04:34:09 GMT):
Has joined the channel.

iamdm (Tue, 13 Mar 2018 12:53:12 GMT):
Has joined the channel.

CarloFerrarini (Tue, 13 Mar 2018 22:13:03 GMT):
Has joined the channel.

sstone1 (Wed, 14 Mar 2018 11:38:19 GMT):
@rameshthoomu @cbf any chance we could get the https://goo.gl/6wtTN5 script updated so that it only grabs the binaries and doesn't do the `docker` parts if docker is not installed/available/desired?

cbf (Wed, 14 Mar 2018 14:15:53 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-release?msg=rSJY5v9HFBJhAa4Bi) @sstone1 why?

cbf (Wed, 14 Mar 2018 14:19:03 GMT):
I guess I am struggling with why we would want to support native orchestration of fabric when with Docker we have more control over what is running.

sstone1 (Wed, 14 Mar 2018 15:00:16 GMT):
@cbf what if i want to use the fabric-ca-client or other binaries to connect to a fabric i've already stood up elsewhere?

sstone1 (Wed, 14 Mar 2018 15:00:16 GMT):
@cbf what if i want to get and use the fabric-ca-client or other binaries to connect to a fabric i've already stood up elsewhere?

sstone1 (Wed, 14 Mar 2018 15:00:48 GMT):
i _think_ the peer binary can be used to connect to a remote peer right?

cbf (Wed, 14 Mar 2018 19:08:27 GMT):
@sstone1 sure, it *can* but why not download the images? It isn't as if Docker is a novelty these days

dave.enyeart (Wed, 14 Mar 2018 20:59:58 GMT):
I agree there should be an option for binary only for clients. The script resides in master so it can be changed at anytime. No need to rush something at the last minute for 1.1. @sstone1 can you open a jira request please?

mastersingh24 (Wed, 14 Mar 2018 21:13:19 GMT):
We don't need to modify the script IMHO .... why not just point people to the folder which has the binary distributions?

dave.enyeart (Wed, 14 Mar 2018 22:39:48 GMT):
yeah we could do that

dave.enyeart (Wed, 14 Mar 2018 22:40:10 GMT):
@sstone1 would going direct meet your need?

dave.enyeart (Wed, 14 Mar 2018 22:40:15 GMT):
https://nexus.hyperledger.org/content/repositories/releases/org/hyperledger/fabric/hyperledger-fabric/

dave.enyeart (Wed, 14 Mar 2018 22:40:58 GMT):
@rameshthoomu perhaps the non-release directories could go into a different directory there?

dave.enyeart (Wed, 14 Mar 2018 22:40:58 GMT):
@rameshthoomu perhaps the non-release directories could go into a different directory there? to avoid confusing people with all that noise...

rameshthoomu (Thu, 15 Mar 2018 01:52:05 GMT):
yes.. we are not pushing non release binaries to this directory..

rameshthoomu (Thu, 15 Mar 2018 01:52:22 GMT):
We are cleaning them up..

duwenhui (Thu, 15 Mar 2018 06:00:48 GMT):
Has joined the channel.

sstone1 (Thu, 15 Mar 2018 07:09:12 GMT):
i agree docker is not a novelty, but it's not available in CI environments that run builds inside docker containers (at least by default)

sstone1 (Thu, 15 Mar 2018 07:12:30 GMT):
the script is handy because it has the "export ARCH" magic

indira.kalagara (Thu, 15 Mar 2018 14:32:52 GMT):
Has joined the channel.

CodeReaper (Thu, 15 Mar 2018 14:43:56 GMT):
Has joined the channel.

dave.enyeart (Thu, 15 Mar 2018 18:23:59 GMT):
Release process for v1.1 starting, although we need to wait for some final automated tests to finish later this afternoon.

caseybecking (Thu, 15 Mar 2018 20:45:31 GMT):
Has joined the channel.

cbf (Thu, 15 Mar 2018 20:49:31 GMT):
@sstone1 ok, will add an option to forgo docker image d/l

cbf (Thu, 15 Mar 2018 21:17:09 GMT):
@sstone1 https://gerrit.hyperledger.org/r/19251

cbf (Thu, 15 Mar 2018 21:17:34 GMT):
basically, I have it set so that if docker not installed, it won't download images - hope that works for you

dave.enyeart (Thu, 15 Mar 2018 21:24:08 GMT):
fabric release CR merged

dave.enyeart (Thu, 15 Mar 2018 21:24:08 GMT):
we'll release and verify in sequence: fabric, fabric-ca, fabric-chaincode-node, fabric-sdk-node

dave.enyeart (Thu, 15 Mar 2018 21:27:48 GMT):
fabric release CR merged

sstone1 (Thu, 15 Mar 2018 21:34:47 GMT):
great, thanks @cbf

cbf (Thu, 15 Mar 2018 21:50:01 GMT):
reverifying fabric-ca

cbf (Thu, 15 Mar 2018 21:50:45 GMT):
@sstone1 please give it a test ... also, when you do incorporate, would you please also use the goo.gl short URL in the fabric docs so we can track more accurately downloads

dave.enyeart (Thu, 15 Mar 2018 22:20:38 GMT):
fabric binaries and images are available for trial: http://hyperledger-fabric.readthedocs.io/en/release-1.1/samples.html#binaries

dave.enyeart (Thu, 15 Mar 2018 22:24:32 GMT):
byfn verified on published 1.1 binaries and images

dave.enyeart (Thu, 15 Mar 2018 22:24:45 GMT):
moving on to fabric-ca next...

cbf (Thu, 15 Mar 2018 23:10:09 GMT):
you -1ed ca reason?

cbf (Thu, 15 Mar 2018 23:10:14 GMT):
CI passed

cbf (Thu, 15 Mar 2018 23:10:23 GMT):
think it is GTG, no?

cbf (Thu, 15 Mar 2018 23:10:23 GMT):
oh no... was looking at wrong CR

cbf (Thu, 15 Mar 2018 23:12:14 GMT):
rebuilding e2e

cbf (Thu, 15 Mar 2018 23:43:14 GMT):
fabric-ca ready to merge

dave.enyeart (Thu, 15 Mar 2018 23:50:47 GMT):
fabric-ca merged

caseybecking (Fri, 16 Mar 2018 00:38:33 GMT):
Will need to re-pull right?

rameshthoomu (Fri, 16 Mar 2018 00:40:50 GMT):
@caseybecking no not yet. fabric-ca release is in-progress.. Once the images are published, Dave will update here..

caseybecking (Fri, 16 Mar 2018 00:41:14 GMT):
:thumbsup:

caseybecking (Fri, 16 Mar 2018 00:41:14 GMT):
While working through this - https://github.com/hyperledger/fabric-samples/tree/master/balance-transfer#sample-rest-apis-requests

cbf (Fri, 16 Mar 2018 00:45:00 GMT):
ramesh https://gerrit.hyperledger.org/r/c/19273/ failing on e2e test

cbf (Fri, 16 Mar 2018 00:45:49 GMT):
@rameshthoomu

rameshthoomu (Fri, 16 Mar 2018 00:45:59 GMT):
checking

rameshthoomu (Fri, 16 Mar 2018 01:34:33 GMT):
I see authorization failure in java e2e tests.. even the re-trigger is failed. Not sure what's wrong. This was passed in the previous patch set..

dave.enyeart (Fri, 16 Mar 2018 01:49:44 GMT):
*fabric* and *fabric-ca* binaries and images are available for trial: http://hyperledger-fabric.readthedocs.io/en/release-1.1/samples.html#binaries

dave.enyeart (Fri, 16 Mar 2018 01:49:57 GMT):
both are working for me

cbf (Fri, 16 Mar 2018 02:06:34 GMT):
hmmm

cbf (Fri, 16 Mar 2018 02:06:45 GMT):
I am getting consistent failure of byfn

cbf (Fri, 16 Mar 2018 02:06:57 GMT):
Error: failed to create deliver client: orderer client failed to connect to orderer.example.com:7050: failed to create new connection: context deadline exceeded

cbf (Fri, 16 Mar 2018 02:51:56 GMT):
ok, so I re-fetched images and binaries and byfn working fine now

cbf (Fri, 16 Mar 2018 02:52:28 GMT):
however, now the fabric-ca e2e test is failing consistently on an authorization failure... is there maybe an expired certificate?

dave.enyeart (Fri, 16 Mar 2018 03:10:28 GMT):
fabric-chaincode-node v1.1.0 is published and working: https://www.npmjs.com/package/fabric-shim

dave.enyeart (Fri, 16 Mar 2018 03:49:11 GMT):
fabric-sdk-node v1.1.0 is published and working

yopep (Fri, 16 Mar 2018 04:00:03 GMT):
Has joined the channel.

khit9 (Fri, 16 Mar 2018 04:11:01 GMT):
Has joined the channel.

dave.enyeart (Fri, 16 Mar 2018 05:02:08 GMT):
Hyperledger Fabric v1.1 release artifacts are published for fabric, fabric-ca, fabric-chaincode-node, fabric-sdk-node, and documentation. Go ahead and download and try it out:

dave.enyeart (Fri, 16 Mar 2018 05:02:19 GMT):
http://hyperledger-fabric.readthedocs.io/en/release-1.1/samples.html#binaries

dave.enyeart (Fri, 16 Mar 2018 05:02:50 GMT):
You can checkout latest master in fabric-samples for trials.

dave.enyeart (Fri, 16 Mar 2018 05:03:44 GMT):
After we get some more success confirmations on various platforms Friday, we will tag fabric-samples and announce the release.

rameshthoomu (Fri, 16 Mar 2018 05:19:44 GMT):
@dave.enyeart I have tested on byfn, efyn with default channel, custom channel, couchdb, node chaincode on x86_64, s390x and ppc64le platforms, and fabcar, balance-transfer, fabric-ca samples on v1.1.0 release -- All worked as expected

rameshthoomu (Fri, 16 Mar 2018 05:19:44 GMT):
@dave.enyeart I have tested byfn, efyn with default channel, custom channel, couchdb, node chaincode on x86_64, s390x and ppc64le platforms, and fabcar, balance-transfer, fabric-ca samples on x86_64 and mac -- All worked as expected

rameshthoomu (Fri, 16 Mar 2018 05:19:58 GMT):
results are updated in the JIRA

yghazi (Fri, 16 Mar 2018 08:10:07 GMT):
Has joined the channel.

papegaaij (Fri, 16 Mar 2018 08:53:08 GMT):
Has joined the channel.

sillysachin (Fri, 16 Mar 2018 12:27:52 GMT):
Has joined the channel.

sigma67 (Fri, 16 Mar 2018 13:05:06 GMT):
Has joined the channel.

dave.enyeart (Fri, 16 Mar 2018 13:28:53 GMT):
fabric-samples v1.1.0 is tagged. All release 1.1 artifacts are published and tested.

caseybecking (Fri, 16 Mar 2018 14:29:15 GMT):
I'm getting an error - not sure if this is the right channel or not

caseybecking (Fri, 16 Mar 2018 14:30:41 GMT):
While working through this - https://github.com/hyperledger/fabric-samples/tree/master/balance-transfer#sample-rest-apis-requests

caseybecking (Fri, 16 Mar 2018 14:30:46 GMT):
```curl -s -X POST http://localhost:4000/users -H "content-type: application/x-www-form-urlencoded" -d 'username=Jim&orgName=Org1' Error

TypeError: Cannot read property 'name' of undefined
    at getOrgName (/Users/caseybecking/Sites/MYSITES/fabric-samples/balance-transfer/app/helper.js:96:19)
    at Object.getRegisteredUsers (/Users/caseybecking/Sites/MYSITES/fabric-samples/balance-transfer/app/helper.js:206:27)
    at /Users/caseybecking/Sites/MYSITES/fabric-samples/balance-transfer/app.js:128:9
    at Layer.handle [as handle_request] (/Users/caseybecking/Sites/MYSITES/fabric-samples/balance-transfer/node_modules/express/lib/router/layer.js:95:5)
    at next (/Users/caseybecking/Sites/MYSITES/fabric-samples/balance-transfer/node_modules/express/lib/router/route.js:137:13)
    at Route.dispatch (/Users/caseybecking/Sites/MYSITES/fabric-samples/balance-transfer/node_modules/express/lib/router/route.js:112:3)
    at Layer.handle [as handle_request] (/Users/caseybecking/Sites/MYSITES/fabric-samples/balance-transfer/node_modules/express/lib/router/layer.js:95:5)
    at /Users/caseybecking/Sites/MYSITES/fabric-samples/balance-transfer/node_modules/express/lib/router/index.js:281:22
    at Function.process_params (/Users/caseybecking/Sites/MYSITES/fabric-samples/balance-transfer/node_modules/express/lib/router/index.js:335:12)
    at next (/Users/caseybecking/Sites/MYSITES/fabric-samples/balance-transfer/node_modules/express/lib/router/index.js:275:10)

```

rajeshlc (Fri, 16 Mar 2018 14:32:23 GMT):
Has joined the channel.

mastersingh24 (Fri, 16 Mar 2018 14:36:43 GMT):
@caseybecking - I'd post this in #fabric-sdk-node

caseybecking (Fri, 16 Mar 2018 14:36:51 GMT):
:thumbsup:

eramitg (Fri, 16 Mar 2018 15:07:45 GMT):
we have meeting . now

cbf (Fri, 16 Mar 2018 15:59:39 GMT):
@caseybecking #fabric-questions or #fabric channels for questions or issues, please

caseybecking (Fri, 16 Mar 2018 16:30:13 GMT):
Sweet I found my own issue but good call out!

praspadm (Sat, 17 Mar 2018 04:50:26 GMT):
Has joined the channel.

VinayChaudhary (Sat, 17 Mar 2018 14:53:07 GMT):
Has joined the channel.

kerokhin (Sun, 18 Mar 2018 12:57:01 GMT):
Has joined the channel.

bh4rtp (Mon, 19 Mar 2018 06:18:38 GMT):
Has joined the channel.

artmedia (Mon, 19 Mar 2018 09:23:48 GMT):
Has joined the channel.

fredbi (Mon, 19 Mar 2018 13:25:11 GMT):
@dave.enyeart hello Dave. I've seen you completed the SideDB in 1.1. Is it still considered experimental or is it readily available in pre-built images?

fredbi (Mon, 19 Mar 2018 13:36:45 GMT):
some images tagged as 1.1.0 have not been released yet on dockerHub: fabric-couchdb, fabric-zookeeper, fabric-kafka

rameshthoomu (Mon, 19 Mar 2018 14:07:23 GMT):
@fredbi couch, zookeeper & kafka images are published as third party images with version `0.4.6` image tag..

fredbi (Mon, 19 Mar 2018 14:12:15 GMT):
so far I've been used to single release tagging (e.g. 1.0.2, ... 1.0.6)

rameshthoomu (Mon, 19 Mar 2018 14:20:33 GMT):
yes, this has been changed since 1.1 release.. see this one https://github.com/hyperledger/fabric/blob/release-1.1/scripts/bootstrap.sh

fredbi (Mon, 19 Mar 2018 14:21:51 GMT):
ok thank you - so far I've found convenient to tag all images with a single tag... now I use several ones...

dave.enyeart (Mon, 19 Mar 2018 15:05:16 GMT):
@fredbi SideDB is experimental in 1.1. Work is underway to make it a production feature in 1.2, you can track progress in this jira: https://jira.hyperledger.org/browse/FAB-8718

dave.enyeart (Mon, 19 Mar 2018 15:05:16 GMT):
@fredbi SideDB is experimental in 1.1 and you must re-compile peer with EXPERIMENTAL=true to get it. Work is underway to make it a production feature in 1.2, you can track progress in this jira: https://jira.hyperledger.org/browse/FAB-8718

fredbi (Mon, 19 Mar 2018 15:27:41 GMT):
@dave.enyeart thank you

pedromlcosta (Mon, 19 Mar 2018 19:43:21 GMT):
Has joined the channel.

davidkhala (Tue, 20 Mar 2018 02:07:45 GMT):
@fredbi I agree with you. It will be better for user experience and upgrade management that each type of image having aligned tag.

davidkhala (Tue, 20 Mar 2018 02:12:33 GMT):
Developers starting from 1.0 might already have their own build script assuming tags are aligned. Thus it might be more work for them before migrate from 1.0 to 1.1.

wjzheng (Tue, 20 Mar 2018 19:08:33 GMT):
Has joined the channel.

ShikarSharma (Tue, 20 Mar 2018 22:45:03 GMT):
Has joined the channel.

bzeyben (Wed, 21 Mar 2018 15:34:57 GMT):
Has joined the channel.

azur3s0ng (Thu, 22 Mar 2018 00:32:42 GMT):
Has joined the channel.

kolawoleOlulana (Fri, 23 Mar 2018 08:33:28 GMT):
Has joined the channel.

scottz (Mon, 26 Mar 2018 19:07:12 GMT):
experimental

nhrishi (Tue, 27 Mar 2018 11:18:02 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-release?msg=3MQinoksXM6Z9evu9) @dave.enyeart Dave, do we also have an experimental Fabric Node SDK (v1.1.0) compatible for SideDB features.

dave.enyeart (Tue, 27 Mar 2018 12:48:02 GMT):
@nhrishi No updates to SDK are required for SideDB. All changes are on the chaincode side. When calling chaincode you can pass private data in the transient field, and then in chaincode call the APIs for GetPrivateData(),PutPrivateData(), etc

nhrishi (Tue, 27 Mar 2018 15:55:54 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-release?msg=w7FCi79FD6imgSbHr) @dave.enyeart Great That is really helpful. Thanks.

thoduerr (Tue, 27 Mar 2018 21:31:51 GMT):
Has joined the channel.

bh4rtp (Wed, 28 Mar 2018 03:25:44 GMT):
does fabric have a plan to support Byzantium consensus in the further release?

dave.enyeart (Wed, 28 Mar 2018 11:36:44 GMT):
@bh4rtp Yes some groundwork is currently being developed, then BFT will be added using https://jira.hyperledger.org/browse/FAB-33

dave.enyeart (Wed, 28 Mar 2018 14:04:50 GMT):
@smithbk @aambati @skarim Saad was asking about getting approvals for FAB-7238. This one is currently about 100th in a list of 134 items in the fabric-ca backlog. I assume it should really be close to the top. In order to make decisions about what goes into v1.2, I think we first need the fabric-ca team to clarify the backlog rankings. Ranking 134 items is obviously difficult, minimally I'd suggest to rank the top 10 or so items, and then maintainers will be able look at the top items in each backlog and have discussion on relative priorities across components and epics. While most of the focus in v1.2 timeframe will go towards the top priority epics, I expect a couple top priorities from each component will also need to go in.

dave.enyeart (Wed, 28 Mar 2018 14:06:20 GMT):
I'm posting this to fabric-release, as the same applies to each of the component backlogs. For a full list of component backlogs, see last page of https://docs.google.com/document/d/1qyYDY6yn8_unFKmxmUDtTs2tP6DHCf9QNE5Rh-w1FMQ/edit#heading=h.guz3k8svs8k8

cbf (Wed, 28 Mar 2018 14:06:53 GMT):
https://jira.hyperledger.org/browse/FAB-7238 seems more like an Epic than a story.

cbf (Wed, 28 Mar 2018 14:07:26 GMT):
IMO, fabric-ca needs to choose 2-3 epics that will go into 1.2 release and manage from that

dave.enyeart (Wed, 28 Mar 2018 14:08:44 GMT):
right, the fabric-ca backlog includes all types of items, the top epics/improvements/stories/features need to be highlighted

bh4rtp (Wed, 28 Mar 2018 15:13:53 GMT):
@dave.enyeart thanks.

aambati (Wed, 28 Mar 2018 17:33:11 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-release?msg=hLKGGzh8TNf2GRXaL) @dave.enyeart yes, we will prioritize

zhouyun-zoe (Thu, 29 Mar 2018 01:38:55 GMT):
Has joined the channel.

duwenhui (Thu, 29 Mar 2018 08:24:46 GMT):
Because my production environment is generated based on the 1.0.0 version. In order to expand the organization, more than a dozen organizations were previously produced. However, only three organizations were actually used. Now that 1.1.0 can dynamically add organizations, the redundant organizations are useless. I am now trying to remove these redundant organizations. I now upgrade all nodes to version 1.1.0, but do not enable Capabilities, and then delete redundant organizations like adding organizations. Then turn on the Capabilities feature. Complete the 1.1.0 upgrade. Is this operation correct?

duwenhui (Thu, 29 Mar 2018 08:24:52 GMT):
@cbf

jaewonha (Fri, 30 Mar 2018 10:34:58 GMT):
Has joined the channel.

pandrejko (Fri, 30 Mar 2018 13:32:42 GMT):
Has joined the channel.

mastersingh24 (Sat, 31 Mar 2018 10:12:22 GMT):
@duwenhui - I assume you want to remove the orgs from the Consortium? In any case, it should not matter which in which order you remove the orgs versus upgrading, but upgrading, removing the orgs and then enabling v1.1 capabilities will work just fine

bh4rtp (Mon, 02 Apr 2018 00:58:04 GMT):
why does the latest fabric remove `javaenv`?

yacovm (Mon, 02 Apr 2018 09:06:57 GMT):
it has its own repository @bh4rtp

mastersingh24 (Mon, 02 Apr 2018 09:49:03 GMT):
@bh4rtp - as @yacovm mentions above, we have moved Java CC to its own repository and work is under way to actually support Java CC rather than having it as an experimental feature. But that work is going to be a major refactor / rewrite so it does not make sense to keep around the current code in any case

bh4rtp (Mon, 02 Apr 2018 11:47:26 GMT):
@yacovm @mastersingh24 thanks.

eabiodun (Mon, 02 Apr 2018 21:23:47 GMT):
Has joined the channel.

richzhao (Wed, 04 Apr 2018 15:57:15 GMT):
Has joined the channel.

aatkddny (Wed, 04 Apr 2018 18:21:03 GMT):
is there an eta for that? java cc that is.

kkado (Sat, 07 Apr 2018 04:15:52 GMT):
Has joined the channel.

duwenhui (Mon, 09 Apr 2018 08:11:26 GMT):
what if I make any mistakes when I upgrade fabric, add orgs and update an channel configuration, How can I roll back the configuration of the previous version? @mastersingh24

dave.enyeart (Mon, 09 Apr 2018 11:56:29 GMT):
@duwenhui The upgrade documentation http://hyperledger-fabric.readthedocs.io/en/latest/upgrading_your_network_tutorial.html mentions to backup the orderers and peers before major changes. If you make a mistake, you can then revert to the backup.

duwenhui (Tue, 10 Apr 2018 02:01:06 GMT):
@dave.enyeart I see.

nhrishi (Tue, 10 Apr 2018 13:00:46 GMT):
@dave.enyeart I've few questions related to Channel Private Data. Would really like to discuss with you and team. What would be the best way to connect. Also do we have any dedicated channel for the same. Thanks for your help.

Chandraamit (Wed, 11 Apr 2018 07:19:17 GMT):
While initiating the chaincode in Peer,I am getting the below error message.I have taken the fabric images of version 1.0.5.Could anyone help me to solve it.

Chandraamit (Wed, 11 Apr 2018 07:19:53 GMT):

Error screen shot1

Chandraamit (Wed, 11 Apr 2018 07:20:53 GMT):

Clipboard - April 11, 2018 12:50 PM

sherrypan (Wed, 11 Apr 2018 08:07:58 GMT):
Has joined the channel.

cbf (Wed, 11 Apr 2018 13:48:16 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-release?msg=MbyYnoxxGoc8ukDLo) @Chandraamit please post questions etc in #fabric-questions - this channel is for discussion about producing releases

eramitg (Wed, 11 Apr 2018 15:40:26 GMT):
Hi Folks , I am an Phd Candidate in www.nitrr.ac.in my Linkedind Profile is https://www.linkedin.com/in/eramitg/ for sake of earning an Phd Degree i was proposed Blockchain Technology research work area to my guide so oom I request all of you gyus ,please guide me and assign me some research oriented task so that we mutullay benifited research related to Hyperledger Umbrella Project , All of you feel free to catch me on twitter or skype to https://twitter.com/eramitg1 or amitg.iitb skype id also in Zoom to in Zoom ID 3649222703 or whatsapp +917773011100 Regards

am (Wed, 11 Apr 2018 21:27:41 GMT):
Has joined the channel.

davidgsmits (Thu, 12 Apr 2018 13:50:16 GMT):
Has joined the channel.

Blaise 4 (Fri, 13 Apr 2018 03:11:11 GMT):
Has joined the channel.

daviorocha (Fri, 13 Apr 2018 21:29:05 GMT):
Has joined the channel.

StevenXu (Mon, 16 Apr 2018 03:40:34 GMT):
Has joined the channel.

Enigmae22 (Tue, 17 Apr 2018 13:01:45 GMT):
Has joined the channel.

duwenhui (Thu, 19 Apr 2018 05:46:18 GMT):
When upgrading 1.1, the upgrade is complete. However, several transactions were written without opening the Capabilities. Is there a problem? Today's upgrade of the production environment encountered a more thorny problem: Orderer reported such errors when reading the system chain. 2018-04-19 05:23:17.321 UTC [orderer/consensus/kafka] try -> DEBU 5c3 [channel: cbcagenesis] Connecting to the Kafka cluster 2018-04-19 05:23:17.322 UTC [orderer/consensus/kafka] try -> DEBU 5c4 [channel: cbcagenesis] Need to retry because process failed = kafka server: The requested offset is outside the range of offsets maintained by the server for the given topic/partition. 2018-04-19 05:23:17.363 UTC [orderer/common/server] Deliver -> DEBU 5c5 Starting new Deliver handler 2018-04-19 05:23:17.363 UTC [common/deliver] Handle -> DEBU 5c6 Starting new deliver loop for 47.95.252.160:50106 2018-04-19 05:23:17.363 UTC [common/deliver] Handle -> DEBU 5c7 Attempting to read seek info message from 47.95.252.160:50106 2018-04-19 05:23:17.364 UTC [common/deliver] deliverBlocks -> WARN 5c8 [channel: cbcagenesis] Rejecting deliver request for 47.95.252.160:50106 because of consenter error 2018-04-19 05:23:17.364 UTC [common/deliver] Handle -> DEBU 5c9 Waiting for new SeekInfo from 47.95.252.160:50106 2018-04-19 05:23:17.364 UTC [common/deliver] Handle -> DEBU 5ca Attempting to read seek info message from 47.95.252.160:50106 2018-04-19 05:23:17.369 UTC [common/deliver] Handle -> WARN 5cb Error reading from 47.95.252.160:50106: rpc error: code = Canceled desc = context canceled 2018-04-19 05:23:17.369 UTC [orderer/common/server] func1 -> DEBU 5cc Closing Deliver stream 2018-04-19 05:23:18.321 UTC [orderer/consensus/kafka] try -> DEBU 5cd [channel: cbcagenesis] Connecting to the Kafka cluster 2018-04-19 05:23:18.322 UTC [orderer/consensus/kafka] try -> DEBU 5ce [channel: cbcagenesis] Need to retry because process failed = kafka server: The requested offset is outside the range of offsets maintained by the server for the given topic/partition.

duwenhui (Thu, 19 Apr 2018 05:47:02 GMT):
@cbf @dave.enyeart

duwenhui (Thu, 19 Apr 2018 12:41:09 GMT):
peer channel fetch config config_block.pb -o orderer0.bqj.cn:7050 -c cbcagenesis --tls --cafile $ORDERER_CA

dave.enyeart (Thu, 19 Apr 2018 12:46:01 GMT):
@duwenhui the experts in that area hang out in #fabric-orderer , please post over there to work through the details. Then if there are some takeaways from a release/upgrade perspective we can post a summary to this channel.

duwenhui (Thu, 19 Apr 2018 12:48:13 GMT):
@dave.enyeart I see, thanks.

bh4rtp (Fri, 20 Apr 2018 00:49:43 GMT):
why does `Makefile` keep ` membersrvc-image` but echo being removed message?

jastisriradheshyam (Fri, 20 Apr 2018 07:46:56 GMT):
Has joined the channel.

rameshthoomu (Fri, 20 Apr 2018 13:08:44 GMT):
@bh4rtp left their to satisfy the CI config.. This can be now removed from master, release-1.0, release-1.1 branches.

smallX (Wed, 25 Apr 2018 10:15:04 GMT):
#fabric-sdk-dev

bh4rtp (Fri, 27 Apr 2018 06:54:34 GMT):
i think the docker images of fabric should take `$ARCH` as suffix of repository, not prefix of tag. for example `hyperledger/fabric-ccenv:amd64-1.2.0` as `hyperledger/fabric-ccenv-amd64:1.2.0`

cbf (Fri, 27 Apr 2018 12:52:02 GMT):
@bh4rtp we are just about to transition to multi-arch docker image manifests so this becomes moot

cbf (Fri, 27 Apr 2018 12:52:57 GMT):
https://jira.hyperledger.org/browse/FAB-9629

friends110110 (Fri, 27 Apr 2018 13:03:53 GMT):
Has joined the channel.

chainsaw (Fri, 27 Apr 2018 15:53:57 GMT):
Has joined the channel.

kostas (Fri, 27 Apr 2018 21:58:09 GMT):
Has left the channel.

bh4rtp (Sat, 28 Apr 2018 08:36:17 GMT):

Clipboard - 2018年4月28日下午4点35分

bh4rtp (Sat, 28 Apr 2018 08:36:56 GMT):
@cbf i have retagged the images, `latest` tag can be used for different arch.

cbf (Sat, 28 Apr 2018 19:52:12 GMT):
@bh4rtp yes, we are evolving to multi-arch manifests, you will be able to have latest tags from dockerhub as well soon

IsaacWong (Sun, 29 Apr 2018 10:12:17 GMT):
Has joined the channel.

tsnyder (Tue, 01 May 2018 12:41:55 GMT):
Has joined the channel.

troyronda (Fri, 04 May 2018 13:41:19 GMT):
@dave.enyeart when do you figure that the first preview tag for 1.2 will be?

troyronda (Fri, 04 May 2018 13:42:09 GMT):
(note: we are using the latest docker images to test Go SDK against the 1.2 stream, it would be good to switch to a tag for CI stability)

troyronda (Fri, 04 May 2018 13:42:09 GMT):
(note: we are using the latest docker images to test Go SDK against the 1.2 stream - particularly to integration test discovery service, it would be good to switch to a tag for CI stability)

troyronda (Fri, 04 May 2018 13:43:30 GMT):
I was guessing maybe shortly after the backend 1.2 dev stream shuts down, but I wasn't sure how other SDKs handle this?

troyronda (Fri, 04 May 2018 13:43:30 GMT):
I was guessing shortly after the backend 1.2 dev stream shuts down, but I wasn't sure how other SDKs handle this?

dave.enyeart (Fri, 04 May 2018 13:56:15 GMT):
@troyronda As we have shifted to quarterly releases with smaller incremental feature sets, there will be no alpha/beta/preview.

troyronda (Fri, 04 May 2018 13:56:33 GMT):
ah interesting, thanks

troyronda (Fri, 04 May 2018 13:57:03 GMT):
Let me shift the next question to the CI channel then.

dave.enyeart (Fri, 04 May 2018 13:57:41 GMT):
the goal is to keep master stable enough such that the community can consume it at any point and test things out

troyronda (Fri, 04 May 2018 13:58:27 GMT):
So your feeling is testing SDKs against docker latest is stable enough?

troyronda (Fri, 04 May 2018 13:59:10 GMT):
(the question I was going to pose, is should there be periodic checkpoints available for testing SDKs against in the CI)

troyronda (Fri, 04 May 2018 13:59:10 GMT):
(the question I was going to pose: should there be periodic checkpoints available for testing SDKs against in the CI)

troyronda (Fri, 04 May 2018 13:59:10 GMT):
(the question I was going to pose: should there be periodic checkpoints, as docker images, available for testing SDKs against in the CI)

yacovm (Fri, 04 May 2018 14:00:05 GMT):
*now* it is not feature complete

yacovm (Fri, 04 May 2018 14:00:44 GMT):
Troy - have you had the chance to test the endorsement queries for SD ?

yacovm (Fri, 04 May 2018 14:00:56 GMT):
for a single chaincode, that is

troyronda (Fri, 04 May 2018 14:01:54 GMT):
@bstasyszyn ^^

bstasyszyn (Fri, 04 May 2018 14:01:54 GMT):
Has joined the channel.

dave.enyeart (Fri, 04 May 2018 14:03:19 GMT):
@troyronda I know that @cbf and @rameshthoomu have been looking into making regular builds available, perhaps with some indication of which ones have had more testing. I'll defer to them for an update...

troyronda (Fri, 04 May 2018 14:13:54 GMT):
thanks dave.

cbf (Fri, 04 May 2018 14:42:10 GMT):
@troyronda yes... we are moving to a process where we anoint a nightly build as "stable" and making the images and binaries downloadable from Nexus

cbf (Fri, 04 May 2018 14:42:29 GMT):
we could definitely use some assistance in making this so!

cbf (Fri, 04 May 2018 14:43:50 GMT):
https://jira.hyperledger.org/browse/FAB-9641

cbf (Fri, 04 May 2018 14:44:49 GMT):
we currently are at a point that the images are archived on Nexus... next we need to transition so that the nightly tests use a chosen set to test with (rather than a new build, which is currently the case)

bstasyszyn (Fri, 04 May 2018 14:58:36 GMT):
@yacovm @troyronda No we haven't tested endorsement queries yet.

yacovm (Fri, 04 May 2018 14:59:04 GMT):
any ETA? :)

bstasyszyn (Fri, 04 May 2018 15:00:12 GMT):
We'll need to look at our current backlog and prioritize - @troyronda?

Vijay.malyavantham (Fri, 04 May 2018 15:20:43 GMT):
Has joined the channel.

SmartContract2018 (Sat, 05 May 2018 16:04:22 GMT):
Has joined the channel.

rameshthoomu (Mon, 07 May 2018 00:36:26 GMT):
@cbf Updated comments in FAB-9641

sstone1 (Tue, 08 May 2018 09:55:38 GMT):
the node.js chaincode in fabric v1.1.1 is completely broken, had to raise FAB-9943 - @rameshthoomu what testing is done on this?

dimaxgl (Tue, 08 May 2018 11:48:17 GMT):
Has joined the channel.

rameshthoomu (Tue, 08 May 2018 11:53:43 GMT):
CI runs `gulp test-headless` & `gulp test-e2e` - https://jenkins.hyperledger.org/job/fabric-chaincode-node-merge-x86_64/81/consoleFull

rameshthoomu (Tue, 08 May 2018 11:54:00 GMT):
@bret

rameshthoomu (Tue, 08 May 2018 11:54:00 GMT):
@bretharrison could you please check

elainejlai (Tue, 08 May 2018 20:13:08 GMT):
Has joined the channel.

sstone1 (Wed, 09 May 2018 07:15:44 GMT):
fabric-ca-client also broken, see FAB-9967

sstone1 (Wed, 09 May 2018 07:21:21 GMT):
@rameshthoomu how do these npm modules get published? manually or via automation?

sstone1 (Wed, 09 May 2018 07:23:58 GMT):
in composer we publish the npm modules to a local npm server (verdaccio). our integration tests then install those npm modules, and run the tests against what was published + installed. that's instead of just running tests against the local source directory. it might avoid these kind of problems in the future if we did the same for all of the fabric npm modules.

mbwhite (Wed, 09 May 2018 07:25:55 GMT):
Has joined the channel.

ShinsukeHasegawa (Wed, 09 May 2018 09:48:34 GMT):
Has joined the channel.

rameshthoomu (Wed, 09 May 2018 12:11:04 GMT):
@sstone1 we publish npm modules through Jenkins release jobs.. I will check with @brett and let you know the update

baoyangc (Thu, 10 May 2018 02:07:46 GMT):
hi all， do we have a channel to discuss the error happened after upgrading to fabric v1.1.0

baoyangc (Thu, 10 May 2018 02:07:48 GMT):
?

dave.enyeart (Thu, 10 May 2018 12:10:43 GMT):
@baoyangc this is as good as any channel... if it ends up getting deep in any specific area we can always move the conversation

dave.enyeart (Thu, 10 May 2018 15:18:13 GMT):
@rameshthoomu We haven't discussed recently so just checking... is this still the latest release process doc:

dave.enyeart (Thu, 10 May 2018 15:18:15 GMT):
https://docs.google.com/document/d/12IpQnREUoJEUj2pF2z-0Up55geItFd94fcsbAkPacTg/edit#

dave.enyeart (Thu, 10 May 2018 15:18:37 GMT):
is it linked to from our wiki and other public places?

rameshthoomu (Thu, 10 May 2018 16:42:58 GMT):
@dave.enyeart still using the same document.. I don't see it in hyperledger wiki page..

rameshthoomu (Thu, 10 May 2018 16:43:27 GMT):
will review this again with the recent changes and will update you..

versus (Mon, 14 May 2018 09:07:39 GMT):
Has joined the channel.

nagap (Tue, 15 May 2018 22:39:31 GMT):
Has joined the channel.

lucienlu (Fri, 18 May 2018 02:30:13 GMT):
Has joined the channel.

kostas (Tue, 22 May 2018 23:36:55 GMT):
Has joined the channel.

kostas (Tue, 22 May 2018 23:37:11 GMT):
Master failing on unit tests?

kostas (Tue, 22 May 2018 23:37:17 GMT):
I've been getting this all day long:

kostas (Tue, 22 May 2018 23:37:17 GMT):
I've been getting this all day long: https://hastebin.com/weyocolopi.hs

kostas (Tue, 22 May 2018 23:37:20 GMT):
```unit-tests_1 | ? github.com/hyperledger/fabric/peer [no test files] unit-tests_1 | 2018-05-22 23:08:58.932 UTC [msp] Setup -> INFO 001 MSP manager already up unit-tests_1 | 2018-05-22 23:08:58.936 UTC [chaincodeCmd] validatePeerConnectionParameters -> WARN 002 received more TLS root cert files (2) than peer addresses (1) unit-tests_1 | 2018-05-22 23:08:58.947 UTC [chaincodeCmd] validatePeerConnectionParameters -> WARN 003 received more TLS root cert files (1) than peer addresses (0) unit-tests_1 | 2018-05-22 23:08:58.958 UTC [chaincodeCmd] ClientWait -> INFO 004 txid [txid0] committed with status (VALID) at peer0 unit-tests_1 | 2018-05-22 23:08:58.996 UTC [msp] Setup -> INFO 005 MSP manager already up unit-tests_1 | 2018-05-22 23:08:58.996 UTC [chaincodeCmd] ClientWait -> INFO 006 txid [txid0] committed with status (VALID) at peer0 unit-tests_1 | 2018-05-22 23:08:58.997 UTC [chaincodeCmd] ClientWait -> INFO 007 txid [txid0] committed with status (VALID) at peer1 unit-tests_1 | 2018-05-22 23:08:58.997 UTC [chaincodeCmd] ClientWait -> INFO 008 txid [txid0] committed with status (VALID) at peer0 unit-tests_1 | 2018-05-22 23:08:58.997 UTC [chaincodeCmd] ClientWait -> INFO 009 txid [txid0] committed with status (VALID) at peer1 unit-tests_1 | Error: Must supply value for chaincode name, path and version parameters. unit-tests_1 | 2018-05-22 23:08:59.010 UTC [chaincodeCmd] checkChaincodeCmdParams -> INFO 00a Using default escc unit-tests_1 | 2018-05-22 23:08:59.010 UTC [chaincodeCmd] checkChaincodeCmdParams -> INFO 00b Using default vscc unit-tests_1 | Error: error getting chaincode code badexample02: path to chaincode does not exist: /opt/gopath/src/github.com/hyperledger/fabric/examples/chaincode/go/bad_example02 unit-tests_1 | 2018-05-22 23:08:59.266 UTC [chaincodeCmd] checkChaincodeCmdParams -> INFO 00c Using escc escc unit-tests_1 | 2018-05-22 23:08:59.266 UTC [chaincodeCmd] checkChaincodeCmdParams -> INFO 00d Using vscc vscc unit-tests_1 | 2018-05-22 23:08:59.266 UTC [chaincodeCmd] install -> INFO 00e Installed remotely response: endorsement:<> unit-tests_1 | Error: failed to unmarshal envelope from bytes unit-tests_1 | 2018-05-22 23:08:59.277 UTC [chaincodeCmd] checkChaincodeCmdParams -> INFO 00f Using escc escc unit-tests_1 | 2018-05-22 23:08:59.277 UTC [chaincodeCmd] checkChaincodeCmdParams -> INFO 010 Using vscc vscc unit-tests_1 | FAIL github.com/hyperledger/fabric/peer/chaincode 24.294s```

kostas (Tue, 22 May 2018 23:38:34 GMT):
My latest run was with the HEAD set to `5636636cf`.

kostas (Tue, 22 May 2018 23:38:34 GMT):
My latest run was with the HEAD set to: `5636636cf`

sklymenko (Wed, 23 May 2018 09:04:17 GMT):
Has joined the channel.

dave.enyeart (Wed, 23 May 2018 18:34:55 GMT):
@cbf @rameshthoomu Could one of you update the release process document based on the new multi-architecture support? https://docs.google.com/document/d/12IpQnREUoJEUj2pF2z-0Up55geItFd94fcsbAkPacTg/edit#

dave.enyeart (Wed, 23 May 2018 18:34:58 GMT):
Also based on the May 10th post above, it sounded like Ramesh had some other changes in mind.

dave.enyeart (Wed, 23 May 2018 18:35:33 GMT):
If there are other engineers working on release process, please mention them here so that we're all on the same page.

dave.enyeart (Wed, 23 May 2018 18:35:33 GMT):
If there are other engineers working on release process, please mention them here so that we're all on the same page, going into June.

rameshthoomu (Wed, 23 May 2018 18:37:09 GMT):
@dave.enyeart I have to update the fabric and fabric-ca release process.. As we introduced publishing images with multi-arch support

rameshthoomu (Wed, 23 May 2018 18:38:24 GMT):
Now the CI publishes docker images and binaries on every successful e2e merge job

dave.enyeart (Wed, 23 May 2018 18:38:52 GMT):
Great! Tell it to the google doc please :)

rameshthoomu (Wed, 23 May 2018 18:39:04 GMT):
there are couple of sections we have to update in that area..

rameshthoomu (Wed, 23 May 2018 18:39:14 GMT):
will do

dave.enyeart (Wed, 23 May 2018 18:40:21 GMT):
@rameshthoomu are the changes for all release branches? or just for master (v1.2)?

rameshthoomu (Wed, 23 May 2018 18:40:58 GMT):
release-1.1 and v1.2

dave.enyeart (Wed, 23 May 2018 18:41:40 GMT):
ok, please make that clear in the doc, as there may be additional release-1.0 fixpacks that would follow the prior process.

cbf (Wed, 23 May 2018 19:03:04 GMT):
@dave.enyeart @rameshthoomu https://jira.hyperledger.org/browse/FAB-9633 has been included in the epic... I need to spend a moment to build the template-based script

cbf (Wed, 23 May 2018 19:03:32 GMT):
https://jira.hyperledger.org/browse/FAB-9652

kostas (Thu, 24 May 2018 01:08:10 GMT):
Has left the channel.

donsonZhang (Thu, 24 May 2018 06:59:16 GMT):
Has joined the channel.

cbf (Thu, 24 May 2018 23:15:42 GMT):
are we merging idemix revocation?

cbf (Thu, 24 May 2018 23:15:45 GMT):
https://gerrit.hyperledger.org/r/c/22209/

cbf (Fri, 25 May 2018 01:18:03 GMT):
@mastersingh24 @dave.enyeart ^^

dave.enyeart (Fri, 25 May 2018 02:49:02 GMT):
@cbf Some parts of revocation were previously merged. We are not merging code to expose it however. If there are fixes to the prior merged code, I don't mind those fixes getting merged. Looks like it has in fact been merged.

Maria (Fri, 25 May 2018 21:10:59 GMT):
@cbf this is not actual revocation - more like mock revocation with algorithm called NO_REVOCATION. It does allocate objects etc. but there is no actual non-revocation proof being generated/verified.... and no certificates being revoked with CRI being updated etc.

Maria (Fri, 25 May 2018 21:10:59 GMT):
@cbf this is not actual revocation - more like mock revocation with the algorithm called NO_REVOCATION. It does allocate objects etc. but there is no actual non-revocation proof being generated/verified.... and no certificates being revoked with CRI being updated etc.

Maria (Fri, 25 May 2018 21:10:59 GMT):
@cbf this is not actual revocation - more like mock revocation with the algorithm called NO_REVOCATION. It does allocate objects and updates protos etc. but there is no actual non-revocation proof being generated/verified.... and no certificates being revoked with CRI being updated etc. so in 1.3 when actual revocation algorithm is merged the previously issued certificates can still be revoked

yacovm (Fri, 25 May 2018 21:18:28 GMT):
regardless of no revocation... i consider that a bug fix, because the essence of the change set is change the serializing of the signature. before the change set, the 2 parts of the signature were just glued together, and you can't figure out where the first part ends and the 2nd part starts... the fix makes it serialize in asn1 so that you have a separation between the fields.

IgorSim (Wed, 30 May 2018 12:17:23 GMT):
Has joined the channel.

vdelbar (Wed, 30 May 2018 15:34:36 GMT):
Has joined the channel.

rogerwilcos (Wed, 30 May 2018 23:28:05 GMT):
Has joined the channel.

rickr (Thu, 31 May 2018 13:04:41 GMT):
@Maria Have a question I'd like answered for the Idemix JSDK work. Is this API now something that we'll use in the future ? I've heard from the team a strong desire to change it in a breaking manner in the following release.

Maria (Thu, 31 May 2018 13:34:09 GMT):
Hi Rick, @rickr , no we do not intend to break the entire SDK in 1.3. As you told us that we cannot change any of the JSDK interfaces now - so we implemented things how you proposed and interfaces are not breaking. However, as you suggested yourself, at some point you plan to change the JSDK interfaces (in 2.0 you said) - so we think that would be a good opportunity to also switch in treating SigningIdentity in the same way as in Fabric (the way we originally thought it could be implemented) which could lead to a few interface changes (but we would do it with a proper design review, in sync with other SDKs, etc.).

Maria (Thu, 31 May 2018 13:34:09 GMT):
Hi Rick, @rickr , no we do not intend to break the entire SDK in 1.2 or 1.3. As you told us that we cannot change any of the JSDK interfaces now - so we implemented things how you proposed and interfaces are not breaking. However, as you suggested yourself, at some point you plan to change the JSDK interfaces (in 2.0 you said) - so we think that would be a good opportunity to also switch in treating SigningIdentity in the same way as in Fabric (the way we originally thought it could be implemented) which could lead to a few interface changes (but we would do it with a proper design review, in sync with other SDKs, etc.).

Maria (Thu, 31 May 2018 13:34:09 GMT):
Hi Rick, @rickr , no we do not intend to break the entire SDK in 1.2 or 1.3. As you told us that we cannot change any of the JSDK interfaces now - so we implemented things how you proposed and interfaces are not breaking. However, as you suggested yourself, at some point you plan to change the JSDK interfaces (in 2.0 you said) - so we think that would be a good opportunity to also switch to treating SigningIdentity in the same way as in Fabric (the way we originally thought it could be implemented) which could lead to a few interface changes (but we would do it with a proper design review, in sync with other SDKs, etc.).

rickr (Thu, 31 May 2018 13:36:52 GMT):
I think we were talking about 1.2 which I agree we can't break. So the plan would be in a 2.0 release that most likely there would be breaking changes ?

rickr (Thu, 31 May 2018 13:51:14 GMT):
@dave.enyeart @mastersingh24 @cbf I've heard _talk_ of a 2.0 release. Any notion how many releases away that might be? I think the new chancode lifecycle might have changes that will be a significant hit on the SDKs and we probably won't be able to support both going to the same channel at the same time.(not really a deprecated api) that 2.0 for that would seem appropriate.

dave.enyeart (Thu, 31 May 2018 13:54:19 GMT):
In my opinion we should bump up to 2.0 when the big lifecycle changes are made, and currently that is targeted for september release.

rickr (Thu, 31 May 2018 17:43:59 GMT):
Any thoughts will there be a 1.3 and then a 2.0 or just a 2.0 ?

Mari499 (Thu, 31 May 2018 23:26:26 GMT):
Has joined the channel.

BhaveshPatadiya (Fri, 01 Jun 2018 05:22:42 GMT):
Has joined the channel.

Steve-IM (Fri, 01 Jun 2018 07:03:41 GMT):
Has joined the channel.

cbf (Fri, 01 Jun 2018 11:31:12 GMT):
we'll cross that bridge when we get there... it will be one or the other

vanitas92 (Sun, 03 Jun 2018 19:03:22 GMT):
Has joined the channel.

mastersingh24 (Mon, 04 Jun 2018 12:47:18 GMT):
I think we should just skip to version 10.0

mastersingh24 (Mon, 04 Jun 2018 12:47:19 GMT):
;)

cbf (Mon, 04 Jun 2018 12:49:11 GMT):
well, at least 3.0

tqumhieh (Wed, 06 Jun 2018 00:18:10 GMT):
Has joined the channel.

jadhavajay (Wed, 06 Jun 2018 13:43:37 GMT):
Hi team,

dave.enyeart (Thu, 07 Jun 2018 14:21:54 GMT):
Function test is completing this week and system test is underway. We will merge defect fixes and important polish items for the next two weeks. Then in mid-June cut a RC1 and release to community, and create a release-1.2 branch. Then the last two weeks of June only critical fixes could get into release-1.2 branch for the final v1.2 release cut. System test will proceed all throughout June. Of course, as we progress through each week of June we will get more and more critical of which CRs to merge.

dave.enyeart (Thu, 07 Jun 2018 14:22:04 GMT):
We are still targeting v1.2 RC1 for the week of June 18th, although it will depend on defect and system test progress.

rangak (Thu, 07 Jun 2018 15:40:19 GMT):
Has joined the channel.

abraham (Fri, 08 Jun 2018 01:04:02 GMT):
Has joined the channel.

vanitas92 (Fri, 08 Jun 2018 11:28:33 GMT):
Hi guys do you know when would be available the instantiation of chaincodes fully integrated within kubernetes? I read that its planned to be available at 1.2?

greg2git (Fri, 08 Jun 2018 11:50:40 GMT):
Has joined the channel.

cbf (Mon, 11 Jun 2018 12:49:00 GMT):
@vanitas92 this requires deeper changes, and is not planned for 1.2. There is keen interest from within the community. Suggest you follow-up on the #fabric-kubernetes channel.

david_dornseifer (Wed, 13 Jun 2018 06:41:31 GMT):
Has joined the channel.

david_dornseifer (Wed, 13 Jun 2018 06:44:00 GMT):
Hi everybody, just wondering when will be the 1.1.1 / 1.2 release available - just asking because 1.1 is based on Go 1.9.2 right now and you know there is the security bug in there

david_dornseifer (Wed, 13 Jun 2018 06:44:20 GMT):
Or is there no 1.1.1 release planned and it will directly be 1.2?

yacovm (Wed, 13 Jun 2018 06:48:41 GMT):
what bug, @david_dornseifer ?

david_dornseifer (Wed, 13 Jun 2018 06:49:42 GMT):
@yacovm https://www.cvedetails.com/vulnerability-list/vendor_id-14185/product_id-29205/version_id-238294/Golang-GO-1.9.2.html its cve 7.5

yacovm (Wed, 13 Jun 2018 06:50:19 GMT):
oh but we don't do `go get` IIRC

yacovm (Wed, 13 Jun 2018 06:50:24 GMT):
in the peer/orderer

david_dornseifer (Wed, 13 Jun 2018 06:52:47 GMT):
hmm ok - just wondering is there a minor release planned soon? Also the kafka / zk and couchd images - they are still on 1.1-preview?

david_dornseifer (Wed, 13 Jun 2018 06:52:47 GMT):
hmm ok - just wondering is there a minor release planned soon? Also the kafka / zk and couchd images? - they are still on 1.1-preview

yacovm (Wed, 13 Jun 2018 06:54:41 GMT):
we always patch v1.1.x

yacovm (Wed, 13 Jun 2018 06:54:55 GMT):
there were multiple releases already introduced for v1.1.x

yacovm (Wed, 13 Jun 2018 06:55:03 GMT):
but v1.2 is right at the door

yacovm (Wed, 13 Jun 2018 06:55:13 GMT):
so you should wait for it

david_dornseifer (Wed, 13 Jun 2018 06:55:38 GMT):
:+1: what is your estimate - how long will it take till 1.2 is available?

yacovm (Wed, 13 Jun 2018 06:56:03 GMT):
I'd say end of this month

david_dornseifer (Wed, 13 Jun 2018 07:06:37 GMT):
ok thx for that information - so there will definitely not be a minor release 1.1.1?

yacovm (Wed, 13 Jun 2018 07:07:16 GMT):
there will probably be more v1.1.x releases

david_dornseifer (Wed, 13 Jun 2018 07:23:07 GMT):
ok, would be nice if Go1.10 would be shipped with 1.1.1

bh4rtp (Wed, 13 Jun 2018 07:32:19 GMT):
i think you can update go1.10 by yourself if required. @david_dornseifer

vanitas92 (Wed, 13 Jun 2018 19:44:33 GMT):

Clipboard - June 13, 2018 9:44 PM

vanitas92 (Wed, 13 Jun 2018 19:44:35 GMT):
Hi guys i have a question about images of zookeeper, kafka and couchdb, they do not have a 1.1 version but the newer images are tagged as 0.4.x. Could somebody clarify this?

rameshthoomu (Wed, 13 Jun 2018 21:18:40 GMT):
@vanitas92 from release-1.1, we are tagging thirdparty images (kafka, zookeeper and couchdb) with baseimage release version. So you see thirdparty image versions like 0.4.x.. So the latest compatible thirdparty version for release-1.1 is 0.4.6 (https://github.com/hyperledger/fabric/blob/release-1.1/Makefile#L47)

rameshthoomu (Wed, 13 Jun 2018 21:18:40 GMT):
@vanitas92 from release-1.1, we are tagging thirdparty images (kafka, zookeeper and couchdb) with baseimage release version. So you see thirdparty image versions like 0.4.x.. latest compatible thirdparty version for release-1.1 is 0.4.6 (https://github.com/hyperledger/fabric/blob/release-1.1/Makefile#L47)

vanitas92 (Thu, 14 Jun 2018 06:58:12 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-release?msg=jzyhuS989GbMjofpw) @rameshthoomu Thanks. Should be better documented either in docker hub repo or in the fabric docs. People could get confused by this change.

alexisjanin (Fri, 15 Jun 2018 06:57:58 GMT):
Has joined the channel.

hatakeyamak1 (Fri, 15 Jun 2018 10:07:17 GMT):
Has joined the channel.

paulananth (Fri, 15 Jun 2018 12:18:16 GMT):
Has joined the channel.

Sambhav (Fri, 15 Jun 2018 18:58:59 GMT):
Has joined the channel.

vudathasaiomkar (Sat, 16 Jun 2018 01:01:42 GMT):
Has joined the channel.

lushan6999 (Sun, 17 Jun 2018 04:31:19 GMT):
Has joined the channel.

raghung (Sun, 17 Jun 2018 07:51:56 GMT):
Has joined the channel.

Kyroy (Mon, 18 Jun 2018 07:36:12 GMT):
Has joined the channel.

dave.enyeart (Tue, 19 Jun 2018 11:36:03 GMT):
@rameshthoomu @cbf Last night I merged and tagged baseimage 0.4.9. We got all three architecture docker images pushed to dockerhub for baseimage. But the third party images only got pushed for ppc64le-0.4.9 and s390x-0.4.9, not for amd64-0.4.9. Can you take a look?

dave.enyeart (Tue, 19 Jun 2018 11:36:50 GMT):
On my local, amd64-0.4.9 did indeed get built successfully and tests successfully

cbf (Tue, 19 Jun 2018 11:37:52 GMT):
@dave.enyeart help me understand why 0.4.9 is being produced? What's in it?

dave.enyeart (Tue, 19 Jun 2018 11:38:30 GMT):
updates to latest recommended node js, and some fixes to couchdb image that got reverted in prior baseimages

cbf (Tue, 19 Jun 2018 11:39:40 GMT):
ah ok, I was looking at an older version that had no changes;-)

cbf (Tue, 19 Jun 2018 11:40:12 GMT):
but help me understand the testing strategy here... we are swapping out the baseimage just before we release rc1?

dave.enyeart (Tue, 19 Jun 2018 11:41:14 GMT):
I thought near the end of each release, the process was to release a baseimage to scoop up the changes and get on the latest dependencies. System test has several weeks ahead still.

cbf (Tue, 19 Jun 2018 11:42:15 GMT):
it would be my preference that we have a couple weeks under our belt with a new baseimage

dave.enyeart (Tue, 19 Jun 2018 11:42:43 GMT):
It would be fine to keep v1.2 on 0.4.8.

cbf (Tue, 19 Jun 2018 11:42:58 GMT):
I guess if we get clean builds we can take the chance... I understand that we've already internalized the node upgrade

dave.enyeart (Tue, 19 Jun 2018 11:43:02 GMT):
We can move to 0.4.9 in v1.3.

cbf (Tue, 19 Jun 2018 11:43:10 GMT):
that would be my preference

dave.enyeart (Tue, 19 Jun 2018 11:44:14 GMT):
ok, let's do that

cbf (Tue, 19 Jun 2018 11:45:22 GMT):
+2

dave.enyeart (Tue, 19 Jun 2018 11:46:22 GMT):
@rameshthoomu would still like you to see what happened with amd64 third party images

cbf (Tue, 19 Jun 2018 11:47:05 GMT):
agree, once sorted I can run the multiarch

rameshthoomu (Tue, 19 Jun 2018 11:50:58 GMT):
I just re-triggered the amd64 thirdparty build job..

rameshthoomu (Tue, 19 Jun 2018 11:51:50 GMT):
last time it failed here `manifest for hyperledger/fabric-baseimage:amd64-0.4.9 not found`

cbf (Tue, 19 Jun 2018 11:52:25 GMT):
@rameshthoomu are you running the multiarch?

cbf (Tue, 19 Jun 2018 11:52:29 GMT):
as part of the release?

rameshthoomu (Tue, 19 Jun 2018 11:52:30 GMT):
no

cbf (Tue, 19 Jun 2018 11:52:38 GMT):
hmmm

rameshthoomu (Tue, 19 Jun 2018 11:52:47 GMT):
for now that's a manual task

cbf (Tue, 19 Jun 2018 11:52:54 GMT):
thought so

cbf (Tue, 19 Jun 2018 11:53:02 GMT):
the error above is odd though

cbf (Tue, 19 Jun 2018 11:53:16 GMT):
guess it means that there is no such image in nexus?

rameshthoomu (Tue, 19 Jun 2018 11:55:32 GMT):
yes that failure happend at a race condition.. to build thirdparty images, it's actually looking for the released baseimage version as the x86_64 build nodes are slow, it failed to build thirdparty build..

cbf (Tue, 19 Jun 2018 11:56:08 GMT):
k

rameshthoomu (Tue, 19 Jun 2018 11:59:53 GMT):
@cbf you can proceed with multiarch now.. We have all the images available in dockerhub

davidkel (Tue, 19 Jun 2018 14:35:46 GMT):
@dave.enyeart for the 1.3 release you will need to review the version of node.js in the base image again and probably update it.

dave.enyeart (Tue, 19 Jun 2018 14:37:28 GMT):
@davidkel node.js version was recently updated and included in 0.4.9. But @cbf and I decided it was not worth the risk to update fabric to 0.4.9. If there is a specific concern with the prior version of node.js we can re-evaluate.

dave.enyeart (Tue, 19 Jun 2018 14:37:28 GMT):
@davidkel node.js version was recently updated and included in baseimage 0.4.9. But @cbf and I decided it was not worth the risk to update fabric to 0.4.9. If there is a specific concern with the prior version of node.js we can re-evaluate.

dave.enyeart (Tue, 19 Jun 2018 14:37:28 GMT):
@davidkel node.js version was recently updated and included in baseimage 0.4.9. But @cbf and I decided it was not worth the risk to update fabric v1.2 to 0.4.9. If there is a specific concern with the prior version of node.js we can re-evaluate.

davidkel (Tue, 19 Jun 2018 14:39:41 GMT):
@dave.enyeart My feeling is that fabric should track the LTS versions of node and always deliver the latest LTS version as possible of node 8 to ensure it is current with bug and security fixes. In the future a more difficult decision will be when to move to the next LTS version of node which will be node v10 due to go LTS before the end of this year, but 8 will stay in LTS for a bit longer

andrew-coleman (Tue, 19 Jun 2018 14:47:30 GMT):
Has joined the channel.

cbf (Tue, 19 Jun 2018 15:48:12 GMT):
@davidkel that makes sense, and would be a good policy to track going forward... but for 1.2 making a change that this point might jeopardize the release. 1.3 is just 3 shortt months away;-(

vijay5378 (Tue, 19 Jun 2018 17:58:03 GMT):
Has joined the channel.

Vishal3152 (Wed, 20 Jun 2018 16:10:03 GMT):
Has joined the channel.

cbf (Wed, 20 Jun 2018 16:46:01 GMT):
@dave.enyeart can you ping me the link to the google doc with the epic status... can't find the link

dave.enyeart (Wed, 20 Jun 2018 16:46:44 GMT):
@cbf release google doc: https://docs.google.com/document/d/1prtMkLOkZZx7RYi_meb-3yY6lgFhISLQtx8AcSMDhdo/edit

cbf (Wed, 20 Jun 2018 16:49:24 GMT):
danke

jdfigure (Wed, 20 Jun 2018 17:36:22 GMT):
Has joined the channel.

cbf (Wed, 20 Jun 2018 18:33:34 GMT):
https://jira.hyperledger.org/browse/FAB-10748

paul.sitoh (Thu, 21 Jun 2018 09:47:46 GMT):
Has joined the channel.

paul.sitoh (Thu, 21 Jun 2018 09:48:17 GMT):
Does anyone know where I can get the roadmap for Fabric? I found one here https://wiki.hyperledger.org/projects/fabric/roadmap but it is very component specific. Is there one that is more overarching and high level -- e.g. statement like adding support for Big Data, version 2.x, something like that? I have also seen some from IBM but I don't know if it represents IBM's view of the Roadmap or Hyperledger's view (https://developer.ibm.com/code/2017/11/27/insights-roadmap-hyperledger-fabric-1-1/)

Senthil1 (Thu, 21 Jun 2018 11:03:28 GMT):
I was trying to rerun one of the manual test (i.e., data consistency check by adding a new peer -- https://gerrit.hyperledger.org/r/#/c/22583/) using the master branch. Now, I get the following error `error starting container: error starting container: Failed to generate platform-specific docker build: Failed to pull hyperledger/fabric-ccenv:amd64-1.2.0: API error (404): manifest for hyperledger/fabric-ccenv:amd64-1.2.0 not found"` `docker images` shows `hyperledger/fabric-ccenv` with tag `amd64-1.2.0-snapshot-fcb7b26`. As per the above error message, it is expecting the ccenv image with tag `amd64-1.2.0`. For now, I need to retag the image and try. Can someone look at this error?

bur (Thu, 21 Jun 2018 11:49:49 GMT):
Try to update your core.yaml. there use fabric-ccenv:latest

bur (Thu, 21 Jun 2018 11:49:49 GMT):
Try to update your core.yaml in the chaincode.builder section and use fabric-ccenv:latest

bur (Thu, 21 Jun 2018 11:52:12 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-release?msg=c6rCSuPBeqABWCnb4) @Senthil1

bur (Thu, 21 Jun 2018 11:52:12 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-release?msg=c6rCSuPBeqABWCnb4) @Senthil1 Try to update your core.yaml in the chaincode.builder section and use fabric-ccenv:latest

Senthil1 (Thu, 21 Jun 2018 12:38:36 GMT):
thanks @bur that should work..

rameshthoomu (Thu, 21 Jun 2018 14:01:45 GMT):
@Senthil1 @bur the above said change is merged with this change https://gerrit.hyperledger.org/r/#/c/22993/6/sampleconfig/core.yaml. You no need to manually edit the core.yaml to set project_version to :latest

rameshthoomu (Thu, 21 Jun 2018 14:01:45 GMT):
@Senthil1 @bur the above said change is merged with this patchset https://gerrit.hyperledger.org/r/#/c/22993/6/sampleconfig/core.yaml. You no need to manually edit the core.yaml to set project_version to :latest

bur (Thu, 21 Jun 2018 14:03:22 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-release?msg=SnpKZ4mMQdooRSxty) @rameshthoomu well, he might use a custom core.yaml :) but yes your are right, the "default" sampleconfig/core.yaml has that change already

Senthil1 (Thu, 21 Jun 2018 15:34:19 GMT):
@rameshthoomu I was using custom core.yaml as predicted by @bur After updating the core.yaml, data consistency test passed as expected.

Senthil1 (Thu, 21 Jun 2018 15:34:19 GMT):
@rameshthoomu I was using a custom core.yaml as predicted by @bur After updating the core.yaml, data consistency test passed as expected.

rameshthoomu (Thu, 21 Jun 2018 15:48:52 GMT):
ok. Good to know

cbf (Thu, 21 Jun 2018 20:59:16 GMT):
MERGE FREEZE -- while we cut the rc1 release, please refrain from merging any CRs thanks

BabyCodet (Thu, 21 Jun 2018 22:20:15 GMT):
Has joined the channel.

dave.enyeart (Fri, 22 Jun 2018 14:02:05 GMT):
To paste what was announced in #fabric-scrum ... fabric v1.2.0-rc1 has been cut, pushed to dockerhub, and tagged. fabric release branch release-1.2 has been created. release-1.2 branch will be used for any critical defects found in rc1 and targeted for the upcoming v1.2.0 release. master branch can be used for new v1.3 development. Merge freeze lifted, go and use master as usual. fabric-ca v1.2.0-rc1 is in final verification, will be pushed to dockerhub shortly. fabric-ca is still in MERGE FREEZE

cbf (Fri, 22 Jun 2018 16:43:49 GMT):
Fabric CA MERGE FREEZE END

dave.enyeart (Fri, 22 Jun 2018 22:18:17 GMT):
v1.2.0-rc1 has been announced on the fabric mailing list: https://lists.hyperledger.org/g/fabric/message/4001

abityildiz (Mon, 25 Jun 2018 06:47:37 GMT):
Has joined the channel.

GiuseppeLittera (Mon, 25 Jun 2018 20:07:30 GMT):
Has joined the channel.

david_dornseifer (Tue, 26 Jun 2018 07:45:04 GMT):
Hi, is there a way to figure out what image / tag on dockerhub is based on what commit - e.g. the 1.1 images on dockerhub are about a month old but the latest patch to the 1.1 release has been committed about five days ago

aatkddny (Tue, 26 Jun 2018 12:43:54 GMT):
Just as an FYI: If you follow the instructions on the mailing list to install it takes you to the regular "use this script to install" page. Doing the usual cut-n-paste into a terminal gives this though: ``` Error response from daemon: manifest for hyperledger/fabric-javaenv:1.2.0-rc1 not found Error response from daemon: No such image: hyperledger/fabric-javaenv:1.2.0-rc1 ``` It also doesn't install the samples ``` ===> Checking out v1.2.0-rc1 branch of hyperledger/fabric-samples error: pathspec 'v1.2.0-rc1' did not match any file(s) known to git. ``` Or for that matter the binaries.

aatkddny (Tue, 26 Jun 2018 12:43:54 GMT):
Just as an FYI: If you follow the instructions on the mailing list to install it takes you to the regular "use this script to install" page. Doing the usual cut-n-paste into a terminal gives this though: ``` Error response from daemon: manifest for hyperledger/fabric-javaenv:1.2.0-rc1 not found Error response from daemon: No such image: hyperledger/fabric-javaenv:1.2.0-rc1 ``` It also doesn't install the binaries. I see from the script that the -s is skipping samples, which confused me until I actually went and looked at it (As a user I'd expect that little fact to be in the documentation given how it is worded), but didn't see a switch to suppress the binaries.

aatkddny (Tue, 26 Jun 2018 12:43:54 GMT):
Just as an FYI: If you follow the instructions on the mailing list to install it takes you to the regular "use this script to install" page. Doing the usual cut-n-paste into a terminal gives this though: ``` Error response from daemon: manifest for hyperledger/fabric-javaenv:1.2.0-rc1 not found Error response from daemon: No such image: hyperledger/fabric-javaenv:1.2.0-rc1 ``` It also doesn't install the binaries. I see from the script that the -s is skipping samples, which confused me until I actually went and looked at it (As a user I'd expect that little fact to be in the documentation given how the same is worded), but didn't see a switch to suppress the binaries.

aatkddny (Tue, 26 Jun 2018 12:43:54 GMT):
Just as an FYI: If you follow the instructions on the mailing list to install it takes you to the regular "use this script to install" page. Doing the usual cut-n-paste into a terminal gives this though: ``` Error response from daemon: manifest for hyperledger/fabric-javaenv:1.2.0-rc1 not found Error response from daemon: No such image: hyperledger/fabric-javaenv:1.2.0-rc1 ``` It also doesn't install the binaries. I see from the script that the -s is skipping samples, which confused me until I actually went and looked at it (As a user I'd expect that little fact to be in the documentation given how the same is worded), but didn't see that the -s switch would suppress the binaries.

dave.enyeart (Tue, 26 Jun 2018 13:04:33 GMT):
@aatkddny Since there is no support for java chaincode that error is benign, we are trying to suppress it for the actual v1.2.0 release

aatkddny (Tue, 26 Jun 2018 13:06:15 GMT):
k. thx.

dave.enyeart (Tue, 26 Jun 2018 13:09:36 GMT):
@cbf What was the intent of -s? If I leave it off I get an error...

aatkddny (Tue, 26 Jun 2018 13:11:37 GMT):
suppress samples

aatkddny (Tue, 26 Jun 2018 13:12:07 GMT):
ergo counterintuitive.

cbf (Tue, 26 Jun 2018 13:15:35 GMT):
-s omits the cloning of the samples repo

cbf (Tue, 26 Jun 2018 13:15:44 GMT):
@dave.enyeart ^^

cbf (Tue, 26 Jun 2018 13:16:45 GMT):
not sure if it is counter=intuitive. If I already have them, why would I clone them again?

aatkddny (Tue, 26 Jun 2018 13:25:03 GMT):
well there are a few changes in 1.2 that i'd hope to see samples for. you know, little things like private data....

dave.enyeart (Tue, 26 Jun 2018 13:26:15 GMT):
@cbf from my trial... with -s I get the samples. if I omit -s, then I get an error:

dave.enyeart (Tue, 26 Jun 2018 13:26:18 GMT):
```$ curl -sSL http://bit.ly/2ysbOFE | bash 1.2.0-rc1 bash: 1.2.0-rc1: No such file or directory (23) Failed writing body```

cbf (Tue, 26 Jun 2018 13:27:14 GMT):
wrong omission

cbf (Tue, 26 Jun 2018 13:27:50 GMT):
you need the -s to pass the argument

cbf (Tue, 26 Jun 2018 13:28:24 GMT):
if you want to curl and omit the samples curl ... | bash -s 1.2.0-rc1 -s

dave.enyeart (Tue, 26 Jun 2018 13:29:01 GMT):
ah right... maybe that's why it is counter-intuitive, we could use some more info on the doc page

cbf (Tue, 26 Jun 2018 13:29:18 GMT):
@aatkddny then cd fabric-samples && git checkout release-1.2 && git pull

aatkddny (Tue, 26 Jun 2018 13:50:40 GMT):
sigh. i know i can do that, but you blithely inserted this into the mainline documentation. go look at the paragraph right above your edit then ask yourself whether that will cause any confusion. a simple one line that says "samples are suppressed until xxx" that can be removed when this goes GA is going to remove the WTF that everyone trying to use this goes through when it doesn't do what it says it is doing.

ctvbds (Wed, 27 Jun 2018 01:18:31 GMT):
Has joined the channel.

nhrishi (Wed, 27 Jun 2018 09:42:12 GMT):
Hi, Quick question, I see docker images are with tag 1.2.0-rc1 on docker hub. Typically, we have platform specific images (e.g. x86_64-1.1.0). Isn't that the case this time?

rameshthoomu (Wed, 27 Jun 2018 11:23:56 GMT):
@nhrishi rc1 images supports multi arch .. so you will see latest, 1.2.0-rc1 and platform specific images on docker hub...

nhrishi (Wed, 27 Jun 2018 12:11:12 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-release?msg=Nl013GyoAOzuNsCpac) @rameshthoomu Ok sure. Thanks!

pd93 (Wed, 27 Jun 2018 13:33:38 GMT):
@rameshthoomu Any advantage to using a platform specific image over a multi-arch image?

rameshthoomu (Wed, 27 Jun 2018 13:35:02 GMT):
@pd93 what you mean multi-arch image?

rameshthoomu (Wed, 27 Jun 2018 13:37:06 GMT):
ex; `hyperledger/fabric-peer:latest` image is compatible for both x and z platforms...

pd93 (Wed, 27 Jun 2018 13:38:00 GMT):
@rameshthoomu Is there an advantage/difference to running `amd64-1.2.0-rc1` rather than `1.2.0-rc1` if I know my target platform arch is `amd64`. Basically, I'm wondering why we still need platform specific images if the multi-arch image can be used everywhere.

rameshthoomu (Wed, 27 Jun 2018 13:38:27 GMT):
both are same...

rameshthoomu (Wed, 27 Jun 2018 13:40:12 GMT):
We have to publish arch based images to docker registry first before run multi-arch script

cbf (Wed, 27 Jun 2018 14:01:38 GMT):
@pd93 the multiarch manifests record both but the docker command will pull only the relevant one for your platform

pd93 (Wed, 27 Jun 2018 14:02:59 GMT):
Okay cool, thanks both :)

SmartContract2018 (Thu, 28 Jun 2018 20:11:59 GMT):
hello all

SmartContract2018 (Thu, 28 Jun 2018 20:12:33 GMT):
has fabric 1.2 been released?

grice_32 (Thu, 28 Jun 2018 20:36:58 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-release?msg=uAmpYJ7bXXo4oxQ5r) @SmartContract2018 v1.2.0-rc1 has been released

SmartContract2018 (Thu, 28 Jun 2018 20:49:07 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-release?msg=64z6SFRJGxMGgXahb) @grice_32 Thanks. Found it. Does anyone know if the private data state is stored in Couchdb as well (like the worldstate)?

grice_32 (Thu, 28 Jun 2018 20:53:02 GMT):
@SmartContract2018 It is in a private database on the peer.. called SideDB: https://hyperledger-fabric.readthedocs.io/en/release-1.2/private-data/private-data.html

SmartContract2018 (Thu, 28 Jun 2018 20:56:45 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-release?msg=6B88ieiSM8cgPToiQ) @grice_32 makes sense. Thanks. :-)

jwagantall (Thu, 28 Jun 2018 22:40:35 GMT):
User User_3 added by jwagantall.

qsmen (Fri, 29 Jun 2018 02:41:19 GMT):
hi, where can I find the difference or improvement from a lower release to a higher release? Thank you

qsmen (Fri, 29 Jun 2018 02:42:18 GMT):
or just tell the improvement of release 1.2 over release 1.1, thanks

dave.enyeart (Fri, 29 Jun 2018 04:32:30 GMT):
@qsmen see the v1.2.0-rc1 release announcement: https://lists.hyperledger.org/g/fabric/message/4001

dave.enyeart (Fri, 29 Jun 2018 04:37:22 GMT):
All - We are preparing to release v1.2.0. As part of that we are going to update baseimage to 0.4.10 (to pick up debian stretch for s390x), and then increment fabric and fabric-ca to utilize baseimage 0.4.10.

dave.enyeart (Fri, 29 Jun 2018 04:37:36 GMT):
CRs to release baseimage:

dave.enyeart (Fri, 29 Jun 2018 04:37:47 GMT):
https://gerrit.hyperledger.org/r/#/c/23857/

dave.enyeart (Fri, 29 Jun 2018 04:38:02 GMT):
https://gerrit.hyperledger.org/r/#/c/23859/

dave.enyeart (Fri, 29 Jun 2018 04:38:26 GMT):
@rameshthoomu @cbf @mastersingh24 ^^^^^^^

cbf (Fri, 29 Jun 2018 04:40:24 GMT):
+2 ed

cbf (Fri, 29 Jun 2018 04:40:35 GMT):
will let CI take its course

cbf (Fri, 29 Jun 2018 04:40:54 GMT):
are we going to omit the fabric-ca images?

cbf (Fri, 29 Jun 2018 04:40:59 GMT):
works for me

dave.enyeart (Fri, 29 Jun 2018 04:41:14 GMT):
what do you mean omit?

cbf (Fri, 29 Jun 2018 04:41:16 GMT):
but I won't have time this morning to work on that

cbf (Fri, 29 Jun 2018 04:41:28 GMT):
as @mastersingh24 suggested

cbf (Fri, 29 Jun 2018 04:41:54 GMT):
eg not publish them

dave.enyeart (Fri, 29 Jun 2018 04:42:26 GMT):
i think we should be consistent with what we've done for 1.1.0 and 1.2.0-rc1

dave.enyeart (Fri, 29 Jun 2018 04:42:36 GMT):
make changes in v1.3

mastersingh24 (Fri, 29 Jun 2018 04:42:55 GMT):
So I'm still not sure why we are changing baseimage to use debian:stretch at this late date?

mastersingh24 (Fri, 29 Jun 2018 04:43:20 GMT):
@dave.enyeart - but being consistently bad is not a good thing ;)

cbf (Fri, 29 Jun 2018 04:43:42 GMT):
@mastersingh24 basically, as a result of removing lts for jessie for s390x the packages are no longer available

dave.enyeart (Fri, 29 Jun 2018 04:43:44 GMT):
i guess i don't understand the proposal of what you want to change for v1.2.0

mastersingh24 (Fri, 29 Jun 2018 04:44:02 GMT):
stop publishing the stupid fabric-ca + fabric images

dave.enyeart (Fri, 29 Jun 2018 04:44:21 GMT):
the fabric-ca sample instructions uses them

cbf (Fri, 29 Jun 2018 04:44:25 GMT):
@dave.enyeart doing this would remove the serialization dependency between fabric and fabric-ca

mastersingh24 (Fri, 29 Jun 2018 04:44:43 GMT):
it's a crappy sample anyway .... but easily updated to tell people how to build the images

dave.enyeart (Fri, 29 Jun 2018 04:45:15 GMT):
i created a jira for that - https://jira.hyperledger.org/browse/FAB-10930 - but thought it was a v1.3 task to re-work the sample instructions

mastersingh24 (Fri, 29 Jun 2018 04:45:44 GMT):
just more baggage for us to carry .... but I'm fine with minimizing the impact on 1.2

mastersingh24 (Fri, 29 Jun 2018 04:46:04 GMT):
I'm still not sure why we are moving to Stretch and getting rid of the baseimage changes

dave.enyeart (Fri, 29 Jun 2018 04:46:49 GMT):
because debian stretch was blocking s390x, which some people are interested in

dave.enyeart (Fri, 29 Jun 2018 04:46:49 GMT):
because debian jessie was blocking s390x, which some people are interested in

dave.enyeart (Fri, 29 Jun 2018 04:47:22 GMT):
and we thought it would be better to be consistent across x86 and s390x releases, rather than do one-offs for each

cbf (Fri, 29 Jun 2018 04:48:37 GMT):
or adding more change at this point to the release

mastersingh24 (Fri, 29 Jun 2018 04:48:41 GMT):
``` apt-get update apt-get -y install softhsm2 ``` in testenv is making us do a last minute update?

dave.enyeart (Fri, 29 Jun 2018 04:48:43 GMT):
all testing has been on baseimage 0.4.8, so we reverted some recent baseimage changes to make 0.4.10 look just like 0.4.8, except with the new debian stretch

rameshthoomu (Fri, 29 Jun 2018 04:49:05 GMT):
@mastersingh24 also blocking sdk-go, sdk-chaincode-node, sdk-node s390x builds and I see people are complaining about it and asking for an update

rameshthoomu (Fri, 29 Jun 2018 04:49:24 GMT):
@mastersingh24 even in tools image

cbf (Fri, 29 Jun 2018 04:49:37 GMT):
own goal

mastersingh24 (Fri, 29 Jun 2018 04:49:40 GMT):
There's something wrong then with the way we are building things

cbf (Fri, 29 Jun 2018 04:49:53 GMT):
yes, and we are fixing that for 1.3;-)

mastersingh24 (Fri, 29 Jun 2018 04:52:53 GMT):
I suppose we are ok given debian:stretch is equivalent to ubuntu:xenial

mastersingh24 (Fri, 29 Jun 2018 04:53:25 GMT):
But I'm not sure why we are reverting all of the other changes we made

mastersingh24 (Fri, 29 Jun 2018 04:53:45 GMT):
seems orthogonal to me

dave.enyeart (Fri, 29 Jun 2018 04:54:02 GMT):
because the couchdb and node js updates havent been well tested

dave.enyeart (Fri, 29 Jun 2018 04:54:16 GMT):
no tested fabric has used those updates

dave.enyeart (Fri, 29 Jun 2018 04:54:32 GMT):
if we had some more days before release, we would have kept them

mastersingh24 (Fri, 29 Jun 2018 04:54:46 GMT):
That is NOT true .... we added the Node.js update specifically because they said they had tested with them

mastersingh24 (Fri, 29 Jun 2018 04:54:58 GMT):
You mean system test?

dave.enyeart (Fri, 29 Jun 2018 04:55:02 GMT):
right

mastersingh24 (Fri, 29 Jun 2018 04:55:09 GMT):
I seriously give up

mastersingh24 (Fri, 29 Jun 2018 04:56:05 GMT):
And the couch changes make sense to me ..... I don't see how they make any different in testing

mastersingh24 (Fri, 29 Jun 2018 04:56:05 GMT):
And the couch changes make sense to me ..... I don't see how they make any difference in testing

mastersingh24 (Fri, 29 Jun 2018 04:56:18 GMT):
And the Node chaincode guys have been running tests with the update

dave.enyeart (Fri, 29 Jun 2018 04:56:31 GMT):
i created baseimage 0.4.9 June 19th to move up to these changes, but that was rejected

mastersingh24 (Fri, 29 Jun 2018 04:57:43 GMT):
ok

mastersingh24 (Fri, 29 Jun 2018 04:57:43 GMT):
ok, merging the baseimage CRs now

cbf (Fri, 29 Jun 2018 04:58:12 GMT):
Gari, had we started June 1 would have been different... I am tired of us making changes this late in the cycle

mastersingh24 (Fri, 29 Jun 2018 04:58:16 GMT):
I'm going to change all of this crap for 1.3 then ..... this is shitty

cbf (Fri, 29 Jun 2018 04:58:24 GMT):
yes, please

mastersingh24 (Fri, 29 Jun 2018 04:58:24 GMT):
We are doing it right now

mastersingh24 (Fri, 29 Jun 2018 04:58:32 GMT):
;)

mastersingh24 (Fri, 29 Jun 2018 04:58:44 GMT):
No one maintains the baseimage .... so it needs to go

mastersingh24 (Fri, 29 Jun 2018 04:59:01 GMT):
OK ... as long as we can change this stupid way things are built for 1.3 I'm ok

mastersingh24 (Fri, 29 Jun 2018 04:59:11 GMT):
buildenv, testenv, bsenv ;)

cbf (Fri, 29 Jun 2018 04:59:14 GMT):
yes, I was *this* close to just cutting s390x images instead of adopting stretch

mastersingh24 (Fri, 29 Jun 2018 04:59:52 GMT):
Given we test with xenial, stretch should be minimal risk from the fabric side ... not sure about s390 side ;)

cbf (Fri, 29 Jun 2018 05:00:52 GMT):
but since SK was going to be building with this change anyway, makes more sense to have the community build consistent

mastersingh24 (Fri, 29 Jun 2018 05:01:28 GMT):
Why was SK building with this change?

mastersingh24 (Fri, 29 Jun 2018 05:01:38 GMT):
Again ... there were other ways to solve this

mastersingh24 (Fri, 29 Jun 2018 05:01:41 GMT):
But fine

cbf (Fri, 29 Jun 2018 05:01:42 GMT):
because they cannot build without it

mastersingh24 (Fri, 29 Jun 2018 05:02:00 GMT):
v1.2 or v1.1 images?

cbf (Fri, 29 Jun 2018 05:02:04 GMT):
1.2

cbf (Fri, 29 Jun 2018 05:02:17 GMT):
(actually, they may have issues with 1.1)

mastersingh24 (Fri, 29 Jun 2018 05:02:27 GMT):
IBP is 1.1

cbf (Fri, 29 Jun 2018 05:02:29 GMT):
if they are still building

cbf (Fri, 29 Jun 2018 05:02:45 GMT):
SK is adopting 1.2 AFAIK

mastersingh24 (Fri, 29 Jun 2018 05:02:54 GMT):
not in IBP

mastersingh24 (Fri, 29 Jun 2018 05:03:26 GMT):
anyway ... I'm done arguing ;) I see your points

cbf (Fri, 29 Jun 2018 21:05:05 GMT):
fucking flight canceled

RealDeanZhao (Mon, 02 Jul 2018 02:38:49 GMT):
Has joined the channel.

JonathanLevi (Tue, 03 Jul 2018 12:31:44 GMT):
It took me 2 days to leave Amsterdam

JonathanLevi (Tue, 03 Jul 2018 12:32:32 GMT):
Nothing to do with the coffee! I had a similar "f.f.canceled" experience.

cbf (Tue, 03 Jul 2018 19:05:33 GMT):
lol

sstone1 (Wed, 04 Jul 2018 15:08:09 GMT):
@cbf fabric v1.2 seems to have been published to docker hub and the docs sites... but no npm modules for the two clients or the shim! when are they likely to get published?

medhak19 (Thu, 05 Jul 2018 06:02:59 GMT):
Has joined the channel.

mbwhite (Thu, 05 Jul 2018 08:13:53 GMT):
^ just checked (9am UK Thursday) - no change on the npm modules

hvandurme (Thu, 05 Jul 2018 08:36:25 GMT):
Has joined the channel.

donsonZhang (Thu, 05 Jul 2018 09:40:41 GMT):
when i updating a Channel Configuration use java sdk, the BatchTimeout:timeout can be updated success and valid; but when i update BatchSize:max_message_count, also can be updated success,but not go into effect example, begin the BatchSize:max_message_count = 10, and update it to 30, now the channel config is 30, but the block max message count is still 10 when i restart the orderer node , the new max_message_count=30 is valid so update channel config for the BatchSize:max_message_count is a bug?

donsonZhang (Thu, 05 Jul 2018 09:41:08 GMT):
version is the fabric release 1.1

sstone1 (Thu, 05 Jul 2018 09:49:21 GMT):
@donsonZhang suggest you ask in #fabric-sdk-java

donsonZhang (Thu, 05 Jul 2018 09:49:55 GMT):
this a bug for fabric release1.1

donsonZhang (Thu, 05 Jul 2018 09:50:31 GMT):
channel config is update success,but for fabric it is not load in memory

cbf (Thu, 05 Jul 2018 10:59:48 GMT):
@sstone1 we haven't been doing that, as everything is pegged to latest -- though I suppose we could do so

davidkel (Thu, 05 Jul 2018 11:15:40 GMT):
@cbf the node modules should be tagged as 1.2 (ie not have a -snapshot value after) and then latest can reference that version. Only the unstable tag should reference a snapshot version. Currently for some odd reason latest points to 1.0.8

sstone1 (Thu, 05 Jul 2018 12:03:00 GMT):
+1 on what dave said, we should really be publishing proper releases across all of the SDKs as well as the core components

mbwhite (Thu, 05 Jul 2018 12:03:06 GMT):
FYI fabric-shim points to 'dist-tags': { latest: '1.1.2', unstable: '1.2.0-snapshot.4' },

sstone1 (Thu, 05 Jul 2018 12:03:40 GMT):
`latest` is just an alias and you don't really want an alias to a `snapshot` version as npm will end up embedding the snapshot version into your package.json

sstone1 (Thu, 05 Jul 2018 12:04:42 GMT):
it's also a bit confusing - going by the latest published versions, i want 1.2.0 of the peer, 1.2.0-snapshot.79 of the client SDK, 1.2.0-snapshot.4 of the shim

ongkhaiwei (Thu, 05 Jul 2018 13:48:01 GMT):
Has joined the channel.

sstone1 (Thu, 05 Jul 2018 16:04:14 GMT):
@cbf any news/comments? causing others confusion - see #fabric channel

adave (Thu, 05 Jul 2018 16:28:10 GMT):
Has joined the channel.

cbf (Thu, 05 Jul 2018 22:23:52 GMT):
I have pushed CRs for 1.2.0 for sdk-node, chaincode-node

cbf (Thu, 05 Jul 2018 22:24:03 GMT):
java I need to talk to rick

ibmamnt (Fri, 06 Jul 2018 00:46:45 GMT):
Has joined the channel.

ztanaka1971 (Fri, 06 Jul 2018 02:00:40 GMT):
Has joined the channel.

JOYELIN (Fri, 06 Jul 2018 02:29:00 GMT):
Has joined the channel.

am (Fri, 06 Jul 2018 03:31:53 GMT):
Hello, is there are upgrade guide available for upgrading from hyperledger fabric 1.1 to 1.2 ? thanks in advance

HoneyShah (Fri, 06 Jul 2018 03:35:37 GMT):
Has joined the channel.

ztanaka1971 (Fri, 06 Jul 2018 07:21:31 GMT):
@am https://hyperledger-fabric.readthedocs.io/en/release-1.2/upgrade_to_newest_version.html

IgorSim (Fri, 06 Jul 2018 10:15:21 GMT):
hi, one question about 1.2 version, is this going to be LTS version?

iserikov (Fri, 06 Jul 2018 15:54:54 GMT):
Has joined the channel.

grice_32 (Fri, 06 Jul 2018 19:47:16 GMT):
Is there a list of supported Linux versions of Fabric? I have a client out of Canada wanting to use Red Hat 7.5 on s390x and I can't seem to a list of supported versions. I would think it would be fine, but I want to make sure.

mastersingh24 (Sun, 08 Jul 2018 02:02:10 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-release?msg=qzoniKfa6GxA2uGSN) @IgorSim No

greg2git (Sun, 08 Jul 2018 13:37:08 GMT):
@mastersingh24 @IgorSim that begs the question: why not? a naive follow-up would be: since 2.0 will come out before long (5 years) support would end?

sstone1 (Sun, 08 Jul 2018 19:15:06 GMT):
@cbf @mastersingh24 thanks for publishing the npm modules for 1.2.0! can we update the release process so that whenever a new version of fabric is published, we also publish the npm modules?

mastersingh24 (Sun, 08 Jul 2018 21:38:31 GMT):
@greg2git - a few reasons: 1) We have *yet* to determine our overall LTS strategy in terms of of how long we'll support LTS versions ... most certainly it will not be 5 years tho 2) It is still way too early in terms of features / functionality and the overall market to actually declare LTS for anything we've published to date

mastersingh24 (Sun, 08 Jul 2018 21:40:30 GMT):
@sstone1 - For the SDKs, they have traditionally lagged a bit behind the fabric / fabric-ca release dates. For chaincode, we

mastersingh24 (Sun, 08 Jul 2018 21:40:30 GMT):
@sstone1 - For the SDKs, they have traditionally lagged a bit behind the fabric / fabric-ca release dates. For chaincode, we had a logistics problem ... should be resolved for future releases

gouthamkrishna31 (Mon, 09 Jul 2018 09:40:07 GMT):
Has joined the channel.

davidorr (Tue, 10 Jul 2018 00:03:32 GMT):
Has joined the channel.

pasimoes (Tue, 10 Jul 2018 15:32:45 GMT):
Has joined the channel.

alokmatta (Tue, 10 Jul 2018 23:44:52 GMT):
Has joined the channel.

wangdong (Wed, 11 Jul 2018 03:29:34 GMT):
Has joined the channel.

mynet (Wed, 11 Jul 2018 04:22:09 GMT):
Has joined the channel.

NoLimitHoldem (Wed, 11 Jul 2018 06:16:04 GMT):
Has joined the channel.

chrisg (Wed, 11 Jul 2018 16:24:43 GMT):
Has joined the channel.

ddurnev (Tue, 17 Jul 2018 07:12:19 GMT):
Has joined the channel.

donsonZhang (Tue, 17 Jul 2018 12:28:00 GMT):
I found a directory named config, it has three file: core.yaml，configtx.yaml and orderer.yaml. so when this directory generate and how to use there files?

Tolotos (Tue, 17 Jul 2018 19:38:55 GMT):
Has joined the channel.

qsmen (Wed, 18 Jul 2018 02:32:38 GMT):
several typical networks are given in the link https://hyperledger-fabric.readthedocs.io/en/release-1.2/network/network.html, if the corresponding config.yaml are given, it would be greater.

angel-ibm (Wed, 18 Jul 2018 08:18:01 GMT):
Has joined the channel.

donsonZhang (Wed, 18 Jul 2018 11:52:15 GMT):
when fabric to support boot and manage Fabric Chaincode container via Kubernetes?

qsmen (Thu, 19 Jul 2018 01:01:30 GMT):
configtx.yaml is generated by the network manager who design the whole network and is used to generate order genesis block, channeltx which is then used to create a channel

donsonZhang (Thu, 19 Jul 2018 01:20:38 GMT):
when fabric to support boot and manage Fabric Chaincode container via Kubernetes?

donsonZhang (Thu, 19 Jul 2018 01:20:40 GMT):
when fabric to support boot and manage Fabric Chaincode container via Kubernetes?

donsonZhang (Thu, 19 Jul 2018 01:20:42 GMT):
when fabric to support boot and manage Fabric Chaincode container via Kubernetes?

Hz (Thu, 19 Jul 2018 03:53:52 GMT):
Has joined the channel.

pandagopal (Fri, 20 Jul 2018 05:04:21 GMT):
Has joined the channel.

pandagopal (Fri, 20 Jul 2018 05:04:38 GMT):
When will the call sart ?

rory83 (Fri, 20 Jul 2018 06:24:54 GMT):
Has joined the channel.

thellimist (Fri, 20 Jul 2018 07:09:24 GMT):
Has joined the channel.

thellimist (Fri, 20 Jul 2018 07:09:53 GMT):
is Zero knowledge proofs implemented yet on fabric?

dave.enyeart (Fri, 20 Jul 2018 11:56:39 GMT):
@thellimist there are various aspects of Zero knowledge. Zero knowledge for transactor anonymity (Identity Mixer) is in development and will likely be available in Q3, followed shortly thereafter by zero knowledge for token/asset transfer.

thellimist (Fri, 20 Jul 2018 12:37:14 GMT):
@dave.enyeart is Private Transactions released yet? https://www.ibm.com/developerworks/cloud/library/cl-blockchain-private-confidential-transactions-hyperledger-fabric-zero-knowledge-proof/index.html

dave.enyeart (Fri, 20 Jul 2018 12:56:39 GMT):
yes, Private Data was released in v1.2: http://hyperledger-fabric.readthedocs.io/en/latest/private-data/private-data.html

PickettMS (Sat, 21 Jul 2018 23:14:30 GMT):
Has joined the channel.

PickettMS (Sat, 21 Jul 2018 23:15:05 GMT):
is this a good channel to ask general fabric questions?

PickettMS (Sat, 21 Jul 2018 23:16:05 GMT):
im trying to construct an idea using Hyperledger fabric and i want to make sure i was structuring everything properly...

dave.enyeart (Sun, 22 Jul 2018 03:51:33 GMT):
@PickettMS fabric-questions is probably a better channel for general questions

bobzhao (Mon, 23 Jul 2018 15:27:49 GMT):
Has joined the channel.

iamksseo (Tue, 24 Jul 2018 01:52:55 GMT):
Has joined the channel.

davidkel (Tue, 24 Jul 2018 14:02:11 GMT):
I was wondering what the process was for being able to release a new version of the node-sdk (for example a 1.2.1 release). I guess the first step is to set the package.json to 1.2.1 then tag that particular revision. Does tagging require special permission and if so who has that ability ?

rameshthoomu (Tue, 24 Jul 2018 14:04:36 GMT):
@davidkel please see the release process document on fabric-sdk-node.. https://docs.google.com/document/d/12IpQnREUoJEUj2pF2z-0Up55geItFd94fcsbAkPacTg/edit#heading=h.auejwwem7iy4

rameshthoomu (Tue, 24 Jul 2018 14:05:10 GMT):
I think @bretharrison has that ability to create a tag..

davidkel (Tue, 24 Jul 2018 14:05:46 GMT):
@rameshthoomu just Bret for the sdk ? how about for the fabric-shim ?

rameshthoomu (Tue, 24 Jul 2018 14:06:15 GMT):
Not sure. Check with Bret

davidkel (Tue, 24 Jul 2018 14:08:22 GMT):
@rameshthoomu if I want to start publishing 1.2.1 snapshots on merge builds do we need a new jenkins job for that ? I changed the package.json to 1.2.1-snapshot but no snapshot builds are published

rameshthoomu (Tue, 24 Jul 2018 14:12:56 GMT):
did the patch merged?

davidkel (Tue, 24 Jul 2018 14:13:42 GMT):
It did

rameshthoomu (Tue, 24 Jul 2018 14:13:54 GMT):
ok let me check

davidkel (Tue, 24 Jul 2018 14:13:58 GMT):
thanks

rameshthoomu (Tue, 24 Jul 2018 14:20:05 GMT):
@davidkel could you please refer the package.json change which got merged recently.

davidkel (Tue, 24 Jul 2018 14:22:15 GMT):
Ah rats, I did it at the top level, not on the individual package levels

davidkel (Tue, 24 Jul 2018 14:22:15 GMT):
Ah rats, I did it at the top level, not on the individual package levels, thought I had done all 3

rameshthoomu (Tue, 24 Jul 2018 14:28:26 GMT):
yes.. will you submit change now?

rameshthoomu (Tue, 24 Jul 2018 14:28:49 GMT):
the merge jobs of sdk-node and chaincode-node jobs push unstable versions from snapshot releases..

davidkel (Tue, 24 Jul 2018 14:36:16 GMT):
I will submit a change later, thanks ramesh

AleksMarts (Tue, 24 Jul 2018 16:40:00 GMT):
Has joined the channel.

nhrishi (Wed, 25 Jul 2018 12:34:51 GMT):
baseimage

dave.enyeart (Fri, 27 Jul 2018 15:58:30 GMT):
@jyellick I know you wanted to get the FAB-11094 fix released into a v1.2.1 sooner than later. @yacovm I believe you were also looking to get a fix into v1.2.1, is that still true and if so do you have a timeframe for the fix?

yacovm (Fri, 27 Jul 2018 17:03:49 GMT):
No, i didn't need to fix

yacovm (Fri, 27 Jul 2018 17:03:55 GMT):
Found a workaround

dave.enyeart (Fri, 27 Jul 2018 17:05:26 GMT):
ok @jyellick that leaves FAB-11094 as the major fix for v1.2.1... did you get any more feedback on how prevalent the problem is and how urgent the fix is?

jyellick (Fri, 27 Jul 2018 17:34:30 GMT):
@dave.enyeart I haven't gotten any additional feedback as of yet, will check in again now.

raccoonrat (Mon, 30 Jul 2018 01:49:39 GMT):
Has joined the channel.

shubhamvrkr (Mon, 30 Jul 2018 04:23:40 GMT):
Has joined the channel.

zmaro (Fri, 03 Aug 2018 15:26:10 GMT):
Has joined the channel.

tijohnson (Mon, 06 Aug 2018 18:31:58 GMT):
@jtclark @rameshthoomu I have received a security alert from GitHub for hyperledger/composer repo (lodash < 4.17.5) Is this something we need to address?

jtclark (Mon, 06 Aug 2018 18:32:48 GMT):
@tijohnson we should probably open a JIRA item against the composer component and mention what the vulerability is

jtclark (Mon, 06 Aug 2018 18:33:00 GMT):
i.e. a bug

rameshthoomu (Mon, 06 Aug 2018 18:42:27 GMT):
@tijohnson I am not sure what that alert is. You can also post the alert information in #composer channel

greg2git (Wed, 08 Aug 2018 23:12:34 GMT):
this statement in the documentation http://hyperledger-fabric.readthedocs.io/en/latest/chaincode4noah.html#system-chaincode reads like a planned feature release: "Note that stop and start lifecycle transactions have not yet been implemented." is there a FAB where i could find more details on it?

dave.enyeart (Thu, 09 Aug 2018 03:30:12 GMT):
@greg2git See https://jira.hyperledger.org/browse/FAB-5781 you'll see that design had started but no development planned as of yet

bh4rtp (Fri, 10 Aug 2018 07:55:34 GMT):
will v1.3.0 be released as scheduled in the end of september?

dave.enyeart (Fri, 10 Aug 2018 11:38:24 GMT):
yes, that is the timeframe, exact date depends on test results from builds in that timeframe

mastersingh24 (Fri, 10 Aug 2018 13:18:45 GMT):
as does exact content .... which should be determined by end of August (meaning which things will actually make it)

gauthampamu (Fri, 10 Aug 2018 17:11:59 GMT):
Has joined the channel.

vijay5378 (Mon, 13 Aug 2018 10:11:11 GMT):
Hi folks. Would configtx.yaml of 1.2 work with 1.1? The reason I ask is because, I can define Policies for an application in 1.2 (As provided in the sample file). However, when I keep the policies and try to construct a channel in 1.1, I get an error -` * 'Application' has invalid keys: Policies * 'Profiles[devproject002Channel].Application' has invalid keys: Policies panic: Error unmarshaling config into struct: 2 error(s) decoding:`

hackorama (Mon, 13 Aug 2018 18:42:30 GMT):
Has joined the channel.

kosullivan_sita (Tue, 14 Aug 2018 08:46:11 GMT):
Has joined the channel.

mulser (Tue, 14 Aug 2018 09:45:22 GMT):
Has joined the channel.

wonderfan (Wed, 15 Aug 2018 05:42:42 GMT):
Has joined the channel.

tijohnson (Thu, 16 Aug 2018 22:33:42 GMT):
@all JIRA will be unavailable 7-10EST

ping40 (Fri, 17 Aug 2018 01:52:23 GMT):
Has joined the channel.

albert.lacambra (Mon, 20 Aug 2018 13:25:48 GMT):
Has joined the channel.

albert.lacambra (Mon, 20 Aug 2018 13:26:31 GMT):
When is the 1.3 release planned?

dave.enyeart (Mon, 20 Aug 2018 14:27:35 GMT):
v1.3 is planned for end of september

bdjidi (Tue, 21 Aug 2018 22:48:59 GMT):
Has joined the channel.

nukulsharma (Fri, 24 Aug 2018 09:04:53 GMT):
Has joined the channel.

StefanRehm (Sat, 25 Aug 2018 22:04:24 GMT):
Has joined the channel.

kheung (Mon, 27 Aug 2018 01:25:37 GMT):
Has joined the channel.

dave.enyeart (Tue, 28 Aug 2018 03:49:19 GMT):
@rameshthoomu Have you had a good test with baseimage 0.4.11? Shall we go ahead and merge https://gerrit.hyperledger.org/r/#/c/25711/ ?

rameshthoomu (Tue, 28 Aug 2018 04:04:04 GMT):
Tested in sandbox but I see byfn with couchdb are failing

rameshthoomu (Tue, 28 Aug 2018 04:04:22 GMT):
Will test again tomorrow and let you know the update

Saachi (Tue, 28 Aug 2018 06:46:50 GMT):
Has joined the channel.

nrohith (Tue, 28 Aug 2018 14:17:49 GMT):
Has joined the channel.

rickr (Tue, 28 Aug 2018 16:47:26 GMT):
Right now JSDK docker compose I have ``` ccenv: image: hyperledger/fabric-ccenv${IMAGE_TAG_FABRIC} ``` I _think_ this handles both the Golang and Node chaincode as both seem work. What is/will be needed for Java chaincode to work ? @gennadyl @dave.enyeart I want people who try the JSDK to just start up it's docker-compose have all three supported chaincodes available.

rickr (Tue, 28 Aug 2018 16:47:26 GMT):
Right now JSDK docker compose I have ``` ccenv: image: hyperledger/fabric-ccenv${IMAGE_TAG_FABRIC} ``` I _think_ this handles both the Golang and Node chaincode as both seem to work. What is/will be needed for Java chaincode to work ? @gennadyl @dave.enyeart I want people who try the JSDK to just start up it's docker-compose have all three supported chaincode environments available.

gennadyl (Tue, 28 Aug 2018 16:47:27 GMT):
Has joined the channel.

gennadyl (Tue, 28 Aug 2018 16:49:29 GMT):
@rickr javaenv image used both for build chaincode and run it

rickr (Tue, 28 Aug 2018 16:49:48 GMT):
?

rickr (Tue, 28 Aug 2018 16:50:56 GMT):
I don't want user to build anything. JSDK and NSDK should at most just need to have it referenced in their docker-compose.

rickr (Tue, 28 Aug 2018 16:50:56 GMT):
I don't want the user to build anything. JSDK and NSDK should at most just need to have it referenced in their docker-compose.

rickr (Tue, 28 Aug 2018 16:50:56 GMT):
I don't want the user to build anything. JSDK and NSDK should _at most_ just need to have it referenced in their docker-compose.

rickr (Tue, 28 Aug 2018 16:50:56 GMT):
I don't want the user to build anything. JSDK and NSDK should _at most_ just need to have it (java chaincode image) referenced in their docker-compose.

dave.enyeart (Tue, 28 Aug 2018 16:54:24 GMT):
You don't need ccenv in docker compose, even for go chaincode

rickr (Tue, 28 Aug 2018 16:54:48 GMT):
right nothing you said is new there

rickr (Tue, 28 Aug 2018 16:55:34 GMT):
If you look again @dave.enyeart I'm asking what will I need for java chaincode !

rickr (Tue, 28 Aug 2018 16:56:10 GMT):
Ok so will I need nothing for java ?

dave.enyeart (Tue, 28 Aug 2018 16:57:49 GMT):
I believe you just need hyperledger/fabric-javaenv image available... you can either build that or pull it from nexus

dave.enyeart (Tue, 28 Aug 2018 16:58:50 GMT):
to build, you have to use `./gradlew buildImage` from fabric-chaincode-java root directory

rickr (Tue, 28 Aug 2018 16:59:09 GMT):
Ok -- that would be a start. Can someone give me a `snippet` I can put in my docker compose to have it working ?

rickr (Tue, 28 Aug 2018 16:59:49 GMT):
@dave.enyeart yes I know I've done that -- I don't want user's to have to do that

rickr (Tue, 28 Aug 2018 17:02:02 GMT):
And if we do pull it from Nexus is that where we plan to have for the release .. or is that just a _temporary_ place until the release

dave.enyeart (Tue, 28 Aug 2018 17:05:18 GMT):
as we wouldn't expect most people to have fabric-chaincode-java environment, the recommendation would be to pull from dockerhub (for regular releases) or nexus (while developing a release)

rickr (Tue, 28 Aug 2018 17:06:58 GMT):
ok so drum role please :: give me what I can use now I publish SNAPSHOT images and if user get the sdk I would like it work

dave.enyeart (Tue, 28 Aug 2018 17:08:39 GMT):
I'd have to defer that question to @rameshthoomu , he added the nexus pull in CI. I suspect regular users could do something similar.

rameshthoomu (Tue, 28 Aug 2018 17:10:46 GMT):
@rickr I think it's better to alter docker-compose file to pull javenv image from nexus instead from hyperledger dockerhub https://github.com/hyperledger/fabric-sdk-java/blob/master/src/test/fixture/sdkintegration/docker-compose.yaml#L176

rameshthoomu (Tue, 28 Aug 2018 17:11:54 GMT):
nexus3.hyperledger.org:10001/fabric-javaenv${IMAGE_TAG_FABRIC_JAVAENV}

dave.enyeart (Tue, 28 Aug 2018 17:13:22 GMT):
why does ccenv (or javaenv) need to be in docker-compose at all? it's not in the byfn docker compose.

rickr (Tue, 28 Aug 2018 17:14:07 GMT):
@dave.enyeart yes -- I just removed that and confirmed I don't need that for Node or GO chaincode to run

rickr (Tue, 28 Aug 2018 17:14:45 GMT):
Which to be frank is news to me

rickr (Tue, 28 Aug 2018 17:15:35 GMT):
So I'd be very happy even for now I could have a snippet of docker compose that would pull it from anywhere .. even if I need to update it after the release

dave.enyeart (Tue, 28 Aug 2018 17:15:45 GMT):
docker compose doesn't start a ccenv container. the peer implicitly uses the image

rickr (Tue, 28 Aug 2018 17:16:10 GMT):
IMO Java _should_ be no different

dave.enyeart (Tue, 28 Aug 2018 17:16:15 GMT):
agreed

dave.enyeart (Tue, 28 Aug 2018 17:16:22 GMT):
you just need to have the image local

dave.enyeart (Tue, 28 Aug 2018 17:16:33 GMT):
prior to starting the docker compose network

rameshthoomu (Tue, 28 Aug 2018 17:18:11 GMT):
refer this https://gerrit.hyperledger.org/r/#/c/25900/3/jjb/fabric-sdk-java/shell/include-raw-fabric-sdk-java-end-to-end-tests.sh@56

gennadyl (Wed, 29 Aug 2018 09:26:24 GMT):
Difference between java and rest chaincodes that java uses iavaenv image instead ccenv image. javaenv image should not be local, once it in docker hub, it will be pulled automatically, same way as ccenv image pulled. Another difference that as runtime java uses same javaenv images as well. Java chaincode uses chaincode.java.runtime image both for build and runtime.

gennadyl (Wed, 29 Aug 2018 09:28:34 GMT):
@rickr You don't need to pull manually any of ccenv or javaenv images (for java it will become true once image published on docker hub). The only reason to do this is to improve performance.

rangak (Wed, 29 Aug 2018 19:42:57 GMT):
rangak

mharris (Thu, 30 Aug 2018 09:45:23 GMT):
Has joined the channel.

vwagner (Thu, 30 Aug 2018 20:03:19 GMT):
Has joined the channel.

zerppen (Fri, 31 Aug 2018 03:42:34 GMT):
Has joined the channel.

dave.enyeart (Fri, 31 Aug 2018 13:43:09 GMT):
@rameshthoomu How is baseimage testing going? We need to finalize baseimage as soon as possible for v1.3 system testing. The log you mentioned in https://gerrit.hyperledger.org/r/#/c/25711/ is not available.

rameshthoomu (Fri, 31 Aug 2018 16:11:20 GMT):
@dave.enyeart Observed byfn tests with couchdb are working as expected but when I execute them as a whole test suite (e2e-daily job) I see byfn with couchdb tests are failing

sureshtedla (Fri, 31 Aug 2018 16:26:03 GMT):
Has joined the channel.

dave.enyeart (Fri, 31 Aug 2018 16:32:14 GMT):
@rameshthoomu Can you point me to the failed test log, as well as the associated peer log?

rameshthoomu (Fri, 31 Aug 2018 16:50:48 GMT):
sure.. will do.. running one more time in sandbox

rameshthoomu (Fri, 31 Aug 2018 21:49:33 GMT):
@dave.enyeart tests are working as expected on sandbox on 0.4.11 image.. Good to release 0.4.11 baseimage

rameshthoomu (Fri, 31 Aug 2018 21:49:33 GMT):
@dave.enyeart tests are working as expected on sandbox on 0.4.11 image.. Good to release 0.4.11 baseimage & thirdparty images

dave.enyeart (Fri, 31 Aug 2018 22:00:28 GMT):
@rameshthoomu I've +2ed https://gerrit.hyperledger.org/r/#/c/25711/ to release baseimage 0.4.11 for v1.3. Will ask @cbf for a second +2. Anything else we need to do?

rameshthoomu (Sat, 01 Sep 2018 04:30:23 GMT):
Once image is available, will push CR to update Baseimage release version in fabric and fabric-ca, fabric-sdk-node repos

cbf (Tue, 04 Sep 2018 13:28:05 GMT):
@dave.enyeart I'll let you merge 25711 when you are ready - +2ed

dave.enyeart (Tue, 04 Sep 2018 13:31:00 GMT):
merged. @rameshthoomu Please submit the CRs for the various projects to move up to 0.4.11. I will review/merge.

dave.enyeart (Tue, 04 Sep 2018 13:31:35 GMT):
as well as the "prepare for next CR" for 0.4.12

rameshthoomu (Tue, 04 Sep 2018 17:07:23 GMT):
@dave.enyeart Patch is merged but tag is not created in baseimage repo... https://github.com/hyperledger/fabric-baseimage/releases Could you please create a tag in baseimage to push images to dockerhub..

rameshthoomu (Tue, 04 Sep 2018 17:07:53 GMT):
Once the images are published, will submit release CR's

rameshthoomu (Tue, 04 Sep 2018 17:07:53 GMT):
Once the images are published, will submit CR's

rameshthoomu (Wed, 05 Sep 2018 14:01:51 GMT):
@dave.enyeart ^^

dave.enyeart (Wed, 05 Sep 2018 16:43:12 GMT):
@rameshthoomu I've tagged and pushed baseimage v0.4.11

rameshthoomu (Wed, 05 Sep 2018 17:44:21 GMT):
Thanks @dave.enyeart Will check and push CR's

rameshthoomu (Wed, 05 Sep 2018 18:47:55 GMT):
@dave.enyeart seems s390x baseimage job failed to build baseimage

rameshthoomu (Wed, 05 Sep 2018 18:48:14 GMT):
I have asked @harrijk to look into it.. He is on it now..

rameshthoomu (Wed, 05 Sep 2018 19:05:30 GMT):
@dave.enyeart amd64 baseimage and thirdparty images published with 0.4.11 version but it seems s390x is blocked now..

rameshthoomu (Wed, 05 Sep 2018 19:05:54 GMT):
@harrijk identified the issue.. he will post his updates here soon

NoLimitHoldem (Thu, 06 Sep 2018 07:05:36 GMT):
Anyone knows what exactly "State-based ownership" and "Composer function integration" mean in roadmap of Hyperledger Fabric v1.3?

NoLimitHoldem (Thu, 06 Sep 2018 07:05:36 GMT):
Anyone knows what exactly is "State-based ownership" and "Composer function integration" mean in roadmap of Hyperledger Fabric v1.3?

dave.enyeart (Thu, 06 Sep 2018 10:28:36 GMT):
The former allows you to set endorsement policy at the key (asset) level rather than at the chaincode level, for example the endorsement policy may follow from the current ownership. For more details see https://jira.hyperledger.org/browse/FAB-8812, especially see the attached PDF.

dave.enyeart (Thu, 06 Sep 2018 10:28:38 GMT):
The latter means some of the Composer functionality is being pushed down to Fabric itself, for details see https://jira.hyperledger.org/browse/FAB-11246

dave.enyeart (Thu, 06 Sep 2018 10:29:24 GMT):
@NoLimitHoldem can you clarify which roadmap you are looking at? which web site or charts?

NoLimitHoldem (Thu, 06 Sep 2018 10:35:55 GMT):
Ok, I see the roadmap on https://www.altoros.com/blog/hyperledger-fabric-v1-2-whats-new-and-roadmap-for-2018/

NoLimitHoldem (Thu, 06 Sep 2018 10:37:11 GMT):
And I observe that there are 2 planned features: "State-based ownership" and "Composer function integration". Then I do some research, cannot figure what they are about :(

NoLimitHoldem (Thu, 06 Sep 2018 10:37:16 GMT):
For v1.3

dave.enyeart (Thu, 06 Sep 2018 10:45:52 GMT):
@NoLimitHoldem Ok, the links above should give you everything you are looking for

dave.enyeart (Thu, 06 Sep 2018 10:48:50 GMT):
Note that the master list of items for next release, and links, can be found at the top left widget of the release dashboard: https://jira.hyperledger.org/secure/Dashboard.jspa?selectPageId=10701

bh4rtp (Thu, 06 Sep 2018 15:04:59 GMT):
noticed that v1.3 will support web3. does this mean hyperledger fabric takes web3 as a good frontend solution?

bh4rtp (Thu, 06 Sep 2018 15:04:59 GMT):
noticed that v1.3 will support web3. does this mean hyperledger fabric takes etherum web3 as a good frontend solution?

bh4rtp (Thu, 06 Sep 2018 15:04:59 GMT):
noticed that v1.3 will support web3. does this mean hyperledger fabric takes ethereum web3 as a good frontend solution?

dave.enyeart (Thu, 06 Sep 2018 15:15:30 GMT):
@cbf @swetha can you comment ^^^^^^^^^^^^^^^

swetha (Thu, 06 Sep 2018 15:15:30 GMT):
Has joined the channel.

swetha (Thu, 06 Sep 2018 16:25:03 GMT):
@bh4rtp, I am not sure what you mean by good frontend solution. The web3 support will only work for those use contracts that can be compiled into bytecode. So in those situations we expect people will use web3 to create their frontends, as this is what I have understood as one of the main tools ethereum developers use. How we are doing this is by implementing a limited set of the ethereum json rpc apis, which means the support isn't necessarily specific to web3.

bh4rtp (Fri, 07 Sep 2018 00:14:05 GMT):
@swetha thanks. web3 and solidity are excellent for ethereum. i think fabric is landing. :grinning:

qiang0723 (Fri, 07 Sep 2018 00:51:18 GMT):
Has joined the channel.

sheetal-hlf (Fri, 07 Sep 2018 04:40:12 GMT):
Has joined the channel.

NoLimitHoldem (Fri, 07 Sep 2018 07:46:00 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-release?msg=xX2JydFDs548dPgEz) @dave.enyeart Many thanks!!

raviyelleni (Sun, 09 Sep 2018 04:42:24 GMT):
Has joined the channel.

LabibFarag (Mon, 10 Sep 2018 04:52:04 GMT):
Has joined the channel.

cbf (Mon, 10 Sep 2018 13:27:22 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-release?msg=9EKeDts6A3rTpmvLq) @bh4rtp only for the fabric-chaincode-evm chaincode and with the proxy server running

cbf (Mon, 10 Sep 2018 13:27:39 GMT):
see the fabric-chaincode-evm repo for details

vikas.kundz (Tue, 11 Sep 2018 13:02:50 GMT):
Has joined the channel.

benxage (Tue, 11 Sep 2018 18:08:37 GMT):
Has joined the channel.

benxage (Tue, 11 Sep 2018 18:29:43 GMT):
Any words on the release of BFT consensus for 1.4? Will that be guaranteed? Namely, what's the new architecture of BFT and how will that be an improvement from v0.6's BFT?

dave.enyeart (Wed, 12 Sep 2018 19:38:11 GMT):
@cbf I discussed with @rameshthoomu , it seems there is still a need for a release CR on release day, in order to update bootstrap.sh , CHANGELOG.md , install.rst , releases.rst. As we don't want these updated with final values until release day.

dave.enyeart (Wed, 12 Sep 2018 19:38:18 GMT):
But none of these impact test results, so we can indeed do all final system testing on the daily binaries/images until we have one we like. It's just not as simple as 'pick any and promote', as we had hoped.

cbf (Wed, 12 Sep 2018 20:52:15 GMT):
releases.rst I want to get rid of

cbf (Wed, 12 Sep 2018 20:52:28 GMT):
but on the others yes

JaydipMakadia (Thu, 13 Sep 2018 13:14:58 GMT):
Has joined the channel.

dave.enyeart (Mon, 17 Sep 2018 21:16:04 GMT):
@cbf release baseimage 0.4.12 (just updates to latest go and java fixpacks) : https://gerrit.hyperledger.org/r/#/c/26353/

dave.enyeart (Mon, 17 Sep 2018 21:16:32 GMT):
has been pre-tested

cbf (Tue, 18 Sep 2018 01:01:27 GMT):
done

rameshthoomu (Tue, 18 Sep 2018 02:37:18 GMT):
@cbf could you please tag 0.4.12

raviyelleni (Tue, 18 Sep 2018 03:13:18 GMT):
Expected features and Release date for v1.3 ?

dave.enyeart (Tue, 18 Sep 2018 14:31:38 GMT):
@rameshthoomu @cbf I've tagged baseimage v0.4.12. Ramesh, go ahead and submit the CRs from the other repos to move up to v0.4.12.

dave.enyeart (Tue, 18 Sep 2018 14:33:03 GMT):
@raviyelleni we're looking at release candidate of v1.3 next week, and final GA release the following week. Content can be seen in the dashboard (top-left widget): https://jira.hyperledger.org/secure/Dashboard.jspa?selectPageId=10701

rameshthoomu (Tue, 18 Sep 2018 14:38:47 GMT):
ok thanks @dae

rameshthoomu (Tue, 18 Sep 2018 14:38:47 GMT):
ok thanks @dave.enyeart

MikeEmery (Tue, 18 Sep 2018 17:21:09 GMT):
Has joined the channel.

tlee38 (Wed, 19 Sep 2018 04:59:53 GMT):
Has joined the channel.

cbf (Wed, 19 Sep 2018 18:25:48 GMT):
@dave.enyeart @rameshthoomu I have +2ed https://gerrit.hyperledger.org/r/c/26354/ assume it is ok to merge?

rameshthoomu (Wed, 19 Sep 2018 18:26:29 GMT):
yes.

dave.enyeart (Wed, 19 Sep 2018 18:27:23 GMT):
yep

dave.enyeart (Wed, 19 Sep 2018 18:27:49 GMT):
done

cbf (Wed, 19 Sep 2018 18:27:51 GMT):
ok

cbf (Wed, 19 Sep 2018 18:28:03 GMT):
looking for straggler CRs

cbf (Wed, 19 Sep 2018 18:28:04 GMT):
https://jira.hyperledger.org/browse/FAB-8722

cbf (Wed, 19 Sep 2018 18:28:14 GMT):
https://gerrit.hyperledger.org/r/c/21467/

cbf (Wed, 19 Sep 2018 18:28:26 GMT):
jira marked as 1.3

cbf (Wed, 19 Sep 2018 18:28:34 GMT):
this looks relevant

dave.enyeart (Wed, 19 Sep 2018 18:31:29 GMT):
haven't freed up to test it enough before baseimage cut-off, i've commented as such and moved to v1.4

cbf (Wed, 19 Sep 2018 18:34:46 GMT):
ok

cbf (Wed, 19 Sep 2018 18:35:37 GMT):
was wondering if it was important to SK since they reviewed it

dave.enyeart (Wed, 19 Sep 2018 18:40:06 GMT):
it has not been raised as a priority, as far as i know

cbf (Wed, 19 Sep 2018 18:48:09 GMT):
ok

cbf (Wed, 19 Sep 2018 18:48:24 GMT):
I moved the remaining JIRAs for BI to 1.4

cbf (Wed, 19 Sep 2018 18:48:35 GMT):
that is, the ones that have CRs

cbf (Wed, 19 Sep 2018 18:48:57 GMT):
odd that we track the fabric release for BI

cbf (Wed, 19 Sep 2018 18:48:59 GMT):
but whatever

cbf (Wed, 19 Sep 2018 19:19:47 GMT):
@dave.enyeart @mastersingh24 we are getting rid of the fabric-ca-(peer, orderer, tools) in 1.3, correct?

cbf (Wed, 19 Sep 2018 19:20:26 GMT):
I've submitted the CR for the samples and test, going to submit the CA change next

dave.enyeart (Wed, 19 Sep 2018 19:30:04 GMT):
that is the intent

dave.enyeart (Wed, 19 Sep 2018 19:30:36 GMT):
it sounds like there are still some open questions though, per the thread in https://jira.hyperledger.org/browse/FABC-131

cbf (Wed, 19 Sep 2018 19:36:04 GMT):
I removed the dependency in fabric-samples and fabric-test

cbf (Wed, 19 Sep 2018 19:43:17 GMT):
https://gerrit.hyperledger.org/r/26401, https://gerrit.hyperledger.org/r/26389. https://gerrit.hyperledger.org/r/26391

cbf (Wed, 19 Sep 2018 20:59:16 GMT):
@dave.enyeart I've reviewed the release process doc and made some updates... I'll need @rameshthoomu to give it a look as well, as some of the manual jenkins processes are not in my repertoire

rameshthoomu (Wed, 19 Sep 2018 21:00:22 GMT):
@cbf I am working on updating the doc with the latest changes.. It's almost done.

rameshthoomu (Wed, 19 Sep 2018 21:01:17 GMT):
I am not modifying the versions specified already in the doc ex: 0.4.6 baseimage or the version's 1.2.0 etc..

rameshthoomu (Wed, 19 Sep 2018 21:02:04 GMT):
Including the latest changes

cbf (Thu, 20 Sep 2018 12:01:28 GMT):
thx

koineramitranjan (Fri, 21 Sep 2018 08:40:15 GMT):
Has joined the channel.

tennenjl (Mon, 24 Sep 2018 02:11:10 GMT):
Has joined the channel.

Ferrymania (Tue, 25 Sep 2018 03:02:00 GMT):
Has joined the channel.

MikeyGarcia (Tue, 25 Sep 2018 13:03:44 GMT):
Has joined the channel.

MattHamilton (Tue, 25 Sep 2018 13:50:35 GMT):
Has joined the channel.

MrHerickZ (Tue, 25 Sep 2018 15:05:26 GMT):
Has joined the channel.

githubcpc (Wed, 26 Sep 2018 03:30:12 GMT):
Has joined the channel.

dave.enyeart (Wed, 26 Sep 2018 05:40:39 GMT):
fabric, fabric-ca, fabric-chaincode-java v1.3.0-rc1 have been released. release-1.3 branch has been created for each for any critical bugs that are found over the next week. master branch is re-opened for v1.4 development. Caveat - please don't merge into fabric-ca yet. e2e tests from the SDKs are still failing there due to java chaincode issues we've been having, related to syncing across the repositories and branches for 1.3.0-SNAPSHOT, 1.3.0-rc1, 1.3.0, and 1.4.0.

dave.enyeart (Wed, 26 Sep 2018 05:40:39 GMT):
fabric, fabric-ca, fabric-chaincode-java v1.3.0-rc1 have been released.

dave.enyeart (Wed, 26 Sep 2018 05:41:01 GMT):
Try it v1.3.0-rc1 here: https://hyperledger-fabric.readthedocs.io/en/release-1.3/install.html

dave.enyeart (Wed, 26 Sep 2018 05:41:01 GMT):
Try out v1.3.0-rc1 here: https://hyperledger-fabric.readthedocs.io/en/release-1.3/install.html

knagware9 (Wed, 26 Sep 2018 11:03:36 GMT):
I tried v1.3.0-rc1 and it work successfully...

knagware9 (Wed, 26 Sep 2018 11:03:54 GMT):
tried balance-transfer example

dave.enyeart (Wed, 26 Sep 2018 19:51:47 GMT):
Fabric v1.3.0-rc1 has been announced! https://lists.hyperledger.org/g/fabric/message/4656

bandreghetti (Wed, 26 Sep 2018 22:37:23 GMT):
Has joined the channel.

AshishMishra 1 (Thu, 27 Sep 2018 10:52:48 GMT):
Has joined the channel.

dexhunter (Thu, 27 Sep 2018 12:59:39 GMT):
Has joined the channel.

shubham_aggarwal (Thu, 27 Sep 2018 15:06:54 GMT):
Has joined the channel.

davidkel (Sat, 29 Sep 2018 09:38:21 GMT):
I see fabric 1.2.1 has been pushed to Docker, but not the manifests. Does anyone know if/when the manifests are to be pushed ?

rameshthoomu (Sat, 29 Sep 2018 12:45:02 GMT):
@cbf could you pls run multiarch script on 1.2.1

gskerry (Mon, 01 Oct 2018 01:21:35 GMT):
Has joined the channel.

Bartb0 (Tue, 02 Oct 2018 10:56:44 GMT):
Has joined the channel.

cbf (Tue, 02 Oct 2018 14:54:37 GMT):
@dave.enyeart @rameshthoomu done for 1.2.1 - for javaenv there is no s390x image

cbf (Tue, 02 Oct 2018 14:54:41 GMT):
is that intentional?

cbf (Tue, 02 Oct 2018 14:54:49 GMT):
(for 1.3.0-rc1)

rameshthoomu (Tue, 02 Oct 2018 15:06:02 GMT):
yes.. @gennadyl created a FAB to work on this..

cbf (Tue, 02 Oct 2018 15:07:47 GMT):
ok so you want me to create multiarch for just the amd64 image?

dave.enyeart (Tue, 02 Oct 2018 15:10:06 GMT):
yes, so that the scripts work

cbf (Tue, 02 Oct 2018 15:10:21 GMT):
ok, so I published the multiarch for just amd64 of javaenv

cbf (Tue, 02 Oct 2018 15:10:41 GMT):
will create a JIRA to build off of the one Gennady opened to publish the s390x

cbf (Tue, 02 Oct 2018 15:11:10 GMT):
does not make sense to add to fabric multiarch.sh script

dave.enyeart (Tue, 02 Oct 2018 15:11:44 GMT):
thanks

dave.enyeart (Tue, 02 Oct 2018 15:11:56 GMT):
i've just confirmed that `curl -sSL http://bit.ly/2ysbOFE | bash -s 1.3.0-rc1` pulls it now

cbf (Tue, 02 Oct 2018 15:16:14 GMT):
https://jira.hyperledger.org/browse/FAB-12268

rameshthoomu (Tue, 02 Oct 2018 15:22:43 GMT):
@cbf @dave.enyeart x86 javaenv is available for 1.3.0-rc1 but not on 1.2.1 x and z

cbf (Tue, 02 Oct 2018 15:24:38 GMT):
I thought that it was only a 1.3 thing

dave.enyeart (Tue, 02 Oct 2018 15:30:20 GMT):
it was available in v1.1.x as experimental but didn't go well...making it's re-debut in v1.3.0

cbf (Tue, 02 Oct 2018 15:48:06 GMT):
righ

cbf (Tue, 02 Oct 2018 15:48:06 GMT):
right

cinnnn (Wed, 03 Oct 2018 07:56:49 GMT):
Has joined the channel.

mrjdomingus (Thu, 04 Oct 2018 08:10:42 GMT):
Has joined the channel.

puilp0502 (Thu, 04 Oct 2018 08:35:26 GMT):
Has joined the channel.

puilp0502 (Thu, 04 Oct 2018 13:16:45 GMT):
hello, is there any roadmap or schedule for PBTF ordering service?

puilp0502 (Thu, 04 Oct 2018 13:16:45 GMT):
hello, is there any roadmap or schedule for PBFT ordering service?

rickr (Thu, 04 Oct 2018 14:52:57 GMT):
@dave.enyeart Have all the JIRA's for the SDKs been created for known work items to be delivered for 1.4 ?

dave.enyeart (Thu, 04 Oct 2018 15:02:13 GMT):
@rickr For the work items I am most familiar with in v1.4, I don't know of SDK impacts. v1.4 is not intended to be a feature-heavy release. That being said, we've requested all components including SDKs to think about their top priority hygiene and serviceability items that can be done in v1.4 timeframe. For SDKs, part of that would be having application samples that demonstrate good practices. Go ahead and open Jira items with your thoughts.

AnilOner (Thu, 04 Oct 2018 15:35:58 GMT):
Has joined the channel.

grice32 (Thu, 04 Oct 2018 17:36:06 GMT):
Has joined the channel.

kostas (Thu, 04 Oct 2018 21:44:04 GMT):
Has joined the channel.

kostas (Thu, 04 Oct 2018 21:44:37 GMT):
Latest master (`342aab690`) failing? `FAIL github.com/hyperledger/fabric/core/chaincode 461.996s`

kostas (Thu, 04 Oct 2018 21:44:37 GMT):
Latest master (`342aab690`) failing?

kostas (Thu, 04 Oct 2018 21:44:37 GMT):
Latest master (342aab690) failing?

kostas (Thu, 04 Oct 2018 21:44:37 GMT):
Latest master (342aab690) failing? `make checks` gives:

kostas (Thu, 04 Oct 2018 21:44:51 GMT):
`FAIL github.com/hyperledger/fabric/core/chaincode 461.996s`

kostas (Thu, 04 Oct 2018 21:45:28 GMT):
@puilp0502: We'll get on it right after we're done with Raft. Hopefully beginning of next year or so.

mahbub227 (Fri, 05 Oct 2018 09:25:56 GMT):
Has joined the channel.

kostas (Fri, 05 Oct 2018 14:04:08 GMT):
^^ Anyone?

mcoblenz (Fri, 05 Oct 2018 15:05:22 GMT):
Has joined the channel.

cbf (Fri, 05 Oct 2018 17:17:41 GMT):
@kostas I see same issue - haven't got time to look into this though

yacovm (Fri, 05 Oct 2018 17:45:31 GMT):
@sykesm ^

sykesm (Fri, 05 Oct 2018 17:45:32 GMT):
Has joined the channel.

sykesm (Fri, 05 Oct 2018 17:46:44 GMT):
I haven't seen it fail in CI or locally and I've been pushing a lot lately.

sykesm (Fri, 05 Oct 2018 17:47:39 GMT):
may want to take a few minutes and run `make clean-all && make`

yacovm (Fri, 05 Oct 2018 18:25:36 GMT):
@sykesm "haven't seen it fail" is my usual excuse

sykesm (Fri, 05 Oct 2018 18:26:18 GMT):
I did make a suggestion. Given the chaincode tests depend on the base images and other things, it's best to make sure you've got the right levels.

kostas (Fri, 05 Oct 2018 18:27:13 GMT):
Roger, thanks for the suggestion. Fairly certain I cleaned all, but I will give it one more go. Will update shortly.

sykesm (Fri, 05 Oct 2018 18:27:47 GMT):
Believe me, if I had been hitting it, I'd be trying to fix it.

kostas (Fri, 05 Oct 2018 18:49:08 GMT):
Dang it, same error.

kostas (Fri, 05 Oct 2018 18:49:35 GMT):
Will look into it more.

sykesm (Fri, 05 Oct 2018 18:58:45 GMT):
well, how is it failing? it's running for more than 7 minutes - what's it doing?

sykesm (Fri, 05 Oct 2018 19:01:38 GMT):
``` $ go test ./... -cover ok github.com/hyperledger/fabric/core/chaincode 108.573s coverage: 94.6% of statements ok github.com/hyperledger/fabric/core/chaincode/accesscontrol 14.079s coverage: 86.4% of statements ? github.com/hyperledger/fabric/core/chaincode/fake [no test files] ok github.com/hyperledger/fabric/core/chaincode/lib/cid 0.028s coverage: 77.6% of statements ok github.com/hyperledger/fabric/core/chaincode/lifecycle 0.073s coverage: 100.0% of statements ? github.com/hyperledger/fabric/core/chaincode/lifecycle/mock [no test files] ? github.com/hyperledger/fabric/core/chaincode/mock [no test files] ok github.com/hyperledger/fabric/core/chaincode/persistence 0.095s coverage: 98.6% of statements ? github.com/hyperledger/fabric/core/chaincode/persistence/mock [no test files] ok github.com/hyperledger/fabric/core/chaincode/platforms 0.039s coverage: 100.0% of statements ok github.com/hyperledger/fabric/core/chaincode/platforms/car 61.034s coverage: 65.4% of statements ok github.com/hyperledger/fabric/core/chaincode/platforms/ccmetadata 0.029s coverage: 90.0% of statements ok github.com/hyperledger/fabric/core/chaincode/platforms/golang 81.106s coverage: 89.4% of statements ok github.com/hyperledger/fabric/core/chaincode/platforms/java 0.048s coverage: 66.1% of statements ? github.com/hyperledger/fabric/core/chaincode/platforms/mock [no test files] ok github.com/hyperledger/fabric/core/chaincode/platforms/node 5.105s coverage: 81.9% of statements ok github.com/hyperledger/fabric/core/chaincode/platforms/util 5.047s coverage: 76.5% of statements ok github.com/hyperledger/fabric/core/chaincode/shim 3.067s coverage: 65.7% of statements ok github.com/hyperledger/fabric/core/chaincode/shim/ext/attrmgr 0.028s coverage: 84.0% of statements ok github.com/hyperledger/fabric/core/chaincode/shim/ext/cid 0.026s coverage: 79.4% of statements ok github.com/hyperledger/fabric/core/chaincode/shim/ext/entities 0.032s coverage: 82.4% of statements ok github.com/hyperledger/fabric/core/chaincode/shim/ext/statebased 0.056s coverage: 89.1% of statements ```

sykesm (Fri, 05 Oct 2018 19:04:56 GMT):
Running `TEST_PKGS=github.com/hyperledger/fabric/core/chaincode/... make unit-test` now as an extra sanity check

sykesm (Fri, 05 Oct 2018 19:10:33 GMT):
Worked with the make process as well ``` cd unit-test && docker-compose up --abort-on-container-exit --force-recreate && docker-compose down The JOB_TYPE variable is not set. Defaulting to a blank string. Creating couchdb ... done Creating unit-test_unit-tests_1 ... Attaching to couchdb, unit-test_unit-tests_1 couchdb | WARNING: no logs are available with the 'none' log driver unit-tests_1 | experimental unit-tests_1 | ok github.com/hyperledger/fabric/core/chaincode 274.104s coverage: 94.6% of statements unit-tests_1 | ok github.com/hyperledger/fabric/core/chaincode/accesscontrol (cached) coverage: 86.4% of statements unit-tests_1 | ? github.com/hyperledger/fabric/core/chaincode/fake [no test files] unit-tests_1 | ok github.com/hyperledger/fabric/core/chaincode/lib/cid (cached) coverage: 77.6% of statements unit-tests_1 | ok github.com/hyperledger/fabric/core/chaincode/lifecycle 1.546s coverage: 100.0% of statements unit-tests_1 | ? github.com/hyperledger/fabric/core/chaincode/lifecycle/mock [no test files] unit-tests_1 | ? github.com/hyperledger/fabric/core/chaincode/mock [no test files] unit-tests_1 | ok github.com/hyperledger/fabric/core/chaincode/persistence (cached) coverage: 98.6% of statements unit-tests_1 | ? github.com/hyperledger/fabric/core/chaincode/persistence/mock [no test files] unit-tests_1 | ok github.com/hyperledger/fabric/core/chaincode/platforms (cached) coverage: 100.0% of statements unit-tests_1 | ok github.com/hyperledger/fabric/core/chaincode/platforms/car (cached) coverage: 65.4% of statements unit-tests_1 | ok github.com/hyperledger/fabric/core/chaincode/platforms/ccmetadata (cached) coverage: 90.0% of statements unit-tests_1 | ok github.com/hyperledger/fabric/core/chaincode/platforms/golang 118.145s coverage: 89.4% of statements unit-tests_1 | ok github.com/hyperledger/fabric/core/chaincode/platforms/java (cached) coverage: 66.1% of statements unit-tests_1 | ? github.com/hyperledger/fabric/core/chaincode/platforms/mock [no test files] unit-tests_1 | ok github.com/hyperledger/fabric/core/chaincode/platforms/node (cached) coverage: 81.9% of statements unit-tests_1 | ok github.com/hyperledger/fabric/core/chaincode/platforms/util (cached) coverage: 43.2% of statements unit-tests_1 | ok github.com/hyperledger/fabric/core/chaincode/shim 4.447s coverage: 65.7% of statements unit-tests_1 | ok github.com/hyperledger/fabric/core/chaincode/shim/ext/attrmgr (cached) coverage: 84.0% of statements unit-tests_1 | ok github.com/hyperledger/fabric/core/chaincode/shim/ext/cid (cached) coverage: 79.4% of statements unit-tests_1 | ok github.com/hyperledger/fabric/core/chaincode/shim/ext/entities (cached) coverage: 82.4% of statements unit-tests_1 | ok github.com/hyperledger/fabric/core/chaincode/shim/ext/statebased (cached) coverage: 89.1% of statements unit-tests_1 | unit-tests_1 | real 5m26.950s unit-tests_1 | user 2m39.310s unit-tests_1 | sys 0m46.130s unit-tests_1 | experimental pluginsenabled ``` (just took a lot longer)

yacovm (Fri, 05 Oct 2018 19:24:12 GMT):
@kostas I assume a good idea to figure out where tests are getting stuck is to `kill -SIGABRT` the test process of the package after enough time, and then look for the goroutine of the test, to figure out in what line in the test it is stuck in.

yacovm (Fri, 05 Oct 2018 19:24:12 GMT):
@kostas I recon a good idea to figure out where tests are getting stuck is to `kill -SIGABRT` the test process of the package after enough time, and then look for the goroutine of the test, to figure out in what line in the test it is stuck in.

sykesm (Fri, 05 Oct 2018 19:27:18 GMT):
@kostas I'm doing a start from scratch build locally as well. Removing all containers and images, clearing any caches, and building with `make`. (`make clean-all && docker system prune -a && make`)

kostas (Fri, 05 Oct 2018 19:28:09 GMT):
> well, how is it failing? it's running for more than 7 minutes - what's it doing?

kostas (Fri, 05 Oct 2018 19:28:46 GMT):
I'm running `make checks` and it's failing in the unit tests phase. All packages are checked, but the chaincode one fails:

kostas (Fri, 05 Oct 2018 19:28:48 GMT):
`FAIL github.com/hyperledger/fabric/core/chaincode 461.996s`

kostas (Fri, 05 Oct 2018 19:29:02 GMT):
> I'm doing a start from scratch build locally as well. Removing all containers and images, clearing any caches, and building with `make`. (`make clean-all && docker system prune -a && make`) Let me also do that.

sykesm (Fri, 05 Oct 2018 19:29:28 GMT):
`checks` just runs the linter, unit tests, and integration tests. It's the unit tests that are failing.

sykesm (Fri, 05 Oct 2018 19:29:57 GMT):
it should give you a lot more info than just timing out - unless you're running out of memory (ask me how I know)

kostas (Fri, 05 Oct 2018 19:31:00 GMT):
ACK. Will have more helpful output in a few. Thanks for the pointers.

kostas (Fri, 05 Oct 2018 20:38:20 GMT):
So, that's fascinating -- at least for my ignorant eyes.

kostas (Fri, 05 Oct 2018 20:38:29 GMT):
`make unit-test` works w/o issues.

kostas (Fri, 05 Oct 2018 20:38:41 GMT):
As does `TEST_PKGS=github.com/hyperledger/fabric/core/chaincode/... make unit-test`

kostas (Fri, 05 Oct 2018 20:39:13 GMT):
The only one that fails is `make checks`. This is a dump of everything I get: https://gist.github.com/kchristidis/aca3d2b7d351668187e56361dd5b3669

kostas (Mon, 08 Oct 2018 14:56:08 GMT):
Bumping the Docker host's memory to 4GB (from my current 2GB), per @sykesm's advice, made it work. /fyi @cbf

cbf (Mon, 08 Oct 2018 15:04:08 GMT):
hmmm

sykesm (Mon, 08 Oct 2018 15:09:16 GMT):
> "However, race-enabled binaries can use ten times the CPU and memory" https://blog.golang.org/race-detector

cbf (Mon, 08 Oct 2018 15:23:03 GMT):
I've tried increasing to 4G and it still fails, though takes less time doing so (~5 mins)

cbf (Mon, 08 Oct 2018 15:23:41 GMT):
@sykesm @kostas - maybe we should modify so that race detection is opt-in?

sykesm (Mon, 08 Oct 2018 15:24:38 GMT):
I would oppose that. I have already fixed dozens of concurrency issues that have been flagged with the race detector. People need to be aware of concurrency issues and address them as they write code.

sykesm (Mon, 08 Oct 2018 15:25:18 GMT):
Enabling race in our test builds has been an ongoing effort since early this year.

cbf (Mon, 08 Oct 2018 15:39:08 GMT):
I'm up to 6G and it still fails

cbf (Mon, 08 Oct 2018 15:39:42 GMT):
though the time to fail is continuing to fall - now at < 4 mins

cbf (Mon, 08 Oct 2018 15:50:00 GMT):
FWIW, I disabled race detection and it still fails, though within 2 minutes now

cbf (Mon, 08 Oct 2018 15:50:07 GMT):
@sykesm

yacovm (Mon, 08 Oct 2018 15:55:16 GMT):
one thing is certain - if we make race detector opt-in and not mandatory - soon enough we'll be swarmed by races again :)

sykesm (Mon, 08 Oct 2018 16:05:12 GMT):
@cbf it doesn't sound like memory (or the race detector) are the source of the problems you're having.

cbf (Mon, 08 Oct 2018 16:26:20 GMT):
indeed, but it is still failing in the chaincode package

sykesm (Mon, 08 Oct 2018 17:02:10 GMT):
@cbf, I'm happy to try and help but will need more to go on. Are you running in a VM? Docker for X? If you run the package in isolation does it work?

cbf (Mon, 08 Oct 2018 19:19:37 GMT):
I am just running make unit-tests

cbf (Mon, 08 Oct 2018 19:19:44 GMT):
on my mac

cbf (Mon, 08 Oct 2018 19:24:17 GMT):
I get the same failure just running the package tests from the commandline

cbf (Mon, 08 Oct 2018 19:24:51 GMT):
2018-10-08 15:21:51.233 EDT [chaincode] Add -> ERRO b32 failed to marshal query result: marshal-failed 2018-10-08 15:21:51.233 EDT [chaincode] Add -> ERRO b33 failed to marshal query result: marshal-failed 2018-10-08 15:21:51.233 EDT [chaincode] BuildQueryResponse -> ERRO b34 Failed to get query result from iterator FAIL FAIL github.com/hyperledger/fabric/core/chaincode 80.374s cbf$

ymlbright (Wed, 10 Oct 2018 07:06:00 GMT):
Has joined the channel.

cbf (Wed, 10 Oct 2018 13:06:12 GMT):
release CRs ready to be merged

mastersingh24 (Wed, 10 Oct 2018 13:41:52 GMT):
woo hoo

dave.enyeart (Wed, 10 Oct 2018 14:17:21 GMT):
fabric and fabric-ca merged

dave.enyeart (Wed, 10 Oct 2018 14:17:45 GMT):
@gennadyl @C0rWin could you review the fabric-chaincode-java release CR? https://gerrit.hyperledger.org/r/#/c/26896/

dave.enyeart (Wed, 10 Oct 2018 14:56:26 GMT):
fabric-chaincode-java merged

cbf (Wed, 10 Oct 2018 14:59:02 GMT):
is there a reason that fabric-peer amd64 image has not been pushed?

cbf (Wed, 10 Oct 2018 14:59:10 GMT):
everything else seems to be

cbf (Wed, 10 Oct 2018 14:59:31 GMT):
@rameshthoomu

rameshthoomu (Wed, 10 Oct 2018 14:59:49 GMT):
checking

rameshthoomu (Wed, 10 Oct 2018 15:02:44 GMT):
it's pushed from the job..

rameshthoomu (Wed, 10 Oct 2018 15:02:59 GMT):
will check after few mins otherwise, will re-trigger again

rameshthoomu (Wed, 10 Oct 2018 15:04:25 GMT):
fabric-ca multiarch is done

rameshthoomu (Wed, 10 Oct 2018 15:08:20 GMT):
@cbf able to pull from docker hub but for reason it's not showing up on UI

rameshthoomu (Wed, 10 Oct 2018 15:08:20 GMT):
@cbf able to pull from docker hub but it's not showing up on UI

rameshthoomu (Wed, 10 Oct 2018 15:08:55 GMT):
done.. I could see now.. Could be network glitch

cbf (Wed, 10 Oct 2018 15:11:22 GMT):
shall I push multiarch?

cbf (Wed, 10 Oct 2018 15:12:42 GMT):
@rameshthoomu @dave.enyeart ?

rameshthoomu (Wed, 10 Oct 2018 15:12:56 GMT):
added jobs to do that

rameshthoomu (Wed, 10 Oct 2018 15:13:00 GMT):
fabric-ca is done..

cbf (Wed, 10 Oct 2018 15:13:02 GMT):
ah!

cbf (Wed, 10 Oct 2018 15:18:16 GMT):
@dave.enyeart can I help by pushing the CRs for next version?

rameshthoomu (Wed, 10 Oct 2018 15:19:03 GMT):
@cbf could you please run multiarch on javaenv

dave.enyeart (Wed, 10 Oct 2018 15:20:12 GMT):
@cbf go ahead on the 'prepare for next' CRs

rameshthoomu (Wed, 10 Oct 2018 15:20:15 GMT):
fabric multiarch is done

cbf (Wed, 10 Oct 2018 15:20:23 GMT):
kk

cbf (Wed, 10 Oct 2018 15:24:30 GMT):
@dave.enyeart seems to me that for the 1.3.1 experimental should be 'false' (actually, we should probably remove for 1.4)

dave.enyeart (Wed, 10 Oct 2018 15:26:22 GMT):
by precedent we would switch it back to 'true', but i agree with you, can keep it 'false' for now and then open a CR to remove it in both release and master branches

dave.enyeart (Wed, 10 Oct 2018 15:26:22 GMT):
by precedent we would switch it back to 'true', but i agree with you, can keep it 'false' for now and then open a jira to remove it in both release and master branches

cbf (Wed, 10 Oct 2018 15:26:46 GMT):
when we are on maaster branch, it makes sense (sort of)

cbf (Wed, 10 Oct 2018 15:27:00 GMT):
seems like no new development should be done on release branches

dave.enyeart (Wed, 10 Oct 2018 15:27:21 GMT):
well, we've decided not to use it going forward. but, never know if that will get overturned...

dave.enyeart (Wed, 10 Oct 2018 15:27:21 GMT):
well, we've decided not to use experimental going forward (do betas instead). but, never know if that will get overturned...

cbf (Wed, 10 Oct 2018 15:33:35 GMT):
@mastersingh24 what say you? eliminate EXPERIMENTAL in fabric Makefile?

mastersingh24 (Wed, 10 Oct 2018 15:33:46 GMT):
I already did ;)

cbf (Wed, 10 Oct 2018 15:33:53 GMT):
heh

mastersingh24 (Wed, 10 Oct 2018 15:34:15 GMT):
https://gerrit.hyperledger.org/r/#/c/26845/

mastersingh24 (Wed, 10 Oct 2018 15:34:31 GMT):
removed it from the Makefile and removed all remnants from any code

firas.qutishat (Wed, 10 Oct 2018 15:37:50 GMT):
is v1.3.0 tag ready

cbf (Wed, 10 Oct 2018 15:38:40 GMT):
patience grasshopper

dave.enyeart (Wed, 10 Oct 2018 15:50:38 GMT):
the published fabric images and binaries are testing out with success.

cbf (Wed, 10 Oct 2018 15:50:50 GMT):
yay

cbf (Wed, 10 Oct 2018 15:50:58 GMT):
ok, prepare next CRs ready for review

dave.enyeart (Wed, 10 Oct 2018 15:52:06 GMT):
since we released from `release-1.3` branch, i will also push a `master` CR to update doc and scripts from v1.3.0-rc1 to v1.3.0, as the install script uses master. I'll mention in the release process doc as well.

cbf (Wed, 10 Oct 2018 15:52:20 GMT):
thx

dave.enyeart (Wed, 10 Oct 2018 15:54:26 GMT):
I'll also do a fabcar trial to make sure fabric-ca is good, before merging 'prepare for next'. @rameshthoomu and team also do tests...

rameshthoomu (Wed, 10 Oct 2018 15:55:06 GMT):
sure.. I did fabcar on mac and it worked

dave.enyeart (Wed, 10 Oct 2018 16:03:12 GMT):
@cbf @rameshthoomu what's the story on multi-arch for javaenv?

cbf (Wed, 10 Oct 2018 16:03:24 GMT):
ok, docs building and I made release-1.3 default

cbf (Wed, 10 Oct 2018 16:03:45 GMT):
we only have one;-)

cbf (Wed, 10 Oct 2018 16:03:55 GMT):
but I can oush that if ramesh has not automated

rameshthoomu (Wed, 10 Oct 2018 16:04:05 GMT):
@cbf pls push..

dave.enyeart (Wed, 10 Oct 2018 16:04:12 GMT):
our download scripts still like multi-arch regardless

cbf (Wed, 10 Oct 2018 16:04:13 GMT):
okie dokie

cbf (Wed, 10 Oct 2018 16:04:20 GMT):
yep

cbf (Wed, 10 Oct 2018 16:12:54 GMT):
Successfully pushed multiarch manifest

dave.enyeart (Wed, 10 Oct 2018 16:18:02 GMT):
ok, download script pulls javaenv now, and i confirmed it works with `./byfn.sh up -l java`

cbf (Wed, 10 Oct 2018 16:20:36 GMT):
build for https://gerrit.hyperledger.org/r/c/26905/ is failing, cannot find shim

dave.enyeart (Wed, 10 Oct 2018 16:44:09 GMT):
@C0rWin said he will take a look at tests

dave.enyeart (Wed, 10 Oct 2018 16:44:38 GMT):
in the meantime @cbf , I can tag fabric, fabric-ca, fabric-chaincode-java for v1.3.0 - i actually prefer to tag prior to prepare for next CR... less chance for me to screw it up

dave.enyeart (Wed, 10 Oct 2018 16:45:32 GMT):
also @bretharrison is preparing node sdk and chaincode release CRs

rameshthoomu (Wed, 10 Oct 2018 16:48:01 GMT):
@dave.enyeart when you will https://github.com/hyperledger/fabric-samples/blob/release-1.3/balance-transfer/package.json#L27-L28push change to update node module versions in release-1.3 fabrci-sampels package.json file.

dave.enyeart (Wed, 10 Oct 2018 16:52:24 GMT):
@rameshthoomu you can see all the release subtasks here: https://jira.hyperledger.org/browse/FAB-12380

dave.enyeart (Wed, 10 Oct 2018 16:52:51 GMT):
i fix up the samples after node sdk and chaincode get pushed to npm (subtask 19)

rameshthoomu (Wed, 10 Oct 2018 16:55:47 GMT):
post qa test (e2e, upgrade, balance transfer, version checks) worked as expected on published images/binaries.. Will re-run these tests once the release tasks are completed

cbf (Wed, 10 Oct 2018 17:09:45 GMT):
https://gerrit.hyperledger.org/r/q/owner:chris.ferris%2540gmail.com+status:open

dave.enyeart (Wed, 10 Oct 2018 17:28:29 GMT):
fabric, fabric-ca, fabric-chaincode-java tagged as v1.3.0

cbf (Wed, 10 Oct 2018 18:02:50 GMT):
thanks

rameshthoomu (Wed, 10 Oct 2018 19:17:47 GMT):
@dave.enyeart @cbf published fabric-chaincode-node, fabric-sdk-node 1.3 tag to npm

rameshthoomu (Wed, 10 Oct 2018 19:18:20 GMT):
We are done with publishing 1.3 build artifacts.

cbf (Wed, 10 Oct 2018 19:59:15 GMT):
I don't understand https://jira.hyperledger.org/browse/FAB-12411

cbf (Wed, 10 Oct 2018 19:59:19 GMT):
@rameshthoomu ^^

dave.enyeart (Wed, 10 Oct 2018 22:25:28 GMT):
Today we tagged for v1.3.0 fabric, fabric-ca, fabric-chaincode-java, fabric-chaincode-node, fabric-sdk-node, fabric-samples.

dave.enyeart (Wed, 10 Oct 2018 22:25:34 GMT):
fabric samples have been pinned to ~1.3.0 and tested.

greg2git (Wed, 10 Oct 2018 23:05:17 GMT):
so, we're officially on 1.3 now, aren't we?

dave.enyeart (Thu, 11 Oct 2018 00:06:34 GMT):
indeed we are. the official announcement will go out...

dave.enyeart (Thu, 11 Oct 2018 12:17:33 GMT):
--------------------------------------------------- Fabric v1.3.0 RELEASE ANNOUNCEMENT: https://lists.hyperledger.org/g/fabric/topic/announcement_hyperledger/27240996?p=,,,20,0,0,0::recentpostdate%2Fsticky,,,20,2,0,27240996 ---------------------------------------------------

DheerajBalodia (Fri, 12 Oct 2018 05:20:51 GMT):
Has joined the channel.

tkg (Fri, 12 Oct 2018 13:48:52 GMT):
Has joined the channel.

jdfigure (Fri, 12 Oct 2018 15:30:22 GMT):
Hi all, will the Hyperledger 1.3.0 fabric-ca-* images be available on Docker Hub? Thanks!

cbf (Fri, 12 Oct 2018 15:45:12 GMT):
they were posted Wednesday

cbf (Fri, 12 Oct 2018 15:45:12 GMT):
they were removed from the release

cbf (Fri, 12 Oct 2018 15:46:03 GMT):
you can create them if you need using a staged build and adding the ca binaries

jdfigure (Fri, 12 Oct 2018 15:50:21 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-release?msg=p7fY4uwb5HPm5juFq) @cbf Thanks!

mobie (Sat, 13 Oct 2018 09:58:37 GMT):
Has joined the channel.

kostas (Sat, 13 Oct 2018 20:19:59 GMT):
Has left the channel.

JanRzepecki (Mon, 15 Oct 2018 08:16:21 GMT):
s390x java

gatakka (Mon, 15 Oct 2018 08:31:57 GMT):
Will fabric-ca images be added to docker hub at some point, or from now we have to build them "by hand"?

mastersingh24 (Mon, 15 Oct 2018 10:47:51 GMT):
@gatakka - we only intend to publish https://hub.docker.com/r/hyperledger/fabric-ca/ from now on

adarshsaraf123 (Tue, 16 Oct 2018 13:02:46 GMT):
Has joined the channel.

kariyappals (Wed, 17 Oct 2018 08:57:05 GMT):
Has joined the channel.

ataul443 (Wed, 17 Oct 2018 18:22:52 GMT):
Has joined the channel.

greg2git (Sun, 21 Oct 2018 12:58:47 GMT):
v1.4 on ubuntu requires xenial 18 and go 1.11, correct?

mastersingh24 (Tue, 23 Oct 2018 12:06:41 GMT):
v1.4 / master is currently using Go 1.11.1 .... we don't really have a prereq on the OS .. although Ubuntu Xenial or later and Debian Stretch or later are typically what people are using

cagdast (Thu, 25 Oct 2018 08:05:38 GMT):
Has joined the channel.

uber.twin (Fri, 26 Oct 2018 10:30:03 GMT):
hi, does the version 1.3 ZKP feature cover the Private Asset Transfer capability too or it's limited to providing Anonymous Client Authentication?

dave.enyeart (Fri, 26 Oct 2018 10:32:24 GMT):
v1.3 has Anonymous Client Authentication. Private Asset Transfer is expected for a future release.

uber.twin (Fri, 26 Oct 2018 10:38:23 GMT):
thank you for the confirmation

githubcpc (Mon, 29 Oct 2018 01:48:53 GMT):
:grin:I used fabric 1.1.0 now and I want to upgrade to 1.3.0,Is there any documents to help me to do ?

githubcpc (Mon, 29 Oct 2018 01:50:17 GMT):
https://hyperledger-fabric.readthedocs.io/en/release-1.3/upgrade_to_newest_version.html

githubcpc (Mon, 29 Oct 2018 01:52:28 GMT):
If I want to upgrade 1.1 to 1.3 ,I must upgrade to 1.2 according this documents?

dave.enyeart (Mon, 29 Oct 2018 02:10:15 GMT):
there are detailed instructions for 1.1 to 1.2 and then 1.2 to 1.3. if you try to do it in a single hop you would have to merge the instructions on your own, use caution.

githubcpc (Mon, 29 Oct 2018 02:14:29 GMT):
OK.I will update to 1.2 first .Thanks.

IgarashiTakashi (Thu, 01 Nov 2018 13:45:52 GMT):
Has joined the channel.

smpakes (Tue, 06 Nov 2018 19:54:58 GMT):
Has joined the channel.

enriquebusti (Wed, 07 Nov 2018 12:01:57 GMT):
Has joined the channel.

matthewphamilton (Wed, 07 Nov 2018 15:21:53 GMT):
Has joined the channel.

githubcpc (Thu, 08 Nov 2018 03:24:12 GMT):
I try to set up HLF 1.2 with 3zk,4kafka,3order,4peer in my local env .I hava already run fabric-samples successfully.Now I run the e2e_cli examples ,but get an error like this , Error: could not assemble transaction, err Proposal response was not successful, error code 500, msg failed to execute transaction fc92d259a61914ad5223d1d0bb5027b441a8908d2593b3ef2ffc78e0276cac6a: error starting container: error starting container: Get https://registry-1.docker.io/v2/: Unauthorized !!!!!!!!!!!!!!! Chaincode instantiation on PEER2 on channel 'mychannel' failed !!!!!!!!!!!!!!!! However, I could't find the error log in my peers' logs.Could someone help me ?Thanks.

githubcpc (Thu, 08 Nov 2018 03:26:36 GMT):
My env is centos7.3,go version go1.11 linux/amd64,docker-compose version 1.12.0,Docker version 1.13.1.

kostas (Mon, 12 Nov 2018 18:15:21 GMT):
Has joined the channel.

kostas (Mon, 12 Nov 2018 18:15:50 GMT):
Isn't `dep ensure` supposed to work w/o issues? This is what I'm getting on latest master:

kostas (Mon, 12 Nov 2018 18:15:50 GMT):
Isn't `dep ensure` supposed to work w/o issues? This is what I'm getting on latest master (tip @ `859de2755`):

kostas (Mon, 12 Nov 2018 18:15:50 GMT):
Isn't `dep ensure` supposed to work w/o issues? This is what I'm getting on the latest master (tip @ `859de2755`):

kostas (Mon, 12 Nov 2018 18:16:12 GMT):
```$ dep ensure Solving failure: No versions of github.com/docker/docker met constraints: 0c5f8d2b9b23ab8d23529b3effdcf53bb058298c: Could not introduce github.com/docker/docker@0c5f8d2b9b23ab8d23529b3effdcf53bb058298c due to a case-only variation: it depends on "github.com/sirupsen/logrus", but "github.com/Sirupsen/logrus" was already established as the case variant for that project root by depender (root)```

kostas (Mon, 12 Nov 2018 18:18:34 GMT):
Anybody else seeing this?

mastersingh24 (Tue, 13 Nov 2018 14:17:03 GMT):
nope

mastersingh24 (Tue, 13 Nov 2018 14:17:03 GMT):
nope - but at `d23da14eb`

kostas (Tue, 13 Nov 2018 20:46:01 GMT):
The culprit was a leftover `build` directory in the project's root. It was importing `github.com/Sirupsen/logrus` and that was messing up the dep solver.

DirkKrueger (Fri, 16 Nov 2018 13:03:27 GMT):
Has joined the channel.

huxiangdong (Tue, 20 Nov 2018 00:35:22 GMT):
Has joined the channel.

aKesav (Sat, 24 Nov 2018 08:18:39 GMT):
Has joined the channel.

longnv1a (Mon, 26 Nov 2018 04:18:16 GMT):
Has joined the channel.

chenshiok (Mon, 26 Nov 2018 09:46:41 GMT):
Has joined the channel.

lwan2000 (Mon, 26 Nov 2018 17:14:27 GMT):
Has joined the channel.

kostas (Wed, 28 Nov 2018 17:44:57 GMT):
`make unit-tests` consistently fails over the past few days: https://hastebin.com/viguwugabi.coffeescript

kostas (Wed, 28 Nov 2018 17:45:20 GMT):
I get an `Error 1` exit code but I don't see a package failng, if that makes sense.

kostas (Wed, 28 Nov 2018 17:45:41 GMT):
https://chat.hyperledger.org/channel/fabric-release?msg=izXTd7jrmqpyiMY9r

kostas (Wed, 28 Nov 2018 17:46:00 GMT):
And I bumped up the Docker host's memory to 6GB to no avail.

kostas (Wed, 28 Nov 2018 17:46:04 GMT):
Anybody else seeing this?

harsha (Wed, 28 Nov 2018 18:11:53 GMT):
I see the error is at `Immutable = [false]Failed initiliazing BCCSP at [{SecLevel:256 HashFamily:SHA2 Ephemeral:false FileKeystore: DummyKeystore: Library: Label:ForFabric Pin:98765432 SoftVerify:true Immutable:false}]: [Failed initializing PKCS11 library ForFabric: No PKCS11 library default]FAIgithub.com/hyperledger/fabric/bccsp/pkcs11 0.118s`

harsha (Wed, 28 Nov 2018 18:11:53 GMT):
I see the error is at ```Immutable = [false]Failed initiliazing BCCSP at [{SecLevel:256 HashFamily:SHA2 Ephemeral:false FileKeystore: DummyKeystore: Library: Label:ForFabric Pin:98765432 SoftVerify:true Immutable:false}]: [Failed initializing PKCS11 library ForFabric: No PKCS11 library default]FAIgithub.com/hyperledger/fabric/bccsp/pkcs11 0.118s```

harsha (Wed, 28 Nov 2018 18:13:19 GMT):
@kostas here's a fix.. it's been tested in jenkins.

harsha (Wed, 28 Nov 2018 18:13:19 GMT):
@kostas here's a fix https://gerrit.hyperledger.org/r/#/c/27759/ .. it's been tested in jenkins.

kostas (Wed, 28 Nov 2018 18:14:20 GMT):
@harsha: Thanks!

kostas (Wed, 28 Nov 2018 18:38:13 GMT):
(@harsha: FWIW, I cherry-picked this one, ran `make unit-test` and still bump into the same issue.)

harsha (Wed, 28 Nov 2018 19:10:02 GMT):
@kostas here's the flow :- 1) After cherry-pick, ./scripts/config_softhsm2.sh 2) Update `SOFTHSM2_CONF` via `export =$HOME/lib/softhsm/softhsm2.conf` 3) make unit-test this should work now.

harsha (Wed, 28 Nov 2018 19:10:02 GMT):
@kostas here's the flow :- 1) After cherry-pick, issue `./scripts/config_softhsm2.sh` 2) Update `SOFTHSM2_CONF` via `export =$HOME/lib/softhsm/softhsm2.conf` 3) make unit-test this should work now.

haggis (Thu, 29 Nov 2018 08:08:31 GMT):
Has joined the channel.

kariyappals (Tue, 04 Dec 2018 14:17:55 GMT):
Is it possible to upgrade the network from solo orderer to kafka orderer without loosing the ledger?

jrosmith (Tue, 04 Dec 2018 14:34:27 GMT):
@kariyappals no, changes to the ordering service of a live network is not supported

arjitkhullar (Wed, 05 Dec 2018 00:04:17 GMT):
Has joined the channel.

MaheshBalan_Pravici (Sat, 08 Dec 2018 22:11:38 GMT):
Has joined the channel.

zwartesokken (Mon, 10 Dec 2018 09:50:13 GMT):
Has joined the channel.

cbf (Mon, 10 Dec 2018 16:49:47 GMT):
@dave.enyeart I cleaned up the various release JIRAs https://jira.hyperledger.org/browse/FAB-13111?

dave.enyeart (Mon, 10 Dec 2018 18:23:27 GMT):
@cbf @mastersingh24 @rameshthoomu Starting release process. fabric release CR: https://gerrit.hyperledger.org/r/#/c/28050/

dave.enyeart (Mon, 10 Dec 2018 20:15:55 GMT):
@cbf @mastersingh24 @rameshthoomu fabric CA release CR: https://gerrit.hyperledger.org/r/#/c/28053/

dave.enyeart (Mon, 10 Dec 2018 20:15:55 GMT):
@cbf @mastersingh24 @rameshthoomu @skarim @smithbk fabric CA release CR: https://gerrit.hyperledger.org/r/#/c/28053/

dave.enyeart (Mon, 10 Dec 2018 20:22:30 GMT):
@odowdaibm provided the fabcar tutorial doc updates https://gerrit.hyperledger.org/r/#/c/27824/ , so we can get that merged and then rebase the fabric release CR on top

dave.enyeart (Mon, 10 Dec 2018 20:22:30 GMT):
@odowdaibm provided the fabcar tutorial doc updates https://gerrit.hyperledger.org/r/#/c/27824/ , although there are some issues in the instructions that need to get resolved. We'll likely need to proceed with RC1 and then let the doc fixes catch up later in the week

dave.enyeart (Mon, 10 Dec 2018 23:42:27 GMT):
release update - we are getting a final fix in fabric-ca reviewed, and then will proceed with fabric and fabric-ca. then move on to node SDK and chaincode tomorrow.

dave.enyeart (Tue, 11 Dec 2018 06:52:28 GMT):
fabric and fabric-ca v1.4.0-rc1 released. fabric release-1.4 branch created. fabric release-1.4 is open for critical release defect fixes. fabric master is open for 2.0.0 development.

dave.enyeart (Tue, 11 Dec 2018 06:52:28 GMT):
fabric and fabric-ca v1.4.0-rc1 released. release-1.4 branches created. release-1.4 is open for critical release defect fixes. master is open for 2.0.0 development.

dave.enyeart (Tue, 11 Dec 2018 06:53:25 GMT):
MERGE FREEZE over for fabric.

dave.enyeart (Tue, 11 Dec 2018 06:53:25 GMT):
MERGE FREEZE over for fabric and fabric-ca

dave.enyeart (Tue, 11 Dec 2018 06:53:58 GMT):
on Tuesday we will do node sdk, node chaincode, java chaincode, and fabric-samples.

dave.enyeart (Tue, 11 Dec 2018 06:53:58 GMT):
on Tuesday we will do node sdk, node chaincode, java chaincode, fabric-samples, and announce

dave.enyeart (Wed, 12 Dec 2018 06:16:21 GMT):
Release update for v1.4.0-rc1 - today we got through publishing of node chaincode to npm and java chaincode (javaenv) to dockerhub and sonatype.

dave.enyeart (Wed, 12 Dec 2018 06:16:33 GMT):
The last piece remaining is node sdk - we hit an issue with the new fabric-network package (npm install of 1.4.0-rc1 package not working). The node sdk developers will finish that off on Wednesday.

dave.enyeart (Wed, 12 Dec 2018 20:31:03 GMT):
--------------------------------------------------- Fabric v1.4.0 RELEASE CANDIDATE ANNOUNCEMENT: https://lists.hyperledger.org/g/fabric/topic/announcement_hyperledger/28735908 ---------------------------------------------------

knagware9 (Thu, 13 Dec 2018 07:11:16 GMT):
I tested first-network sample and byfn script required sudo to succesful

knagware9 (Thu, 13 Dec 2018 07:58:44 GMT):
almost every sample(first-network,fabcar tried) code required sudo otherwise failed with permission denied in Ubuntu 16.04

knagware9 (Thu, 13 Dec 2018 12:03:40 GMT):
Its working fine , no issues. Run all samples , upgrade E2E

BellaAdams (Fri, 14 Dec 2018 03:23:44 GMT):
Has joined the channel.

mallikarjunasai995 (Fri, 14 Dec 2018 06:14:09 GMT):
Has joined the channel.

mallikarjunasai995 (Fri, 14 Dec 2018 06:14:32 GMT):
not able to head the video currently going on in the one webinar

mallikarjunasai995 (Fri, 14 Dec 2018 06:15:10 GMT):
hear the audio

kostas (Sat, 15 Dec 2018 22:08:44 GMT):
Has left the channel.

dave.enyeart (Tue, 18 Dec 2018 03:29:46 GMT):
Final system tests for Fabric v1.4 has identified a few issues that are currently being resolved. We expect to release a rc2 this week with the final updates. Pending results of rc2 testing, a final v1.4 release can then be expected at the beginning of January.

lfeagan (Tue, 18 Dec 2018 07:16:30 GMT):
Has joined the channel.

shniu (Thu, 20 Dec 2018 03:28:28 GMT):
Has joined the channel.

mqmatt (Thu, 20 Dec 2018 13:24:22 GMT):
Has joined the channel.

dave.enyeart (Thu, 20 Dec 2018 14:07:26 GMT):
release process starting for v1.4.0-rc2

dave.enyeart (Thu, 20 Dec 2018 14:07:34 GMT):
fabric release CR: https://gerrit.hyperledger.org/r/#/c/28325/

dave.enyeart (Thu, 20 Dec 2018 14:19:15 GMT):
fabric-ca release CR: https://gerrit.hyperledger.org/r/#/c/28326/

mastersingh24 (Thu, 20 Dec 2018 14:45:44 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-release?msg=8vYbke7nkkmk5gK3k) @dave.enyeart added a comment

vijay.bP (Thu, 20 Dec 2018 15:42:23 GMT):
Has joined the channel.

antoniovassell (Thu, 20 Dec 2018 18:21:00 GMT):
Has joined the channel.

dave.enyeart (Thu, 20 Dec 2018 18:30:04 GMT):
@lehors and all ... all release artifacts are pushed, re-pulled, verified. Everything looks good. Go ahead with your own tests on Windows, etc

dave.enyeart (Thu, 20 Dec 2018 18:30:27 GMT):
I will tag all repositories with v1.4.0-rc2 shortly

dave.enyeart (Thu, 20 Dec 2018 18:31:07 GMT):
RTD instructions are updated: https://hyperledger-fabric.readthedocs.io/en/release-1.4/install.html

dave.enyeart (Thu, 20 Dec 2018 19:16:04 GMT):
fabric, fabric-ca, fabric-chaincode-java, fabric-chaincode-node are all tagged for v1.4.0-rc2. fabric-chaincode-sdk was already tagged for v1.4.0-rc2.

dave.enyeart (Thu, 20 Dec 2018 22:58:33 GMT):
fabric-samples also tagged for v1.4.0-rc2. Release process completed!

dave.enyeart (Thu, 20 Dec 2018 23:12:18 GMT):
--------------------------------------------------- Fabric v1.4.0 RELEASE CANDIDATE 2 ANNOUNCEMENT: https://lists.hyperledger.org/g/fabric/topic/announcement_hyperledger/28815938 ---------------------------------------------------

akshay.lawange (Mon, 24 Dec 2018 13:08:36 GMT):
Hi, one quick question, what is the latest release of fabric binaries? Because i have downloaded for 1.3.0 configtxgen --version shows me 1.2.0

dave.enyeart (Mon, 24 Dec 2018 13:44:31 GMT):
@akshay.lawange latest release is 1.3.0. there is also a 1.4.0-rc2 (release candidate 2).

dave.enyeart (Mon, 24 Dec 2018 13:44:55 GMT):
I have a configtxgen downloaded for 1.3.0 and it's binary shows correct version:

dave.enyeart (Mon, 24 Dec 2018 13:44:58 GMT):
```$ ./configtxgen --version configtxgen: Version: 1.3.0```

tuckerg (Mon, 24 Dec 2018 13:48:25 GMT):
Has joined the channel.

akshay.lawange (Mon, 24 Dec 2018 14:20:54 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-release?msg=iQFKsNMfXvDG5WnDE) @dave.enyeart Thanks. So for fabric v1.3.0, is 1.2.0 binary compatible?

dave.enyeart (Mon, 24 Dec 2018 14:33:25 GMT):
Back versions of SDK clients are tested for backwards compatibility so that client applications do not break, other tools are not (use back versions at your own risk).

JonathanC (Mon, 24 Dec 2018 16:03:14 GMT):
Has joined the channel.

JonathanC (Mon, 24 Dec 2018 16:03:56 GMT):
Hi guys, quick question I didn't get it clearly will the next version after 1.4 will be 2.0 or another one ?

yacovm (Mon, 24 Dec 2018 16:06:53 GMT):
2.0, yes

yacovm (Mon, 24 Dec 2018 16:07:23 GMT):
fabric versions are in modulo 5 field

JonathanC (Mon, 24 Dec 2018 16:07:37 GMT):
Thanks a lot ! Who can I contact to get a jira account ?

yacovm (Mon, 24 Dec 2018 16:07:52 GMT):
try to go to http://jira.hyperledger.org/

yacovm (Mon, 24 Dec 2018 16:07:55 GMT):
and there should be a link

yacovm (Mon, 24 Dec 2018 16:08:11 GMT):
https://identity.linuxfoundation.org/

JonathanC (Mon, 24 Dec 2018 16:27:11 GMT):
J

JonathanC (Mon, 24 Dec 2018 16:27:29 GMT):
Didn't know it was working with Linux Identity thanks !

puilp0502 (Mon, 31 Dec 2018 09:03:44 GMT):
Hello everyone, is there any schedule for 2.0 release? We were waiting for raft implementation, and we

puilp0502 (Mon, 31 Dec 2018 09:03:44 GMT):
Hello everyone, is there any schedule for 2.0 release? We were waiting for raft implementation, and we'd like to know if there is some sort of release schedule

mastersingh24 (Mon, 31 Dec 2018 10:05:50 GMT):
@puilp0502 - we have been putting out quarterly releases (1.4.0 will ship in early Jan due to the holiday). So the next release is expected at the end of March. Ideally it will include Raft

puilp0502 (Mon, 31 Dec 2018 10:13:12 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-release?msg=TmwtokaHvWfyd6FG3) @mastersingh24 oh ok, thanks!

gongliaoan (Wed, 02 Jan 2019 09:04:49 GMT):
Has joined the channel.

ydcandrew (Fri, 04 Jan 2019 05:34:45 GMT):
Has joined the channel.

svgsenthil (Fri, 04 Jan 2019 07:18:16 GMT):
Has joined the channel.

mrudav.shukla (Fri, 04 Jan 2019 13:05:38 GMT):
Has joined the channel.

rodolfoleal (Sat, 05 Jan 2019 22:34:01 GMT):
Has joined the channel.

hhlee (Mon, 07 Jan 2019 02:57:01 GMT):
Has joined the channel.

guoger (Mon, 07 Jan 2019 14:19:37 GMT):
maybe this has been answered many times already, but i've always wondered, why 2.0 instead of 1.5? breaking api?

dave.enyeart (Mon, 07 Jan 2019 15:41:37 GMT):
@guoger Calling it 2.0 due to major changes to lifecycle, new raft-based ordering service with some different assumptions, and SDKs are evaluating whether APIs need to change/break.

ScottAllan (Mon, 07 Jan 2019 22:10:22 GMT):
Has joined the channel.

knagware9 (Tue, 08 Jan 2019 09:51:13 GMT):
https://lists.hyperledger.org/g/fabric/topic/announcement_hyperledger/28815938 check this

dave.enyeart (Tue, 08 Jan 2019 16:39:16 GMT):
Starting final v1.4.0 release process...

bretharrison (Wed, 09 Jan 2019 15:07:06 GMT):
How is it going with 1.4.0, should I see the 1.4.0 docker images on docker hub ?

dave.enyeart (Wed, 09 Jan 2019 15:49:15 GMT):
just merged fabric and fabric-ca release CRs, they will show up in dockerhub in about an hour

dave.enyeart (Wed, 09 Jan 2019 20:38:39 GMT):
All release artifacts have been published

dave.enyeart (Wed, 09 Jan 2019 20:38:39 GMT):
All release artifacts have been published for fabric, fabric-ca, fabric-chaincode-java, fabric-chaincode-node, fabric-sdk-node

dave.enyeart (Wed, 09 Jan 2019 20:38:39 GMT):
All release artifacts have been published for fabric, fabric-ca, fabric-chaincode-java, fabric-chaincode-node, fabric-sdk-node. I've pulled and verified each.

dave.enyeart (Wed, 09 Jan 2019 20:39:39 GMT):
Release CR for fabric-samples: https://gerrit.hyperledger.org/r/#/c/28598/ @cbf @mastersingh24

rkrish82 (Thu, 10 Jan 2019 05:07:00 GMT):
Has joined the channel.

knagware9 (Thu, 10 Jan 2019 06:15:40 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-release?msg=zZRahuwmd6uG64pYb) @dave.enyeart Fabric-ca still tagged as 1.4.0-rc2 ?

knagware9 (Thu, 10 Jan 2019 06:16:32 GMT):

Screenshot from 2019-01-10 11-46-10.png

knagware9 (Thu, 10 Jan 2019 06:20:28 GMT):
when I use curl -sSL http://bit.ly/2ysbOFE | bash -s 1.4.0 1.4.0 0.4.14 then fabric-ca 1.4.0 downloaded but when I use just curl -sSL http://bit.ly/2ysbOFE | bash -s 1.4.0 then fabric-ca is downloaded with Rc2

dave.enyeart (Thu, 10 Jan 2019 12:42:22 GMT):
@knagware9 The download script updates were just merged, should be good now

knagware9 (Thu, 10 Jan 2019 12:44:55 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-release?msg=nTZ8ASJioGPHxRNaf) @dave.enyeart Yes ,, Tried its good now

vikpande (Thu, 10 Jan 2019 20:17:28 GMT):
Has joined the channel.

venu.vemula (Thu, 10 Jan 2019 20:35:14 GMT):
Has joined the channel.

tahaf10 (Thu, 10 Jan 2019 21:02:25 GMT):
Has joined the channel.

PradeepJaligama (Thu, 10 Jan 2019 21:18:04 GMT):
Has joined the channel.

dave.enyeart (Thu, 10 Jan 2019 22:33:32 GMT):
------------------------------------------------------------------- Hyperledger Fabric v1.4 LTS RELEASE ANNOUNCEMENT: https://lists.hyperledger.org/g/fabric/topic/announcement_hyperledger/29001113 -------------------------------------------------------------------

tonyyu (Thu, 10 Jan 2019 23:50:17 GMT):
Has joined the channel.

NeelKantht (Fri, 11 Jan 2019 05:25:55 GMT):
Has joined the channel.

Lug 5 (Fri, 11 Jan 2019 07:59:12 GMT):
Has joined the channel.

cbf (Fri, 11 Jan 2019 16:15:28 GMT):
:woo: :thumbsup:

h2rashwan@gmail.com (Sat, 12 Jan 2019 07:44:47 GMT):
Has joined the channel.

h2rashwan@gmail.com (Sat, 12 Jan 2019 07:49:54 GMT):
First of all congratulations on the new release 1.4 the new contract-api npm package is way simpler to use . This article https://www.ledgerinsights.com/enterprise-blockchain-hyperledger-fabric-long-term-support/ shines the light on version 2.0 where can I stay up to date with what is planned to 2.0 . Thanks

mastersingh24 (Sat, 12 Jan 2019 14:49:21 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-release?msg=LxCnZw4NxmW3yDaF3) @h2rashwan@gmail.com https://jira.hyperledger.org/secure/Dashboard.jspa?selectPageId=10104

dave.enyeart (Sat, 12 Jan 2019 15:10:17 GMT):
You can also see the 2.0 plan in the last maintainer meeting recording: https://drive.google.com/open?id=1u1X9PHO3w7xgLT8-i6Lzo5w5rmrCl25n

sstone1 (Mon, 14 Jan 2019 10:27:21 GMT):
@h2rashwan@gmail.com thanks for the feedback :+1:

ycarmel (Mon, 21 Jan 2019 15:02:06 GMT):
Has joined the channel.

incarose (Wed, 23 Jan 2019 00:26:23 GMT):
Has joined the channel.

ddhulla (Wed, 23 Jan 2019 08:13:45 GMT):
When we run query.js in fabcar, keep getting an error which says, Failed to connect before the deadline

ddhulla (Wed, 23 Jan 2019 08:13:53 GMT):
ubuntu@rtmpeernodeinst:~/data/fabric-samples/fabcar$ netstat -at Active Internet connections (servers and established) Proto Recv-Q Send-Q Local Address Foreign Address State tcp 0 0 *:ssh *:* LISTEN tcp 0 0 192.168.14.4:ssh 10.49.153.46:64085 ESTABLISHED tcp 0 204 192.168.14.4:ssh 10.49.153.46:62530 ESTABLISHED tcp6 0 0 [::]:7050 [::]:* LISTEN tcp6 0 0 [::]:7051 [::]:* LISTEN tcp6 0 0 [::]:7053 [::]:* LISTEN tcp6 0 0 [::]:7054 [::]:* LISTEN tcp6 0 0 [::]:ssh [::]:* LISTEN tcp6 0 0 [::]:5984 [::]:* LISTEN ubuntu@rtmpeernodeinst:~/data/fabric-samples/fabcar$ vi query.js ubuntu@rtmpeernodeinst:~/data/fabric-samples/fabcar$ node query.js Store path:/home/ubuntu/data/fabric-samples/fabcar/hfc-key-store (node:1640) DeprecationWarning: grpc.load: Use the @grpc/proto-loader module with grpc.loadPackageDefinition instead Successfully loaded user1 from persistence error: [Remote.js]: Error: Failed to connect before the deadline URL:grpc://192.168.14.4:7051

dan13 (Wed, 23 Jan 2019 19:44:01 GMT):
Has joined the channel.

npc0405 (Thu, 24 Jan 2019 05:58:56 GMT):
Has joined the channel.

npc0405 (Thu, 24 Jan 2019 05:59:02 GMT):
hi

knagware9 (Thu, 24 Jan 2019 10:16:14 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-release?msg=mWHrvrKvPjWPnM9hX) @ddhulla please ask in #fabric-questions , this is related to orderer.First check your orderer container is running ?

nasht00 (Wed, 06 Feb 2019 13:55:05 GMT):
Has left the channel.

nitishbhardwaj19 (Mon, 11 Feb 2019 08:23:09 GMT):
Has joined the channel.

jv_400 (Thu, 14 Feb 2019 08:58:50 GMT):
Has joined the channel.

jv_400 (Thu, 14 Feb 2019 09:22:02 GMT):
Fabric 1.4 is a fantabulous release!! The new contract api is cool. However i still feel the composer Business abstractions, queries and permissions were much cooler!! Are there any plans to implement similar features in the upcoming releases?

dave.enyeart (Thu, 14 Feb 2019 13:01:30 GMT):
@sstone1 Can you look at this question?

dave.enyeart (Thu, 14 Feb 2019 13:01:30 GMT):
@sstone1 @odowdaibm @mbwhite Can you look at this question?

KartikChauhan (Fri, 15 Feb 2019 08:17:29 GMT):
Has joined the channel.

JayJong (Tue, 19 Feb 2019 16:39:34 GMT):
Has joined the channel.

MuhammedHafil (Tue, 19 Feb 2019 17:02:38 GMT):
Has joined the channel.

JayJong (Wed, 20 Feb 2019 03:18:57 GMT):
Hi, anyone knows when v1.3.1 or v1.4.1 will be out?

jv_400 (Wed, 20 Feb 2019 08:22:58 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-release?msg=DJYGc4PYibDHmCB4E) @dave.enyeart Hi, Any insights into this is greatly appreciated?

dave.enyeart (Wed, 20 Feb 2019 13:03:22 GMT):
@JayJong v1.4.0 includes fixes since v1.3.0 timeframe and is the long-term support release. Therefore we don't expect a v1.3.1 at this time. As the LTS release, there will be a series of v1.4.x releases throughout the year. Currently targeting end of March for v1.4.1.

JayJong (Wed, 20 Feb 2019 13:36:57 GMT):
@dave.enyeart thanks for the info!

sstone1 (Wed, 20 Feb 2019 14:18:29 GMT):
@jv_400 we'd like to bring those business abstractions (assets, participants, transactions, etc) to fabric at some point; no fixed plans as of yet, but domain specific APIs are high up our priority list

raj_shekhar (Fri, 22 Feb 2019 05:36:03 GMT):
Has joined the channel.

halilkalkan (Fri, 22 Feb 2019 07:02:08 GMT):
Has joined the channel.

jv_400 (Thu, 28 Feb 2019 13:49:20 GMT):
@sstone1 on a similar note is there anything on the roadmap that allows to add collection members at runtime without a chaincode upgrade!

sstone1 (Thu, 28 Feb 2019 16:26:52 GMT):
not my area of fabric i'm afraid, maybe @dave.enyeart can answer that one

dave.enyeart (Thu, 28 Feb 2019 16:29:13 GMT):
@jv_400 yes, that is part of the updated v2.0 lifecycle

dave.enyeart (Thu, 28 Feb 2019 16:29:13 GMT):
@jv_400 yes, that is part of the updated lifecycle planned for v2.0

SatoshiNishishita (Fri, 01 Mar 2019 01:26:34 GMT):
Has joined the channel.

luckforzhang (Thu, 07 Mar 2019 09:56:21 GMT):
Has joined the channel.

luckforzhang (Fri, 08 Mar 2019 01:31:44 GMT):
Is there any plan to put audit function on fabric? It's kind of pretty useful in some Business scenes...... And I have seen the ibm docs of idemix which had mentioned the auditor with idemix users, but I haven't found any further infos about them. If there is any helpful docs that can I refer to would be very nice.

dave.enyeart (Fri, 08 Mar 2019 16:08:12 GMT):
@luckforzhang Many solutions have some type of auditor or regulator role, who owns their own peer, is involved in endorsements, and is entitled to chaincode queries to audit data. Can you be more specific about what you are looking for?

dave.enyeart (Fri, 08 Mar 2019 16:08:12 GMT):
@luckforzhang Many solutions have some type of auditor or regulator role, who owns their own peer, is involved in endorsements, is included in private channels or private data collections, is entitled to chaincode queries to audit data, etc. Can you be more specific about what you are looking for?

dave.enyeart (Fri, 08 Mar 2019 16:08:12 GMT):
@luckforzhang Many solutions even today on current Fabric releases have some type of auditor or regulator role, who runs their own peer, is involved in endorsements, is included in private channels or private data collections, is entitled to chaincode queries to audit data, etc. Can you be more specific about what you are looking for?

Yogendrasri (Mon, 11 Mar 2019 12:08:24 GMT):
We are looking to create Ethereum ERC 20 tokens but within HL Fabric runtime. we have found that we need to use fab proxy to connect to Eth VM in HL Fabric env. And that there is a constraint of one user per fab proxy, This is a issue because we need to move tokens between users, and this means that if we need to create 5k users, which also implies that we need to create 5K Fab Proxies. is there any way fab proxy constraint can be managed/eliminated?

knagware9 (Mon, 11 Mar 2019 13:24:08 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-release?msg=crPfom8idcRt8rkb8) @Yogendrasri please post to #fabric-evm channel, may be they can help

KyunghoKim (Tue, 12 Mar 2019 03:11:11 GMT):
Has joined the channel.

Pradeep_Pentakota (Tue, 12 Mar 2019 12:43:32 GMT):
Has joined the channel.

krabradosty (Thu, 14 Mar 2019 10:43:37 GMT):
Has joined the channel.

MarioPissardo (Thu, 14 Mar 2019 22:29:51 GMT):
Has joined the channel.

RealDeanZhao (Fri, 15 Mar 2019 07:42:28 GMT):
Has left the channel.

akoita (Fri, 15 Mar 2019 15:03:58 GMT):
Has joined the channel.

seokm0 (Wed, 20 Mar 2019 02:26:20 GMT):
Has joined the channel.

bbehlendorf (Thu, 21 Mar 2019 21:35:46 GMT):
Has joined the channel.

Tom-Xu-CNXA (Fri, 22 Mar 2019 06:33:19 GMT):
Has joined the channel.

Tom-Xu-CNXA (Fri, 22 Mar 2019 06:38:29 GMT):
For　https://github.com/hyperledger/fabric-sdk-node/blob/release-1.4/fabric-client/lib/ChannelEventHub.js#L1551 , 'delete chaincode_event.payload;' and its comments, I suggest updating document at: https://fabric-sdk-node.github.io/global.html#ChaincodeEvent, to avoid any confusion at 'payload'.

dave.enyeart (Fri, 22 Mar 2019 11:21:12 GMT):
@Tom-Xu-CNXA This channel is for release discussion. Please post your comment in #fabric-sdk-node

dave.enyeart (Fri, 22 Mar 2019 11:21:12 GMT):
@Tom-Xu-CNXA This channel is for release discussion. Please post your comment in #fabric-sdk-node where those maintainers hang out

dave.enyeart (Sat, 30 Mar 2019 03:30:42 GMT):
Fabric v1.4.1-rc1 release candidate is available, see download instructions at https://hyperledger-fabric.readthedocs.io/en/release-1.4/install.html

dave.enyeart (Sat, 30 Mar 2019 03:30:42 GMT):
Fabric v1.4.1-rc1 release candidate has been tagged and is available for download. See download instructions at https://hyperledger-fabric.readthedocs.io/en/release-1.4/install.html

Tom-Xu-CNXA (Sat, 30 Mar 2019 04:30:01 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-release?msg=hpJWhMGzqxcHba5Mz) @dave.enyeart Sure, thank yuou Dave.

Tom-Xu-CNXA (Sat, 30 Mar 2019 04:30:01 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-release?msg=hpJWhMGzqxcHba5Mz) @dave.enyeart Sure, thank you Dave.

dave.enyeart (Sat, 30 Mar 2019 20:16:18 GMT):
---------------------------------------------------------------------- Hyperledger Fabric v1.4.1-rc1 RELEASE ANNOUNCEMENT: https://lists.hyperledger.org/g/fabric/message/5788 ----------------------------------------------------------------------

khudeja (Mon, 01 Apr 2019 05:17:06 GMT):
Has joined the channel.

knagware9 (Mon, 01 Apr 2019 07:04:37 GMT):
Hi, I think V1.4.1-rc1 docker image repository is down, while trying to run this command (curl -sSL http://bit.ly/2ysbOFE | bash -s 1.4.1-rc1 1.4.0 0.4.15) its stucked after downloading some images yesterday it was working fine

knagware9 (Mon, 01 Apr 2019 08:04:11 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-release?msg=TAxGsKHXssfHgyMqd) please ignore , its working now! It was due to docker deamon issue

notnull (Mon, 01 Apr 2019 15:48:14 GMT):
Has joined the channel.

mbanerjee (Mon, 01 Apr 2019 21:12:09 GMT):
Has joined the channel.

SaphiraBjartskular (Mon, 01 Apr 2019 22:32:42 GMT):
Has joined the channel.

SaphiraBjartskular (Mon, 01 Apr 2019 22:34:04 GMT):
What and when is the next major release of Fabric? There are rumors about v2.0 being released soon but that just doesnt make sense to me. Any clarification?

sah (Tue, 02 Apr 2019 01:14:49 GMT):
Has joined the channel.

swikar (Tue, 02 Apr 2019 04:16:45 GMT):
Has joined the channel.

swikar (Tue, 02 Apr 2019 04:16:56 GMT):
Hi All, Can anyone help me as I would want to understand code in Hyperledger Fabric. Since many source folders in golang Please let me know where is the entry point of code where to start. I want first understand code architecture and then contribute. Hope I will get advice.

sah (Tue, 02 Apr 2019 21:57:50 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-release?msg=tSbKJj69FyvQgH259) @swikar I'm just a beginner, but knowing the general architecture of a fabric network is what helped me start to navigate my way through the code. So, the first-network shows that there are several containers, each performing various jobs, but the key ones are the orderer, and the peer. under fabric/ there are two directories that are named orderer/ and peer/ which each have a main.go which seems like a good place to start. As you go through that code though, you'll realise that often they're starting servers, which you will then need to grep through fabric/ to find

swikar (Wed, 03 Apr 2019 04:43:07 GMT):
Thanks Sah. Will look at it.

swikar (Wed, 03 Apr 2019 12:09:11 GMT):
@sah thanks I found main entry point. I still need to know where to go afterwards? architecture diagram, flow diagram where and how system works..etc. Anyone have any idea, advice. Please tell me. Thanks

sah (Wed, 03 Apr 2019 23:58:27 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-release?msg=bq5Q3b2LFWjauBkWw) @swikar This may be a case of the blind leading the blind. I'm finding things the hard way, For example, I am trying to debug how a cli container talks to an external network. That's caused me to find github.com/hyperledger/fabric-cli, and reading *that* code has caused me to find github.com/hyperledger/fabric/peer/chaincode/* which has the chaincode commands that I can call (I'm reluctant to use the word invoke here because that word has special meaning in fabric) from the cli. And I found that code with `find . -name chaincode` and noted that one of the results was in a directory named `peer` which is the name of the directory that you run the commands from in the cli container

sah (Thu, 04 Apr 2019 00:49:49 GMT):
@swikar WRT architecture/flow diagrams, I've not seen any, but if you find some I'd appreciate it if you shared :) Having said that, I read https://medium.com/@benbjohnson/standard-package-layout-7cdbc8391fc1 some months back, it, and pages similar to it, gave me a basic understanding how code is laid out on most projects (There's no 'standard' way, it's a matter of each project organically implementing one layout or another (or even a mix) and you as someone new identifying what's been used)

swikar (Thu, 04 Apr 2019 12:55:12 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-release?msg=yz75HAs6FPtcAwQ9D) @sah @sah this i found helpful to understand underlying structure. https://hyperledger-fabric.readthedocs.io/en/release-1.3/peers/peers.html

Tom-Xu-CNXA (Fri, 05 Apr 2019 08:20:18 GMT):
It seems that 'operations|metrics' configuration in core.yaml or orderer.yaml doesn't work in 1.4.1-rc1, I tried several ways (try setting it in docker yaml ENV) but the operation service even didn't start. Do we have any information on this? (No steps, per core.yaml, it should start as default, right?)

toddinpal (Sat, 06 Apr 2019 20:06:44 GMT):
Has joined the channel.

mhs22 (Tue, 09 Apr 2019 05:46:37 GMT):
Has joined the channel.

mhs22 (Tue, 09 Apr 2019 05:51:05 GMT):
Hello,

mhs22 (Tue, 09 Apr 2019 05:51:45 GMT):
Does anyonw know when v1.4.1 will be released?

knagware9 (Tue, 09 Apr 2019 09:07:44 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-release?msg=2eqSeKzNfZsmhy6Ww) @mhs22 Hyperledger Fabric v1.4.1-rc1 RELEASE ANNOUNCEMENT: https://lists.hyperledger.org/g/fabric/message/5788

dave.enyeart (Tue, 09 Apr 2019 11:11:55 GMT):
@mhs22 We are targeting v2.0.0-alpha release for first half of this week, and v1.4.1 release for second half of this week.

ilyahq (Wed, 10 Apr 2019 08:10:09 GMT):
Has joined the channel.

shekharrajak (Wed, 10 Apr 2019 08:51:31 GMT):
Has joined the channel.

dave.enyeart (Wed, 10 Apr 2019 14:52:36 GMT):
---------------------------------------------------------------------- Hyperledger Fabric v2.0.0-alpha RELEASE ANNOUNCEMENT: https://lists.hyperledger.org/g/fabric/message/5851 ----------------------------------------------------------------------

SaphiraBjartskular (Wed, 10 Apr 2019 16:55:43 GMT):
the "latest" tag is pulling fabric peers 1.4.1-rc1 is it recommended to use this or the v2.0.0-alpha?

SaphiraBjartskular (Wed, 10 Apr 2019 16:55:43 GMT):
@dave.enyeart the "latest" tag is pulling fabric peers 1.4.1-rc1, is it recommended to use this or the v2.0.0-alpha?

rameshthoomu (Wed, 10 Apr 2019 17:05:46 GMT):
@SaphiraBjartskular yes "latest" tag is associated with 1.4.1-rc1 images.. If you want to try 2.0.0-alpha, please use 2.0.0-alpha image tag.. `curl -sSL http://bit.ly/2ysbOFE | bash -s -- 2.0.0-alpha 2.0.0-alpha 0.4.15` or look here https://hyperledger-fabric.readthedocs.io/en/master/install.html#install-samples-binaries-and-docker-images

dave.enyeart (Wed, 10 Apr 2019 17:11:01 GMT):
@SaphiraBjartskular If you need stability, use Long-Term Support release v1.4.0 or upcoming v1.4.1. If you want to try out the new features use v2.0.0-alpha.

dave.enyeart (Wed, 10 Apr 2019 17:11:05 GMT):
Since the `latest` tag is confusing we will likely retire it when v2.0 goes out mid-year. When v1.4.1 is released (target later this week) it will get the `latest` tag.

SaphiraBjartskular (Wed, 10 Apr 2019 17:22:29 GMT):
@dave.enyeart thank you, will use v1.4.1 for serious project @rameshthoomu thank you I will play around with v2

BrettLogan (Thu, 11 Apr 2019 14:01:54 GMT):
Has joined the channel.

dave.enyeart (Thu, 11 Apr 2019 20:51:35 GMT):
---------------------------------------------------------------------- Hyperledger Fabric v1.4.1 RELEASE ANNOUNCEMENT: https://lists.hyperledger.org/g/fabric/message/5862 ----------------------------------------------------------------------

ranjan008 (Tue, 16 Apr 2019 05:16:24 GMT):
Has joined the channel.

mhs22 (Tue, 16 Apr 2019 09:42:49 GMT):
raft

GowriR (Wed, 17 Apr 2019 07:38:31 GMT):
Has joined the channel.

GowriR (Wed, 17 Apr 2019 07:40:14 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-release?msg=xoLWF4pbRQ5SCdD9G) @dave.enyeart Hi Dave, Where do I find the image for 1.4.1 nodeenv? https://hub.docker.com/r/hyperledger/fabric-nodeenv/tags - does not have 1.4.1

dave.enyeart (Wed, 17 Apr 2019 12:57:02 GMT):
@GowriR This is expected. v1.4.x does not use nodeenv... node chaincode uses fabric-baseimage in v1.4.x.

GowriR (Sat, 20 Apr 2019 07:41:37 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-release?msg=MQWxWszwxziwm4W2F) @dave.enyeart thanks @dave.enyeart

GowriR (Sat, 20 Apr 2019 12:44:17 GMT):
Hi, I am using fabric 1.4.1 with raft

GowriR (Sat, 20 Apr 2019 12:44:48 GMT):
am unable to get the orderers running - i followed the examples with 5 orderer nodes

GowriR (Sat, 20 Apr 2019 12:45:32 GMT):
# TickInterval is the time interval between two Node.Tick invocations. # if it is commented - panic: [channel: byfn-sys-channel] Error creating consenter: failed to parse TickInterval () to time duration # fails if with "ms" at generating genesis block # if no "ms" and plain 500 fails too - 019-04-20 12:41:12.955 UTC [orderer.commmon.multichannel] newChainSupport -> PANI 455 [channel: byfn-sys-channel] Error creating consenter: failed to parse TickInterval () to time duration #panic: [channel: byfn-sys-channel] Error creating consenter: failed to parse TickInterval () to time duration TickInterval: 500

GowriR (Sat, 20 Apr 2019 12:46:22 GMT):
what should i be doing here? Orderers dont get created. Is this a bug? The same bug was in JIRA but now it is closed.

GowriR (Sat, 20 Apr 2019 12:47:48 GMT):
https://jira.hyperledger.org/browse/FAB-14451?workflowName=FAB%3A+Bug+Workflow&stepId=6

dave.enyeart (Sun, 21 Apr 2019 03:53:00 GMT):
@GowriR The channel is for release discussion. For orderer questions please use #fabric-orderer

dave.enyeart (Sun, 21 Apr 2019 03:53:00 GMT):
@GowriR The channel is for release discussion. For orderer questions please use #fabric-orderer where those experts hang out.

dave.enyeart (Sun, 21 Apr 2019 03:53:00 GMT):
@GowriR This channel is for release discussion. For orderer questions please use #fabric-orderer where those experts hang out.

GowriR (Sun, 21 Apr 2019 12:26:32 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-release?msg=ADGRzEPSmX3j7xaMy) @dave.enyeart Sure, Dave thanks

suryalanka (Mon, 22 Apr 2019 14:02:31 GMT):
Has joined the channel.

MohammedR (Thu, 25 Apr 2019 06:11:19 GMT):
Has joined the channel.

AnilSingh (Sat, 27 Apr 2019 10:04:07 GMT):
Has joined the channel.

Allea (Tue, 30 Apr 2019 22:26:22 GMT):
Has joined the channel.

Allea (Tue, 30 Apr 2019 22:26:56 GMT):
Howdy all! Does anyone know does anyone know when FabToken is moving out of Alpha, or, alternately, if it is ready to support NFTs?

aspring (Wed, 01 May 2019 04:59:32 GMT):
Has joined the channel.

aspring (Wed, 01 May 2019 05:00:54 GMT):
@Allea have you tried FabToken alpha with a third user? If so what's your experience?

Allea (Thu, 02 May 2019 20:24:37 GMT):
@aspring We're researching tech stack before we start developing a game.

Allea (Thu, 02 May 2019 20:24:48 GMT):
So not yet.

aspring (Thu, 02 May 2019 20:55:09 GMT):
@Allea ok, imho, definitely you should try it hands-on to check out its core functionality before diving into NFT etc.

yerganat (Fri, 03 May 2019 05:16:20 GMT):
Has joined the channel.

Allea (Fri, 03 May 2019 15:35:29 GMT):
@aspring Thanks!

Allea (Fri, 03 May 2019 15:35:35 GMT):
Will do.

KOttoni (Fri, 03 May 2019 17:18:56 GMT):
Has joined the channel.

c-an (Wed, 08 May 2019 01:26:01 GMT):
Has joined the channel.

c-an (Wed, 08 May 2019 01:40:46 GMT):
hello!

circlespainter (Sat, 18 May 2019 07:39:55 GMT):
Has joined the channel.

ynamiki (Tue, 21 May 2019 03:42:37 GMT):
Has left the channel.

Mayuzumi (Tue, 21 May 2019 08:03:15 GMT):
Has joined the channel.

IgorSim (Tue, 21 May 2019 20:59:48 GMT):
Hi, can someone shed some light regarding current status of collections types in v2.0.0-alpha: local, all, implicit collections (implicit org-specific)..etc are those already implemented/supported? If not is anything planned for v2.0 ? Thanks.

dave.enyeart (Wed, 22 May 2019 11:45:41 GMT):
answered in mailing list: https://lists.hyperledger.org/g/fabric/message/6147

IgorSim (Wed, 22 May 2019 11:57:14 GMT):
thanks

sekhmette (Thu, 23 May 2019 17:42:17 GMT):
Has joined the channel.

sekhmette (Thu, 23 May 2019 17:42:20 GMT):
For the IBM signed images (ibmblockchain dockerhub), when will version 1.4.1 be released? x86/s390x?

githubcpc (Thu, 30 May 2019 03:24:51 GMT):
I hava already read the doc from https://hyperledger-fabric.readthedocs.io/en/release-1.4/upgrading_your_network_tutorial.html.But I hava some questions. Can I upgrade 1.4.0 to 1.4.1 through the steps in the document? I hava set up HLF v1.4.0 environment, 3zk+4kafka+3order+4peer+ca+4couchdb. I want to upgrade the v1.4.1 in order to user RBFT orderType.

dave.enyeart (Thu, 30 May 2019 07:14:10 GMT):
yes, the steps for a 3rd digit upgrade would be the same, although note that that kafka to raft migration is not yet supported... it is planned for v1.4.2.

githubcpc (Thu, 30 May 2019 07:17:06 GMT):
So...Now I can not migrate old block data to new version.Right?

dave.enyeart (Thu, 30 May 2019 07:18:17 GMT):
you can upgrade and keep using kafka. if you want to migrate to raft you must wait until planned v1.4.2

githubcpc (Thu, 30 May 2019 07:18:57 GMT):
Thanks.

raidinesh80 (Tue, 04 Jun 2019 18:51:17 GMT):
Has joined the channel.

raidinesh80 (Tue, 04 Jun 2019 18:51:37 GMT):
yes

charyorde (Wed, 05 Jun 2019 23:58:06 GMT):
Has joined the channel.

charyorde (Thu, 06 Jun 2019 00:12:22 GMT):
see https://hyperledger-fabric.readthedocs.io/en/latest/token/FabToken.html#future-features

charyorde (Thu, 06 Jun 2019 00:12:22 GMT):
@Allea see https://hyperledger-fabric.readthedocs.io/en/latest/token/FabToken.html#future-features

charyorde (Thu, 06 Jun 2019 05:41:42 GMT):
Can we get v2.0.0-alpha release for https://github.com/hyperledger/fabric-samples

dave.enyeart (Fri, 07 Jun 2019 13:28:21 GMT):
@sstone1 @lehors We had not yet tagged fabric-samples with v2.0.0-alpha. I can do that today. Just wanted to double check with you that fabric-samples is in a good state currently, or whether you'd recommend anything else be merged before we tag.

lehors (Fri, 07 Jun 2019 13:29:10 GMT):
well, I wouldn't say it is in good shape unfortunately

lehors (Fri, 07 Jun 2019 13:29:25 GMT):
the CI builds have been failing pretty consistantly

dave.enyeart (Fri, 07 Jun 2019 13:29:41 GMT):
due to the official couchdb taking longer?

dave.enyeart (Fri, 07 Jun 2019 13:29:41 GMT):
due to the official couchdb taking longer? ... I know that has been one issue

dave.enyeart (Fri, 07 Jun 2019 13:29:41 GMT):
due to the official couchdb taking longer to spin up? ... I know that has been one issue

lehors (Fri, 07 Jun 2019 13:29:44 GMT):
I opened a JIRA ticket and @sstone1 said he'd look at it

lehors (Fri, 07 Jun 2019 13:30:31 GMT):
in the time I was able to spend on it I couldn't quite figure out the root cause

lehors (Fri, 07 Jun 2019 13:30:52 GMT):
when I tried to run it locally to see if I could reproduce the problem I faced a different problem!?

dave.enyeart (Fri, 07 Jun 2019 13:31:13 GMT):
ok, let's get to the bottom of these current problem(s) before tagging

lehors (Fri, 07 Jun 2019 13:31:27 GMT):
we did already make some change to accommodate for couchdb taking longer to start

lehors (Fri, 07 Jun 2019 13:31:36 GMT):
but there is something else going on

dave.enyeart (Fri, 07 Jun 2019 13:32:05 GMT):
we can also tag a prior commit if we find some problem that was introduced

lehors (Fri, 07 Jun 2019 13:32:55 GMT):
yeah but I'm uncertain as to when it really started unfortunately

lehors (Fri, 07 Jun 2019 13:33:11 GMT):
at first it seemed to just be a timing issue

lehors (Fri, 07 Jun 2019 13:33:29 GMT):
so people tried to work around it submitting a bunch of reverify

dave.enyeart (Fri, 07 Jun 2019 13:33:30 GMT):
e.g. we could tag commit prior to "Use official CouchDB image". but it would be kind of nice to pick up "Make FabCar use BYFN, not basic-network"

lehors (Fri, 07 Jun 2019 13:34:12 GMT):
yes, although this may be when the problem came in actually

lehors (Fri, 07 Jun 2019 13:34:22 GMT):
it's the fabcar test that fails

lehors (Fri, 07 Jun 2019 13:34:32 GMT):
during the CI builds

lehors (Fri, 07 Jun 2019 13:35:17 GMT):
that's why I asked Simon to look into it

dave.enyeart (Fri, 07 Jun 2019 13:35:33 GMT):
makes sense...let's see what Simon comes up with

lehors (Fri, 07 Jun 2019 13:35:41 GMT):
ok

mastersingh24 (Sat, 08 Jun 2019 09:20:44 GMT):
I really don't think we should be doing this at this time; if we decide to do a beta we could attempt to do this. We really need to allocate some more time on what we are actually going to do with these samples moving forward.

smithbk (Tue, 11 Jun 2019 18:58:55 GMT):
Has left the channel.

Mihir2.0 (Tue, 11 Jun 2019 19:01:22 GMT):
Has joined the channel.

Mihir2.0 (Tue, 11 Jun 2019 19:01:24 GMT):
When can we expect tokens with chaincode interoperability with v2.0 (not alpha)?

Mihir2.0 (Tue, 11 Jun 2019 19:01:24 GMT):
When is the release of v2.0 (not alpha) with tokens and chaincode interoperability?

mastersingh24 (Tue, 11 Jun 2019 19:21:59 GMT):
Not sure what you mean by "chaincode interoperability"? Tokens will not be in 2.0

charyorde (Wed, 12 Jun 2019 05:50:20 GMT):
@mastersingh24 What! The roadmap says FabToken will be completed in August.

charyorde (Wed, 12 Jun 2019 05:50:20 GMT):
@mastersingh24 What! The roadmap says FabToken will be completed in August. Maybe 2.1.0?

yacovm (Wed, 12 Jun 2019 07:28:39 GMT):
@dave.enyeart ^

ihormudryy (Wed, 12 Jun 2019 08:57:35 GMT):
Has joined the channel.

dave.enyeart (Wed, 12 Jun 2019 12:07:43 GMT):
@charyorde this was discussed in the maintainer meeting two weeks ago...FabToken has changed to 'Future' pending broader work in the processing model. Also see the related post in the mailing list: https://lists.hyperledger.org/g/fabric/topic/31628218#6228

charyorde (Wed, 12 Jun 2019 13:48:43 GMT):
Oh no!

swikar (Tue, 18 Jun 2019 09:00:51 GMT):
Has left the channel.

Coada (Mon, 24 Jun 2019 13:59:55 GMT):
Has joined the channel.

Coada (Mon, 24 Jun 2019 13:59:55 GMT):
Is there an ETA for 1.4.2?

mastersingh24 (Mon, 24 Jun 2019 16:26:34 GMT):
mid-July

Daniela_Barbosa (Mon, 24 Jun 2019 23:13:45 GMT):
Has joined the channel.

tsnyder (Wed, 26 Jun 2019 03:23:33 GMT):
When will the Fabric 1.4.1 ibm image be available on https://hub.docker.com/u/ibmblockchain/?

tsnyder (Wed, 26 Jun 2019 03:23:33 GMT):
When will the Fabric 1.4.1 ibm images be available on https://hub.docker.com/u/ibmblockchain/?

lucaslep (Wed, 26 Jun 2019 10:04:37 GMT):
Has joined the channel.

lucaslep (Wed, 26 Jun 2019 10:04:37 GMT):
When will the new 2.0 version be probably released?

dave.enyeart (Mon, 01 Jul 2019 23:50:40 GMT):
@lucaslep v2.0 is not on the quarterly release schedule - the maintainers are taking the major release step as an opportunity to make some larger changes.

dave.enyeart (Mon, 01 Jul 2019 23:51:19 GMT):
We are closing down the next quarterly release, v1.4.2, in the release-1.4 branch for a release in mid-July. While we don't do code freezes per se until release day, we need to be increasingly cautious with merges as we get into July. There of course are automated tests running all the time and additional release testing going on, but be careful out there!

dave.enyeart (Mon, 01 Jul 2019 23:51:19 GMT):
We are closing down the next quarterly release, v1.4.2, in the release-1.4 branch for a release in mid-July. While we don't do code freezes per se until release week, we need to be increasingly cautious with merges as we get into July. There of course are automated tests running all the time and additional release testing going on, but be careful out there!

guoger (Tue, 02 Jul 2019 01:30:51 GMT):
@dave.enyeart what's the process of including something in release note? https://gerrit.hyperledger.org/r/c/fabric/+/32138 makes a small change to config yaml parsing, which probably should be included in release note. thx

mastersingh24 (Tue, 02 Jul 2019 08:49:08 GMT):
We hand create the release notes, so if you want to kick things off, create a v1.4.2.txt under release_notes and then add the info under the "Changes,..." section ;)

dave.enyeart (Tue, 02 Jul 2019 10:54:25 GMT):
@guoger Yeah, best to draft release notes as we go, but in reality I often look over the entire release content in the final weeks and draft them myself. Tagging the Jira fields "Release Note Required" and "Release Note" at least leaves a breadcrumb trail that helps me pull them together.

dave.enyeart (Tue, 02 Jul 2019 10:55:22 GMT):
I've tagged this one with some placeholder text in the Jira field. Would be great to replace with better text.

dave.enyeart (Tue, 02 Jul 2019 10:59:31 GMT):
If this one is v2.0, we can change v2.0.0-alpha.txt to v2.0.0.txt and evolve it for v2.0.0. Many of the alpha release notes will persist into the v2.0.0 release notes.

florianc (Fri, 12 Jul 2019 12:26:35 GMT):
Has joined the channel.

dave.enyeart (Mon, 15 Jul 2019 14:50:53 GMT):
v1.4.2 release update - early this week there is some final testing ongoing including testing the updated node OU support and dependency updates to couchdb, kafka, zookeeper (https://gerrit.hyperledger.org/r/#/c/fabric-baseimage/+/32176/). I will also be updating release notes. If everything goes smoothly we expect to release v1.4.2 midweek. Please post here if anybody knows of any remaining issues or tasks that need to be addressed before v1.4.2 release.

dave.enyeart (Mon, 15 Jul 2019 14:50:53 GMT):
v1.4.2 release update - early this week there is some final testing ongoing If everything goes smoothly we expect to release v1.4.2 midweek. Please post here if anybody knows of any remaining issues or tasks that need to be addressed before v1.4.2 release.

haniavis (Mon, 15 Jul 2019 22:14:36 GMT):
Has joined the channel.

SamYuan1990 (Tue, 16 Jul 2019 05:53:02 GMT):
Has joined the channel.

dave.enyeart (Wed, 17 Jul 2019 22:34:59 GMT):
Fabric and Fabric-CA v1.4.2 is published and tagged

dave.enyeart (Sat, 20 Jul 2019 14:28:46 GMT):
---------------------------------------------------------------------- Hyperledger Fabric v1.4.2 RELEASE ANNOUNCEMENT: https://lists.hyperledger.org/g/fabric/message/6484 ----------------------------------------------------------------------

StephanieYi (Mon, 22 Jul 2019 17:03:24 GMT):
Has joined the channel.

huxd (Fri, 02 Aug 2019 01:30:49 GMT):
Has joined the channel.

conanoc (Fri, 02 Aug 2019 03:59:16 GMT):
Has joined the channel.

qsmen (Wed, 14 Aug 2019 01:49:35 GMT):
hi experts, in email list, one security problem is pointed out. only one org can upgrade a chaincode and change its endorsing policy. This is a very serious security problem. I also notice that more versions like 1.4.x are released. I suggest in the future version 1.4.x+1 this problem is solved after all it is a long term service version and may be used in production environment.

qsmen (Wed, 14 Aug 2019 01:49:35 GMT):
hi experts, in email list, one security problem in version 1.4.x is pointed out. only one org can upgrade a chaincode and change its endorsing policy. This is a very serious security problem. I also notice that more versions like 1.4.x are released. I suggest in the future version 1.4.x+1 this problem is solved after all it is a long term service version and may be used in production environment.

qsmen (Wed, 14 Aug 2019 01:49:35 GMT):
hi experts, in email list, one security problem in version 1.4.x is pointed out that only one org can upgrade a chaincode and change its endorsing policy. This is a very serious security problem. I also notice that more versions like 1.4.x are released in sequence. I suggest in the future version 1.4.x+1 this problem can be solved after all it is a long term service version and may be already used in production environment by many teams

qsmen (Wed, 14 Aug 2019 01:49:35 GMT):
hi experts, in email list, one security problem in version 1.4.x is pointed out that any one org can upgrade a chaincode and change its endorsing policy. This is a very serious security problem. I also notice that more versions like 1.4.x are released in sequence. I suggest in the future version 1.4.x+1 this problem can be solved after all it is a long term service version and may be already used in production environment by many teams

qsmen (Wed, 14 Aug 2019 01:49:35 GMT):
hi experts, in email list, one security problem in version 1.4.x is pointed out that one org can upgrade a chaincode and change its endorsing policy. This is a very serious security problem. I also notice that more versions like 1.4.x are released in sequence. I suggest in the future version 1.4.x+1 this problem can be solved after all it is a long term service version and may be already used in production environment by many teams

dave.enyeart (Wed, 14 Aug 2019 14:47:56 GMT):
@qsmen This is how v1.x is designed... in the chaincode instantiation policy you identify which org should control instantiations and upgrades. v2.0 is nearing development completion and adds support for decentralized chaincode governance where you can define a policy of which orgs need to come to agreement on chaincode definitions and upgrades. You can check out the 2.0 alpha with decentralized chaincode governance and let us know your feedback: https://hyperledger-fabric.readthedocs.io/en/master/whatsnew.html#fabric-chaincode-lifecycle

dave.enyeart (Wed, 14 Aug 2019 14:48:25 GMT):
This is how v1.x is designed... in the chaincode instantiation policy you identify which org should control instantiations and upgrades. v2.0 is nearing development completion and adds support for decentralized chaincode governance where you can define a policy of which orgs need to come to agreement on chaincode definitions and upgrades. You can check out the 2.0 alpha with decentralized chaincode governance and let us know your feedback: https://hyperledger-fabric.readthedocs.io/en/master/whatsnew.html#fabric-chaincode-lifecycle

dave.enyeart (Wed, 14 Aug 2019 14:48:25 GMT):
This is how v1.x is designed... in the chaincode instantiation policy you identify which org should control instantiations and upgrades. v2.0 is nearing development completion and adds support for decentralized chaincode governance where you can define a policy of which orgs need to come to agreement on chaincode definitions and upgrades before they are active. You can check out the 2.0 alpha with decentralized chaincode governance and let us know your feedback: https://hyperledger-fabric.readthedocs.io/en/master/whatsnew.html#fabric-chaincode-lifecycle

qsmen (Thu, 15 Aug 2019 01:10:51 GMT):
Thank you Dave. Do you mean it is hard or impossible to change the problem in 1.4.x?

dave.enyeart (Thu, 15 Aug 2019 01:18:47 GMT):
It has been a substantial amount of new design and code to support decentralized chaincode governance... if you added it all to v1.4.x you would end up with v2.0 :)

qsmen (Thu, 15 Aug 2019 05:45:07 GMT):
I see. Thank you again. :-)

tinywell (Tue, 20 Aug 2019 00:59:41 GMT):
Has joined the channel.

galaxystar (Tue, 20 Aug 2019 01:24:50 GMT):
Has joined the channel.

bjcawanglu (Tue, 20 Aug 2019 02:06:43 GMT):
Has joined the channel.

ibmamnt (Tue, 20 Aug 2019 06:21:09 GMT):
Assuming v2.0.0 to be released is not LTS, can we assume v1.4.x is going to be maintained next year ? I mean, after Jan/10th/2020 ? I mean this statement ``` the Fabric maintainers are pledging to provide bug fixes for a period of one year from the date of release (Jan 10) ```

dave.enyeart (Tue, 20 Aug 2019 12:40:20 GMT):
Yes, I expect maintainers will extend support for v1.4.x LTS well into next year.

dave.enyeart (Tue, 20 Aug 2019 12:40:20 GMT):
Yes, I expect maintainers will extend support for v1.4.x LTS well into next year. Exact timeframe to be decided upon v2.0 release.

dave.enyeart (Tue, 20 Aug 2019 12:40:20 GMT):
Yes, I expect maintainers will extend support for v1.4.x LTS well into next year. Exact timeframe to be decided upon v2.0 release, to ensure sufficient overlap in support.

ibmamnt (Wed, 21 Aug 2019 00:18:40 GMT):
thank you !

narendranathreddy (Wed, 21 Aug 2019 04:35:31 GMT):
Has joined the channel.

shitaibin (Thu, 22 Aug 2019 12:17:59 GMT):
Has joined the channel.

dave.enyeart (Tue, 27 Aug 2019 03:43:11 GMT):
---------------------------------------------------------------------- Hyperledger Fabric v1.4.3 RELEASE ANNOUNCEMENT: https://lists.hyperledger.org/g/fabric/message/6709 ----------------------------------------------------------------------

paranjan (Tue, 27 Aug 2019 05:27:27 GMT):
Has joined the channel.

ihormudryy (Thu, 05 Sep 2019 11:00:30 GMT):
raft leader

simsonraj (Tue, 10 Sep 2019 06:59:23 GMT):
Has joined the channel.

soumyanayak (Sun, 15 Sep 2019 04:55:54 GMT):
Has joined the channel.

soumyanayak (Sun, 15 Sep 2019 04:59:40 GMT):
2.0 release

soumyanayak (Sun, 15 Sep 2019 05:00:47 GMT):
When will be the v2.0 released ?

greg2git (Sun, 15 Sep 2019 11:13:31 GMT):
@soumyanayak i'm expecting it by the end of 4Q2019

generak (Sun, 15 Sep 2019 11:45:22 GMT):
Has joined the channel.

medikent (Tue, 24 Sep 2019 20:25:20 GMT):
Has joined the channel.

jona-sc (Thu, 26 Sep 2019 10:28:51 GMT):
Has joined the channel.

japidei (Sun, 29 Sep 2019 04:49:19 GMT):
Has joined the channel.

EltonSearcy (Mon, 30 Sep 2019 17:06:34 GMT):
Has joined the channel.

HLFPOC (Tue, 01 Oct 2019 16:58:49 GMT):
Has joined the channel.

sanket1211 (Fri, 04 Oct 2019 05:04:57 GMT):
Has joined the channel.

Adhavpavan (Fri, 04 Oct 2019 09:25:31 GMT):
Has joined the channel.

dave.enyeart (Sun, 06 Oct 2019 17:12:43 GMT):
@BrettLogan @vijay.bP baseimage 0.4.16 release CR has been merged by @mastersingh24 , images are on dockerhub, go ahead and run the multiarch job

dave.enyeart (Sun, 06 Oct 2019 17:12:43 GMT):
@BrettLogan @vijay.bP baseimage 0.4.16 release CR has been pushed by @mastersingh24 , images are on dockerhub, go ahead and run the multiarch job

dave.enyeart (Sun, 06 Oct 2019 17:13:05 GMT):
I've submitted CR to prepare for 0.4.17 as well as CRs in each repository to use 0.4.16

BrettLogan (Sun, 06 Oct 2019 17:34:09 GMT):
triggered @dave.enyeart

BrettLogan (Sun, 06 Oct 2019 17:43:43 GMT):
https://hub.docker.com/r/hyperledger/fabric-baseimage/tags?page=1&name=latest

BrettLogan (Sun, 06 Oct 2019 17:43:45 GMT):
Published

BrettLogan (Mon, 07 Oct 2019 03:04:59 GMT):
@mastersingh24 @dave.enyeart The fabric-baseimage update breaks the Fabric-CA FVT tests. Postgres 9.5 doesn't exist in the debian repository anymore on that OS level, so the FVT image can't be built. This won't be a problem later this week when I finish the work on making Postgres, MySQL and LDAP standalone containers, but CI will be hung up until I finish that work. Finished MySQL tonight, starting Postgres in the morning. Just an FYI in case you want to force-merge the Fabric-CA update to update baseimage 0.4.16.

BrettLogan (Mon, 07 Oct 2019 03:04:59 GMT):
@mastersingh24 @dave.enyeart The fabric-baseimage update breaks the Fabric-CA FVT tests. Postgres 9.5 doesn't exist in the debian repository anymore on that OS level, so the FVT image can't be built. This won't be a problem later this week when I finish the work on making Postgres, MySQL and LDAP standalone containers, but CI will be hung up until I finish that work. I finished MySQL tonight, starting Postgres in the morning. Just an FYI in case you want to force-merge the Fabric-CA update to update baseimage 0.4.16.

BrettLogan (Mon, 07 Oct 2019 03:04:59 GMT):
@mastersingh24 @dave.enyeart The fabric-baseimage update breaks the Fabric-CA FVT tests. Postgres 9.5 doesn't exist in the debian repository anymore on that OS level, so the FVT image can't be built. This won't be a problem later this week when I finish the work on making Postgres, MySQL and LDAP standalone containers, but CI will be hung up until I finish that work. I finished MySQL tonight, starting Postgres in the morning. Just an FYI in case you want to force-merge the Fabric-CA PR to update baseimage 0.4.16.

mastersingh24 (Mon, 07 Oct 2019 08:13:54 GMT):
I'll take a look ... we can always keep the FVT image at the old level if needed

mastersingh24 (Mon, 07 Oct 2019 12:48:22 GMT):
I think I got around the postgresql issue (the image now builds), but seems like tests are failing for other reasons

mastersingh24 (Mon, 07 Oct 2019 12:48:36 GMT):
And they are nearly impossible to debug

mastersingh24 (Mon, 07 Oct 2019 13:23:52 GMT):
Those CA FVT tests take forever

BrettLogan (Mon, 07 Oct 2019 13:33:30 GMT):
Tell me about it. Its been miserable debugging it. I started going in to the run_fvt_tests script, and just limiting it to a test I knew was failing. Also removed the image rebuild from the make Target so I didn't have to wait 10 minutes for the image to build every time

BrettLogan (Tue, 08 Oct 2019 21:41:27 GMT):
@dave.enyeart I identified the issue with baseimage 0.4.16 in Fabric CA. I passed the info on to Gari to see if he can help me resolve it. It's related to certificate generation using SSL

BrettLogan (Tue, 08 Oct 2019 21:43:17 GMT):
https://jira.hyperledger.org/browse/FABC-878

mastersingh24 (Thu, 10 Oct 2019 11:35:41 GMT):
Yay! I think I finally got past this

hyper-sunder (Wed, 23 Oct 2019 03:32:19 GMT):
Has joined the channel.

pradeeppadmarajaiah (Mon, 11 Nov 2019 11:18:01 GMT):
When will be the v2.0 getting released. Will it include fab coins ??

knagware9 (Mon, 11 Nov 2019 12:46:35 GMT):
V2.0 will be released Q1 2020 and fabcoins is removed from this release

BrettLogan (Mon, 11 Nov 2019 14:28:26 GMT):
We are targeting a beta of v2 in early December and then yes, early 2020 for v2. And yes, fabtoken has been removed, you can check out the mailing list for the reasons behind the removal

dave.enyeart (Thu, 14 Nov 2019 22:49:25 GMT):
Fabric v1.4.4 is being released... for the latest status see #fabric-maintainers chat

Coada (Fri, 15 Nov 2019 08:01:38 GMT):
what changes have been added to the release? The only note I can see is FAB-17072 and that you've moved to Azure Pipelines

BrettLogan (Fri, 15 Nov 2019 13:40:01 GMT):
@Coada We We are working on that. For some reason GitHub isn't rendering the release notes properly.

BrettLogan (Fri, 15 Nov 2019 13:40:40 GMT):
If you want to check it out immediately the release notes are available in the release_notes folder in the repo

BrettLogan (Fri, 15 Nov 2019 15:05:40 GMT):
We fixed it, it should be good now

dave.enyeart (Fri, 15 Nov 2019 15:46:47 GMT):
Yeah, release notes are rendering properly here: https://github.com/hyperledger/fabric/releases/tag/v1.4.4

dave.enyeart (Fri, 15 Nov 2019 19:42:39 GMT):
All done with Fabric and Fabric-CA v1.4.4 releases.

GioG12 (Mon, 18 Nov 2019 14:22:27 GMT):
Has joined the channel.

GioG12 (Mon, 18 Nov 2019 14:22:27 GMT):
Hello guys, is it easy to migrate from 1.4 to 2.0?

dave.enyeart (Mon, 18 Nov 2019 18:38:48 GMT):
The upgrade is currently being documented, you can see a preview of the steps at https://jira.hyperledger.org/browse/FAB-16754

ssk-git (Tue, 19 Nov 2019 06:39:49 GMT):
Has joined the channel.

SamYuan1990 (Mon, 02 Dec 2019 12:42:17 GMT):
hello, can anyone help verify FAB-17151, FAB-17152, FAB-17149 are still issue on current master branch? I try to fix them with defer os.removeall(tempdir) but I back to latest master tested locally, can not reproduce. via go test .

SamYuan1990 (Mon, 02 Dec 2019 12:43:53 GMT):
or do i need some specific script to run the test?

dtomczyk (Thu, 05 Dec 2019 12:23:08 GMT):
Has joined the channel.

icarrascol (Thu, 05 Dec 2019 20:33:24 GMT):
Has joined the channel.

SimonJousse (Fri, 06 Dec 2019 10:03:06 GMT):
Has joined the channel.

joserobleslima (Sat, 14 Dec 2019 18:34:39 GMT):
Has joined the channel.

zwartesokken (Mon, 16 Dec 2019 09:20:28 GMT):
Hi guys, any update about what the new LTS will be? According to this blog post https://www.hyperledger.org/blog/2019/01/10/introducing-hyperledger-fabric-1-4-lts LTS will be outdated on 10th of january 2020.

easeev (Mon, 16 Dec 2019 12:15:56 GMT):
Has joined the channel.

BrettLogan (Mon, 16 Dec 2019 13:05:25 GMT):
2.0 is slated for sometime in January. 1.4 will have it's EOL extended for a period to allow people time to plan their migrations

BrettLogan (Mon, 16 Dec 2019 13:05:25 GMT):
1.4 has had it's EOL extended. 2.0 LTS is slated for sometime in January. 1.4 will have it EOL extended 1 year from the date we release 2.0. So EOL for 1.4 will be sometime in early 2021

BrettLogan (Mon, 16 Dec 2019 13:05:25 GMT):
1.4 has had it's EOL extended. 2.0 LTS is slated for sometime in January. 1.4 will have it EOL extended for some period to allow people time to plan their migrations

BrettLogan (Mon, 16 Dec 2019 13:05:25 GMT):
2.0 LTS is slated for sometime in January. 1.4 will have it EOL extended for some period to allow people time to plan their migrations

BrettLogan (Mon, 16 Dec 2019 13:05:25 GMT):
2.0 LTS is slated for sometime in January. 1.4 will have it's EOL extended for a period to allow people time to plan their migrations

dave.enyeart (Mon, 16 Dec 2019 19:50:31 GMT):
---------------------------------------------------------------------- Hyperledger Fabric v2.0 Beta RELEASE ANNOUNCEMENT: https://lists.hyperledger.org/g/fabric/message/7427 ----------------------------------------------------------------------

githubcpc (Tue, 17 Dec 2019 09:31:01 GMT):
@dave.enyeart Could HLF support to deploy on arm64v8 ?

mastersingh24 (Tue, 17 Dec 2019 09:38:03 GMT):
I believe Fabric should build fine on arm64v8 but we do not plan an providing any prebuilt binaries at this point.

githubcpc (Tue, 17 Dec 2019 09:40:40 GMT):
I find something about this in Jira.They seem to deploy HLF on Raspberry Pi 3.

githubcpc (Wed, 18 Dec 2019 08:10:32 GMT):
I hava already build successfully on ubuntu18.04 arm64v8. Thanks :)

ChaoLiu (Sat, 21 Dec 2019 17:14:39 GMT):
Has joined the channel.

andreevym (Wed, 25 Dec 2019 17:26:31 GMT):
Has joined the channel.

rohand (Fri, 03 Jan 2020 13:48:30 GMT):
Has joined the channel.

rohand (Fri, 03 Jan 2020 13:48:33 GMT):
Hello guys, when can we expect a stable release of HLF 2.0?

BrettLogan (Fri, 03 Jan 2020 22:42:29 GMT):
We are targeting January still

rohand (Mon, 06 Jan 2020 12:39:03 GMT):
Good to know. Thanks.

mastersingh24 (Tue, 07 Jan 2020 12:10:40 GMT):
although the beta should be stable

ZainabM (Thu, 09 Jan 2020 11:49:00 GMT):
Has joined the channel.

dave.enyeart (Thu, 30 Jan 2020 14:57:34 GMT):
---------------------------------------------------------------------- Hyperledger Fabric v2.0 RELEASE ANNOUNCEMENT: https://lists.hyperledger.org/g/fabric/message/7662 ----------------------------------------------------------------------

knagware9 (Sat, 01 Feb 2020 09:29:26 GMT):
Is Fabric samples also released? Not getting downloaded & not even available in git repo ===> Checking out v2.0.0 of hyperledger/fabric-samples error: pathspec 'v2.0.0' did not match any file(s) known to git.

BrettLogan (Sat, 01 Feb 2020 15:04:34 GMT):
@knagware9 we haven't yet tagged Fabric samples, we are working on some updates yet. But you can ignore that error for now. Since when it fails to checkout v2.0.0 it defaults to the master branch, you are getting what will eventually be the 2.0.0 tag anyway

knagware9 (Sat, 01 Feb 2020 16:44:41 GMT):
okay...did the same as of now

BrettLogan (Sat, 01 Feb 2020 16:50:14 GMT):
Again, just ignore the error, it doesn't affect anything. It'll be a few days till we tag samples

knagware9 (Sat, 01 Feb 2020 16:54:11 GMT):
yes..Thanks

narendranathreddy (Sat, 08 Feb 2020 08:29:29 GMT):
Hello All iam proud to announce that my book `Mastering Hyperledger fabric` is now available for pre-order https://www.amazon.com/dp/B084KZP9M7?ref_=pe_3052080_276849420

narendranathreddy (Sat, 08 Feb 2020 08:29:29 GMT):
Hello All iam proud to announce that my book `Mastering Hyperledger fabric` is now available for pre-order https://amzn.to/2UI38ok

yacovm (Sat, 08 Feb 2020 11:17:49 GMT):
"and written with three years of hyperledger fabric production experience." - Well but Fabric 1.0 was released in the second half of 2017 so it doesn't even exist for 3 years.

narendranathreddy (Tue, 11 Feb 2020 14:49:08 GMT):

Clipboard - February 11, 2020 6:49 PM

narendranathreddy (Tue, 11 Feb 2020 14:51:00 GMT):

Mastering Hyperledger Fabric - February 11, 2020 6:50 PM

narendranathreddy (Tue, 11 Feb 2020 14:59:24 GMT):
Mastering Hyperledger Fabric. A one-stop solution to become Master in the Hyperledger Fabric Key Features Detailed Explanation of One way TLS and mutual TLS Detailed Explanation of docker sockets (docker.sock) Exposed functionalities of Fabric CLI’s and SDK’s Enterprise level chaincode development Advanced examples of Node and golang Fabric SDK Onboard new organization using nodejs SDK (No more CLI) CI/CD for chaincode (Install chaincode directly onto peers from GitHub using Node.js) Fabric setup explanation with Different real time use cases Deployment of Hyperledger Fabric using docker swarm and kubernetes Setup and configure caliper to check benchmarks Monitor consortium with Prometheus and grafana Monitor docker and docker swarm using swarmpit and logspout Logging consortium with ELK/EFK stack Some interesting open source tools and some Bonus concepts Table of Contents Chapter1: Introduction to the Hyperledger Landscape Chapter2: The Disruptive Potential of TLS Chapter3: All about docker sockets Chapter4: Installation Guide Of Prerequisites Chapter5: All about fabric CLI Chapter6: All about SDK's (go lang and Node.js) Chapter7: Advanced Chaincode Chapter8: Running fabric consortium with Solo consensus using docker Chapter9: Running fabric Consortium with Kafka consensus using docker swarm Chapter10: Running fabric Consortium with Raft consensus using kubernetes Chapter11: Private Data Concept Chapter12: Setup and Benchmark Blockchain Consortium Using Caliper Chapter13: Monitoring Consortium with Prometheus and grafana Chapter14: Logging Consortium with ELK Stack Chapter15: Some Interesting tools Who this Book is For This Book benefits Software Engineers who are ready to shift their focus to distributed technologies and Blockchain. This book provides a comprehensive view of Solution Architecture so, it will be easy for architects to architect their solution. CTO’s around the world want to add hyperledger fabric to their technology stack. Managers to cope up with the latest trend. Faculty Professors in order to get industry insights. Even Engineering Students who want to be ready with the latest technologies. Book Description Mastering Hyperledger Fabric is a craving topic for all Hyperledger Fabric Developers around the world. Hyperledger Fabric is an open-source project that helps organizations create and maintain permissioned distributed Blockchain consortiums. This book is for readers who are looking for Hyperledger offerings to build end-to-end projects with growing complexity and functionalities. This book will be a one-stop solution for all developers who want to build blockchain consortiums using Hyperledger Fabric. Topics includes TLS, Unix sockets, caliper(Benchmark tool), raft consensus, advanced chaincode development, key collision and MVCC, chaincode access controls, chaincode encryption, node.js SDK, golang SDK, docker daemon API, private data concepts, onboarding organizations using node.js SDK, deploy hyperledger fabric using Kubernetes, deploy hyperledger fabric using docker swarm, monitoring hyperledger fabric, monitoring Kubernetes, monitoring docker swarm, logging hyperledger fabric. After reading this book the reader will be able to set up Production grade hyperledger fabric consortium using raft consensus mechanisms with monitoring using Prometheus and grafana, even logging. This book can be read by software engineers, blockchain engineers, university professors, university students, any level from beginner to master. A deep learning cure is there for beginners. This book explains so many key concepts of hyperledger fabric and written with three years of hyperledger fabric production experience.

ahmedsajid (Thu, 13 Feb 2020 14:57:52 GMT):
Has joined the channel.

Satoshi24 (Fri, 14 Feb 2020 07:47:06 GMT):
Has joined the channel.

japidei (Tue, 25 Feb 2020 11:21:46 GMT):
# curl -sSL http://bit.ly/2ysbOFE | bash -s -- 1.4.4 1.4.4 -s -d Pull Hyperledger Fabric binaries ===> Downloading version 1.4.4 platform specific fabric binaries ===> Downloading: https://github.com/hyperledger/fabric/releases/download/v1.4.4/hyperledger-fabric-linux-amd64-1.4.4.tar.gz % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 100 633 100 633 0 0 1540 0 --:--:-- --:--:-- --:--:-- 1536 100 79.6M 100 79.6M 0 0 13.7M 0 0:00:05 0:00:05 --:--:-- 17.4M ==> Done. ===> Downloading version 1.4.4 platform specific fabric-ca-client binary ===> Downloading: https://github.com/hyperledger/fabric-ca/releases/download/v1.4.4/hyperledger-fabric-ca-linux-amd64-1.4.4.tar.gz % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 100 636 100 636 0 0 1700 0 --:--:-- --:--:-- --:--:-- 1696 100 19.7M 100 19.7M 0 0 7456k 0 0:00:02 0:00:02 --:--:-- 15.1M ==> Done. # bin/fabric-ca-server start -b admin:adminpw 2020/02/25 11:14:39 [INFO] Configuration file location: /root/fabric-ca-server-config.yaml 2020/02/25 11:14:39 [INFO] Starting server in home directory: /root 2020/02/25 11:14:39 [INFO] Server Version: 1.4.4 2020/02/25 11:14:39 [INFO] Server Levels: &{Identity:2 Affiliation:1 Certificate:1 Credential:1 RAInfo:1 Nonce:1} 2020/02/25 11:14:39 [INFO] The CA key and certificate already exist 2020/02/25 11:14:39 [INFO] The key is stored by BCCSP provider 'SW' 2020/02/25 11:14:39 [INFO] The certificate is at: /root/ca-cert.pem *2020/02/25 11:14:39 [ERROR] Error occurred initializing database: Failed to open sqlite3 DB: sql: unknown driver "sqlite3" (forgotten import?)* 2020/02/25 11:14:39 [INFO] Home directory for default CA: /root 2020/02/25 11:14:39 [INFO] Operation Server Listening on 127.0.0.1:9443 2020/02/25 11:14:39 [INFO] Listening on http://0.0.0.0:7054

japidei (Tue, 25 Feb 2020 11:22:21 GMT):
Happens since fabric-ca-server can be downloaded with bootstrap.sh (1.4.4, 1.4.5)

BrettLogan (Tue, 25 Feb 2020 13:22:15 GMT):
I'll take a look at it today

japidei (Tue, 25 Feb 2020 14:42:49 GMT):
Thanks

BrettLogan (Tue, 25 Feb 2020 17:49:09 GMT):
We validated the problem and are working on a fix, thank you for bringing to our attention @japidei

japidei (Tue, 25 Feb 2020 18:04:03 GMT):
Thanks you for the quick answer!

BrettLogan (Tue, 25 Feb 2020 23:01:39 GMT):
1.4.6 fabric-ca is release with a fixed binary, thanks again. You can download it using the bootstrap script or grab it right from github @japidei

BrettLogan (Tue, 25 Feb 2020 23:01:39 GMT):
1.4.6 fabric-ca is released with a fixed binary, thanks again. You can download it using the bootstrap script or grab it right from github @japidei

japidei (Wed, 26 Feb 2020 07:45:42 GMT):
Thanks a lot

japidei (Wed, 26 Feb 2020 08:25:32 GMT):
Maybe for the next release it will be great to fix the bootstrap script in the release-1.4 since the nexus repositories no longer work

japidei (Wed, 26 Feb 2020 08:25:40 GMT):
diff --git a/scripts/bootstrap.sh b/scripts/bootstrap.sh index 351a10094..0cd8c2f72 100755 --- a/scripts/bootstrap.sh +++ b/scripts/bootstrap.sh @@ -79,7 +79,7 @@ samplesInstall() { binaryIncrementalDownload() { local BINARY_FILE=$1 local URL=$2 - curl -f -s -C - ${URL} -o ${BINARY_FILE} || rc=$? + curl -f -s -L -C - ${URL} -o ${BINARY_FILE} || rc=$? # Due to limitations in the current Nexus repo: # curl returns 33 when there's a resume attempt with no more bytes to download # curl returns 2 after finishing a resumed download @@ -121,7 +121,7 @@ binaryDownload() { echo "==> Partial binary file found. Resuming download..." binaryIncrementalDownload ${BINARY_FILE} ${URL} else - curl ${URL} | tar xz || rc=$? + curl -L ${URL} | tar xz || rc=$? if [ ! -z "$rc" ]; then echo "==> There was an error downloading the binary file. Switching to incremental download." echo "==> Downloading file..." @@ -134,7 +134,7 @@ binaryDownload() { binariesInstall() { echo "===> Downloading version ${FABRIC_TAG} platform specific fabric binaries" - binaryDownload ${BINARY_FILE} https://nexus.hyperledger.org/content/repositories/releases/org/hyperledger/fabric/hyperledger-fabric/${ARCH}-${VERSION}/${BINARY_FILE} + binaryDownload ${BINARY_FILE} https://github.com/hyperledger/fabric/releases/download/v${VERSION}/${BINARY_FILE} if [ $? -eq 22 ]; then echo echo "------> ${FABRIC_TAG} platform specific fabric binary is not available to download <----" @@ -142,7 +142,7 @@ binariesInstall() { fi echo "===> Downloading version ${CA_TAG} platform specific fabric-ca-client binary" - binaryDownload ${CA_BINARY_FILE} https://nexus.hyperledger.org/content/repositories/releases/org/hyperledger/fabric-ca/hyperledger-fabric-ca/${ARCH}-${CA_VERSION}/${CA_BINARY_FILE} + binaryDownload ${BINARY_FILE} https://github.com/hyperledger/fabric-ca/releases/download/v${VERSION}/${CA_BINARY_FILE} if [ $? -eq 22 ]; then echo echo "------> ${CA_TAG} fabric-ca-client binary is not available to download (Available from 1.1.0-rc1) <----"

japidei (Wed, 26 Feb 2020 08:26:52 GMT):
I meant in the release-1.4 branch

dave.enyeart (Wed, 26 Feb 2020 22:21:21 GMT):
v2.0.1 released.

japidei (Mon, 02 Mar 2020 11:18:59 GMT):
fabric-ca-server 1.4.6 keep failing with sqlite in the linux-amd64 version of the binaries

japidei (Mon, 02 Mar 2020 11:19:14 GMT):
# fabric-ca-server start -b admin:adminpw 2020/03/02 12:14:18 [INFO] Created default configuration file at /tmp/fabric-ca-server-config.yaml 2020/03/02 12:14:18 [INFO] Starting server in home directory: /tmp 2020/03/02 12:14:18 [INFO] Server Version: 1.4.6 2020/03/02 12:14:18 [INFO] Server Levels: &{Identity:2 Affiliation:1 Certificate:1 Credential:1 RAInfo:1 Nonce:1} 2020/03/02 12:14:18 [WARNING] &{69 The specified CA certificate file /tmp/ca-cert.pem does not exist} 2020/03/02 12:14:18 [INFO] generating key: &{A:ecdsa S:256} 2020/03/02 12:14:18 [INFO] encoded CSR 2020/03/02 12:14:18 [INFO] signed certificate with serial number 203546683472891104476120144848843755988183526234 2020/03/02 12:14:18 [INFO] The CA key and certificate were generated for CA 2020/03/02 12:14:18 [INFO] The key was stored by BCCSP provider 'SW' 2020/03/02 12:14:18 [INFO] The certificate is at: /tmp/ca-cert.pem *2020/03/02 12:14:18 [ERROR] Error occurred initializing database: Failed to open sqlite3 DB: Binary was compiled with 'CGO_ENABLED=0', go-sqlite3 requires cgo to work. This is a stub *2020/03/02 12:14:18 [INFO] Home directory for default CA: /tmp

japidei (Mon, 02 Mar 2020 11:19:14 GMT):
# fabric-ca-server start -b admin:adminpw 2020/03/02 12:14:18 [INFO] Created default configuration file at /tmp/fabric-ca-server-config.yaml 2020/03/02 12:14:18 [INFO] Starting server in home directory: /tmp 2020/03/02 12:14:18 [INFO] Server Version: 1.4.6 2020/03/02 12:14:18 [INFO] Server Levels: &{Identity:2 Affiliation:1 Certificate:1 Credential:1 RAInfo:1 Nonce:1} 2020/03/02 12:14:18 [WARNING] &{69 The specified CA certificate file /tmp/ca-cert.pem does not exist} 2020/03/02 12:14:18 [INFO] generating key: &{A:ecdsa S:256} 2020/03/02 12:14:18 [INFO] encoded CSR 2020/03/02 12:14:18 [INFO] signed certificate with serial number 203546683472891104476120144848843755988183526234 2020/03/02 12:14:18 [INFO] The CA key and certificate were generated for CA 2020/03/02 12:14:18 [INFO] The key was stored by BCCSP provider 'SW' 2020/03/02 12:14:18 [INFO] The certificate is at: /tmp/ca-cert.pem *2020/03/02 12:14:18 [ERROR] Error occurred initializing database: Failed to open sqlite3 DB: Binary was compiled with 'CGO_ENABLED=0', go-sqlite3 requires cgo to work. This is a stub* 2020/03/02 12:14:18 [INFO] Home directory for default CA: /tmp

japidei (Mon, 02 Mar 2020 11:19:32 GMT):
Sorry, I just tested the darwin-amd64 version

jital (Mon, 09 Mar 2020 18:36:08 GMT):
Has joined the channel.

matanyahu (Mon, 06 Apr 2020 17:52:35 GMT):
Has joined the channel.

pritam_01 (Sat, 11 Apr 2020 07:27:40 GMT):
Has joined the channel.

dave.enyeart (Fri, 17 Apr 2020 03:08:20 GMT):
---------------------------------------------------------------------- Hyperledger Fabric v2.1 RELEASE ANNOUNCEMENT: https://lists.hyperledger.org/g/fabric/message/8091 ----------------------------------------------------------------------

fk2 (Thu, 23 Apr 2020 00:01:00 GMT):
Has joined the channel.

SviatoslavButskyi (Sun, 03 May 2020 13:57:21 GMT):
Has joined the channel.

nao (Tue, 19 May 2020 08:38:16 GMT):
Has joined the channel.

nao (Tue, 19 May 2020 08:38:16 GMT):
LTS

Matrixik (Mon, 25 May 2020 08:26:59 GMT):
Has joined the channel.

tatsu-sato (Fri, 19 Jun 2020 16:56:21 GMT):
Has joined the channel.

JohnSColeman (Tue, 23 Jun 2020 10:24:00 GMT):
Has joined the channel.

JohnSColeman (Tue, 23 Jun 2020 10:24:01 GMT):
Hi, when are we likely to see a release with more significant performance improvements such as caching the results of Protocol Buffers unmarshaling of blocks?

dave.enyeart (Tue, 23 Jun 2020 18:19:59 GMT):
@JohnSColeman you're right that is the next most obvious performance improvement to go after - https://jira.hyperledger.org/browse/FAB-14645 . The person that was going to work on it picked up something else instead. It is not scheduled for any release at the moment. I've tagged the issue as `help-wanted` for anybody to pick up.

n-horiguchi (Thu, 25 Jun 2020 01:00:49 GMT):
Has joined the channel.

dave.enyeart (Thu, 09 Jul 2020 20:43:55 GMT):
---------------------------------------------------------------------- Hyperledger Fabric v2.2 LTS RELEASE ANNOUNCEMENT: https://lists.hyperledger.org/g/fabric/message/8643 ----------------------------------------------------------------------

dave.enyeart (Wed, 22 Jul 2020 21:41:46 GMT):
---------------------------------------------------------------------- Hyperledger Fabric v1.4.8 RELEASE ANNOUNCEMENT: https://lists.hyperledger.org/g/fabric/message/8703 ----------------------------------------------------------------------

davidkhala (Thu, 23 Jul 2020 07:59:22 GMT):
@dave.enyeart @dave.enyeart Dear Dave and Bret after my first try on 1.4.8, I find execution of curl -sSL http://bit.ly/2ysbOFE | bash -s -- 1.4.8 1.4.7 0.4.21 -s has a problem that it will try to fetch an non-exist docker image ====> hyperledger/fabric-javaenv:1.4.8 Error response from daemon: manifest for hyperledger/fabric-javaenv:1.4.8 not found: manifest unknown: manifest unknown Error response from daemon: No such image: hyperledger/fabric-javaenv:1.4.8 Error response from daemon: No such image: hyperledger/fabric-javaenv:1.4.8

davidkhala (Thu, 23 Jul 2020 07:59:22 GMT):
@dave.enyeart @BrettLogan Dear Dave and Bret after my first try on 1.4.8, I find execution of curl -sSL http://bit.ly/2ysbOFE | bash -s -- 1.4.8 1.4.7 0.4.21 -s has a problem that it will try to fetch an non-exist docker image ====> hyperledger/fabric-javaenv:1.4.8 Error response from daemon: manifest for hyperledger/fabric-javaenv:1.4.8 not found: manifest unknown: manifest unknown Error response from daemon: No such image: hyperledger/fabric-javaenv:1.4.8 Error response from daemon: No such image: hyperledger/fabric-javaenv:1.4.8

dave.enyeart (Thu, 23 Jul 2020 10:36:25 GMT):
Yeah, since we no longer keep java chaincode and node.js chaincode on the same 3rd digit releases this will happen, but it is benign because at runtime it will use most recent javaenv:1.4, and pull if needed. I'm thinking we should simply remove javaenv and nodeenv from the download script and people can pull what they need. Alternatively it could just pull most recent javaenv:1.4. What do you think @davidkhala @BrettLogan ?

davidkhala (Thu, 23 Jul 2020 12:24:56 GMT):
Remove it is OK for me while we should give more hints document about chaincode language dependent image requirement.

davidkhala (Thu, 23 Jul 2020 12:24:56 GMT):
Remove it is OK for me while we should give more hints in document about chaincode language dependent docker image requirement.

davidkhala (Thu, 23 Jul 2020 12:27:19 GMT):
Or could we add one more token such as `--chaincode-lang=java`

davidkhala (Thu, 23 Jul 2020 12:27:19 GMT):
Or could we add one more token such as `--chaincode-lang=java` to be recognized in download script?

BrettLogan (Thu, 23 Jul 2020 12:33:45 GMT):
https://github.com/hyperledger/fabric/pull/1633

BrettLogan (Thu, 23 Jul 2020 12:34:30 GMT):
My issue with adding any more complexity to bootstrap.sh is people already mess it up all the time. If anything we need to find ways of making it simpler

BrettLogan (Thu, 23 Jul 2020 12:36:03 GMT):
I do agree though, there isn't really any good information about what `chaincode.builder` and `chaincode..runtime` are and the fact they should be set. So unless someone is going through the entire `core.yaml` they wouldn't even know these exist_

BrettLogan (Thu, 23 Jul 2020 12:36:03 GMT):
I do agree though, there isn't really any good information about what `chaincode.builder` and `chaincode..runtime` are in the doc and the fact they should be set. So unless someone is going through the entire `core.yaml` they wouldn't even know these exist_

dave.enyeart (Fri, 24 Jul 2020 12:36:16 GMT):
To document the outcome... fabric-javaenv and fabric-nodeenv have been removed from the download script to avoid this confusion. Those images (with 1.4 tag) will still be pulled from dockerhub if needed at runtime, but we'd expect most deployments to pull down locally if they know they will be needed at runtime.

jtonline (Fri, 24 Jul 2020 12:41:33 GMT):
Has joined the channel.

davidkhala (Fri, 24 Jul 2020 15:04:09 GMT):
I think it is good enough

davidkhala (Fri, 24 Jul 2020 15:05:01 GMT):
:+1: and we should always keep it clean

ysai (Wed, 29 Jul 2020 05:50:08 GMT):
Has joined the channel.

xachen (Thu, 27 Aug 2020 01:16:46 GMT):
Has joined the channel.

nkl199 (Tue, 01 Sep 2020 09:54:45 GMT):
Has left the channel.

sstone1 (Thu, 03 Sep 2020 07:15:15 GMT):
Has left the channel.

nleut (Tue, 29 Sep 2020 20:53:29 GMT):
Has joined the channel.

nleut (Tue, 29 Sep 2020 20:55:23 GMT):
is there an estimate on when 2.2.1 will be released? or any other way to use the bug fix in FAB-18194 for legacy chaincode cache?

dave.enyeart (Wed, 30 Sep 2020 12:06:33 GMT):
We are expecting to release Fabric v1.4.9 and v2.2.1, and Fabric CA v1.4.9 this afternoon. @nleut in the interim you can build from the head of release-2.2 release branch.

dave.enyeart (Wed, 30 Sep 2020 22:41:05 GMT):
---------------------------------------------------------------------- Hyperledger Fabric v1.4.9 and v2.2.1 RELEASE ANNOUNCEMENT: https://lists.hyperledger.org/g/fabric/message/9088 ----------------------------------------------------------------------

gravity (Wed, 07 Oct 2020 14:26:45 GMT):
Has joined the channel.

gravity (Wed, 07 Oct 2020 14:29:09 GMT):
Hello Does anybody know when is EOL of 1.4 LTS? https://www.hyperledger.org/blog/2019/01/10/introducing-hyperledger-fabric-1-4-lts here it's mentioned that it will be supported for 1 year after the release and 1.4 was released on 10 Jan. 2019, but the most recent update in 1.4 is 1.4.9 (7 days ago)

dave.enyeart (Wed, 14 Oct 2020 14:13:50 GMT):
@gravity For 1.4 it is April 2021, see https://github.com/hyperledger/fabric#releases and the linked references that describe the LTS strategy

antoniovassell (Thu, 15 Oct 2020 12:56:07 GMT):
Hi, is there a `fabric-ca-client` binary that was released that can work with `2.2.1` docker images? For example using the `fabric-ca-client:1.4.9` binary an image with `hyperledger/fabric-tools` just says not found and the binary isn't working. I need it to generate certs.

antoniovassell (Thu, 15 Oct 2020 12:56:07 GMT):
Hi, is there a `fabric-ca-client` binary that was released that can work with `2.2.1` docker images? For example using the `fabric-ca-client:1.4.9` binary on an image with `hyperledger/fabric-tools` just says not found and the binary isn't working. I need it to generate certs.

antoniovassell (Thu, 15 Oct 2020 12:56:07 GMT):
Hi, is there a `fabric-ca-client` binary that was released that can work with `2.2.1` docker images? For example using the `fabric-ca-client:1.4.9` binary on an image with `hyperledger/fabric-tools` just says not found and the binary isn't working. I am trying to use it to generate certs.

dave.enyeart (Sun, 18 Oct 2020 04:17:57 GMT):
Fabric CA v1.4.9 client and server can be used to generate certs for Fabric v2.2.1, but there is no packaging that ties them together as such. You can see the operations guide https://hyperledger-fabric-ca.readthedocs.io/en/release-1.4/operations_guide.html deployment guide https://hyperledger-fabric-ca.readthedocs.io/en/release-1.4/deployguide/ca-deploy.html for guidance generating the certs.

dave.enyeart (Sun, 18 Oct 2020 04:18:21 GMT):
Fabric CA v1.4.9 client and server can be used to generate certs for Fabric v2.2.1, but there is no packaging that ties them together as such. You can see the operations guide https://hyperledger-fabric-ca.readthedocs.io/en/release-1.4/operations_guide.html deployment guide https://hyperledger-fabric-ca.readthedocs.io/en/release-1.4/deployguide/ca-deploy.html for guidance generating the certs.

dave.enyeart (Sun, 18 Oct 2020 04:18:21 GMT):
Fabric CA v1.4.9 client and server can be used to generate certs for Fabric v2.2.1, but there is no packaging that ties them together as such. You can see the operations guide https://hyperledger-fabric-ca.readthedocs.io/en/release-1.4/operations_guide.html and deployment guide https://hyperledger-fabric-ca.readthedocs.io/en/release-1.4/deployguide/ca-deploy.html for guidance generating the certs.

antoniovassell (Fri, 23 Oct 2020 12:19:04 GMT):
@dave.enyeart thanks. will run in a separate container

abhishek.medhane (Mon, 26 Oct 2020 06:16:38 GMT):
Has joined the channel.

heena066 (Mon, 02 Nov 2020 09:37:06 GMT):
Has joined the channel.

dave.enyeart (Wed, 18 Nov 2020 20:36:24 GMT):
---------------------------------------------------------------------- Hyperledger Fabric v2.3.0 RELEASE ANNOUNCEMENT: https://lists.hyperledger.org/g/fabric/message/9302 ----------------------------------------------------------------------

bh4rtp (Sat, 21 Nov 2020 01:52:31 GMT):
@dave.enyeart can i upgrade from v2.2.0 to v2.3.0 without any changes with configuration?

bh4rtp (Sat, 21 Nov 2020 01:52:31 GMT):
@dave.enyeart can i upgrade from v2.2.0 to v2.3.0 without any changes to configuration?

bh4rtp (Sat, 21 Nov 2020 01:52:31 GMT):
@dave.enyeart can i upgrade from v2.2.0 to v2.3.0 without any changes to configuration files, such as configtx.yaml, core.yaml, orderer.yaml?

bh4rtp (Sat, 21 Nov 2020 01:52:31 GMT):
@dave.enyeart can i upgrade from v2.2.0 to v2.3.0 without any changes to configuration files, such as configtx.yaml, core.yaml and orderer.yaml?

bh4rtp (Sat, 21 Nov 2020 01:52:31 GMT):
@dave.enyeart can i upgrade from `v2.2.0` to `v2.3.0` without any changes to configuration files, such as `configtx.yaml`, `core.yaml` and `orderer.yaml`?

BrettLogan (Mon, 23 Nov 2020 02:32:58 GMT):
You can, the only change is if you want to enable the beta of the `Channel Participation without System Channel API`

SamYuan1990 (Tue, 24 Nov 2020 15:33:03 GMT):
hi it seems that 2.3 binary is not match with 2.2 docker image, as I reproduced my ci error with fabric sample ci with PR here https://github.com/hyperledger/fabric-samples/pull/379

SamYuan1990 (Tue, 24 Nov 2020 15:33:11 GMT):

Clipboard - 2020年11月24日晚上11点32分

Roger (Thu, 07 Jan 2021 07:26:40 GMT):
Has left the channel.

dave.enyeart (Thu, 28 Jan 2021 19:18:42 GMT):
--------------------------------------------------------------------------------------- Hyperledger Fabric v1.4.10 and v2.2.2 RELEASE ANNOUNCEMENT: https://lists.hyperledger.org/g/fabric/message/9548 ----------------------------------------------------------------------------------------

greg2git (Fri, 29 Jan 2021 16:09:46 GMT):
wow, there is a lot of docker images deprecation going on with this .2 release. should we start considering kubernetes as the ultimate replacement of docker?

avidkucing (Fri, 29 Jan 2021 16:57:58 GMT):
Has joined the channel.

BrettLogan (Fri, 29 Jan 2021 20:27:54 GMT):
Those deprecations have been around for a long time. We only supported those images in 1.4 Fabric. In 2.x fabric we switched to using publicly available open source images for things like couchdb

greg2git (Sat, 30 Jan 2021 13:28:22 GMT):
sorry, didn't notice the brackets in _Deprecations (existing)_ - should it say 'pre-existing' (since 2.0) ? - whenever i'm pulling >=2.0 images some of them are from a different 'source' than <2.0 ?

BrettLogan (Sun, 31 Jan 2021 03:21:33 GMT):
None of those images were ever required to run fabric, they were convenience images to support fabric-samples. The images on dockerhub are only there to support fabric-samples, they are not meant for any other use case

BrettLogan (Sun, 31 Jan 2021 03:22:07 GMT):
And fabric-samples handles pulling all of the required images for you

vmanolas (Sun, 31 Jan 2021 14:55:08 GMT):
Has joined the channel.

RonaldReagan (Mon, 22 Feb 2021 01:09:45 GMT):
Has joined the channel.

dave.enyeart (Tue, 02 Mar 2021 20:50:20 GMT):
--------------------------------------------------------------------------------------- Hyperledger Fabric v1.4.11 RELEASE ANNOUNCEMENT: https://lists.hyperledger.org/g/fabric/message/9699 ----------------------------------------------------------------------------------------

barankilic (Wed, 03 Mar 2021 19:14:57 GMT):
Has joined the channel.

pakasi (Fri, 12 Mar 2021 05:52:47 GMT):
Has joined the channel.

DutyCat (Tue, 20 Apr 2021 00:17:13 GMT):
Has joined the channel.

DutyCat (Tue, 20 Apr 2021 00:17:13 GMT):
fresh hand coming

davidkhala (Wed, 21 Apr 2021 10:01:14 GMT):
@dave.enyeart Dear Dave,, per my email to Fabric mail list, would you consider give `https://github.com/hyperledger/fabric-chaincode-go` and `https://github.com/hyperledger/fabric-protos` some git tags like v2.2.x on Github?

greg2git (Sat, 24 Apr 2021 12:11:57 GMT):
wasn there some kind of version update on 4/23 that was supposed to be posted here?

greg2git (Sat, 24 Apr 2021 12:11:57 GMT):
wasn't there some kind of version update on 4/23 that was supposed to be posted here?

davidkhala (Fri, 30 Apr 2021 07:49:29 GMT):
@dave.enyeart Dear Dave, is there any chance we bump spf13/viper to a newer version in release-1.4

dave.enyeart (Thu, 06 May 2021 03:13:36 GMT):
See response at https://lists.hyperledger.org/g/fabric/message/9972

dave.enyeart (Thu, 06 May 2021 03:16:24 GMT):
Going forward we'll just announce on the mailing list, see https://lists.hyperledger.org/g/fabric/message/9895

ankitm123 (Thu, 06 May 2021 18:30:06 GMT):
Has joined the channel.

davidkhala (Tue, 18 May 2021 01:54:18 GMT):
Has left the channel.

jimthematrix (Mon, 07 Jun 2021 16:00:42 GMT):
Has left the channel.

davidkel (Thu, 15 Jul 2021 10:25:16 GMT):
Has left the channel.

Maginaro (Wed, 21 Jul 2021 10:04:34 GMT):
Has joined the channel.

asaningmaxchain123 (Thu, 25 Nov 2021 05:59:19 GMT):
Has joined the channel.

rjones (Wed, 23 Mar 2022 17:35:27 GMT):