Re: [namedgraphs] Maven Coordinates?

[Tim P. <ti...@pa...>]

Hi Olaf, 


On Monday 15 February 2010 18:11:44 Olaf Hartig wrote:
> Hey all,
> 
> I'm back from vacation.
> 
> On Wednesday 10 February 2010 19:29:08 Tim Pizey wrote:
> > [...]
> > I have released 0.9.3 and we are now working on 0.9.4-SNAPSHOT
> > [...]
> > I have not updated the wiki nor the sourceforge downloads
> 
> Does it mean in Maven we have a 0.9.3 but "officially" (i.e. on the Web sites) 
> it is still the old 0.9.2?

yes
 
> If so, I better prepare the official 0.9.3 package - i.e. doing the things 
> listed in http://sf.net/apps/mediawiki/ng4j/index.php?title=Release_Process
>  - Right?
> Did you tag the release in CVS?

yes


Of the steps in the wiki:

Steps to Create the Source Package 
cvs co 
 Update and commit the file doc/index.html (adjust the sections News and Download). 

no

 If it is the first release of a new year update the copyright notices in the source files and commit these changes. 

No
(Surely not, the copyright is the year the source is written, no?)

ant clean 
rm lib/ng4j* 

No

Change the version property in build.xml. 

Yes

 Change the version in pom.xml. 

Yes

 Change the version number of the SWClLib in src/de/fuberlin/wiwiss/ng4j/semwebclient/CommandLineQuery.java. 

yes

 Reflect the new release in CHANGES. 

yes

ant
 
 Tag the CVS with the new version number (e.g. cvs -q tag v0_9_1). 

yes

 Change the version in build.xml and in pom.xml to reflect the post-release state. 
 Create a new ng4j-${version} directory somewhere. 
 Unzip the new ZIP file in this new directory. 
 Remove all IDE-specific config and project files from the new directory. 

I think that we should store the IDE specific configs that we use: 
there are not many IDEs. 



 Zip the new directory. 
 Steps to Publish the Source Package 
 Create a new release on SourceForge 
 Kindly ask Chris to upload the updated doc/index.html. 
 Announce the new release. 
 Open a beer ;-) 


I used the maven release tool: 
mvn release:prepare 
mvn release:perform

This does the editting of the pom and the tagging and committing. 

I put both the ant and maven builds into http://hudson.paneris.net/ 


I think that the only thing to do is update doc/index.html, 
run ant and upload artifacts to sourceforge. 


cheers
tim





-- 
We are in dialogue.