Skip to content

Make 13.6 release #145

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
3 tasks done
chrisdone opened this issue May 19, 2013 · 9 comments
Closed
3 tasks done

Make 13.6 release #145

chrisdone opened this issue May 19, 2013 · 9 comments
Assignees
Milestone

Comments

@chrisdone
Copy link
Member

Two things to do:

  • Establish which features and bugfixes will make it into 13.6.
  • Make release on June 1st.
  • Move any big changes/features over to 13.7.

All issues should be marked with:

  • P1: Must have it in for this release.
  • P2: Should have it in for this release, but no big deal if not.
  • P3: Optionally in this release, otherwise next one.

Release will be tagged 13.6, which will make a Github tarball, and will be announced to the haskellmode-emacs mailing list. Maintainers of distributions/package managers can follow this monthly release cycle.

@chrisdone
Copy link
Member Author

Release note: #150 removes the haskell-site-file.el, so distributions should provide the make'd .el/.elc file.

@chrisdone
Copy link
Member Author

All P1's done, release on target looks likely.

@hvr
Copy link
Member

hvr commented May 27, 2013

Yey! :-)

btw, as the version is now inferred via git describe and since we seem to be jumping from the previous 2.9.1 version to 13.6, maybe we could use a tagging scheme, which is easy to match with git describe's --match option (which supports only glob-patterns), a commonly used pattern would be --match v[0-9]*.

Alternatively, 'annotated tags' could be used to differentiate between versioning tags an non-versioning tags, which could then also carry release notes (which can then be collected/aggregated automatically into an autogenerated NEWS file)

There are a few ways how to use git to automate releases, we just need to agree on which scheme to follow...

@chrisdone
Copy link
Member Author

Let's bump the tag to v13.06?

@hvr
Copy link
Member

hvr commented Jun 1, 2013

Great, I just need to adapt the Makefile before the actual tagging is done (btw, when are you planning to tag v13.06?)

@chrisdone
Copy link
Member Author

As soon as you're ready! I've done the P1 issues for this milestone. Let me know when you're happy to go.

@hvr
Copy link
Member

hvr commented Jun 1, 2013

@chrisdone I'm happy to go... git tag v13.06 away... ;-)

@chrisdone
Copy link
Member Author

Hurrah!

@chrisdone
Copy link
Member Author

Will send out an announcement to haskellmode-emacs later.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants