Conversation
ghost
requested a review
from 
| Some of our repositories are used as libraries and included as a requirement in other repositories. | ||
| eg https://github.com/OpenDataServices/flatten-tool/releases | ||
|
|
||
| For these libraries, we want to version them to make it easier to do this. |
There was a problem hiding this comment.
I think that docs should state what we do, not what we want to do. So, we should say "For these libraries, we version them to make it easier to do this. This applies to all new libraries. As of July 2018, work to version existing libraries is still in progress".
There was a problem hiding this comment.
I'm not sure we have fully agreed about this - and I note your later comment talks about User needs, which might contradict this. Can we leave this pull request at it is (just saying "some", which is technically true) and have some Loomio discussion to clarify and make more specific points like this later?
|
|
||
| Work is merged to the "master" branch, and versions are tagged directly on the master branch. | ||
|
|
||
| This means that when a later version is released, no bug fixes to earlier versions will be released any more. |
| ------------------- | ||
|
|
||
| Some of our repositories are used as libraries and included as a requirement in other repositories. | ||
| eg https://github.com/OpenDataServices/flatten-tool/releases |
There was a problem hiding this comment.
Is the /releases page the correct one to link to here?
There was a problem hiding this comment.
Well, it's just an example link, and given the whole point of this page is released versions then releases seems like a good page to link to.
|
This seems sensible. We should do the work on this in response to identified user need - eg flatten-tool has been requested, I believe? |
Details to be fleshed out with more Loomio discussion.
2 participants
Details to be fleshed out with more Loomio discussion.