How to Triage Issues?
by Rob Stryker
Hi All:
Do we have a document available with the proper way to triage issues? I
seriously have no idea anymore, and every time I try to change an old
issue, I end up getting an email telling me that it's not triaged now.
I used to assign myself, even if I didn't intend to work on it, to
indicate that it "was read". I was told this was incorrect, and that
there should be no assignee if nobody is actively working on it.
I also used to mark it as targeted to later, but I was told this was
vague and should not be used as a dumping ground for all issues that
aren't on the plan.
But if I leave the fix version blank (to indicate it is not on my plan),
I get an email telling me the issue is untriaged.
I also tried commenting on issues, to indicate that I've seen them, but
didn't change the fix version or assignee since I did not have a firm
target for it.... but this gets the same emails.
Should I go in right now and bulk-change all my unassigned untargeted
issues to myself with a fix version, even if I have no idea if that fix
version is accurate? Or should I mark all I don't have a firm target for
to "Later" ?
What's the process here?
12 years
I didn't get any reply from you for a long time, so I send you this e-mail, can you still get my e-mail?
by Ted Hoo
Hi,
I didn't get any reply from you for a long time, so I send you this e-mail, can you still get my e-mail?
We are a factory from China. We are looking for the distributors or importers for our diving masks, diving snorkels, swimming products and ski goggles, if you are still interested, tell me so I can send the price list to you. In the past we mainly exported to America, West Europe, Japan and South Korea.
Ted Hoo
12 years
Re: [jbosstools-dev] Need help with hudson builds at eclipse.org
by Bob Brodt
Whew! Finally got this thing to build again after fiddling with various maven plugin versions.
@Paul, looks like we will have a version 1.0.4 of BPEL Designer for Luna. We also have new MDT-BPMN2 version 1.0.0 and BPMN2 Modeler 1.1.0 (that hasn't changed since last we spoke).
Again, the release date for Luna is June 25.
Thanks all!
Bob
----- Original Message -----
> Hi all,
>
> Sorry for spamming this mailing list, but I'm getting desperate :(
>
> Apparently the Maven jar signing and packing plugins that I've been using to
> build the BPEL Designer at eclipse.org have been deprecated and the build
> that's been running quite happily for the last year or so, is now failing.
>
> I've tried updating to the newer versions of these plugins, but I'm no Maven
> expert and can't seem to get past the final packaging stage of the update
> site zip.
>
> If anyone has any experience with this sh...tuff, and has some spare cycles,
> please contact me directly.
>
> Thanks in advance,
> Bob
>
> ________________________
> Robert ("Bob") Brodt
> Senior Software Engineer
> JBoss by Red Hat
>
>
12 years
Need help with hudson builds at eclipse.org
by Bob Brodt
Hi all,
Sorry for spamming this mailing list too, but I'm really getting desperate :(
Apparently the Maven jar signing and packing plugins that I've been using to build the BPEL Designer at eclipse.org have been deprecated and the build that's been running quite happily for the last year or so, is now failing.
I've tried updating to the newer versions of these plugins, but I'm no Maven expert and can't seem to get past the final packaging stage of the update site zip.
If anyone has any experience with this sh...tuff, and has some spare cycles, please contact me directly.
Thanks in advance,
Bob
________________________
Robert ("Bob") Brodt
Senior Software Engineer
JBoss by Red Hat
12 years
"As-you-type" validation for JAX-RS classes
by Xavier Coulon
Hello,
My JAX-RS validator is based on our org.jboss.tools.common.validation.ValidationErrorManager, but it is currently triggered when the user saves a file or during a full build, only.
What I would like to try is to have "as-you-type" validation, so that problem markers can be added/removed without having to wait for the next build, just like JDT does. Is there a way to configure the validator to get this behaviour, or is it a limitation of the WST Validator ?
Thanks.
Best regards,
/Xavier
12 years
JBT / JBDS / Central Target Platform versions in Beta2 & Beta3 (master branch)
by Nick Boldt
In case you're a bit confused about the current versions of target
platforms in use in the Beta2x branch (JBoss Tools 4.2.0.Beta2a / JBDS
8.0.0.Beta2a), here's a quick recap of the current versions currently
being used:
= In jbosstools-4.2.0.Beta2x branch, we have:
== JBT 4.2.0.Beta2a
Target Platform: 4.40.0.Beta3 (released to Nexus)
Central - Core: 4.40.0.Beta3-SNAPSHOT
Central - Early Access: 4.40.0.Beta3-SNAPSHOT
== JBDS 8.0.0.Beta2a
Target Platform: 4.40.0.Beta3 (released to Nexus)
Central - Core: 4.40.0.Beta3-SNAPSHOT
Central - Early Access: 4.40.0.Beta3-SNAPSHOT
= In Master branch, we have (or will have):
== JBT 4.2.0.Beta3
Target Platform: 4.40.0.Beta4-SNAPSHOT
Central - Core: 4.40.0.Beta3-SNAPSHOT (4.40.0.Beta4-SNAPSHOT)
Central - Early Access: 4.40.0.Beta3-SNAPSHOT (4.40.0.Beta4-SNAPSHOT)
== JBDS 8.0.0.Beta3
Target Platform: 4.40.0.Beta4-SNAPSHOT
Central - Core: 4.40.0.Beta3-SNAPSHOT (4.40.0.Beta4-SNAPSHOT)
Central - Early Access: 4.40.0.Beta3-SNAPSHOT (4.40.0.Beta4-SNAPSHOT)
If you're wondering why we have a Beta3 TP for the Beta2 release, it's
simple: we released the TP thinking we were done, then found a critical
bug. Since you can't re-release an artifact to JBoss Nexus using the
same version, we had to upversion from Beta2 to Beta3-SNAPSHOT, then
release that as Beta3.
As a result, master branch is now Beta4-SNAPSHOT for the JBT/JBDS TPs,
but for the moment, Central target platforms in both Beta2x and master
are at Beta3-SNAPSHOT, and will remain that way until we are sure the
content is ready to be released to Nexus.
--
Nick Boldt :: JBoss by Red Hat
Productization Lead :: JBoss Tools & Dev Studio
http://nick.divbyzero.com
12 years
