> > > > > The VERSION file contains the full version with date, something like > > "bee-<compiler_version>-<date>". This version will be helpful in > > order to know what this is about when users report problems. > > Isn't the revision number more dominant, or is this easy to derive from > the bee package contents?
You're right, a revision number would be better. I'll change this (maybe not for sunday) > > > > These bee packages are also here to encourage integration to > > TORELEASE, including dependencies, as soon as possible. So once > > you're done on an isssue/task, update TORELEASE (and CHANGELOG) so > > it's included in next bee packages ! > > I'm not sure I understand this completely. Do you mean that the bee > packages are a also a test if TORELEASE is complete? This is a test to check if TORELEASE is consistent. For instance, last release showed there were missing files, dependencies, in TORELEASE. Bee will automatically detect this. Beside that, since we're going to release very often, I suggest to have the good habit to populate TORELEASE as soon as possible, so Bee can integrate it and make it available for daring user. Thinking again about this, maybe you'd like to have bee package for all devices ? (jallib-all_devices). Let me know. Seb --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
