[Hyperledger Composer] Deprecation of Composer

Krupal_Agileinfoways <krupal.shah@...>


It is unfortunate that you have deprecated composer toolchain.
With the increasing number of frameworks, shall we also assume deprecation of some frameworks as well?
We can see most frameworks other than Fabric and Sawtooth are useless. Is there any explanation for such useless fragmentation?

Thanks & Regards,
Krupal Shah
Sr. Software Developer

Mailtrack Sender notified by
Mailtrack 08/29/19, 5:53:26 PM

On Wed, 28 Aug 2019 at 18:14, Simon Stone <sstone1@...> wrote:

It's been a whole year since the IBM team contributing to Composer moved to focus on Fabric. Dan Selman, the other maintainer, has been focusing on smart legal contracts under the Accord project.

In that time, very little activity has occurred in Composer, with the exception of us publishing several bug fix releases for users we know of who are still using Composer in production (these users are all in the process of migrating their solutions to Fabric). Also in this time, no other contributors have stepped forward to take over development of the Composer project.

We have been following the output of the Project Lifecycle Task Force, and we would like to propose to the TSC that the Composer project is moved into deprecated status. As mentioned above, we are continuing to support certain users, and we are also happy to continue to merge and publish fixes from other contributors if they arise.

We understand that after we move into deprecated status, there will be a period of 6 months before Composer is moved into EOL. We have no problems with this, but nearer the time we may want to discuss options around continuing to support certain users.

Please let me know if I misunderstood anything, or if you need us to do anything else on top of this note.

Many thanks,
Simon StoneUnless stated otherwise above:
IBM United Kingdom Limited - Registered in England and Wales with number 741598.
Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU