Timeline for How to manage common library dependencies to prevent cross-application breakage?
Current License: CC BY-SA 4.0
23 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jul 7 at 10:22 | answer | added | gnasher729 | timeline score: 0 | |
| Jul 7 at 8:20 | answer | added | Simon B | timeline score: 0 | |
| S Jul 6 at 16:38 | history | suggested | Rohit Gupta | CC BY-SA 4.0 |
Made a list of the problem items
|
| May 10 at 15:36 | review | Suggested edits | |||
| S Jul 6 at 16:38 | |||||
| May 9 at 21:29 | answer | added | Greg Burghardt | timeline score: 0 | |
| Apr 16 at 11:36 | answer | added | Joop Eggen | timeline score: 1 | |
| Apr 16 at 9:37 | answer | added | Caleth | timeline score: 1 | |
| Apr 16 at 7:42 | answer | added | Steve | timeline score: 4 | |
| Apr 15 at 22:45 | history | reopened |
Hans-Martin Mosner Basilevs Doc Brown |
||
| Apr 15 at 10:49 | comment | added | amon | Is this a cultural problem or a technical problem? Do developers don't care that they're breaking stuff, or are they simply unaware? What kind of breakage tends to occur? API changes that can be detected as type errors, or more subtle changes in behaviour? My point here is that there's a huge arsenal of QA techniques beyond mere unit tests. Code reviews, type checks, and (possibly manual) end to end smoke tests are also super helpful. Splitting up multiple repos won't help until you have regression tests + a stronger compatibility culture. | |
| Apr 15 at 10:10 | comment | added | Basilevs | The original was fine too! | |
| Apr 15 at 7:01 | comment | added | Hans-Martin Mosner | VTR - I think the question as rewritten is focused enough and answerable now. | |
| Apr 14 at 18:54 | history | edited | titanicsnake | CC BY-SA 4.0 |
added 3 characters in body
|
| S Apr 14 at 18:54 | review | Reopen votes | |||
| Apr 15 at 22:49 | |||||
| S Apr 14 at 18:54 | history | edited | titanicsnake | CC BY-SA 4.0 |
deleted 3023 characters in body; edited tags; edited title
Added to review
|
| Apr 14 at 17:44 | comment | added | titanicsnake | Thank you for the comments. I will try to heavily change the question so that it's focused on the main problem. @DocBrown The proposed solution was not there to make any advertisement or polititics but to share an IDEA of solution I thought about. | |
| Apr 13 at 21:37 | comment | added | Greg Burghardt | We have a limit of one question per post. Questions do best when you identify a tightly-focused problem to solve. There is nothing wrong with detail — we like detail — we just need the post to be more focused. | |
| Apr 13 at 21:34 | history | closed |
gnat Arseni Mourzenko Greg Burghardt |
Needs more focus | |
| Apr 13 at 18:21 | comment | added | Arseni Mourzenko | There are quite a lot of issues with your question. The issues include, but are not limited to, the fact that (1) it is too large, (2) it asks for tools recommendations, which is off-topic, (3) it invites for a discussion, like it a forum, rather than answers, and (4) it includes irrelevant subjects, such as multiple vs. single git repository. In order to have a better grasp at how StackExchange sites work, make sure you skim through a few other questions, to see what's welcome and what's not, what gets upvoted, and what receives downvotes. | |
| Apr 13 at 17:40 | history | edited | titanicsnake | CC BY-SA 4.0 |
added 240 characters in body
|
| Apr 13 at 17:04 | review | Close votes | |||
| S Apr 13 at 21:40 | |||||
| S Apr 13 at 16:40 | review | First questions | |||
| S Apr 13 at 21:40 | |||||
| S Apr 13 at 16:40 | history | asked | titanicsnake | CC BY-SA 4.0 |