AW: DISCUSS How to retire a subproject/component

2016-11-30 Thread jhm
Thanks for feedback. > Since some of the subtitles are common between « Retire » and « > Reactivate », there are duplicate anchors, so some links are not > working as expected. Fixed by adding a prefix "retire: " / "reactivate: " > In http://materne.de/ant/processes.html#mailing list >

AW: DISCUSS How to retire a subproject/component

2016-11-30 Thread jhm
November 2016 13:35 > An: dev@ant.apache.org > Betreff: Re: DISCUSS How to retire a subproject/component > > On 2016-11-30, Jan Matèrne (jhm) wrote: > > >> This topic raises another question. What should we do about the > >> artifact released in dist ? I gue

Re: DISCUSS How to retire a subproject/component

2016-11-30 Thread Stefan Bodewig
On 2016-11-30, Jan Matèrne (jhm) wrote: >> This topic raises another question. What should we do about the >> artifact released in dist ? I guess we should delete them so they get >> archived ? > Sounds good. > But if we delete them, how get they archived? They should already be somewhere under

AW: DISCUSS How to retire a subproject/component

2016-11-30 Thread jhm
> > - release further resources > > > > Maybe a subproject locks further resources (update-site, ...). So we have > > to release them? > > I don’t understand this. How a retirement of a sub project should > trigger the release of a related project ? This is a misunderstanding in my wording.

Re: DISCUSS How to retire a subproject/component

2016-11-30 Thread Nicolas Lalevée
Hi, See my comments inline. > Le 25 nov. 2016 à 08:18, Jan Matèrne (jhm) a écrit : > > There aren't as many comments as I hoped to get ... > A main comment was that we also need a process of reactivating a subproject. > > So here are the updated proposals for the two

Re: DISCUSS How to retire a subproject/component

2016-11-28 Thread Conor MacNeill
It does look good. +1 from me Conor On 25 November 2016 at 18:18, Jan Matèrne (jhm) wrote: > There aren't as many comments as I hoped to get ... > A main comment was that we also need a process of reactivating a subproject. > > So here are the updated proposals for the two

Re: DISCUSS How to retire a subproject/component

2016-11-28 Thread Stefan Bodewig
On 2016-11-25, Jan Matèrne (jhm) wrote: > So here are the updated proposals for the two processes/todo-lists. looks good to me Stefan - To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org For additional commands,

AW: DISCUSS How to retire a subproject/component

2016-11-24 Thread jhm
There aren't as many comments as I hoped to get ... A main comment was that we also need a process of reactivating a subproject. So here are the updated proposals for the two processes/todo-lists. Again - please comment. Jan -- The retirenment of a

Re: DISCUSS How to retire a subproject/component

2016-11-22 Thread Stefan Bodewig
On 2016-11-21, Jan Matèrne wrote: > When retiring a subproject/component, what should and have we to do? > I collect some topics: > - version control > Most of our source code is in git, only "site" and "sandbox" use > subversion. > I propose to simply place a marker file on the top

Re: DISCUSS How to retire a subproject/component

2016-11-21 Thread Rm Beer
is this a free software. is obviously that anyone can contribute or not contribute. You only need remember that have one or something subproject without maintain and later hope. This subprojects always can hope, not need a clean 2016-11-21 4:08 GMT-03:00 Jan Matèrne : >

DISCUSS How to retire a subproject/component

2016-11-20 Thread Jan Matèrne
Sadly we have some subprojects without any committer nor community background. Instead of leaving them as they are and hoping that "someone" will "sometime in the future" work harder on them and do a release we retire them. In that way we will reflect the real current status. As for top level