-
-
Notifications
You must be signed in to change notification settings - Fork 302
Hackathon June 2012
fhuberts edited this page May 19, 2012
·
37 revisions
Discuss:
- build fidelity
- bndtools must be able to build itself (#327: bndtools can't build itself from a clean checkout) (the bnd build also fails)
- #107: cache used bundles under ~/.obr
- #164: bundle version do not align
- Release/Development policy (OIOW: 'next is the new master')
- development for the next version should happen on master
- new features should be developed on a feature branch and merged into master when the feature is complete and it has been decided that the feature will be in the next release
- releases should be tagged with an annotated tag (we probably need a script for this)
- do NOT release from a dirty workspace
- do NOT create changes with whitespace damage
- http://wiki.eclipse.org/EGit/Contributor_Guide#Granularity_of_Changes
- Just Another Package Manager (JPM)
- ant, and all other build tools
- maven integration
- external tool integration (Apache ACE for example)
- coupling of sources in Eclipse; right now we if you drill down into the sources you'll probably land in the OSGi provides j2ee files. This makes it hard to drill down into the actual implementation that is used.