Timeline for How to manage ongoing development of two variants of the same library?
Current License: CC BY-SA 4.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Nov 16, 2021 at 6:33 | history | edited | Doc Brown | CC BY-SA 4.0 |
deleted 14 characters in body
|
| Oct 28, 2021 at 13:01 | comment | added | einpoklum | So, it'll have to be the second option I guess. I can't follow the Python scheme. | |
| Oct 28, 2021 at 12:41 | comment | added | Doc Brown | @einpoklum: an "advertising version number" would not be used that way - Python 2 and 3 are different products, and a successor in the "Python 2 product line" has always the name "Python 2.x". If you cannot adapt this naming scheme to your lib, choose two different names, like "cuda-api-wrappers-standard" and "cuda-api-wrappers-modern", or "cuda-api-wrappers-radio" vs. "cuda-api-wrappers-TV", or whatever you prefer. | |
| Oct 28, 2021 at 12:35 | history | edited | Doc Brown | CC BY-SA 4.0 |
added 13 characters in body
|
| Oct 28, 2021 at 12:23 | comment | added | einpoklum | "Why" - because it's not like Python 2 and Python 3. Image you had a Pyton 4 release that built upon Python 2, then a Python 5 release that built on Python 3. | |
| Oct 28, 2021 at 12:15 | history | edited | Doc Brown | CC BY-SA 4.0 |
added 2005 characters in body
|
| Oct 27, 2021 at 13:40 | history | answered | Doc Brown | CC BY-SA 4.0 |