14 Feb
2014
14 Feb
'14
12:19 p.m.
Hi devs,
I’d like to propose a Deprecation Fixing Day for the next XWiki Day, ie for the 20 Feb
2014.
The rules I propose:
* On that day, I send the reminder email with inside the # of deprecated calls found in
Commons, Rendering and Platform. For example right now it’s:
- Commons: 39
(http://sonar.xwiki.org/drilldown/issues/1?&rule=squid%3ACallToDeprecate…)
- Rendering: 3
(http://sonar.xwiki.org/drilldown/issues/915?&rule=squid%3ACallToDepreca…)
- Platform: (still being computed, I don’t have a link to give ATM ;))
* One goal is to replace calls to deprecated methods by new API calls
* Another goal is to move deprecated methods and types to legacy modules
* On that day, I'll prepare a Blog post on xwiki.org (not published) and everyone who
participates to this day should edit the blog post with his score for the day (since it’s
hard to compute automatically). There’ll be 2 scores for everyone: a score for removed
deprecated calls (1 point per removal) and a score for types and methods moved to legacy
modules (1 point per type and method moved).
WDYT?
Note that in the future I’d like to expand this to a more generic Violation Fixing Day
which would be about fixing any type of violations as reported by Sonar but before we do
this we need to decide which violations we consider important and configuration Sonar
properly for that. I’ll try to propose something on this soon.
Thanks
-Vincent
14 Feb
14 Feb
12:21 p.m.
New subject: [xwiki-devs] [Proposal] XWiki Day for 20 Feb 2014: Deprecation Fixing Day
Sounds good.
On Fri, Feb 14, 2014 at 12:19 PM, vincent(a)massol.net <vincent(a)massol.net> wrote:
Hi devs,
I'd like to propose a Deprecation Fixing Day for the next XWiki Day, ie for the 20
Feb 2014.
The rules I propose:
* On that day, I send the reminder email with inside the # of deprecated calls found in
Commons, Rendering and Platform. For example right now it's:
- Commons: 39
(http://sonar.xwiki.org/drilldown/issues/1?&rule=squid%3ACallToDeprecate…)
- Rendering: 3
(http://sonar.xwiki.org/drilldown/issues/915?&rule=squid%3ACallToDepreca…)
- Platform: (still being computed, I don't have a link to give ATM ;))
* One goal is to replace calls to deprecated methods by new API calls
* Another goal is to move deprecated methods and types to legacy modules
* On that day, I'll prepare a Blog post on xwiki.org (not published) and everyone who
participates to this day should edit the blog post with his score for the day (since
it's hard to compute automatically). There'll be 2 scores for everyone: a score
for removed deprecated calls (1 point per removal) and a score for types and methods moved
to legacy modules (1 point per type and method moved).
WDYT?
Note that in the future I'd like to expand this to a more generic Violation Fixing
Day which would be about fixing any type of violations as reported by Sonar but before we
do this we need to decide which violations we consider important and configuration Sonar
properly for that. I'll try to propose something on this soon.
Thanks
-Vincent
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs
--
Thomas Mortagne
2:58 p.m.
New subject: [xwiki-devs] [Proposal] XWiki Day for 20 Feb 2014: Deprecation Fixing Day
Hi devs,
I’d like to propose a Deprecation Fixing Day for the next XWiki Day, ie for the 20 Feb
2014.
The rules I propose:
* On that day, I send the reminder email with inside the # of deprecated calls found in
Commons, Rendering and Platform. For example right now it’s:
- Commons: 39
(http://sonar.xwiki.org/drilldown/issues/1?&rule=squid%3ACallToDeprecate…)
- Rendering: 3
(http://sonar.xwiki.org/drilldown/issues/915?&rule=squid%3ACallToDepreca…)
- Platform: (still being computed, I don’t have a link to give ATM ;))
* One goal is to replace calls to deprecated methods by new API calls
* Another goal is to move deprecated methods and types to legacy modules
* On that day, I'll prepare a Blog post on xwiki.org (not published) and everyone who
participates to this day should edit the blog post with his score for the day (since it’s
hard to compute automatically). There’ll be 2 scores for everyone: a score for removed
deprecated calls (1 point per removal) and a score for types and methods moved to legacy
modules (1 point per type and method moved).
WDYT?
Good idea. Do deprecated calls in Wiki documents serialised as *.xml also count?
I worry a bit about how to avoid two people fixing the same calls concurrently.
Formally one might be able to achieve this by this workflow:
- before you start on one point, edit the said Blog post, but score yourself 0 points for
the change you want to do
(only after checking that nobody else already did so, of course)
- fix the problem
- afterwards add the correct score to yourself
However I guess that is just too much red tape, and dropping a line in chat is good enough
to coordinate ?
Cheers,
Clemens
Note that in the future I’d like to expand this to a
more generic Violation Fixing Day which would be about fixing any type of violations as
reported by Sonar but before we do this we need to decide which violations we consider
important and configuration Sonar properly for that. I’ll try to propose something on this
soon.
Thanks
-Vincent
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs
3:15 p.m.
New subject: [xwiki-devs] [Proposal] XWiki Day for 20 Feb 2014: Deprecation Fixing Day
Hi Clemens,
On 14 Feb 2014 at 14:58:33, Clemens Klein-Robbenhaar
(c.robbenhaar@espresto.com(mailto:c.robbenhaar@espresto.com)) wrote:
Normally there aren’t any since we normally fail the build in the webstandards functional
tests when they happen.
Do you have any in mind? :)
Hi devs,
I’d like to propose a Deprecation Fixing Day for the next XWiki Day, ie for the 20 Feb
2014.
The rules I propose:
* On that day, I send the reminder email with inside the # of deprecated calls found in
Commons, Rendering and Platform. For example right now it’s:
- Commons: 39
(http://sonar.xwiki.org/drilldown/issues/1?&rule=squid%3ACallToDeprecate…)
- Rendering: 3
(http://sonar.xwiki.org/drilldown/issues/915?&rule=squid%3ACallToDepreca…)
- Platform: (still being computed, I don’t have a link to give ATM ;))
* One goal is to replace calls to deprecated methods by new API calls
* Another goal is to move deprecated methods and types to legacy modules
* On that day, I'll prepare a Blog post on xwiki.org (not published) and everyone who
participates to this day should edit the blog post with his score for the day (since it’s
hard to compute automatically). There’ll be 2 scores for everyone: a score for removed
deprecated calls (1 point per removal) and a score for types and methods moved to legacy
modules (1 point per type and method moved).
WDYT?
Good idea. Do deprecated calls in Wiki documents serialised as *.xml also count? I worry a bit about how to avoid two people fixing the
same calls concurrently.
Formally one might be able to achieve this by this workflow:
- before you start on one point, edit the said Blog post, but score yourself 0 points for
the change you want to do
(only after checking that nobody else already did so, of course)
- fix the problem
- afterwards add the correct score to yourself
However I guess that is just too much red tape, and dropping a line in chat is good
enough to coordinate ?
Yes IMO using IRC to coordinate is good enough.
Alternatively we could decide to create jira issues with component being “Development
issue only” (this component already exists).
Thanks
-Vincent
Cheers,
Clemens
> Note that in the future I’d like to expand this to a more generic Violation Fixing
Day which would be about fixing any type of violations as reported by Sonar but before we
do this we need to decide which violations we consider important and configuration Sonar
properly for that. I’ll try to propose something on this soon.
>
> Thanks
> -Vincent
5:38 p.m.
New subject: [xwiki-devs] [Proposal] XWiki Day for 20 Feb 2014: Deprecation Fixing Day
Hi Vincent,
On 02/14/2014 03:15 PM, vincent(a)massol.net wrote:
Hi Clemens,
On 14 Feb 2014 at 14:58:33, Clemens Klein-Robbenhaar
(c.robbenhaar@espresto.com(mailto:c.robbenhaar@espresto.com)) wrote:
Ah, that's why I cannot find any :)
Actually I thought I have seen quite a lot of deprecation warnings in the logs for this
and that page, but when
I check with the latests 6.0-SNAPSHOT I see the fews that show up come from extensions or
velocity marcros in dated test content ...
Cheers,
Clemens
[...] Do deprecated calls in Wiki documents
serialised as *.xml also count?
Normally there aren’t any since we normally fail the build in the webstandards functional
tests when they happen.
Do you have any in mind? :)
15 Feb
15 Feb
10:41 a.m.
New subject: [xwiki-devs] [Proposal] XWiki Day for 20 Feb 2014: Deprecation Fixing Day
+1
Thanks,
Marius
On Feb 14, 2014 1:19 PM, "vincent(a)massol.net" <vincent(a)massol.net> wrote:
Hi devs,
I'd like to propose a Deprecation Fixing Day for the next XWiki Day, ie
for the
20 Feb 2014.
The rules I propose:
* On that day, I send the reminder email with inside the # of deprecated
calls
found in Commons, Rendering and Platform. For example right now it's:
- Commons: 39 (
http://sonar.xwiki.org/drilldown/issues/1?&rule=squid%3ACallToDeprecate…
)
- Rendering: 3 (
http://sonar.xwiki.org/drilldown/issues/915?&rule=squid%3ACallToDepreca…
)
- Platform: (still being computed, I don't have a
link to give ATM ;))
* One goal is to replace calls to deprecated methods by new API calls
* Another goal is to move deprecated methods and types to legacy modules
* On that day, I'll prepare a Blog post on xwiki.org (not published) and
everyone who participates to this day should edit the blog post with his
score for the day (since it's hard to compute automatically). There'll be 2
scores for everyone: a score for removed deprecated calls (1 point per
removal) and a score for types and methods moved to legacy modules (1 point
per type and method moved).
WDYT?
Note that in the future I'd like to expand this to a more generic
Violation
Fixing Day which would be about fixing any type of violations as
reported by Sonar but before we do this we need to decide which violations
we consider important and configuration Sonar properly for that. I'll try
to propose something on this soon.
Thanks
-Vincent
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs
11:37 a.m.
New subject: [xwiki-devs] [Proposal] XWiki Day for 20 Feb 2014: Deprecation Fixing Day
Here’s a global view to show all deprecations across commons, rendering and platform:
http://sonar.xwiki.org/drilldown/issues/6131?&rule=squid%3ACallToDeprec…
2088 in platform to fix ;)
Thanks
-Vincent
On 14 Feb 2014 at 12:19:25, vincent(a)massol.net
(vincent@massol.net(mailto:vincent@massol.net)) wrote:
Hi devs,
I’d like to propose a Deprecation Fixing Day for the next XWiki Day, ie for the 20 Feb
2014.
The rules I propose:
* On that day, I send the reminder email with inside the # of deprecated calls found in
Commons, Rendering and Platform. For example right now it’s:
- Commons: 39
(http://sonar.xwiki.org/drilldown/issues/1?&rule=squid%3ACallToDeprecate…)
- Rendering: 3
(http://sonar.xwiki.org/drilldown/issues/915?&rule=squid%3ACallToDepreca…)
- Platform: (still being computed, I don’t have a link to give ATM ;))
* One goal is to replace calls to deprecated methods by new API calls
* Another goal is to move deprecated methods and types to legacy modules
* On that day, I'll prepare a Blog post on xwiki.org (not published) and everyone who
participates to this day should edit the blog post with his score for the day (since it’s
hard to compute automatically). There’ll be 2 scores for everyone: a score for removed
deprecated calls (1 point per removal) and a score for types and methods moved to legacy
modules (1 point per type and method moved).
WDYT?
Note that in the future I’d like to expand this to a more generic Violation Fixing Day
which would be about fixing any type of violations as reported by Sonar but before we do
this we need to decide which violations we consider important and configuration Sonar
properly for that. I’ll try to propose something on this soon.
Thanks
-Vincent
3866
days inactive
3867
days old
6 comments
4 participants
participants (4)
-
Clemens Klein-Robbenhaar -
Marius Dumitru Florea -
Thomas Mortagne -
vincent＠massol.net