On Tue, Dec 24, 2013 at 10:36 PM, Giuseppe Scrivano gscriv...@gnu.orgwrote:
Noël Köthe n...@debian.org 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.
I tried going through the Debian bugtracker just now. Didn't see any
patches available
which haven't already been applied. However there are a couple of bug
reports on it
that we must look into. I'll try and reproduce them if possible.
Specifically, I'm
looking at bug reports #701032 and #709637.
@nok: It would be very nice of you if you could report these as bugs in the
upstream
bug tracker. I know they're both marked as non-reproducible in your system.
While
I'll attempt to reproduce #701032, there seems to be a definite bug in wget
based on
the extensive logs provided in #709637.
@Giuseppe: It's upto you to decide if #709637 should be a blocking bug. The
logs do
seem to show an error on Wget's part, but I haven't had a chance to create
an isolated
test case for it yet. With all the headers available, it shouldn't be too
great an issue.
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 don't have editing permissions on Savannah either. Giuseppe would have to
do that.
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
It's a documentation change that does look good.
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 :-)
+1
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.
I think we should have a 6 month release cycle. With 5 months open for
submission of new features / patches, while the last month is only a
alpha/beta
testing phase.
--
Thanking You,
Darshit Shah
