Cluster Feature Collecting
by Rob Stryker
Hi All:
I'd like to hear any and all clustering use cases relevant to tooling
that any of you have run into. Whether it be creating multiple servers /
runtimes / profiles, actions you'd like supported on a cluster type node
in the view, anything you can imagine. Spit it out. Speak up. Or
forever hold your peace ;)
15 years, 6 months
Re: ACTION REQUIRED: Has your component's feature version incremented in 3.0.1 branch? (was Re: Code freeze of 3.0.1 branch)
by Denny Xu
WS and ESB components were changed and need to update its feature
version numbers, but I not sure what version number I should update
them to,
just update to 3.0.1, right? is there a version number increment rule?
Denny
Nick Boldt wrote:
> I need to know which components have incremented their overall feature
> version. Here's what we had for {2,3}.0.0.GA:
>
> # component versions, JBT
> richfaces=3.0.0.GA
> archives=3.0.0.GA
> as=2.0.0.GA
> freemarker=1.0.2.GA
> jbpm=3.1.7.GA
> hibernate-tools=GA
> seam=3.0.0.GA
> struts=3.0.0.GA
> esb=1.1.0.GA
> tests=3.0.0.GA
> ws=1.0.0.GA
> birt=1.0.0.GA
> portlet=1.0.0.GA
> tptp=1.0.0.GA
> smooks=1.0.0.GA
> drools-ide=5.0.0.CR1
> examples=1.0.0.GA
> jbpm-convert=1.0.0.GA
> jmx=1.0.0.GA
> xulrunner=1.0.0.GA
>
> # component versions, JBDS
> equinox-transforms=1.0.0.GA
> runtime=1.0.0.GA
>
> If your component is now on x.y.1, let me know. I can dredge thru SVN
> for this information, but it's hella faster if you can just tell me. :)
>
> Thx,
>
> Nick
>
> Nick Boldt wrote:
>> 3.0.1.GA / 2.0.1.GA have been tagged in SVN, and the first builds
>> will start soon:
>>
>> http://hudson.qa.jboss.com/hudson/job/jbosstools-release-3.0.x/
>> http://hudson.qa.jboss.com/hudson/job/devstudio-release-2.0.x/
>>
>> Meanwhile, QA keeners can start on these N builds:
>>
>> http://hudson.qa.jboss.com/hudson/job/jbosstools-nightly-3.0.x/ (#52)
>> http://download.jboss.org/jbosstools/builds/nightly/3.0.1.Alpha1/20090428...
>>
>> http://download.jboss.org/jbosstools/updates/nightly/3.0.x/
>>
>> http://hudson.qa.jboss.com/hudson/job/devstudio-nightly-2.0.x/ (#64)
>> http://reports.qa.atl.jboss.com/binaries/RHDS/nightly/2.0.1.Alpha1/200904...
>>
>> http://reports.qa.atl.jboss.com/binaries/RHDS/updates/nightly/2.0.x/
>>
>> Nick
>>
>> Max Rydahl Andersen wrote:
>>> Hi,
>>>
>>> As discussed last week the 3.0.1 branch now has a code freeze and
>>> you should not be committing to this branch without approval from
>>> either me or Denis.
>>>
>>> Nick will follow up to this email with links to the builds QA and
>>> those have fixed issues should be using when testing the release.
>>>
>>> Thanks,
>>> /max
>>>
>>
>
15 years, 7 months
Re: ACTION REQUIRED: Has your component's feature version incremented in 3.0.1 branch? (was Re: Code freeze of 3.0.1 branch)
by Max Rydahl Andersen
Hibernate needs updating too afaik, but for some weird reason we are
versioned as GA in this file (which is correct) but should get updated a
number in its other file.
as and archives also received fixes afaik.
Same with ws.
Actually, I think svn diff between 3.0.0.GA and 3.0.1.GA will be the
safest/fastest way of checking this....otherwise i'm sure we will miss some.
/max
Nick Boldt wrote:
> I need to know which components have incremented their overall feature
> version. Here's what we had for {2,3}.0.0.GA:
>
> # component versions, JBT
> richfaces=3.0.0.GA
> archives=3.0.0.GA
> as=2.0.0.GA
> freemarker=1.0.2.GA
> jbpm=3.1.7.GA
> hibernate-tools=GA
> seam=3.0.0.GA
> struts=3.0.0.GA
> esb=1.1.0.GA
> tests=3.0.0.GA
> ws=1.0.0.GA
> birt=1.0.0.GA
> portlet=1.0.0.GA
> tptp=1.0.0.GA
> smooks=1.0.0.GA
> drools-ide=5.0.0.CR1
> examples=1.0.0.GA
> jbpm-convert=1.0.0.GA
> jmx=1.0.0.GA
> xulrunner=1.0.0.GA
>
> # component versions, JBDS
> equinox-transforms=1.0.0.GA
> runtime=1.0.0.GA
>
> If your component is now on x.y.1, let me know. I can dredge thru SVN
> for this information, but it's hella faster if you can just tell me. :)
>
> Thx,
>
> Nick
>
> Nick Boldt wrote:
>> 3.0.1.GA / 2.0.1.GA have been tagged in SVN, and the first builds
>> will start soon:
>>
>> http://hudson.qa.jboss.com/hudson/job/jbosstools-release-3.0.x/
>> http://hudson.qa.jboss.com/hudson/job/devstudio-release-2.0.x/
>>
>> Meanwhile, QA keeners can start on these N builds:
>>
>> http://hudson.qa.jboss.com/hudson/job/jbosstools-nightly-3.0.x/ (#52)
>> http://download.jboss.org/jbosstools/builds/nightly/3.0.1.Alpha1/20090428...
>>
>> http://download.jboss.org/jbosstools/updates/nightly/3.0.x/
>>
>> http://hudson.qa.jboss.com/hudson/job/devstudio-nightly-2.0.x/ (#64)
>> http://reports.qa.atl.jboss.com/binaries/RHDS/nightly/2.0.1.Alpha1/200904...
>>
>> http://reports.qa.atl.jboss.com/binaries/RHDS/updates/nightly/2.0.x/
>>
>> Nick
>>
>> Max Rydahl Andersen wrote:
>>> Hi,
>>>
>>> As discussed last week the 3.0.1 branch now has a code freeze and
>>> you should not be committing to this branch without approval from
>>> either me or Denis.
>>>
>>> Nick will follow up to this email with links to the builds QA and
>>> those have fixed issues should be using when testing the release.
>>>
>>> Thanks,
>>> /max
15 years, 8 months
Re[2]: Code freeze of 3.0.1 branch
by Anton Klimkovich
Hello Nick,
Wednesday, April 29, 2009, 6:39:55 PM, you wrote:
Nick> 3.0.1.GA / 2.0.1.GA have been tagged in SVN, and the first builds will
Nick> start soon:
Nick> http://hudson.qa.jboss.com/hudson/job/jbosstools-release-3.0.x/
Nick> http://hudson.qa.jboss.com/hudson/job/devstudio-release-2.0.x/
Nick> Meanwhile, QA keeners can start on these N builds:
Nick> http://hudson.qa.jboss.com/hudson/job/jbosstools-nightly-3.0.x/ (#52)
Nick> http://download.jboss.org/jbosstools/builds/nightly/3.0.1.Alpha1/20090428...
We already use this build for issues verification. Smoke tests and
functional tests will be executed on release build.
Nick> http://download.jboss.org/jbosstools/updates/nightly/3.0.x/
Nick> http://hudson.qa.jboss.com/hudson/job/devstudio-nightly-2.0.x/ (#64)
Nick> http://reports.qa.atl.jboss.com/binaries/RHDS/nightly/2.0.1.Alpha1/200904...
Nick> http://reports.qa.atl.jboss.com/binaries/RHDS/updates/nightly/2.0.x/
Nick> Nick
Nick> Max Rydahl Andersen wrote:
>> Hi,
>>
>> As discussed last week the 3.0.1 branch now has a code freeze and you
>> should not be committing to this branch without approval from either me
>> or Denis.
>>
>> Nick will follow up to this email with links to the builds QA and those
>> have fixed issues should be using when testing the release.
>>
>> Thanks,
>> /max
>>
--
Best regards,
Anton Klimkovich mailto:aklimkovich@exadel.com
15 years, 8 months
Re: ACTION REQUIRED: Has your component's feature version incremented in 3.0.1 branch? (was Re: Code freeze of 3.0.1 branch)
by Alexey Kazakov
Following components were changed in 3.0.1 and should be incremented:
seam=3.0.1
richfaces=3.0.1
Nick Boldt wrote:
> I need to know which components have incremented their overall feature
> version. Here's what we had for {2,3}.0.0.GA:
>
> # component versions, JBT
> richfaces=3.0.0.GA
> archives=3.0.0.GA
> as=2.0.0.GA
> freemarker=1.0.2.GA
> jbpm=3.1.7.GA
> hibernate-tools=GA
> seam=3.0.0.GA
> struts=3.0.0.GA
> esb=1.1.0.GA
> tests=3.0.0.GA
> ws=1.0.0.GA
> birt=1.0.0.GA
> portlet=1.0.0.GA
> tptp=1.0.0.GA
> smooks=1.0.0.GA
> drools-ide=5.0.0.CR1
> examples=1.0.0.GA
> jbpm-convert=1.0.0.GA
> jmx=1.0.0.GA
> xulrunner=1.0.0.GA
>
> # component versions, JBDS
> equinox-transforms=1.0.0.GA
> runtime=1.0.0.GA
>
> If your component is now on x.y.1, let me know. I can dredge thru SVN
> for this information, but it's hella faster if you can just tell me. :)
>
> Thx,
>
> Nick
>
> Nick Boldt wrote:
>> 3.0.1.GA / 2.0.1.GA have been tagged in SVN, and the first builds
>> will start soon:
>>
>> http://hudson.qa.jboss.com/hudson/job/jbosstools-release-3.0.x/
>> http://hudson.qa.jboss.com/hudson/job/devstudio-release-2.0.x/
>>
>> Meanwhile, QA keeners can start on these N builds:
>>
>> http://hudson.qa.jboss.com/hudson/job/jbosstools-nightly-3.0.x/ (#52)
>> http://download.jboss.org/jbosstools/builds/nightly/3.0.1.Alpha1/20090428...
>>
>> http://download.jboss.org/jbosstools/updates/nightly/3.0.x/
>>
>> http://hudson.qa.jboss.com/hudson/job/devstudio-nightly-2.0.x/ (#64)
>> http://reports.qa.atl.jboss.com/binaries/RHDS/nightly/2.0.1.Alpha1/200904...
>>
>> http://reports.qa.atl.jboss.com/binaries/RHDS/updates/nightly/2.0.x/
>>
>> Nick
>>
>> Max Rydahl Andersen wrote:
>>> Hi,
>>>
>>> As discussed last week the 3.0.1 branch now has a code freeze and
>>> you should not be committing to this branch without approval from
>>> either me or Denis.
>>>
>>> Nick will follow up to this email with links to the builds QA and
>>> those have fixed issues should be using when testing the release.
>>>
>>> Thanks,
>>> /max
>>>
>>
>
15 years, 8 months
Code freeze of 3.0.1 branch
by Max Rydahl Andersen
Hi,
As discussed last week the 3.0.1 branch now has a code freeze and you
should not be committing to this branch without approval from either me
or Denis.
Nick will follow up to this email with links to the builds QA and those
have fixed issues should be using when testing the release.
Thanks,
/max
15 years, 8 months
Friendly reminder about jira
by Max Rydahl Andersen
Hi,
While working on various issues I noticed that there is a growing
tendency to forget setting the fix version on resolved jira's.
By not having a fix version on resolved jira's our changelog's we use
for announcements are not correct nor is it easy
to see when an issue is fixed since you have to manually go in to SVN
and retrace what release the specific commits
went into.
Thus please remember to set the fix version when resolving something as
Done!
And to anyone doing QA please don't close resolved issues that does not
have a fix version - reopen them.
As a reminder here is the wiki that describes the workflow for JBoss
Tools jira http://www.jboss.org/community/docs/DOC-12834
/max
15 years, 8 months
Release plans
by Max Rydahl Andersen
Hi,
3.0.1
====
It is time to get 3.0.1 ready for QA and get it released.
Currently we got 8 issues open, please check if you are a assigned or
can help out:
https://jira.jboss.org/jira/secure/IssueNavigator.jspa?reset=true&mode=hi...
The codefreeze is set to be next week wednesday April 29th where after
we will do a build which QA will take for a spin.
I expect that to be done in about a week times, making it possible to
have the 3.0.1 release out by May 7th.
Please let me know if there is something preventing this.
3.1.0.M1 (the release formerly known as 3.1.0.Alpha1)
=======
As soon as we get it built against a stable Eclipse 3.5 I think we
should get this out to gather some feedback from early adopters.
Note: M6 was not good enough for XULRunner to work so we will have to
wait for M7 which is coming next week.
We want to make the early adopters able to see how good-bad the
intermediate builds are and we want to be able to with a
much bigger certainty to declare good builds and hence release.
This means focus for 3.1.x is get it to build on 3.5 and then following
is to get the build green and continue to have the build being green
and keep the quality and relevance of the tests improving.
As always, if you got any questions or feedback just shoot an email.
-max
15 years, 8 months
