Hey, * Pirate Praveen <prav...@onenetbeyond.org> [2018-12-18 09:34:46 CET]: > On 12/3/18 8:11 PM, Dominik George wrote: > >> well, Debian is using gitlab!!! so this sentence has no sense. The > >> problem here > >> is that is a complex software that depends of a lot of pieces and it's > >> not > >> easy/possible to fit the definition. So, maybe we should create another > >> category > >> of software. > > > > Yes, and that Debian officially uses GitLab, from a foreign source, without > > being able to support it in Debian, does make me feel ashamed for the > > project. > > > >> maybe creating another kind of repo. debian-contributuions > >> debian-blabla, whatever. > >> > > > > We had volatile, which, redefined properly, could help. I am trying to > > draft such a definition. > > Did you get a chance to work on it?
Yes, it looks very much that the shutting down of volatile made wishes appear for backports to cover it - while it wasn't (and shouldn't) be the scope for it. It would make it indistinguishable which packages within backports are following the regular rules and which would be those fast moving targets without any useful tracking or upgrade features in the regular sense. (Part of that was btw. also the creation of a seperate sloppy pocket for backports from oldstable+2 releases, to make it clear what to expect in there) And yes, I'm with Alexander, the volatile maintenance can't be dumped on the backports team. It's a different workflow anyway. Good luck, Rhonda -- Fühlst du dich mutlos, fass endlich Mut, los | Fühlst du dich hilflos, geh raus und hilf, los | Wir sind Helden Fühlst du dich machtlos, geh raus und mach, los | 23.55: Alles auf Anfang Fühlst du dich haltlos, such Halt und lass los |