Skip to content

create dev area post 0.1.5 release #99

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.

Sign up for GitHub

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

Jump to bottom
Merged
merged 10 commits into from
Dec 27, 2016
Merged

create dev area post 0.1.5 release #99

merged 10 commits into from
Dec 27, 2016

Conversation

bewest
Copy link
Member

@bewest bewest commented May 31, 2016

Release planning happens here. 😺

bewest and others added 10 commits May 30, 2016 20:27
@bewest
create dev area post 0.1.5 release
d4f1aa5
@bewest
bless many uses with --gaps and other features
6fee307 
Support following switches:
    --count
    --microseconds
    --seconds
    --minutes
    --hours
@bewest
provide a calibrations use formatted for Nightscout
9f7c636 
Should help @Spazholio and others upload calibrations to
Nightscout so that raw can be shown.

CC @jasoncalabrese.
@bewest
allow empty time/since specs.
ade7cc0 
This allows providing only the count, skipping the since specs.
This fixes an issue where it was very easy to get an empty array because there
are no records since "now."
@bewest
ensure positionals appear after switches
06c5d02 
In general, optional switches should come before required positionals.
This helps encourage moving switches towards the beginning of the line.
In addition, this helps tweak issue #102
#102 (comment), by
fixing an issue in the handling of the INI file for the oref0_glucose
report.
@davidofwatkins
Fix 'no_raw' being overridden to False when running oref0_glucose rep…
a98bb14 
…ort (fixes G5)
@jasoncalabrese
add hostname to the device field: openaps://host/device
933183e
@jasoncalabrese
Merge pull request #104 from davidofwatkins/fix_glucose_no_raw_g5
a006184 
Fix oref0_glucose report on G5
@jasoncalabrese
Merge pull request #107 from openaps/wip/glucose-hostname
43401bc 
add hostname to the device field: openaps://host/device
@oskarpearson @scottleibrand
Add new radio_locale parameter for Medtronic pumps (#112)
ceac808
@scottleibrand scottleibrand merged commit 953347a into master Dec 27, 2016
@scottleibrand
Copy link
Contributor

@bewest it appears I may not have the required PyPi maintainer permissions to be able to release a new version? Can you check that?

@bewest
Copy link
Member Author

bewest commented Dec 30, 2016

Howdy @scottleibrand please, set up a practice/demo project/repo and go through a few release exercises.

@oskarpearson
Copy link
Contributor

Hey @bewest - Scott's asked me to help out with the pypi side of things.

I was wondering if you could confirm the general (overall) release process, so that I am sure I'm doing things correctly. I've been releasing mmeowlink with pypi for a bit, and am pretty happy with things (though I don't use pypi at $WORK)

Once you've had some time to confirm the below, I'll go through a test process with my pypi account.

From what I can see:

  • A commit like this is made in the dev branch and pushed to github: d4f1aa5 (increment version number, add -dev to it). Title "create dev area post 0.1.5 release" for example
  • A new PR with the text 'Release planning happens here' is created from master -> dev immediately. At the start, it only has the above commit.
  • Over time, more PRs are created by developers against the 'dev' branch.
  • When enough work has been done to warrant a release, the "create dev area post 0.1.5 release" PR is merged into master.

Then some manual steps happen (I'm guessing at this process), on your dev box:

  • A commit like this is done to master, which changes the version in setup.py, removing the '-dev' 0478313
  • A git tag is created (eg: v0.1.5)
  • A release is pushed to the production pypi
  • The new commit and tag are 'git push'ed to master

Once all the above is done, we're at the same point as when we started, and the process repeats.

If you're happy with things, if you could grant me permissions on pypi and testpypi? My username is oskarpearson on both of them.

I'll do some testing with a test name value in setup.py first, then with the real package name but uploading to testpypi.

If everything then goes to plan, I'll push to pypi.

Thanks for your help.

@oskarpearson oskarpearson mentioned this pull request Jan 1, 2017
Open
@bewest
Copy link
Member Author

bewest commented Jan 6, 2017

Howdy, I created a simple python package here to practice with: openaps/stdprojectexample#1

@bewest
Copy link
Member Author

bewest commented Jan 8, 2017

Thanks for doing that @oskarpearson, looks good. I've add you on pypi for a bunch of projects including this one. 😸

@bewest
Copy link
Member Author

bewest commented Jan 8, 2017

Err, except openaps, this one is the only one for not not included for you in pypi, once you get some practice with stdprojectexample or others on pypi, I'll add openaps core as well.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
5 participants
@bewest @scottleibrand @oskarpearson @jasoncalabrese @davidofwatkins