29/11/13 12:31, intrigeri wrote:
> Hi,
>
> (I'm acting with my RM hat for the next two Tails releases on.)
>
> It's now clear feature/spoof-mac won't make it into 0.22. No big deal,
> as long as it's merged soon enough and we can publish some beta
> version of it by the end of the year. I'd like to have some visibility
> on what's left to do for this to happen.
>
> I've updated the existing tickets to match the current state.
>
> anonym, I think now would be a great time to sum up what the current
> state is:
>
> * remaining coding blockers
I don't think there are any now. I recently fixed the following (IMHO)
code blockers:
* Reverted the "Running in a VM warning" (and, as a consequence, the
special treatment of our test suite) in Tails Greeter commits ce391d4
and 960267f. I simply cannot reproduce it, and am starting to get
convinced it must have been a temporary bug in VirtualBox.
* Tails Greeter commits d9e257e and d4324c2 for logging failures of the
network unblocking script.
I also merged Tails Greeter's master into the feature branch.
> * remaining design documentation blockers (the blueprint didn't
> make it into a design doc yet, right?)
Done. Most of the blueprint was moved into our old
`wiki/src/contribute/design/MAC_address.mdwn`, replacing its old
contents. To me it reads like a decent design document and description
of the current implementation, although it possibly could use another
(external) read by now.
> * remaining user documentation blockers (are there placeholders doc
> pages with indications for doc writers already?)
There now is. The old user doc page was completely re-written in commit
ed50222.
> * once all coding blockers are solved, I think a bolder call for
> testing (pointing to a nightly built ISO from experimental) would
> be good: some of us told that they are lost in this huge thread,
> and it's unclear to them how close we are to the "please widely
> test this code" state
I think we're here now. As we discussed privately, it's probably better
to build the test ISO from the feature branch and keep it up-to-date
with devel, which it currently is. Could any one with the know-how set
up a nightly build of feature/spoof-mac?
I'll start preparing a public call for testing post.
> I'd love to see tickets created for all the blockers, so that one can
> easily track the progress of this feature.
After scanning through this thread once more I created the following
non-blockers:
https://labs.riseup.net/code/issues/6525
https://labs.riseup.net/code/issues/6526
The only blocker is, from how I understand our previous discussions, the
following task you created:
https://labs.riseup.net/code/issues/6454
I've assigned myself to it (with a due date!). Hopefully it'll lead to a
quick solution for its parent (#6453) so we can even have it in the
first non-test release (0.23 I suppose) as well.
Cheers!
