2011/7/19 Olivier Grisel <[email protected]>: > 2011/7/19 Fabian Christ <[email protected]>: >> Hi, >> >> since the license issues are solved we can release just from the >> trunk. The release will contain everything that is in the default >> build. I think, this is the easiest way to do it now. > > Great. Would it be possible build a 0.9.0-RC1-incubating release > candidate set of artifacts that are not uploaded to the official maven > repo but just used for testing purpose (e.g. to check that all legal > files are included, and so on)?
I had a look at Apache Sling and their release process. When doing a release all released artifacts are uploaded into a staging repository for review and vote. In staging phase everyone can check the release on legal issues etc. > Also the stable launchers includes opennlp models that have no clear > license status (statistical models derived from copyrighted documents) > hence are not hostable / distributable on a the Apache maven repo. > Right now the models are downloaded from > http://opennlp.sourceforge.net/models-1.5/ and included in the > defaultdata bundle that is then uploaded to the maven repo of Nuxeo. > The OpenNLP project is working on building models out of pure open > data corpus (wikipedia / wikinews / dbpedia) but this is still work in > progress. > > I don't know what to do in the short term. Maybe the first release of > Stanbol could be done without the launcher bundle? Maybe we could > build a launcher that without the defaultdata bundle and tell in the > readme to download it manually from the nuxeo maven repo [1] so as to > but it in the right sling/ folder after the first start? > > https://maven.nuxeo.org/nexus/content/repositories/vendor-releases/org/apache/stanbol/org.apache.stanbol.defaultdata/ If I understand the Apache way right we are free in the way we want to do it as long as we respect the licenses. I would suggest to remove everything from the launchers that is not conform with Apache license and make it optional in the build. IMO there should be no difference between our standard build and doing a release. That would make things really easy for the release manager. -- Fabian
