Howdy bugcommunity! Despite the hellish weather across the northeast and all the delays it causes, we're shipping!
Also! We're shipping new SW! Orders filled from today on (January 31st 2011) on will include (at least) R2.0.1, our maintenance release following our initial 2.0 release. Here's the info: The build artifacts can be found at: http://dauber/buildbot/repo/full/12909 (internal) and http://bugcommunity.com/downloads/files/2.0/Releases/R2.0.1/ Redmine roadmap associated with this release: http://redmine.buglabs.net/versions/show/53
Issues addressed (or scheduled to be addressed for this release):
- Defect #1551: minimal dev/testing image (minimal-image?)
- Defect #1595: com.buglabs.bug.osgi does not implement ManagedService
- Defect #1598: bugdash2: View logs should point to /var/log/felix.log
- Defect #1599: bugdash2: View logs > Messages log - output differs from messages on BUG
- Defect #1605: ServiceTrackerHelper fails to track services in some situations
- Defect #1606: Felix has two log services registered by default
- Defect #1607: felix log level property invalid
- Defect #1608: ServiceTrackerHelper fails to restart ManagedRunnables after a dependent service bounces.
- Defect #1660: Old swarm portal demo code in rootfs
- Defect #1671: ManagedRunnable/ServiceTrackerHelper API does not support getting access to service properties.
- Defect #1692: Video OSGi services are not unregistered when video module is removed.
- Defect #1693: ConfigAdmin code expects Configuration.getProperties() to never return null.
- Defect #1698: ship dhclient by default
- Feature #1326: Camera 2.0 integration. API/Userland tools.
- Feature #1425: battery status LED indicator
- Feature #1597: Remove PhoneME-isms from base code
- Feature #1656: Ship bug2v4l2 in R2.0.1
- Feature #1670: Bundle swarm connector and portal in release?
- Support #1589: revamp http://www.buglabs.net/downloads for R2.0.1/SDK2.1 release
- Support #1657: create buildslave for R2.0.1 branch
Redmine activity associated with this project (contains defects associated with R2.0.0, R2.0.1, etc): http://redmine.buglabs.net/projects/activity/bug-prod-sw Still no webui at svn://bugcamp.net, so for the log, do: svn log svn://bugcamp.net/bug/trunk -r 12909:12659 Known Issues for this project (These may be found in Redmine): http://redmine.buglabs.net/projects/bug-prod-sw/issues This release is tagged in SVN at: svn://bugcamp.net/bug/tags/releases/R2.0.1 Some important notes on this release:
- This release includes fully baked support for the Camera module. Lane Brooks and David Findlay did an excellent job with this and I think it's our best module to date. Docs in the new wiki.
- Pre-alpha support for BUGswarm client code.
- Fixes some under-the-hood defects that were present in RC2.0.5/R2.0(.0).
- BUGdash got a makeover
- There's now a ramdisk image if you're keen on testing or developing with a very-small-footprint.
- LED magic for battery. Behavior: red when dangerously low, green until not dangerously low. More in sysfs at /sys/class/power_supply.
- You may notice that there's been
some version-soup lately. The following versioning mechanism has been
adopted and will continue to be adhered to from this point forward.
- X.Y.Z.B, where:
- X=major, indicating support for a new architecture (think 1.3A=>2.0, where we moved from i.mx31 [armv6] to omap3 [armv7a]).
- Y=minor, indicating API breakage, a kernel change, support for new modules (think maybe 2.6.31-omap=>2.6.35-linaro, or swapping concierge for felix).
- Z=revision, indicating a maintenance release, addressing defects and adding new features that do not break APIs.
- B=build #, and does not apply to releases to the general public. RC's have this information available, a la RC220.127.116.11.
- We're engineers, so these things are zero-indexed. ;D
- X.Y.Z.B, where:
- We're pleased to announce the addition of some new devs here at the BUG development team, Far McKon, Andrew Turley, Camilo Aguilar, Cameron Cundiff, welcome!
- Our release process has been slightly broken lately, no emails notifying about release candidates, QA cycles, etc. We're embarking on a new development process here and these things will not be overlooked! Stay tuned!