Repository navigation
Replies: 2 comments
Much appreciated 🙏 Let me start by pointing out (and clarifying my own stance) that v1 means very different things in different projects. For me semantic versioning is predominantly a signal around interface stability, i.e. forwards compatibility. Tagging something as v1 means that a separate branch would be maintained that has stable APIs, config, etc while receiving select feature additions, fixes, ... .
Ultimately, it's more a question of your comfort. We've probably all seen our fair share of buggy v1s, me tagging something as such isn't a silver bullet. Personally, I don't try to make anything available on the main branch and releases that hasn't received at least some amount of testing and QA. I can tell you that there are folks who claim to use TB in production (whatever that means in practice, it's not my job to be nosy). You could have a look at the release notes for
Sadly no. This is partly due to me prioritizing things that users request. In other words, I do have a list of things I'd like to add over time but I'm always grateful if someone tells me there's something more important. Right now I'm working on username-based and anonymous auth (besides email). Another critical thing that pops to mind: WASIp3 when it becomes available. Other bigger features that could hypothetically also go into later releases:
Not sure how useful this was but I hope this gives you a better sense of where my mind's at and my general approach. Happy to answer any questions |
|
sounds like a very reasonable approach and I like your thinking! |
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Hello,
first of all thanks for the great work on this project, this seems like the dream infrastructure that I would love to use for all upcoming projects!
Is there any plan on missing and broken features in other words what would be expected to tag the project 1.0?
I am thinking about basing a upcoming project on trailbase and trying to assess where the development stands, which features are stable and working and which features are still missing before you guys would be comfortable with a production project running on top of it?
Thanks for the insight!
Best,
Jan
All reactions