> It's only a blink file, and hey, the LED blinks. If we keep > discussing the right move moment, it will never happen.
Putting files in validated won't make the release process faster (on the contrary). The "right move moment" is about deciding what to put in the next release. When we know that, we'll know the moment will happen. I've already talked about defining a release content. Maybe that was too early. We can discuss it again. And we can create, in the issue too, a list of issue that must adressed before the release. A roadmap... > We need to release something as well: > > Relase Early, Release Often. "... and Release something functional !" Again: blink files only are not enough, need device files (in other words, dependencies, but keep reading) > and nobody said that either /validated or a relase is completely bug- > free. IMHO /validated means: it has worked for <name> at <date> and > he can be reached if you have problems. > > And yes, this means we have to release the device files too. Yes, we have to release them too, but, again: they're changing a lot, so it's too early for them right now, so... blink files, without them, shouldn't go to validated... IMHO: the /validated's goal is the following: we should be able, at anytime, to grab all files in validated to release. /validated must be a coherent place. > This is what the test page and the matrix are all about: we have > tested all this subsystems. We can't do more. Instead of filling /validated, we can create and prepare test page, and put information about what's been tested. Seb -- Sébastien LELONG http://www.sirloon.net http://sirbot.org --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "jallib" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/jallib?hl=en -~----------~----~----~----~------~----~------~--~---
