Skip to content

Stable Releases #297

Open
landonf opened this Issue Dec 30, 2012 · 2 comments

2 participants

@landonf
landonf commented Dec 30, 2012

Any chance of returning to stable versioned releases? It would make it a lot easier to track the project externally, and at the risk of being inappropriately forward, it might make it easier to focus development towards stable targets, rather than being in a persistent state of pull request churn.

@tomaz
Owner
tomaz commented Dec 31, 2012

You mean reintroducing development branch? Or better versioning system/tags?

For 3.0 I've introduced automated build and versioning handling by using git and build scripts, so this should provide more stable release targets. I'm also thinking on stricter contribution requirements. But other that that, I'm open for any ideas in this direction. I'd love if you can elaborate on this.

@landonf
landonf commented Jan 18, 2013

You mean reintroducing development branch? Or better versioning system/tags?

I think both would be great, especially if there were built versioned releases to download.

For 3.0 I've introduced automated build and versioning handling by using git and build scripts, so this should provide more stable release targets. I'm also thinking on stricter contribution requirements. But other that that, I'm open for any ideas in this direction. I'd love if you can elaborate on this.

The big thing for replacing doxygen in our own libraries (OSS and internal) is in having stable releases with changelogs of what's changed between releases, minimal regressions across releases, and stability over time so we can be reasonably assured that we can rebuild documentation for older projects with newer tools if we don't have the time or resources to do a sweep of a project to rework its documentation.

Requiring that pull requests also incorporate tests (unit tests or regression tests) could help a lot here.

These wishes of mine are all very heavy on open-source entitlement, apologies :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.