Summary for the First Board Meeting

As announced earlier, our first monthly board meeting was held on October 12th at SKT-tower, Seoul. Committers and stakeholders of metatron were present. We shared ideas on our three main agendas:

• Open-source development process and policies
• Release history and future release plans
• Issues in-progress

Stay updated with this brief review for the meeting!

Development process and policies

1. Versioning Policy

We follow the semantic versioning format with the extension of {Hotfix} label. Given a version number {Major}.{Minor}.{Patch}.{Hotfix}, we update the:

1. {Major} version when we add remarkable concept changes, after some minor builds.
2. {Minor} version on three to four months basis as we make minor improvements,
3. {Patch} version on two weeks basis of iterative development,
4. {Hotfix} version when urgent issue is resolved.

2. Branch Policy

Master branch is kept stable and clean. For every two weeks’ iteration, a release branch is created. Further developments are made on this release branch, and a feature branch is created for each issues.

3. Development Process

Roles

• Requester: Registers internal/external bug reports, feature requests and other issues.
• Product managers: Review and select issues, plan and confirm releases.
• Designers
• Issue Owner: Follow up issues on a workflow basis.
• Developers
• Reviewer: The whole metatron team
• CI (Continuous Integration): Branch, repository management

Workflow

To review issues, board meeting will be held every month, open for any of those concerned. As for the team only, sprint meeting will be held every two weeks. After the development sprint and unit test, patch release and minor release test will be conducted every one or two weeks.

Upcoming month, we are planning for an integration test with a professional GA team.
Question regarding how to acquire information of the owner of the issue after registering on Github was brought up. At present, issue-owner concept is not clearly established. For now, issues are tagged and distributed to development/design managers in charge of specific parts.

Releases

1. Release History

4 iterations were implemented so far (3.0.1~3.0.4)
3.0.1
– Introduced Multi-Datasource in Dashboard
– Improved chart properties (y axis, max category in pie chart)

3.0.2
– Window function support on Data preparation stage
– Improved data connection user interface

3.0.3
– Stabilization Season 1 (DT portal opened)
– Numerous bug fixes

3.0.4
– Query progress and cancel feature on Workbench
– Stabilization Season 2 (T-Map opened)

*Our releases are updated on: https://github.com/metatron-app/metatron-discovery/releases

2. Future Release Plans

3.1 (by November 30th, 2018)
After 2 iterations covering following updates:
– Introduce Map View
– Improve user interface for Multi-Datasource and filter
– Show ingestion status of data source
– Support Metadata User View
– Improvement on Timestamps
– Continuous bug fixes

3.2 (by March 30th, 2019)
– Support Map Analysis
– Support Data preparation on Workspace
– Introduce Search-based analysis
– Implement Pluggable structure on open-source code – improve scalability

3. Further upcoming supports

– Language: English will be fully supported for Github issues starting from November
– Committer-friendly process and documents soon to be provided