release 0.28 is overdue, issue management #371

Closed
simonmichael opened this Issue Jul 17, 2016 · 4 comments

Projects

None yet

2 participants

@simonmichael
Owner
simonmichael commented Jul 17, 2016 edited

It has been too long since a major release. 0.28 keeps getting pushed back. Contributing factors include:

  1. feature creep, unclear priorities, unclear release goals
  2. a tedious release notes process that I avoid
  3. joint release of the hledger-* packages means waiting for sufficient visible changes in all of them

1 has been enabled by my extensive private task list which has grown into a second (third, fourth ? see also notes.org, trello.hledger.org) issue tracker.

Corrective actions:

  • issue tracker gardening: issues, labels, milestones, urls, clarify & document usage for bugs/features/tasks
  • clean up private backlog, begin moving to issue tracker as appropriate
  • minimise work on things not in the issue tracker
  • mark issues and PRs for 0.28 milestone
  • review, prioritise, estimate, adjust, set dates, limit WIP
  • list remaining release tasks
  • review/merge/drop notes.org
  • clarify/streamline processes where possible
  • switch to package.yaml files
  •  simplify version string updates

milestones
currently scheduled for 0.28
currently not scheduled for 0.28

0.28 release plan:

  • focus issue tracking
  • issue/PR triage
  • close open 0.28 issues
  • merge PRs
  • rename to 1.0
  • release notes
  • release announcement
  • tag, release, announce

@simonmichael simonmichael added the A BUG label Jul 17, 2016
@simonmichael simonmichael added this to the 0.28 milestone Jul 17, 2016
@simonmichael simonmichael self-assigned this Jul 17, 2016
@simonmichael
Owner

How to help: close issues in the 0.28 milestone!

@simonmichael simonmichael changed the title from release 0.28 is overdue to release 0.28 is overdue, issues need more focus Jul 18, 2016
@simonmichael simonmichael changed the title from release 0.28 is overdue, issues need more focus to release 0.28 is overdue Jul 18, 2016
@simonmichael simonmichael changed the title from release 0.28 is overdue to release 0.28 is overdue, issue management Jul 27, 2016
@simonmichael simonmichael added a commit that referenced this issue Aug 9, 2016
@simonmichael lib, cli, web, api: use hpack (package.yaml) for all packages at last #…
…371

Generated package.yaml files from the old cabal files with hpack-convert,
removed some problematic blank lines manually,
regenerated the cabal files from the package.yaml files with hpack.
Tests pass, looks like all the info is still there.

This means that from now on, we don't edit cabal files directly.
We edit the less verbose package.yaml files. stack will update
the cabal files automatically (or non-stack users can use hpack).
The changes to both are committed, as we still want to provide
the cabal files to downloaders.
d165600
@crocket
crocket commented Sep 12, 2016

Is the latest master stable most of the time?

@simonmichael
Owner

Yes.

@simonmichael
Owner

Done, ignoring unimportant open issues and calling it 1.0.

@mstksg mstksg added a commit to mstksg/hledger that referenced this issue Feb 3, 2017
@simonmichael @mstksg + mstksg lib, cli, web, api: use hpack (package.yaml) for all packages at last #…
…371

Generated package.yaml files from the old cabal files with hpack-convert,
removed some problematic blank lines manually,
regenerated the cabal files from the package.yaml files with hpack.
Tests pass, looks like all the info is still there.

This means that from now on, we don't edit cabal files directly.
We edit the less verbose package.yaml files. stack will update
the cabal files automatically (or non-stack users can use hpack).
The changes to both are committed, as we still want to provide
the cabal files to downloaders.
76c0ce5
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment