[jbosstools-dev] Re: We have branched !

[Denis Golovin]

I'v made branch for jbosstools
https://svn.jboss.org/repos/jbosstools/branches/jbosstools-3.0.0.Beta1
and for releng and installer
https://svn.jboss.org/repos/devstudio/branches/devstudio-3.0.0.Beta1
we have two new build projects on hudson
for jbosstools 3.0.0.Beta1
http://hudson.qa.jboss.com/hudson/view/DevStudio/job/jbosstools-nightly-3.0.0.Beta1/
and JBDS 2.0.0.Beta1
http://hudson.qa.jboss.com/hudson/view/DevStudio/job/devstudio-nightly-2.0.0.Beta1/
there are two eclipse update sites for jbosstools:
1. Nightly build from trunk
http://download.jboss.org/jbosstools/updates/nightly/trunk
2. Nightly build from 2.0.0.Beta1 branch
http://download.jboss.org/jbosstools/updates/nightly/3.0.0.Beta1


Max Rydahl Andersen wrote:
> Hi,
>
> In case you don't follow svn-commits, Denis created the 
> jbosstools-3.0.0.Beta1 branch last night.
>
> What does this mean ?
>
> It means that if you do fixes that needs to go into Beta1 you need to 
> do it both in branches/jbosstools-3.0.0.Beta1
> and in /trunk.
>
> If you are doing stuff that should not go into Beta1 you only commit 
> in trunk.
>
> Also remember this when you resolve issues - make sure the fix version 
> is correct! either 3.0.0.Beta1 (in beta1 and trunk) or 3.0.0.cr1 (only 
> in trunk)
> I recommend you use svnmerge.py to keep track of which revisions you 
> have merged!
>
> If you committed after the branch (Rob ?), please verify if your fixes 
> needs to go into the branch too.
>
> This also means that Beta1 should now not receive any new features 
> unless it is something critical. Beta1 branch is intended to be stable 
> and ready for
> QA so we can have the planned release on 31st October.
>
> Thanks,