Skip to content

Plan to v2 and introduce Breaking Change  #174

@shirou

Description

@shirou

After replacing lsof (#164) , I have a plan to use semantic versioning and use gopkg.in. Current will be tagged the v1 at that time, and start v2 branch.

I will appreciate if you write some comments about this idea.

list of (possible) breaking changes

  • change JSON key from snake_case to camlCase.
  • [ ] change types from int32/64 and so on, to just int and uint.
  • golint acceptable
    • net.NetConnections -> net.Connections, disk.DiskPartitions -> disk.Partitions and so on
  • process.State() returns 'R' not 'running' in Linux (see Breaking change: use state code rather than "description" #173)

... (add whenever we found something)

When v2 is introduced?

Target is end of March, 2016. But it may postponed.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions