Skip to content

Prioritizing next batch of improvements, cleanups #64

Open

Description

@emiliom

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.

For Milestone 0.6.0:

Assessment and extension of class inheritance

  • It seems to have been implemented successfully for SamplingFeatures and Results. Are there any concerns or problems with extending it to other entities?

RDBMS packages as optional installs

Removing unused or tangential code

Python 3 readiness

Activity

  1. added this to the milestone on May 1, 2016
  2. lsetiawan commented on Jan 16, 2018

    @lsetiawan
    Member

    @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.

  3. emiliom commented on Jan 17, 2018

    @emiliom
    MemberAuthor

    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.

  4. removed this from the milestone on Jan 17, 2018
  5. changed the title [-]"Milestone 0.6.0" - Prioritizing next batch of improvements, cleanups[/-] [+]Prioritizing next batch of improvements, cleanups[/+] on Aug 30, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions