Noël Köthe <[email protected]> writes: > I could drop 3 documentation patches. > The Debian bugtracker does not have additional patches. > I don't track which wget upstream patch fixed which Debian bug if this > is your request.
would you mind to send the patches to the ML, either by git send-email or attaching the output git format-patch? It helps to get more eyes on them. Get these patches upstream will make things easier for you as well, you will have less stuff to rebase when a new version is out. >> > If anything needs fixing, I'd like to help and ensure a new release >> > ASAP. > > Maybe going through https://savannah.gnu.org/bugs/?group=wget in some > spare time and comment, tag, close some bugs.:) e.g. bug #36580 just > need a person with the right savannah account/permissions (nok does not > have;)). > >> I've delayed it since there were some new bug reports and I had no time >> to go trough all of them. From a first check, it seems there is nothing >> blocking a release, so I will probably do that in the next few days. >> >> Is there something we should absolutely consider for inclusion before we >> make a new release? > > Maybe only a small documentation fix but its minor. > https://savannah.gnu.org/bugs/index.php?33826 > > As a friend of release early and release often: > Go for it;) and the wget user will get a lot of fixes from the 16 month > of development. we definitely need a better model than "let's release when we think it is ok" :-) Should we move to a release every 3/6 months? I don't think that doing it more often would make any sense, given the activity that usually wget has. Cheers, Giuseppe
