No, when we deprecate something it means no more work will be done on it. Triaging issues, reviewing and merging other people prs and continuing doing releases it’s work. We aren’t supposed to do anything else when we deprecate.
People can freely create and maintain a fork, but it won’t be official and won’t live in the Apache repo. El miércoles, 8 de agosto de 2018, Jan Piotrowski <piotrow...@gmail.com> escribió: > Let me play devil's advocate: > > Archiving means disabling everything - issues, PRs, etc. > Don't we want to let people create PRs with bug fixes or changes (we > may or may not choose to merge) for other people to benefit from? > > -J > > 2018-08-08 3:40 GMT+02:00 Gearóid M <d...@gearoid.me>: > > +1 on archiving deprecated repos, it's an easy way to make it very clear > that it is no longer maintained > > > > On Wed, 8 Aug 2018, at 01:37, Chris Brody wrote: > >> +1 > >> On Tue, Aug 7, 2018 at 11:32 AM julio cesar sanchez > >> <jcesarmob...@gmail.com> wrote: > >> > > >> > Archived repos are read only. > >> > > >> > People can still clone and/or fork them, they just can't send PRs or > create > >> > new issues. > >> > > >> > I'm +1 on archiving them. > >> > > >> > > >> > > >> > El mar., 7 ago. 2018 a las 17:25, <raphine...@gmail.com> escribió: > >> > > >> > > I suggest archiving them all and deal with any issues as they > appear. After > >> > > all, repos can be unarchived if necessary. > >> > > > >> > > Chris Brody <chris.br...@gmail.com> schrieb am Di., 7. Aug. 2018, > 17:16: > >> > > > >> > > > Continuation of discussion from > >> > > > > >> > > > > >> > > https://lists.apache.org/thread.html/affbc74f0ff4d34bc09657c3c302e1 > 85cc98b946d260184847fdf191@%3Cdev.cordova.apache.org%3E > >> > > > > >> > > > I think it is not desired to actively support deprecated repos. I > >> > > > think the easiest solution is to simply make those repos archived. > >> > > > > >> > > > But what if there are people still using the deprecated repos who > are > >> > > > motivated to take them over? > >> > > > > >> > > > ------------------------------------------------------------ > --------- > >> > > > To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org > >> > > > For additional commands, e-mail: dev-h...@cordova.apache.org > >> > > > > >> > > > > >> > > > >> > >> --------------------------------------------------------------------- > >> To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org > >> For additional commands, e-mail: dev-h...@cordova.apache.org > >> > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org > > For additional commands, e-mail: dev-h...@cordova.apache.org > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org > For additional commands, e-mail: dev-h...@cordova.apache.org > >
