You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Prioritizing next batch of improvements, cleanups #64
Let's see if using Milestones can help us organize our distributed contributions. These are my suggestions, not a definitive, consensus Milestone features. Some of these may already be implemented, but either the corresponding issue isn't closed or I didn't check thoroughly.
It seems to have been implemented successfully for SamplingFeatures and Results. Are there any concerns or problems with extending it to other entities?
It's a mixed bag. I'll assess this later in the month, after we issue the next odm2api release (it's not like anyone paid any attention to this milestone wish list from 19 months ago!). In the meantime, I'll delete the milestone I had created for it way back then.
changed the title [-]"Milestone 0.6.0" - Prioritizing next batch of improvements, cleanups[/-][+]Prioritizing next batch of improvements, cleanups[/+]on Aug 30, 2018
Activity
lsetiawan commentedon Jan 16, 2018
@emiliom Do you know if most of these issues/pr's have been addressed? Seems like some of them are not. This is the only thing in milestone 0.6.0.
emiliom commentedon Jan 17, 2018
It's a mixed bag. I'll assess this later in the month, after we issue the next odm2api release (it's not like anyone paid any attention to this milestone wish list from 19 months ago!). In the meantime, I'll delete the milestone I had created for it way back then.
[-]"Milestone 0.6.0" - Prioritizing next batch of improvements, cleanups[/-][+]Prioritizing next batch of improvements, cleanups[/+]