ACTION REQUIRED: Project leads, please tag your projects [ branch jbosstools-4.1.1.x -> tag jbosstools-4.1.1.Final ]
4 p.m.
Project leads, please tag your projects!
co jbosstools-4.1.1.x
git tag jbosstools-4.1.1.Final
git push origin jbosstools-4.1.1.Final
(This single email replaces 17 Task JIRAs. If you prefer this approach,
let me know. If you prefer JIRAs, let me know that too.)
--
Nick Boldt :: JBoss by Red Hat
Productization Lead :: JBoss Tools & Dev Studio
http://nick.divbyzero.com
6:09 p.m.
Done for base, jst and javaee
On 12/12/2013 02:00 PM, Nick Boldt wrote:
Project leads, please tag your projects!
co jbosstools-4.1.1.x
git tag jbosstools-4.1.1.Final
git push origin jbosstools-4.1.1.Final
(This single email replaces 17 Task JIRAs. If you prefer this approach,
let me know. If you prefer JIRAs, let me know that too.)
2:30 a.m.
Done for LiveReload and WebServices.
Best regards,
/Xavier
On Dec 13, 2013, at 1:09 AM, Alexey Kazakov wrote:
Done for base, jst and javaee
On 12/12/2013 02:00 PM, Nick Boldt wrote:
> Project leads, please tag your projects!
>
> co jbosstools-4.1.1.x
> git tag jbosstools-4.1.1.Final
> git push origin jbosstools-4.1.1.Final
>
>
> (This single email replaces 17 Task JIRAs. If you prefer this approach,
> let me know. If you prefer JIRAs, let me know that too.)
>
_______________________________________________
jbosstools-dev mailing list
jbosstools-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jbosstools-dev
5:59 a.m.
Central done
Le 13/12/2013 09:30, Xavier Coulon a écrit :
Done for LiveReload and WebServices.
Best regards,
/Xavier
On Dec 13, 2013, at 1:09 AM, Alexey Kazakov wrote:
> Done for base, jst and javaee
>
> On 12/12/2013 02:00 PM, Nick Boldt wrote:
>> Project leads, please tag your projects!
>>
>> co jbosstools-4.1.1.x
>> git tag jbosstools-4.1.1.Final
>> git push origin jbosstools-4.1.1.Final
>>
>>
>> (This single email replaces 17 Task JIRAs. If you prefer this approach,
>> let me know. If you prefer JIRAs, let me know that too.)
>>
>
> _______________________________________________
> jbosstools-dev mailing list
> jbosstools-dev(a)lists.jboss.org <mailto:jbosstools-dev@lists.jboss.org>
> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
_______________________________________________
jbosstools-dev mailing list
jbosstools-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jbosstools-dev
---
Ce courrier électronique ne contient aucun virus ou logiciel malveillant parce que la
protection avast! Antivirus est active.
http://www.avast.com
6:37 a.m.
I have done it for arquillian,birt and portlet.
Snjeza
On 12/12/2013 11:00 PM, Nick Boldt wrote:
Project leads, please tag your projects!
co jbosstools-4.1.1.x
git tag jbosstools-4.1.1.Final
git push origin jbosstools-4.1.1.Final
(This single email replaces 17 Task JIRAs. If you prefer this approach,
let me know. If you prefer JIRAs, let me know that too.)
7:11 a.m.
Done for VPE. As for me, email is better notification way.
On 12/13/2013 1:00 AM, Nick Boldt wrote:
Project leads, please tag your projects!
co jbosstools-4.1.1.x
git tag jbosstools-4.1.1.Final
git push origin jbosstools-4.1.1.Final
(This single email replaces 17 Task JIRAs. If you prefer this approach,
let me know. If you prefer JIRAs, let me know that too.)
7:25 a.m.
Done for openshift.
btw. I personally prefer the jira approach, keeps jira as the single
task-listing authority, no mail-spams "Yes, done here".
On 12/12/2013 11:00 PM, Nick Boldt wrote:
Project leads, please tag your projects!
co jbosstools-4.1.1.x
git tag jbosstools-4.1.1.Final
git push origin jbosstools-4.1.1.Final
(This single email replaces 17 Task JIRAs. If you prefer this approach,
let me know. If you prefer JIRAs, let me know that too.)
9:41 a.m.
Thanks to everyone who's tagged!
To reply to Andre's comment about jiras vs. emails (so far the only
feedback):
Task JIRAs still generate email... in fact, they generate way more (for
me, anyway) because as the opener of all the JIRAs, I get one for each
status change of: "assigned to ___" "started working",
"resolved", and
"closed". So that's generally 1 or 2 JIRA emails for each of the 17
projects.
OTOH, when people reply to the mailing list on this thread, then
EVERYONE sees the confirmation/acknowledgement - but for people who can
tag multiple projects, it reduces their overhead from 3 x 2 JIRAs down
to 1 single email.
Replying to me directly would produce the same confirmation response but
w/o the list-spam & dozens of people hitting their delete keys. :)
What about having *1 JIRA for all project tagging*, and everyone can
just comment there when done, without having to take ownership of the
JIRA? That would provide tracking/confirmation/auditing/accountability,
and also reduce the amount of mail generated.
As a project lead, you'd still get everyone's "___ is tagged" emails as
generated by JIRA, but then the whole world wouldn't also see their
spammy goodness in jbosstools-dev@.
WDYT?
N
On 12/13/2013 08:25 AM, Andr� Dietisheim wrote:
Done for openshift.
btw. I personally prefer the jira approach, keeps jira as the single
task-listing authority, no mail-spams "Yes, done here".
On 12/12/2013 11:00 PM, Nick Boldt wrote:
> Project leads, please tag your projects!
>
> co jbosstools-4.1.1.x
> git tag jbosstools-4.1.1.Final
> git push origin jbosstools-4.1.1.Final
>
>
> (This single email replaces 17 Task JIRAs. If you prefer this approach,
> let me know. If you prefer JIRAs, let me know that too.)
>
--
Nick Boldt :: JBoss by Red Hat
Productization Lead :: JBoss Tools & Dev Studio
http://nick.divbyzero.com
9:57 a.m.
On 12/13/2013 04:41 PM, Nick Boldt wrote:
What about having *1 JIRA for all project tagging*, and everyone can
just comment there when done, without having to take ownership of the
JIRA? That would provide tracking/confirmation/auditing/accountability,
and also reduce the amount of mail generated.
Yes, that would be the best thing
IMO.
The Jira would list all projects, and everytime a repository is tagged,
developer come to Jira and says it's done. We close the Jira when all
projects are done.
--
Mickael Istria
Eclipse developer at JBoss, by Red Hat <http://www.jboss.org/tools>
My blog <http://mickaelistria.wordpress.com> - My Tweets
<http://twitter.com/mickaelistria>
10:57 a.m.
a single global jira works for me too, as would any solution, no big
deal. It's more that I love to have my item in my task-list (jira
assigned to me).
On 12/13/2013 04:41 PM, Nick Boldt wrote:
Thanks to everyone who's tagged!
To reply to Andre's comment about jiras vs. emails (so far the only
feedback):
Task JIRAs still generate email... in fact, they generate way more
(for me, anyway) because as the opener of all the JIRAs, I get one for
each status change of: "assigned to ___" "started working",
"resolved", and "closed". So that's generally 1 or 2 JIRA emails
for
each of the 17 projects.
OTOH, when people reply to the mailing list on this thread, then
EVERYONE sees the confirmation/acknowledgement - but for people who
can tag multiple projects, it reduces their overhead from 3 x 2 JIRAs
down to 1 single email.
Replying to me directly would produce the same confirmation response
but w/o the list-spam & dozens of people hitting their delete keys. :)
What about having *1 JIRA for all project tagging*, and everyone can
just comment there when done, without having to take ownership of the
JIRA? That would provide
tracking/confirmation/auditing/accountability, and also reduce the
amount of mail generated.
As a project lead, you'd still get everyone's "___ is tagged" emails
as generated by JIRA, but then the whole world wouldn't also see their
spammy goodness in jbosstools-dev@.
WDYT?
N
On 12/13/2013 08:25 AM, Andr� Dietisheim wrote:
> Done for openshift.
>
> btw. I personally prefer the jira approach, keeps jira as the single
> task-listing authority, no mail-spams "Yes, done here".
>
> On 12/12/2013 11:00 PM, Nick Boldt wrote:
>> Project leads, please tag your projects!
>>
>> co jbosstools-4.1.1.x
>> git tag jbosstools-4.1.1.Final
>> git push origin jbosstools-4.1.1.Final
>>
>>
>> (This single email replaces 17 Task JIRAs. If you prefer this approach,
>> let me know. If you prefer JIRAs, let me know that too.)
>>
>
3:40 p.m.
One key point missing here - please be sure jbosstools-4.1.x have all the commits that
4.1.1.Final has.
A few days ago that was not the case for all repositories!
/max
On 12 Dec 2013, at 23:00, Nick Boldt <nboldt(a)redhat.com> wrote:
Project leads, please tag your projects!
co jbosstools-4.1.1.x
git tag jbosstools-4.1.1.Final
git push origin jbosstools-4.1.1.Final
(This single email replaces 17 Task JIRAs. If you prefer this approach,
let me know. If you prefer JIRAs, let me know that too.)
--
Nick Boldt :: JBoss by Red Hat
Productization Lead :: JBoss Tools & Dev Studio
http://nick.divbyzero.com
_______________________________________________
jbosstools-dev mailing list
jbosstools-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jbosstools-dev
4044
days inactive
4048
days old
jbosstools-dev@lists.jboss.org
10 comments
9 participants
participants (9)
-
Alexey Kazakov -
André Dietisheim -
Fred Bricon -
Konstantin Marmalyukov -
Max Rydahl Andersen -
Mickael Istria -
Nick Boldt -
Snjezana Peco -
Xavier Coulon