issue_comments: 485922055
This data as json
| html_url | issue_url | id | node_id | user | created_at | updated_at | author_association | body | reactions | performed_via_github_app | issue |
|---|---|---|---|---|---|---|---|---|---|---|---|
| https://github.com/pydata/xarray/issues/2888#issuecomment-485922055 | https://api.github.com/repos/pydata/xarray/issues/2888 | 485922055 | MDEyOklzc3VlQ29tbWVudDQ4NTkyMjA1NQ== | 240623 | 2019-04-23T18:31:02Z | 2019-04-23T18:31:02Z | NONE | WRT points: - right, it's not tracked and that's the motivation for this issue - just because it's not widely done is not a reason to ignore it and does not justify not doing it - IMO it is not widely done because many science projects are lapse in managing version dependencies using SEM-VER best practices, leaving it to the consumers, who are often clueless about these matters, to wonder why their project crashes with one or more dependencies that they don't understand nor care to dive into at any depth - many science projects avoid the whole problem by lagging with 0.x releases, failing to commit to stable, reliable APIs with at least 1.x releases - by adopting better SEM-VER practices, across the board, it should provide more confidence to arrive at 1.x releases. But this is not my battle to wage, I'm just the messenger for thousands of consumers who have no idea what versions are compatible or not. |
{
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
432058005 |