Re: [E-devel] Gitlab
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 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. On Sat, Aug 11, 2018 at 2:56 AM Jonathan Aquilina 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 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
Re: [E-devel] Gitlab
The way I see it if there is lack of activity it gets closed and if need be reopened when the issue resurfaced Sent from my iPhone > On 16 Aug 2018, at 16:29, Mike Blumenkrantz > wrote: > > 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 > 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. > > On Sat, Aug 11, 2018 at 2:56 AM Jonathan Aquilina > 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 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 -- 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
Re: [E-devel] Gitlab
Also to add I think stuff wiht lack of activity or things have changed for now should be closed as well. I see the issue tracker as something for key issues that are reproducible as well as key things that need to get done that are key for a release or bugs to be fixed. On 2018-08-16 14:38, Jonathan Aquilina wrote: The way I see it if there is lack of activity it gets closed and if need be reopened when the issue resurfaced Sent from my iPhone On 16 Aug 2018, at 16:29, Mike Blumenkrantz wrote: 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 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. On Sat, Aug 11, 2018 at 2:56 AM Jonathan Aquilina 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 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 -- 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
