Hi, So it looks like only 1 issue remains for 0.0.1? https://issues.apache.org/jira/browse/DROIDS/fixforversion/12313486
Good work Bertil & Co.! Otis ----- Original Message ---- > From: Chapuis Bertil <[email protected]> > To: [email protected] > Sent: Thu, March 10, 2011 4:41:21 PM > Subject: Re: Droids 0.1 release > > Hello, > > What's the current status for the release? Should we start working on 0.0.2 > without this step? The problem I see is that by applying the small patches > on 0.0.1 we break all the bigger patches provided for 0.0.2. The one I tried > to apply are already applied partially. So the more we wait to apply them > the more work we will have. > > Thanks for your answer, > > Bertil > > On 1 March 2011 18:31, Chapuis Bertil <[email protected]> wrote: > > > > > > > On 1 March 2011 15:14, Thorsten Scherler <[email protected]> wrote: > > > >> On Tue, 2011-03-01 at 09:55 +0100, Chapuis Bertil wrote: > >> > I had a look at the different way available to automatically generate > >> the > >> > team list and changes files. It seems it will be difficult to use them > >> with > >> > our current documentation workflow. In consequence I hard coded the > >> > team-list.xml and the changes.xml files in the documentation folder. > >> > > >> > For the project team, I took all the committers and all the contributors > >> who > >> > provided patches. > >> > >> The problem with this as I see it is that this puts a too high value on > >> code contributions and too less on community contributions. For example > >> Otis who mainly contributed to the mailing list is not listed on the > >> team but personally I value his contribution equally as a patch. > >> > >> To draw a line I think we should only list official committers as the > >> TEAM. > >> > >> WDYT? > >> > > > > That's ok for me. I did it without really knowing what the practices are in > > this area. > > > > > >> > >> > For the changes, I used the report generated by jira for 0.0.1 and > >> formated > >> > it in xdoc. > >> > Please check if modifications or additions are required. > >> > >> That is fine, I see the initial changes more as pin pointing the main > >> feature of droids but yours is good. > >> > >> > > >> > I think the aim for 0.0.1 is to release as soon as possible. It seems > >> > several people are motivated to work on 0.0.2. > >> > >> Yeah, I just tried the deploy again (had to fix an issue with the > >> version of the buildnumber-maven-plugin) but as well get a 401. Will > >> review my config again. > >> > > > > I just read one of the article [1] pointed by someone in the general > > mailing list. The idea is to create a long lived stable branch and to keep > > the trunk really dynamic. It may be a really good practice for us, what do > > you think? > > > > [1] - > > http://lsimons.wordpress.com/2010/02/19/using-long-lived-stable-branches/ > > > > > >> > >> salu2 > >> > >> > >> > On 25 February 2011 19:12, Eugen Paraschiv <[email protected]> > >> wrote: > >> > > >> > > Hi, > >> > > About the changes.xml file - is there anything to add here, seeing how > >> > > there > >> > > is no previous release? > >> > > Should the release use the apache-release maven profile > >> (-Papache-release)? > >> > > Is there anything I can help with? > >> > > Eugen. > >> > > > >> > > On Fri, Feb 25, 2011 at 12:29 PM, Thorsten Scherler < > >> [email protected] > >> > > >wrote: > >> > > > >> > > > Ok, will try that this afternoon, need to attend some meetings now. > >> > > > > >> > > > salu2 > >> > > > > >> > > > On Fri, 2011-02-25 at 11:05 +0100, Chapuis Bertil wrote: > >> > > > > simply mvn deploy. > >> > > > > > >> > > > > On 25 February 2011 10:55, Thorsten Scherler <[email protected]> > >> > > wrote: > >> > > > > > >> > > > > > What is the command you tried? > >> > > > > > > >> > > > > > Will try it then. > >> > > > > > > >> > > > > > salu2 > >> > > > > > > >> > > > > > On Fri, 2011-02-25 at 10:47 +0100, Chapuis Bertil wrote: > >> > > > > > > I tried to publish the project on the snapshot repository [1]. > >> I > >> > > get > >> > > > the > >> > > > > > > following error: > >> > > > > > > > >> > > > > > > Error deploying artifact: Authorization failed: Access denied > >> to: > >> > > > > > > > >> > > > > > > >> > > > > >> > > > >> >https://repository.apache.org/content/repositories/snapshots/org/apache/droids/droids/0.1-incubating-SNAPSHOT/droids-0.1-incubating-20110225.093122-54.pom > > >> > > > > > > > >> > > > > > > My settings.xml contains the correct servers [2]. I tried with > >> > > > plain-text > >> > > > > > > and encrypted passwords. The strange thing is that I am able > >> to > >> > > login > >> > > > the > >> > > > > > > nexus server through the web interface. The thread [3] is > >> > > describing > >> > > > a > >> > > > > > > similar problem. I probably simply don't have the right to > >> deploy. > >> > > > Could > >> > > > > > > someone with sufficient rights do the release? > >> > > > > > > > >> > > > > > > Thanks in advance. > >> > > > > > > > >> > > > > > > [1] - > >> > > > > > > > >> > > > > > > >> > > > > >> > > > >> http://www.apache.org/dev/publishing-maven-artifacts.html#publish-snapshot > >> > > > > > > [2] - > >> http://maven.apache.org/developers/committer-settings.html > >> > > > > > > [3] - > >> > > > > > > > >> > > > > > > >> > > > > >> > > > >> http://maven.40175.n5.nabble.com/Plugin-deployment-problems-td2842738.html > >> > > > > > > > >> > > > > > > > >> > > > > > > On 25 February 2011 09:13, Chapuis Bertil < > >> [email protected]> > >> > > > wrote: > >> > > > > > > > >> > > > > > > > About the documentation file what's the convention? Do we > >> have to > >> > > > put > >> > > > > > the > >> > > > > > > > apache license in their headers? > >> > > > > > > > > >> > > > > > > > On 24 February 2011 18:27, Richard Frovarp < > >> [email protected]> > >> > > > > > wrote: > >> > > > > > > > > >> > > > > > > >> On 02/24/2011 05:47 AM, Chapuis Bertil wrote: > >> > > > > > > >> > >> > > > > > > >> Make sure that all your files contain a ASF licence header > >> > > (look > >> > > > at > >> > > > > > > >>> the RAT report when in doubt, generated with mvn site) > >> > > > > > > >>> => mvn rat:check leads to a build failure with "too many > >> > > > unlicensed > >> > > > > > > >>> files: > >> > > > > > > >>> 199", looks quite strange. I'd love if someone had a look > >> at > >> > > > this, in > >> > > > > > my > >> > > > > > > >>> opinion most classes and resources contains the ASF > >> license > >> > > > header. > >> > > > > > > >>> > >> > > > > > > >>> > >> > > > > > > >> There was this, where the number of correct was reported > >> back > >> > > > instead > >> > > > > > of > >> > > > > > > >> the number wrong: > >> > > > > > > >> > >> > > > > > > >> https://issues.apache.org/jira/browse/RAT-35 > >> > > > > > > >> > >> > > > > > > >> I don't know if it was fixed in 0.7 or not. > >> > > > > > > >> > >> > > > > > > >> At the bottom you will see the problem files. Shouldn't > >> docs > >> > > come > >> > > > out > >> > > > > > of > >> > > > > > > >> this area of svn? > >> > > > > > > >> > >> > > > > > > >> The most troublesome of the files are these two: > >> > > > > > > >> > >> > > > > > > >> droids-examples/src/main/java/org/apache/droids/App.java > >> > > > > > > >> > >> droids-examples/src/test/java/org/apache/droids/AppTest.java > >> > > > > > > >> > >> > > > > > > >> They've got GPL headers on them, but on the positive side > >> they > >> > > > don't > >> > > > > > do > >> > > > > > > >> anything. They have been removed in r1074224. > >> > > > > > > >> > >> > > > > > > >> docs/mail-lists.dispatcher.css > >> > > > > > > >> docs/linkmap.html > >> > > > > > > >> docs/changes.dispatcher.css > >> > > > > > > >> docs/default.html > >> > > > > > > >> docs/contrib.html > >> > > > > > > >> docs/index.dispatcher.css > >> > > > > > > >> docs/mail-lists.html > >> > > > > > > >> docs/default.dispatcher.css > >> > > > > > > >> docs/contrib.dispatcher.css > >> > > > > > > >> docs/themes/droids.css > >> > > > > > > >> docs/api/droids-norobots/package-list > >> > > > > > > >> docs/api/droids-wicket/package-list > >> > > > > > > >> docs/api/droids-tika/package-list > >> > > > > > > >> docs/api/droids-solr/package-list > >> > > > > > > >> docs/api/droids-core/package-list > >> > > > > > > >> docs/api/droids-spring/package-list > >> > > > > > > >> docs/develope.html > >> > > > > > > >> docs/changes.rss > >> > > > > > > >> docs/develope.dispatcher.css > >> > > > > > > >> docs/changes.html > >> > > > > > > >> docs/todo.html > >> > > > > > > >> docs/todo.dispatcher.css > >> > > > > > > >> docs/index.html > >> > > > > > > >> docs/linkmap.dispatcher.css > >> > > > > > > >> docs/develop/develop.dispatcher.css > >> > > > > > > >> docs/develop/hello-crawler.html > >> > > > > > > >> docs/develop/develop.html > >> > > > > > > >> docs/develop/hello-crawler.dispatcher.css > >> > > > > > > >> docs/install.html > >> > > > > > > >> docs/install.dispatcher.css > >> > > > > > > >> droids-examples/pom.xml > >> > > > > > > >> droids-examples/src/main/java/org/apache/droids/App.java > >> > > > > > > >> droids-examples/src/site/apt/index.apt > >> > > > > > > >> droids-examples/src/site/site.xml > >> > > > > > > >> droids-examples/src/site/fml/faq.fml > >> > > > > > > >> > >> droids-examples/src/test/java/org/apache/droids/AppTest.java > >> > > > > > > >> testing.properties > >> > > > > > > >> doap.rdf > >> > > > > > > >> tools/ant/bin/README-forrest-upgrade.txt > >> > > > > > > >> src/templates/component/DROIDS-README.txt > >> > > > > > > >> src/documentation/content/xdocs/images/droidsOverview.svg > >> > > > > > > >> src/documentation/resources/themes/common/css/droids.css > >> > > > > > > >> droids-crawler-web/droids-crawler-web.iml > >> > > > > > > >> > >> > > > > > > > > >> > > > > > > > > >> > > > > > > > > >> > > > > > > > -- > >> > > > > > > > Bertil Chapuis > >> > > > > > > > Agimem Sàrl > >> > > > > > > > http://www.agimem.com > >> > > > > > > > > >> > > > > > > > > >> > > > > > > > >> > > > > > > > >> > > > > > > >> > > > > > -- > >> > > > > > Thorsten Scherler <thorsten.at.apache.org> > >> > > > > > codeBusters S.L. - web based systems > >> > > > > > <consulting, training and solutions> > >> > > > > > http://www.codebusters.es/ > >> > > > > > > >> > > > > > > >> > > > > > >> > > > > > >> > > > > >> > > > -- > >> > > > Thorsten Scherler <thorsten.at.apache.org> > >> > > > codeBusters S.L. - web based systems > >> > > > <consulting, training and solutions> > >> > > > http://www.codebusters.es/ > >> > > > > >> > > > > >> > > > >> > > >> > > >> > > >> > >> -- > >> Thorsten Scherler <thorsten.at.apache.org> > >> codeBusters S.L. - web based systems > >> <consulting, training and solutions> > >> http://www.codebusters.es/ > >> > >> > > > > > > -- > > Bertil Chapuis > > Agimem Sàrl > > http://www.agimem.com > > > > > > > -- > Bertil Chapuis > Agimem Sàrl > http://www.agimem.com >
