Quoting Pirate Praveen (2020-09-21 09:15:46) > > > On 2020, സെപ്റ്റംബർ 21 3:37:01 AM IST, Jonas Smedegaard <jo...@jones.dk> > wrote: > >> I think we should create a release team within js team to handle it > >> like how release team works for transitions. > > > >What do you mean more concretely? > > > >That only a smaller elite group should (approve) upload to unstable, > >and everyone else should upload only to experimental, or...? > > For major updates that has reverse dependencies, some one should > approve. It can even be anyone in the team and not just a fixed > smaller group. At least one other person should approve. > > The request should include if they ran autopkgtests and rebuilds of > affected packages and list any failed packages. > > It can even be auto approval in case no one objects in a week's time. > > The more important part is asking before upload, than who gets to > approve. We can document this in js team policy. > > Ruby team already documented it (expectations from people uploading > breaking changes) > https://wiki.debian.org/Teams/Ruby/Packaging#Updating_packages_with_API_breaking_changes
If you simply mean a loose "don't break reverse dependencies!" and write some suggestions down on a wiki page, then I fully agree: That is common for Debian in general. What might be notable about node.js is the likelyhood of complying with semantic versioning, and it might be helpful to emphasize that in this team. If you propose a formal screening process, then I am sceptical both how to practically enforce that and whether it is the right approach. - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private
signature.asc
Description: signature
