The vote about archiving IvyDE starts on 05.December 2016 [1].
The result is:
* binding votes
+1: (Jan), (Nicolas), Jean-Louis, Dominique,
0: Stefan
-1: --
asks for cancelling: Nicolas [3], Jan [4]
* non binding votes
+1: --
0: --
-1: Gintas [2]
I interpret the asks for
A short report on status (and more detailed answers to Nicholas questions):
- the doc builds correctly once I clone ant-xooki repository on Github
into doc/xooki;
- the style clone on Github is empty; I did "wget -np -nd -r
> Very well, how does one revive a project?
>
> Gintas
If you ask for the process of reactivating it after archiving, that's
documented at http://ant.apache.org/processes.html.
But ATM it is still alive - but sleeping. ;-)
Jan
AFAICS, Subversion is invoked in one of the targets connected to packaging
of a release, and I'm looking into an equivalent for Git.
What is more interesting is getting all Eclipse components. Current process
depends on finding a "good" mirror, and I'm tempted to investigate a
possibility to use
Very well, how does one revive a project?
Gintas
2016-12-08 21:01 GMT+01:00 Jan Matèrne (jhm) :
> > Considering the current discussion around IvyDE and the involvement of
> > Gintas, maybe we could cancel this vote, at least postpone it ?
> >
> > Nicolas
>
>
> Yes, I agree.
>
> Considering the current discussion around IvyDE and the involvement of
> Gintas, maybe we could cancel this vote, at least postpone it ?
>
> Nicolas
Yes, I agree.
The discussion and the vote about retiring IvyDE had brought much more activity
than the months before (as I recognized).
But I
Considering the current discussion around IvyDE and the involvement of Gintas,
maybe we could cancel this vote, at least postpone it ?
Nicolas
> Le 5 déc. 2016 à 08:04, Jan Matèrne (jhm) a écrit :
>
> I start a vote for retiring IvyDE.
>
> The last release was in 11/2013.
I am forking the thread to not pollute the vote.
> Le 7 déc. 2016 à 19:56, Gintautas Grigelionis a
> écrit :
>
> I decided to take a quick look at the build process and it's not broken per
> se, rather it's hardcoded to Eclipse SDK 3.7.1 foe Win32.
You confirm the doc
I decided to take a quick look at the build process and it's not broken per
se, rather it's hardcoded to Eclipse SDK 3.7.1 foe Win32. I would like to
make the process to adapt to the build platform. Any suggestions for a
reasonable Eclipse baseline? Should we target Java 8, that would be 4.5 (or
> Le 7 déc. 2016 à 12:34, Gintautas Grigelionis a
> écrit :
>
> I would prefer an agreement on status. IvyDE is dependent on Ivy and
> ideally their release cycles should be synced.
> Since there seem to be some changes brewing in Ivy, IvyDE could be used as
> a test
I would prefer an agreement on status. IvyDE is dependent on Ivy and
ideally their release cycles should be synced.
Since there seem to be some changes brewing in Ivy, IvyDE could be used as
a test case.
Gintas
2016-12-07 11:37 GMT+01:00 Stefan Bodewig :
> On 2016-12-07,
On 2016-12-07, Gintautas Grigelionis wrote:
> Somebody mentioned that IvyDE build process is broken and I would like to
> look into that if it could help to prevent retirement.
That would be wonderful, regardless of whether it prevents retirement.
Stefan
Somebody mentioned that IvyDE build process is broken and I would like to
look into that if it could help to prevent retirement.
Gintas
2016-12-07 10:00 GMT+01:00 Dominique Devienne :
> +1
>
> On Wed, Dec 7, 2016 at 8:41 AM, Jean-Louis Boudart <
>
+1
On Wed, Dec 7, 2016 at 8:41 AM, Jean-Louis Boudart <
jeanlouis.boud...@gmail.com> wrote:
> +1
>
> Le 6 déc. 2016 6:51 PM, "Nicolas Lalevée" a
> écrit :
>
> > +1
> >
> > Nicolas
> >
> > > Le 6 déc. 2016 à 17:22, Stefan Bodewig a écrit :
> > >
>
+1
Le 6 déc. 2016 6:51 PM, "Nicolas Lalevée" a
écrit :
> +1
>
> Nicolas
>
> > Le 6 déc. 2016 à 17:22, Stefan Bodewig a écrit :
> >
> > On 2016-12-05, Jan Matèrne (jhm) wrote:
> >
> >> I start a vote for retiring IvyDE.
> >
> > +0
> >
> > The
+1
Nicolas
> Le 6 déc. 2016 à 17:22, Stefan Bodewig a écrit :
>
> On 2016-12-05, Jan Matèrne (jhm) wrote:
>
>> I start a vote for retiring IvyDE.
>
> +0
>
> The discussion in the "Ivy" thread makes me think we'd probably want to
> update it with new Ivy releases, even if
On 2016-12-05, Jan Matèrne (jhm) wrote:
> I start a vote for retiring IvyDE.
+0
The discussion in the "Ivy" thread makes me think we'd probably want to
update it with new Ivy releases, even if nothing else changes in
between.
Stefan
I start a vote for retiring IvyDE.
The last release was in 11/2013.
The last 'real' code activity was in 08/2014.
It seems that we havent the community, committers and PMC to hold this
subproject.
The general procedure is described in http://ant.apache.org/processes.html.
I start
18 matches
Mail list logo