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

Testing #105

Merged
merged 4 commits into from Apr 27, 2018
Merged

Testing #105

merged 4 commits into from Apr 27, 2018

Conversation

maniackcrudelis
Copy link
Contributor

@maniackcrudelis maniackcrudelis commented Apr 17, 2018

Problem

  • Instal doesn't work on stretch

Solution

PR Status

Work finished. Package_check, basic tests and upgrade from last version OK.
Could be reviewed and tested.

Validation


Minor decision

  • Upgrade previous version :
  • Code review : JimboJoe from Fix stretch #96
  • Approval (LGTM) : JimboJoe from Fix stretch #96
  • Approval (LGTM) : frju365 from Fix stretch #96
  • CI succeeded : Build Status
    When the PR is mark as ready to merge, you have to wait for 3 days before really merge it.

@frju365
Copy link
Member

frju365 commented Apr 20, 2018

perhaps let's merge it quickly ?

@maniackcrudelis
Copy link
Contributor Author

Are we in such a hurry ?

@frju365
Copy link
Member

frju365 commented Apr 20, 2018

no, but we 4 reviews and it's a little fix ;)

@maniackcrudelis
Copy link
Contributor Author

4 reviews for a PR currently in "pending"...
Not that I don't want to take notice of your reviews, but our procedure is to let to a testing release 7 days (at least) to be tested by the community, then if no other commits are added and if no regressions have been mentioned, we can start to review it.

Of course, if no commits are added until these 7 days, I will consider these reviews. But what if we have to rewrite this PR because of a regression or new commits ?
There's no security issue here, so let's not fall in a useless hastiness. I know that our procedure can be sometimes frustrating, but it's also a guaranty of quality for our apps.

So, for my part, I rather prefer to wait since there's no fix except for stretch (which I already try with success). So let's be sure this stretch fix will not break jessie.

@frju365
Copy link
Member

frju365 commented Apr 20, 2018

yes, yes, of course. I didn't mean to merge it today. (I didn't need a so long explanation ;-) )

@maniackcrudelis
Copy link
Contributor Author

Will be merged in 3 days

@maniackcrudelis maniackcrudelis merged commit 1e35eb7 into master Apr 27, 2018
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

Successfully merging this pull request may close these issues.

None yet

5 participants