I'd thought we could make a list of which features we want in that release, and which bugs still would need to be squashed (and other things). Other can go into the next versions (@joostverdoorn you know best what the minimum is we now need for inventid, so I suggest we start with that)
@joostverdoorn @steffansluis Since you can edit my posts (if I'm not mistaken) let's keep a record here of what we want to finish. Also ensure we label issues with the correct milestone. Also ensure that an issue exists for stuff you are creating, since it enables us to keep track of stuff and leaves room for discussion.
In case there are reasons why we cannot make a release (yet) or this month, I'm open for suggestions how we could and should proceed (and what you would recommend obviously!).
The list is created using the following markdown syntax- [ ] [Increase coverage to at least 80%](#20)
Since we really need a stable version soon (also for inventid I'd like one at least) I created a milestone (https://github.com/inventid/tails/milestones/Release%200.1.0)
I'd thought we could make a list of which features we want in that release, and which bugs still would need to be squashed (and other things). Other can go into the next versions (@joostverdoorn you know best what the minimum is we now need for inventid, so I suggest we start with that)
Features
Bugs
Other
@joostverdoorn @steffansluis Since you can edit my posts (if I'm not mistaken) let's keep a record here of what we want to finish. Also ensure we label issues with the correct milestone. Also ensure that an issue exists for stuff you are creating, since it enables us to keep track of stuff and leaves room for discussion.
In case there are reasons why we cannot make a release (yet) or this month, I'm open for suggestions how we could and should proceed (and what you would recommend obviously!).
The list is created using the following markdown syntax
- [ ] [Increase coverage to at least 80%](#20)