6
votes
Code quality on backports branch with limitted lifespan
If I had a dollar for every time I heard "It will be dropped in X months, don't bother".....
But in your case you are the person who decides how long to maintain the version and how much work to put ...
- 84.4k
6
votes
Accepted
User Stories and Epics
Before I say anything else, I want to say this - don't waste too much time trying to adhere to a best practice or a prescribed format. Instead, just do whatever lets you capture the requirements and ...
- 9,490
5
votes
Accepted
Where to determine different behaviour for a child class with feature flags
Where you check the feature flag depends on the scope of the feature.
Checking the feature flag in the Parent class is ideal for cases where you do not want the Child class behavior changed globally. ...
- 46.1k
5
votes
Why shouldn't I merge two feature branches in git-flow?
Merging two features
If you merge feature branch B into feature branch A, then A contains both the features of A and B. That's what merging is, after all.
This means that you no longer have two ...
- 59.5k
4
votes
Code quality on backports branch with limitted lifespan
I don't know Julia enough to know if the following can be applied to your situation in full, but to give you a general answer for comparable situations: IMHO it is a good idea to avoid maintaining two ...
- 220k
4
votes
What's the correct Git flow to develop on two independent features + one feature that relies on both?
If feature C depends on features A and B in the sense that both should be implemented, verified and correct for C to work correctly, then the canonical way is to delay development of C until the ...
4
votes
What log level use for deprecated features?
In my past experience, I usually use the lowest level enabled in production environment (INFO?). Then, prefix log msg with keyword tag, say DEPRECATED. In log monitor/alert tool (can't suggest any ...
- 675
3
votes
Working Through a User Story
Hm. I look at your three scenarios and I see a dependency that worries me: scenario 1 seems to assume that you've already delivered scenario 2. When this happens to me, I look for alternative ways to ...
3
votes
Working Through a User Story
It sounds like you are looking for BDD, and the Gherkin specification language. The gherkin language is a way to express business scenarios that can then be used to stub out code-level tests. Once you ...
- 3,303
2
votes
Feature toggle: How to toggle without spreading same toggle all over the code?
It's hard to give a concrete answer without the actual code but from experience I often found that I could make the database and the UI work transparently for both with and without the new feature.
...
- 1,258
2
votes
What's the correct Git flow to develop on two independent features + one feature that relies on both?
You seem to assume that developing a feature requires a feature branch. In this case, the canonical branching would look like:
------------------------
\ \--A--/ \ /
\--B--/ \ /
...
- 82.2k
1
vote
Where to determine different behaviour for a child class with feature flags
It is difficult to answer with such an abstract example, there are situations where both options are the most ideal. Ultimately, the question is which class "knowing" about the flag makes ...
- 121
1
vote
What log level use for deprecated features?
Neither.
Add a metric to your server which records the volume/rate of calls to all methods.
Or even better the client version connecting.
You can then report on usage as required.
Logging is ...
- 84.4k
1
vote
What log level use for deprecated features?
I'm using NLog as an example here as it's the logging framework I most often use. I expect similar frameworks to have similar features.
WARNING, because it’s necessary to eventually upgrade all ...
- 59.5k
1
vote
Accepted
Feature toggle: How to toggle without spreading same toggle all over the code?
To avoid changes in many places, there are some strategies:
The obvious one: Put as much of the feature specific code in one place.
The other obvious one: Choose behaviour by picking the right ...
- 49.4k
1
vote
should we consider a feature set as a microservice in FDD?
Microservices, like any other architecture, should help you and not burden you. Things that change together should stay together. So if one of the features change leads to modifications in others, ...
- 121
1
vote
How to track features in trunk based development?
Traceability is useful, but note that feature branches too cease to provide any traceability once they are merged: Git branches are just transient pointers rather than persistently recorded attributes ...
- 136k
1
vote
Automated test "all changes are feature-flagged", possible?
I think the only way to do this is to have extensive testing for all the existing features, including testing things like the content of menus to make sure no new unexpected items show up.
If the ...
- 3,924
1
vote
Automated test "all changes are feature-flagged", possible?
I think you totally miss the root cause of your problem. I guess your real porblem is this:
want features to only become active when someone who is not a developer (management?) decides that now is ...
- 4,638
Only top scored, non community-wiki answers of a minimum length are eligible