On domenica 31 dicembre 2017 14:12:19 CET Sandro Knauß wrote:
> Hey,
> > I'd kindly ask you to hold that until:
> > a) KDEPIM 17.08.3 migrates to testing
> > b) I sort out the coinstallation issues with kdepim4
> my thought was to use experimental to prepare 17.12 and also use a debian/
> experimental branch in git to not interfere or do you need experimental to 
> prepare something too?

I'm still doing changes (see my other email), so I'd really prefer to
not deal with pending changes merged to another one, as it will make
also your work more annoying.

I can understand you want to work on PIM 17.12, but 17.08 has still_not_
migrated to testing as of today, so mixing stuff will not help.

> > c) possibly triage old bugs
> I'm quite bad in triage bugs and keep the overview as we already have 
> multiple 
> hundreads of bugs inside kdepim. Does someone has any thoughts, how we may 
> manage to triage those?

- go source by source
- start with forwarded bugs with fixed-upstream tag: check what is the
  upstream status, figure out when they were closed, why, in which
  actual Debian source is the fix (in case reassign), and close properly
- check the non-forwarded bugs: see whether they are reproducible with
  the versions in unstable, check whether there is an upstream bug about
  them (in case set as forwarded URL), possibly forward upstream, etc

> Maybe we have to be realistitic and say everything 
> older than 4 years we will close and tell the authos, that we have too less 
> manpower to handle the bugs?

IMHO being realistic about the fact that there is not enough manpower
is one thing, while closing bugs outright without even looking at them
is another thing, which does not give us a good impression by the users
("I reported a bug, and they closed it without even reading it").

> > > (17.12 should be much easier, because we only have one new source
> > > package: ksmtp [1])
> > Sort-of ready in git, but "needs" (thanks Laurent Montel for the
> > unneeded requirement bumps) newer Frameworks than what is in unstable.
> as I said - prepare in experimental :D

Sure, ksmtp can be already prepared, and sent to NEW for experimental.

Pino Toscano

Attachment: signature.asc
Description: This is a digitally signed message part.


Reply via email to