# Scheduling icepyx releases

**URL:** <https://discourse.pangeo.io/t/scheduling-icepyx-releases/780>\
**Category:** ICESat-2\
**Created:** [July 30, 2020, 5:54pm UTC](https://discourse.pangeo.io/t/scheduling-icepyx-releases/780 "2020-07-30T17:54:53Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![JessicaS11](https://yyz2.discourse-cdn.com/flex030/user_avatar/discourse.pangeo.io/jessicas11/32/229_2.png) [@JessicaS11](https://discourse.pangeo.io/u/JessicaS11)\
**Post date:** [July 30, 2020, 5:54pm UTC](https://discourse.pangeo.io/t/scheduling-icepyx-releases/780/1 "2020-07-30T17:54:53Z")

</div>

At our last meeting, we discussed using GitHub projects and milestones to organize and schedule icepyx releases. Some highlights from our conversation:

- we need to create and update a release log
- milestones, complete with deadlines, will be used to determine which features will be completed next and who is in charge of each one
- bug fixes will be added to the next scheduled release (milestone)
- currently, the listed projects correspond to releases/milestones, but larger features with multiple steps can ultimately have their own projects (though unfortunately we cannot assign an entire project or project notecard to a milestone unless it is also an issue)

Please check out the current [projects](https://github.com/icesat2py/icepyx/projects) and [milestones](https://github.com/icesat2py/icepyx/milestones). Feel free to assign yourself some issues. At our next meeting, we’ll assign leads for the outstanding issues in the [0.3.1 release project](https://github.com/icesat2py/icepyx/milestone/3) and discuss the deadline set for the associated milestone.