On Thu, 16 Aug 2018 10:29:15 -0400 Mike Blumenkrantz <michael.blumenkra...@gmail.com> said:
> I am a bit curious where you think we need this much work with triaging? > > The biggest issue that we will have here is actually from our > passive-aggressive method of rejecting things we don't like. For example, > there are many, many patches that have been rejected and are idle for a > long time but not abandoned. These will not be closed using the current a lot of patches are rejected or have been asked for changes and the submitter never does it and they don't abandon. to forcibly kill it off you have to first commandeer then abandon as the new submitter. i got tired of doing that and just waited for submitters to do it. invariably many did not. this isn't passive-agreessive. it's submitters not ackowledging the patch should be abandoned. this is of course different to patches that were forgotten about. i think your characterization here is entirely wrong. > migration method. There are also unlimited tickets set to 'pending on user > input' which are dead; these also will not be closed. Most likely both of > these types of open items should just be closed during migration. probably. > On Sat, Aug 11, 2018 at 2:56 AM Jonathan Aquilina <jaquil...@eagleeyet.net> > wrote: > > > Guess then would be to migrate everything and I’ll work on triaging the > > bigs after > > > > Sent from my iPhone > > > > > On 11 Aug 2018, at 08:23, Pierre Couderc <pie...@couderc.eu> wrote: > > > > > >> On 08/11/2018 07:30 AM, jaquil...@eagleeyet.net wrote: > > >> If we are going to migrate I think we should migrate tickets slowly to > > see which ones are still valid and not pollute the new tracker with issues > > that are either moot or no longer valid. > > >> > > > Mmm, it is not logical. Migrate is a thing. Process tickets is another > > thing. Trying to do 2 independant things simulteaneoulsy....? > > > > > > > > ------------------------------------------------------------------------------ > > > Check out the vibrant tech community on one of the world's most > > > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > > > _______________________________________________ > > > enlightenment-devel mailing list > > > enlightenment-devel@lists.sourceforge.net > > > https://lists.sourceforge.net/lists/listinfo/enlightenment-devel > > > > > > > > ------------------------------------------------------------------------------ > > Check out the vibrant tech community on one of the world's most > > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > > _______________________________________________ > > enlightenment-devel mailing list > > enlightenment-devel@lists.sourceforge.net > > https://lists.sourceforge.net/lists/listinfo/enlightenment-devel > > > ------------------------------------------------------------------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > _______________________________________________ > enlightenment-devel mailing list > enlightenment-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/enlightenment-devel -- ------------- Codito, ergo sum - "I code, therefore I am" -------------- Carsten Haitzler - ras...@rasterman.com ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
