Comments (11)
Following semantic versioning your first release should be numbered 0.1 http://semver.org/#how-should-i-deal-with-revisions-in-the-0yz-initial-development-phase 0.1.1 would then be your first bug fix release and 1.0.0 would be for your first "major" release.
0.0.1 would be the first bug fix release for the 0.0 series, which means your first release should be 0.0.0 not 0.0.1 which is a little weird, hence the 0.1 not 0.0 ;)
from plasmapy.
But zero-based indexing.... :P
from plasmapy.
Sorry! Wrong button! 18th of January sounds good to me. And I think that list of features is a good starting point, perhaps with one or two more major-ish features added.
from plasmapy.
#181 tries to handle this a bit. I'll keep this open for discussion, though.
from plasmapy.
Space wombats...?
I'd say my approach at the simulation aspect can be 'working' in that timeframe, but not necessarily properly tested and verified. I think we should set a date for this as well, I think setting deadlines will help us push on with things and make sure we get regular releases out.
from plasmapy.
I mean release version 0.0.0 if you want :D
from plasmapy.
That is helpful, @Cadair! Following your suggestion, I will rename this issue so that we're discussing what to include in 0.1. Would December/January be a good time to tentatively plan for a 0.1 release?
from plasmapy.
December/January sounds reasonable to me, depending on how much ends up going in it.
from plasmapy.
I tentatively put January 18, 2018 as the v0.1 due date, though this is arbitrary so I am completely open to changing it (especially if there are meetings or other conflicts that core developers have). I'll probably regret it on January 17! 😿 We would probably want a feature freeze, beta release, and branch created a month before, and a release candidate a week before if we follow Astropy's stated practices.
Useful links:
- Astropy release schedule and version numbering - I'm happy to learn from Astropy and SunPy whenever possible!
- Emoji cheat sheet for GitHub and other sites
from plasmapy.
Seeing as we're about a month away from tentative v0.1 milestone, it might be a good time to review what progress has been made, what needs to be done, and prioritize open issues.
from plasmapy.
Seeing as we're about a month away from tentative v0.1 milestone, it might be a good time to review what progress has been made, what needs to be done, and prioritize open issues.
Welp.
from plasmapy.
Related Issues (20)
- Address functions in `distributions.py` with unexpected possible `return None`
- Add minimal example for `@validate_quantities` in coding guide
- Seeking help on Plasma-flow simulation
- Speed up documentation builds done via GitHub Actions in CI by caching previous build
- Use `sphinx_toolbox.rest_example` to de-duplicate reST example code blocks with copied output HOT 1
- Move most links & substitutions from `docs/common_links.rst` to individual files HOT 1
- Use `sphinxcontrib-globalsubs` to define reST substitutions instead of `rst_epilog`
- ExcessStatistics class throws an error for `time_step` with an astropy unit
- Use `pre-commit-search-and-replace` to replace LaTeX-style characters with Unicode characters?
- Unpin version of Sphinx after next release of sphinx-notfound-page HOT 1
- Set pytest flag to change warnings into test failures in CI HOT 1
- Add a class representing a force-free 1D current sheet equilibrium HOT 4
- Loader for MDSPlus Files
- Fix `DeprecationWarning` in grids functionality regarding deleting a single level of a `MultiIndex`
- Add "force-free" to glossary and apply it in documentation
- Update or consolidate lite function versions of plasma dispersion function and derivative
- Verify correctness of two methods in `MaxwellianCollisionFrequencies`
- Reorganize and clean up `docs/conf.py`
- Better describe what the number density represents in `beta` and `thermal_pressure` HOT 5
- Add pre-commit hooks to validate GitHub actions & workflows HOT 1
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from plasmapy.