You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The "current" version of pinax-models (e.g. what you get when you use pip install pinax-models) appears to date back to a much earlier version of the code. As such, it would be useful to be able to reference, instead, an updated version of the code in a requirements.txt file.
However, there are currently no tags for the various versions, only the master branch. As a result, it is possible (indeed, I have had it happen for other github repos) that if the master branch of pinax-models were used as a requirement for a deployed server, the server could break the next time it was deployed if there were an error or problem in the source code.
Instead, we should have tagged versions of the code, so that we can indicate which version we want to use when pulling in the code from github.
Also, version numbers should be incremented when significant changes are made to the code. For example, the code for deleting related objects has changed substantially from code for 2.0 but the version number is still 2.0.
The text was updated successfully, but these errors were encountered:
The "current" version of pinax-models (e.g. what you get when you use
pip install pinax-models
) appears to date back to a much earlier version of the code. As such, it would be useful to be able to reference, instead, an updated version of the code in a requirements.txt file.However, there are currently no tags for the various versions, only the master branch. As a result, it is possible (indeed, I have had it happen for other github repos) that if the master branch of pinax-models were used as a requirement for a deployed server, the server could break the next time it was deployed if there were an error or problem in the source code.
Instead, we should have tagged versions of the code, so that we can indicate which version we want to use when pulling in the code from github.
Also, version numbers should be incremented when significant changes are made to the code. For example, the code for deleting related objects has changed substantially from code for 2.0 but the version number is still 2.0.
The text was updated successfully, but these errors were encountered: