mirror of
https://github.com/not-kennethreitz/convore.json.git
synced 2026-06-05 23:20:19 +00:00
Kenneth Reitz
1 line
2.9 KiB
JSON
1 line
2.9 KiB
JSON
[{"user_id": 1127, "stars": [], "topic_id": 34505, "date_created": 1305010712.5856659, "message": "http://github.com/django-debug-toolbar/django-debug-toolbar/issues", "group_id": 81, "id": 986073}, {"user_id": 1127, "stars": [], "topic_id": 34505, "date_created": 1305010679.6291289, "message": "If you have an open issue in django-debug-toolbar can you please confirm it's broken in the latest master?", "group_id": 81, "id": 986068}, {"user_id": 213, "stars": [], "topic_id": 34505, "date_created": 1305017841.1936281, "message": "why the hell isn't the develop branch used for development anymore?", "group_id": 81, "id": 987047}, {"user_id": 1127, "stars": [], "topic_id": 34505, "date_created": 1305044970.9503319, "message": "Why does it need to be? Theres pypi (and tags) for all releases. We wanted to move toasted more continuous development and that becomes easier when it follows an accepted standard", "group_id": 81, "id": 992455}, {"user_id": 1127, "stars": [{"date_created": 1305839131.10868, "user_id": 12817}], "topic_id": 34505, "date_created": 1305044994.262641, "message": "Toasted -> towards", "group_id": 81, "id": 992464}, {"user_id": 1736, "stars": [], "topic_id": 34505, "date_created": 1305046580.5501261, "message": "@jezdez Why would people install from git and assume stability?", "group_id": 81, "id": 992844}, {"user_id": 1127, "stars": [], "topic_id": 34505, "date_created": 1305047784.3897259, "message": "As well as in our qa env", "group_id": 81, "id": 993182}, {"user_id": 1127, "stars": [], "topic_id": 34505, "date_created": 1305047772.5644121, "message": "Well I would assume stability, but potential more problems than a release. Were using master In dev", "group_id": 81, "id": 993175}, {"user_id": 213, "stars": [], "topic_id": 34505, "date_created": 1305796722.3386791, "message": "@coderanger If there was a distinct decission to split development and release branches, then yes, I assume that I can rely on it. This change in policy broke that assumption without any notice which I frankly can't stand. It's not like Git forces you to use master. Good thing I know where to complain about any instability in released version now, @zeeg :)", "group_id": 81, "id": 1109801}, {"user_id": 1127, "stars": [], "topic_id": 34505, "date_created": 1305837054.237293, "message": "I may push it back to git-flow after we get a release out, but need to make sure everyone that actively commits also rebases their forks off of git-flow to do that", "group_id": 81, "id": 1115925}, {"user_id": 213, "stars": [], "topic_id": 34505, "date_created": 1305894163.51915, "message": "@zeeg you can even select the develop branch as the main branch in github, if you want to hide the master branch", "group_id": 81, "id": 1124896}, {"user_id": 213, "stars": [], "topic_id": 34505, "date_created": 1305894121.673629, "message": "why rebasing, \"development happens in the develop branch\". done.", "group_id": 81, "id": 1124894}] |