Replies: 3 comments 1 reply
-
|
So I was looking into: can you do pre-release on PyPI: and yes; you can. See: |
Beta Was this translation helpful? Give feedback.
-
|
One point that was brought up is: will the change log be hard to work with so many releases? If you have to go through github releases I think that will be true. However, if we implement an effective changelog, this should be well mitigated. |
Beta Was this translation helpful? Give feedback.
-
|
First impression is that continuous deployment to pre-release versions would be quite nice. For the changelog, could one do something like: Major Version N+1Minor Release m+1pre-release p+1
pre-release p
Major Release N. . . |
Beta Was this translation helpful? Give feedback.
-
|
So I was thinking of making a CD release to Alpha would be a huge part of this. In #380 I introduced a changelog. I was thinking of doing some sort of keyword system like you proposed there. Then in CD:
|
Beta Was this translation helpful? Give feedback.
-
After #336 is released, deploys should be a lot easier due to the entire process being almost entirely automated, including version numbering.
This makes me think: is there much value in doing deployment staging? I think now once a feature/fix is merged into Develop it could be immediately deployed. This then would mean deleting develop and merging everything into main, and making much more frequent deployments.
Pros
Cons
Alpha Testing
This would renew the need for alpha-testing.
Do we continue with this just being a git based branch that testers clone? Or do we do alpha deployments to GitHub or (inclusive) PyPI?
Thoughts @tjlaboss?
Beta Was this translation helpful? Give feedback.
All reactions