Anything still blocking the release? 12 month release cycle sounds good to me. I'm trying to replicate the aforementioned issues, but no luck still.
On Thu, Dec 26, 2013 at 4:49 PM, Noël Köthe <n...@debian.org> wrote: > Hello, > > Am Dienstag, den 24.12.2013, 18:06 +0100 schrieb Giuseppe Scrivano: > > > > 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. > > Sure, but the 3 additional patches are included in 1.14.96-38327. > wget release 1.14 in Debian is carrying the following patches: > http://patch-tracker.debian.org/package/wget/1.14-5 > and the 1.14.96-38327 reduces them by 3: > http://patch-tracker.debian.org/package/wget/1.14.96.38327-2 > They are only documentation patches. I hope I didn't misunderstand your > request again. > > > > 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? > > 12 month would be fine too but I don't have a strong option on this. > > > I don't think that doing it more often would make any sense, given the > > activity that usually wget has. > > ACK. > > -- > Noël Köthe <noel debian.org> > Debian GNU/Linux, www.debian.org > -- Thanking You, Darshit Shah
