Typically if you do a release: You make sure everything on trunk is as you want to release it. version number etc. commit that. Let tc build the artifacts. create a branch. update version of trunk to a new snapshot version (or your release will get overwritten every time you make a new commit). commit new version.
Note maven has a release plugin that probably does something like the above but i have no experience with it. As for the /releases svn path, i don't think there is anything special to it. but i could be wrong :). Anyway i have never used it myself. If you plan to continue development on a branch (bugfixes or something like that) we can set up a new build for that branch on tc. Maurice On Wed, Jun 4, 2008 at 9:32 PM, Edvin Syse <[EMAIL PROTECTED]> wrote: > Hi, > > I'd like to create a release for wicketstuff-jquery, as it is still > 0.1-SNAPSHOT, and I've gotten feedback from people saying they won't rely on > it until there is a release available. > > Can someone point me to some info on how I can create a release? Is there > some convention that branches created on /releases will be automatically > kept or something? > > I created an account on teamcity (username edvinsyse) and it recognizes me > as a committer, btw. > > Also, can I get access in wicketstuff.org/jira so I can close some > outstanding WSJQUERY tickets there? > > I'm sorry for my ignorance :)) > > -- Edvin >
