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
Now that the site breakage is fixed (as per #7 ) the site content needs updating. I'll create new issues for things I note here.
Key things that need changing
New pre-release required
Switch to semantic versioning rather than ubuntu style chronological. Last release was 1.0.12.0 I'll rebrand that as 1.12.0, since that seems to make a lot of sense. However, next actual release will be "2.12.1":
We always bump the patch number
The new release will not worry about backwards compatibility per se nor seek breakage, but 1.0.12.0 (and hence 1.12.0) was targeted at python 2 with some limited python 3 support. This release will drop python 2 support, and so fundamentally be a breaking update - hence the major version number change.
References to sourceforge
References to SVN
References to CVS
Examples that are on the website need to be runnable
Examples that are in the repository that need work needs capturing
When this is done, the website content can be viewed as up to date.
The follow on work is to fix issues in the codebase.
A more critical short term issue is [ #14 ] - to enable SSL on the website, which is higher priority than content updates.
The markdown for the website will be able to be pulled into a public repo. When that markdown is in the public repo and updated, that will mark the completion of this issue. The tooling and markdown files will be updated to make this quicker/easier.
The text was updated successfully, but these errors were encountered:
Revamped infrastructure is now in directory Website of this repo. NB, this is incomplete - primarily because this is just the generated and generatable content. The non-generated/generatable content needs thinking about.
Now that the site breakage is fixed (as per #7 ) the site content needs updating. I'll create new issues for things I note here.
Key things that need changing
When this is done, the website content can be viewed as up to date.
The follow on work is to fix issues in the codebase.
A more critical short term issue is [ #14 ] - to enable SSL on the website, which is higher priority than content updates.
The markdown for the website will be able to be pulled into a public repo. When that markdown is in the public repo and updated, that will mark the completion of this issue. The tooling and markdown files will be updated to make this quicker/easier.
The text was updated successfully, but these errors were encountered: