Push and tag a commit including the version updates after a milestone build

Open
#2,633 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
20/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Domain
build-system, release

Research direction

Start by reviewing the milestone build and release workflow to identify where version updates are produced and where released bits are assembled. Determine how a commit containing the exact released content should be created and tagged. Done means the process reliably publishes that commit and tag for each milestone build.

Written by the indexing model from the issue text.

Description

releng

It'd be nice to have a commit that has the exact content of the released bits.

Dominant language
Java
Stars
831
Forks
330
Avg merge
3d 7h
Merged PRs (30d)
12

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from eclipse-xtext/xtext

All issues in eclipse-xtext/xtext

Similar issues

More Java issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.