Hackathon June 2012
fhuberts edited this page Aug 1, 2012
·
37 revisions
Discuss:
This week:
- [DONE] MO/FH templates should include timestamp in version
- [DONE] FH bnd findbugs
- [DONE] PK define source code formatting
- [DONE] error free init / build: bndtools must be able to build itself (#327: bndtools can't build itself from a clean checkout) (the bnd build also fails) (Marian will look into this, maybe add tests with paths with spaces)
- [DONE] FH URL <--> URI
- localOBR builds should work
- PK Demo: Just Another Package Manager (JPM)
- PK/MO ant, maven, and all other build tools. MO will talk to Stuart wrt Maven
- PB external tool integration: plugin API/system? (Apache ACE for example). We need an API that allows plugins handling these things.
- MO discuss and design a release procedure when using BndTools to develop open source software
- OSGi rest services
- web framework
- PK source bundle -> project
- MO easy installation of Felix DM annotations (or any other -plugin)
- PKS Demo: tool to determine which projects need to be released (compare file change dates with released jar date or something similar?!)
- PB compare repositories: which bundles are in one repository but not in another (to determine what you need to push for example)
- PB add support for rebuilding a bundle on resource file changes (html files for example). fixed, need to test
- add delete operation on repositories
Generic
- FH 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
Later
- [DONE] #107: cache used bundles under ~/.obr
- FH #164: bundle version do not align
- FH coupling of sources in Eclipse; right now when 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. We should at least have javadoc.
- FH determine a release/deprecation plan
- MO marketing
- PK single project distribution/sharing
- PK version control model for cnf
- PK make ???
- PB bindex tool parameters are broken (order matters!?!)
- Ma R5 resolver
- add a repository deploy option