Skip to content
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

How do we support backporting ? What should the procedure be for that ? #5

Closed
wsdookadr opened this issue Feb 22, 2013 · 0 comments
Closed

Comments

@wsdookadr
Copy link
Contributor

There are cases where we'll need to patch an older version, and we bump into backporting.

This is a situation where we would need this =>

So if we have the following chain of versions

  • 0.1
  • 0.2
  • 0.3

We're currently using 0.3 , but then we decide that we should fallback to 0.2 but we need to apply some changes to it, then 0.2.1 will emerge from this so now we have

  • 0.1
  • 0.2
  • 0.2.1
  • 0.3

Request for comments (from a git point-of-view and a debian/changelog point-of-view )

P.S. This came about when we did massive refactoring in udp-filters and webstatscollector and then we went back to a previous version.

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

1 participant