Replies: 1 comment 7 replies
-
|
More generally, I would like to see a more "little and often" approach to releases. I hope that @xperiandri 's huge efforts recently will lay the groundwork for this! |
Beta Was this translation helpful? Give feedback.
-
|
The only thing that is now in disbalance is that we have GitHub workflows and |
Beta Was this translation helpful? Give feedback.
-
|
The nice thing about Build.fsx is that you can run it locally. I use it when I make my changes to be sure that I didn't break anything. |
Beta Was this translation helpful? Give feedback.
-
|
But I have an issue, that FAKE does not work with .NET 7 SDK |
Beta Was this translation helpful? Give feedback.
-
|
Could FAKE be replaced by a simple bash script that calls Or even a The project build is not very complex. |
Beta Was this translation helpful? Give feedback.
-
|
I didn't take the time yet, but it looks like there are some workaround suggested here: fsprojects/FAKE#2719 |
Beta Was this translation helpful? Give feedback.
-
I'm thinking about how we can bring some update regularity into this project, so I want to share an idea with you and hear your thoughts.
I guess everybody involved would agree that it would be nice if there were a mechanism that would make sure that the "clock ticks" in this project and that in a way that is not overly dependant on the individual contributors.
To be more specific:
Basically, the idea is to define a state machine (which is not necessarily automated) in which every state transition is accompanied by a timeout default transition. Of course, as soon as we introduce something like this we'll probably also want to introduce a set of default or usual acceptance criteria for these states. For example, we might require a certain test coverage threshold for code changes.
Beta Was this translation helpful? Give feedback.
All reactions