Comments (3)
I think #210 is worthy too :-)
from boots.
@jacobweinstock I think we should create trackable issues for each of these items (although some items may fit into the same issue). This roadmap issue contains items that could extend for sometime. The bulleted items are missing context that would be provided in a dedicated issue. Those issues can be linked to in the bulleted list above. I think we could then create a meaningful epic of this issue, targeting a specific goal achievable by completing some set of the bulleted items (roadmap is not a specific goal). As you point out, instead of using a tracking issue, we could make a project geared towards specific goals if we have a clear goal and a path to achieve it.
I don't have the option of creating a project, but I can create a milestone and I think this could work well enough for now.
Since we are currently at v0.6.0, we could create v0.7.0, v0.8.0, and v1.0.0 milestones. These issues could be placed in the slot that seems most likely to match efforts. If something is 'broken' it should land in v0.7.0. If it requires more thinking or coordination, it can land in a later milestone. We can move items around as releases happen and we fit features in or need to push them back.
from boots.
When linking items in this list, let's link to issues rather than pull requests. Pull requests have a tendency to be too broad or incomplete towards resolving any one issue, PRs can also be revertible and misguided.
Let's let issues represent the ask and pull requests represent some effort that may or may not fulfill some asks. In the issues that we create we need to do a better job of defining what it means to be done. For example, I replaced the last item in the bulleted list with #210
, but looking back at this issue I have no idea how to suggest a user take advantage of this feature. We didn't track a need for documentation to be provided before the issue could be closed.
from boots.
Related Issues (20)
- Doc: dead link in iPXE Doc on main branch HOT 1
- Stop building 32b images
- Provide a configurable minimum lease expiry for DHCPOFFERs
- Release 0.7 HOT 1
- Add documentation around updated components in Boots HOT 1
- Deprecate and remove Cacher backend
- Remove Cacher backend HOT 1
- Support customization of HTTP port HOT 1
- Consume Tink v1alpha2 APIs
- Customscript error handling does not seem correct HOT 7
- [pls ignore] pxe boot HOT 1
- kernel arg `ip=dhcp` can cause very long boot time in Hook HOT 1
- Binding DHCP server to a specific interface instead of 0.0.0.0 HOT 2
- Add flag to set TFTP block size. HOT 1
- smee/dhcprelay is broadcasting DHCPOFFER instead of unicasting in an L3 environment
- The file backend does not update the runtime config on file change HOT 2
- documenation | static ip addresses | example required HOT 1
- Does smee support binding to IPv6 address ? HOT 4
- Default command-line option values depend on other command-line options (ref `detectPublicIPv4`) HOT 2
- Smee panic in proxy mode HOT 6
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from boots.