Did you finally tried "full graph analysis on Central to see what Maven plugins
actually depend on SLF4J or an implementation" as intended on february 1st?
This was a great idea to have some facts to predict problems like SONAR-3979
But if such idea is harder than expected, doing a release and se
With a bit of a notice (don't care if it's one week or 4 days or….), I
certainly support this path. We need to talking about it and get 3.1 out.
Dan
On Feb 26, 2013, at 9:05 AM, Jason van Zyl wrote:
> As I posted previously I would like to do the 3.1.0 release but I don't want
> to do the
OK, I follow the logic now.
On Tue, Feb 26, 2013 at 9:55 AM, Stephen Connolly
wrote:
> I thought about that, but I suspect that we are at least 1 week away from
> being ready to cut 3.1.0 anyway, so 1 week seems safest and gives potential
> volunteers time to chime in. If Jason thinks he will be
I thought about that, but I suspect that we are at least 1 week away from
being ready to cut 3.1.0 anyway, so 1 week seems safest and gives potential
volunteers time to chime in. If Jason thinks he will be ready to cut 3.1.0
in 4 days time, then I would consider 4 days...
On 26 February 2013 14:1
Yup, sounds reasonable.
On Feb 26, 2013, at 9:14 AM, Stephen Connolly
wrote:
> I would propose that we give until this time next week for somebody to
> stand up and state that they feel the isolation is necessary and that they
> are prepared to do the work to implement the isolation.
>
> If th
I think that a week is quite generous. I'd cut it down to 4 days. In
any case, I support the general scheme here.
On Tue, Feb 26, 2013 at 9:14 AM, Stephen Connolly
wrote:
> I would propose that we give until this time next week for somebody to
> stand up and state that they feel the isolation is
I would propose that we give until this time next week for somebody to
stand up and state that they feel the isolation is necessary and that they
are prepared to do the work to implement the isolation.
If there is at least one person committing themselves, then we should
discuss the timetable they
As I posted previously I would like to do the 3.1.0 release but I don't want to
do the work of isolating SLF4J until it's shown that it will be a problem. I
don't the believe the adoption of 3.1.0 is going to be so quick that we can't
create a fix if necessary. I would rather do the release in a
