Inside dubbogo v1.5.1: Project Management, Roadmap, and Community Insights

Project Overview

dubbogo has entered its fifth year. After two years of building the Hessian2 protocol library, network library, and core framework, the project became fully compatible with Dubbo v2.7.x and released Dubbo‑go v1.5.1.

Milestones & Roadmap

The project defines milestones that start with implementing a specific Dubbo feature and evolve with emerging technologies. Each release follows a "develop current version → plan next version → adjust based on feedback" cycle.

Full compatibility with Dubbo.

A Go‑based communication framework that leverages Go’s strengths for cloud‑native environments.

dubbo‑go‑proxy Initiative

The community is incubating a new HTTP gateway built on dubbogo, aiming to create a production‑grade proxy/sidecar that extends dubbogo’s traffic‑control capabilities.

Deliver a usable gateway.

Validate dubbogo’s abilities and guide its future evolution.

Improve stability and performance.

Team & Community

After project initiation, the community recruited members through issue and PR contributions, attracting developers from companies such as Ctrip, Tuya, Douyu, Huya, Ant Financial, and Alibaba. Collaboration with other open‑source communities (MOSN, Sentinel, Apollo, Nacos) expanded functionality and cross‑project expertise.

Management Practices

Project management includes defining direction, milestones, version plans, and short‑term development tasks. Early roadmaps may be vague, becoming clearer as the project progresses.

Requirement Collection

Initial goals focused on matching a Dubbo version. After the v1.0 release in August 2019, requirements grew to include production needs and technology previews, such as a K8s‑based registry and later an operator.

Implement specific Dubbo version features.

Address production‑grade user demands.

Explore cutting‑edge technology trends.

Project Management

Tasks are broken down, assigned to feature owners, and tracked via GitHub Projects. Each version has a release owner responsible for task splitting, progress tracking, code review, and final testing. Teams are kept small (≤7 members) to limit communication overhead.

Code Quality

Despite contributors working part‑time, the project enforces strict quality standards. Automated tools such as auto‑comment, hound, travis, goreportcard, and internal code style guidelines are used. Every pull request requires at least three senior reviewers.

Future Outlook

Each release is accompanied by a "What’s New" summary that highlights features, recent progress, and upcoming plans. Identified shortcomings include documentation quality, API usability, configuration complexity, performance optimizations, observability metrics, protocol extensions, and richer sample cases.

The community hopes to address these issues collectively and invites interested developers to join the discussion.