Sebastien LELONG wrote:

> The validation wiki page is quite filled, even if most of us did not vote for 
> everything (this probably shows this method might not be the most effective, 
> more, this page also store test results that should be stored in the testing 
> matrix, but the jallib script was not ready. Anyway...). I've also seen 
> improvements on libs + more tests, so maybe that's time to beta-release, 
> before moving to something else.

I was about to ask for permission ;-) to update the device files one 
more time. MPLAB 8.15 came out and it has some improvements. I generated 
new device files and saw several changes. Most are however of minor 
importance. Some of the more important changes apply mostly to the newer 
(maybe even future) PICs which are probably not used yet. Since some 
errors which I 'fixed' in the .dev files are back in 8.15 I need some 
time to be sure everything is OK.
So I guess 'no more device files updates' when we release soon, and we 
keep some improvements in the pipeline!


> Except some -1 for blink samples which are outdated since Rob did the trick 
> (again), there are only positive votes. Some row has no vote at all. If 
> everybody have performed the tests they need (did you run tests again last 
> device files commit ?), here's what we can do:

>  1. wait until this WE, so everyone has time to read this mail...
>  2. copy the files listed in this page to "validated", except those which 
> don't have votes. I can do this, but if someone else wants to do it, no 
> problem, just tell us. (Eur, add your last committed samples if you feel 
> confortable with them !)
>  3. ... release ! (using "make release" on "validated" map)
> 
> Well... for 3., I see few things that need to be dealt with:
> 
>  * LICENSE file. Are we happy with current one or not ?
>  * are we all happy with README files ?
>  * are we all happy with how things are packaged ? (see example in this 
> group's files section)
>  * we need to write an "[ANN] jallib 0.1 beta released !" mail for jallist 
> (and for jallib here for our own ego), where we explain what's been done, 
> why, how to download the package, we need testers, contributors, people who 
> can give feedback, and also we thank all the respective authors of original 
> libs which have been included here, bla, bla, bla, blabla, bla... 

I think license and readme files are good enough.

> So... Do we release ?

Yes! Let's do it!

Regards, Rob.

-- 
Rob Hamerling, Vianen, NL (http://www.robh.nl/)

--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to