htdig-dev

[htdig-dev] Release this code! 3.2 is done!??!

[Neal R. <ne...@ri...>]

Hey all,
 	This think we should just call it a day on version 3.2 and release 
it.  Any objections?

 	Geoff: could you create a release tarball (and maybe create a 
document detailed how you generaly do this)

Steps:
 	1) Create release tarball
 	2) Update WWW site
 	3) Call Bill Gates, Larry Page and Sergey Brin and let them know.

Thanks

-- 
Neal Richter
Knowledgebase Developer
RightNow Technologies, Inc.
Customer Service for Every Web Site
Office: 406-522-1485

Re: [htdig-dev] Release this code! 3.2 is done!??!

[Jim <li...@yg...>]

On Fri, 25 Feb 2005, Neal Richter wrote:

> Hey all,
> 	This think we should just call it a day on version 3.2 and release 
> it.  Any objections?

I think we should at least take a look at the current bug list and see
if there is anything that deserves attention before going to 3.2. I know
that there is at least one major bug in SSL handling. I provided a
possible fix but never received any feedback. I also didn't receive any
response when I asked about getting sufficient access to apply the patch
and perhaps do some other project related housekeeping. Probably just
bad timing; I know everyone is very busy.

I am also aware of an argument parsing bug in the external parser code
that I tracked down when following up on a problem reported on the
htdig-general list. I don't think this one ever made it to the bug list.

In addition we should really follow up on the cross-site scripting
vulnerability that was recently reported for ht://Dig.

   http://securitytracker.com/alerts/2005/Feb/1013078.html

Gentoo, Red Hat, and Debian have already released fixes, and I don't
think it has even been discussed here aside from one message asking
about the vulnerability on htdig-general.

> 	Geoff: could you create a release tarball (and maybe create a 
> document detailed how you generaly do this)

If there is existing documentation describing the process, or someone
with a clue is willing to walk me through it, I would be willing to try
taking over this task for future releases.


Jim

Re: [htdig-dev] Release this code! 3.2 is done!??!

[Geoff H. <ge...@ge...>]

> 	Geoff: could you create a release tarball (and maybe create a 
> document detailed how you generaly do this)

Such a document already exists. It's a little out-of-date (since it's 
back in the days before SourceForge), but it's still pretty much 
correct:

http://htdig.org/dev/checklist.html

I'd also add (before tagging the CVS release)
* Check copyright dates in maindocs/ README, and code to ensure they 
include the current year.

And after adding the tar and diff to the /files directory, you'll also 
need to:
* Add tar and diff to SF.net release manager
* Add NEWS item to SF.net project page

I think that's pretty much complete.

I'd be glad to help anyone going through the process to make sure 
there's accurate, up-to-date documentation of what to do. But I 
*really* think the more people who go through it, the better for the 
project. If I'm the only one who does it and I'm hit by a bus or fall 
off the map tomorrow, we're in trouble. :-)

-Geoff

Re: [htdig-dev] Release this code! 3.2 is done!??!

[Dan L. <da...@la...>]

On 1 Mar 2005 at 13:02, Geoff Hutchison wrote:

> > 	Geoff: could you create a release tarball (and maybe create a 
> > document detailed how you generaly do this)
> 
> Such a document already exists. It's a little out-of-date (since it's 
> back in the days before SourceForge), but it's still pretty much 
> correct:
> 
> http://htdig.org/dev/checklist.html

I can do some of that, mostly test compiling on FreeBSD.  Do I have 
volunteers for other platforms?

From that list, there is a "Pre-Release Checklist" and a "Release 
Checklist".  Has the former been done yet?

If the "Pre-Release Checklist" has not been done, I have no clues 
about LeakTester, checker, purify, gprof.  Anyone?

> I'd also add (before tagging the CVS release)
> * Check copyright dates in maindocs/ README, and code to ensure they 
> include the current year.
> 
> And after adding the tar and diff to the /files directory, you'll also 
> need to:
> * Add tar and diff to SF.net release manager
> * Add NEWS item to SF.net project page
> 
> I think that's pretty much complete.
> 
> I'd be glad to help anyone going through the process to make sure 
> there's accurate, up-to-date documentation of what to do. But I 
> *really* think the more people who go through it, the better for the 
> project. If I'm the only one who does it and I'm hit by a bus or fall 
> off the map tomorrow, we're in trouble. :-)

cheers
-- 
Dan Langille : http://www.langille.org/
BSDCan - The Technical BSD Conference - http://www.bsdcan.org/

Re: [htdig-dev] Release this code! 3.2 is done!??!

[Ted Stresen-R. <ted...@ma...>]

Mac OS X (10.3.8) here... I'll also make a package installer for this 
platform as well.

http://xoops.tedmasterweb.com/modules/mydownloads/viewcat.php?cid=1

Ted Stresen-Reuter
(Yes, I'm still here, still reading, and still trying to support this 
project)

On Mar 8, 2005, at 11:44 AM, Dan Langille wrote:

> On 1 Mar 2005 at 13:02, Geoff Hutchison wrote:
>
>>> 	Geoff: could you create a release tarball (and maybe create a
>>> document detailed how you generaly do this)
>>
>> Such a document already exists. It's a little out-of-date (since it's
>> back in the days before SourceForge), but it's still pretty much
>> correct:
>>
>> http://htdig.org/dev/checklist.html
>
> I can do some of that, mostly test compiling on FreeBSD.  Do I have
> volunteers for other platforms?
>
> From that list, there is a "Pre-Release Checklist" and a "Release
> Checklist".  Has the former been done yet?
>
> If the "Pre-Release Checklist" has not been done, I have no clues
> about LeakTester, checker, purify, gprof.  Anyone?
>
>> I'd also add (before tagging the CVS release)
>> * Check copyright dates in maindocs/ README, and code to ensure they
>> include the current year.
>>
>> And after adding the tar and diff to the /files directory, you'll also
>> need to:
>> * Add tar and diff to SF.net release manager
>> * Add NEWS item to SF.net project page
>>
>> I think that's pretty much complete.
>>
>> I'd be glad to help anyone going through the process to make sure
>> there's accurate, up-to-date documentation of what to do. But I
>> *really* think the more people who go through it, the better for the
>> project. If I'm the only one who does it and I'm hit by a bus or fall
>> off the map tomorrow, we're in trouble. :-)
>
> cheers
> -- 
> Dan Langille : http://www.langille.org/
> BSDCan - The Technical BSD Conference - http://www.bsdcan.org/
>
>
>
> -------------------------------------------------------
> SF email is sponsored by - The IT Product Guide
> Read honest & candid reviews on hundreds of IT Products from real 
> users.
> Discover which products truly live up to the hype. Start reading now.
> http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
> _______________________________________________
> ht://Dig Developer mailing list:
> htd...@li...
> List information (subscribe/unsubscribe, etc.)
> https://lists.sourceforge.net/lists/listinfo/htdig-dev
>

Re: [htdig-dev] Release this code! 3.2 is done!??!

[Dan L. <da...@la...>]

On 9 Mar 2005 at 13:16, Ted Stresen-Reuter wrote:

> Mac OS X (10.3.8) here... I'll also make a package installer for this 
> platform as well.
> 
> http://xoops.tedmasterweb.com/modules/mydownloads/viewcat.php?cid=1
> 
> Ted Stresen-Reuter
> (Yes, I'm still here, still reading, and still trying to support this 
> project)

That's great!

Do we have anyone for Linux... any Linux?


> On Mar 8, 2005, at 11:44 AM, Dan Langille wrote:
> 
> > On 1 Mar 2005 at 13:02, Geoff Hutchison wrote:
> >
> >>> 	Geoff: could you create a release tarball (and maybe create a
> >>> document detailed how you generaly do this)
> >>
> >> Such a document already exists. It's a little out-of-date (since it's
> >> back in the days before SourceForge), but it's still pretty much
> >> correct:
> >>
> >> http://htdig.org/dev/checklist.html
> >
> > I can do some of that, mostly test compiling on FreeBSD.  Do I have
> > volunteers for other platforms?
> >
> > From that list, there is a "Pre-Release Checklist" and a "Release
> > Checklist".  Has the former been done yet?
> >
> > If the "Pre-Release Checklist" has not been done, I have no clues
> > about LeakTester, checker, purify, gprof.  Anyone?
> >
> >> I'd also add (before tagging the CVS release)
> >> * Check copyright dates in maindocs/ README, and code to ensure they
> >> include the current year.
> >>
> >> And after adding the tar and diff to the /files directory, you'll also
> >> need to:
> >> * Add tar and diff to SF.net release manager
> >> * Add NEWS item to SF.net project page
> >>
> >> I think that's pretty much complete.
> >>
> >> I'd be glad to help anyone going through the process to make sure
> >> there's accurate, up-to-date documentation of what to do. But I
> >> *really* think the more people who go through it, the better for the
> >> project. If I'm the only one who does it and I'm hit by a bus or fall
> >> off the map tomorrow, we're in trouble. :-)
> >
> > cheers
> > -- 
> > Dan Langille : http://www.langille.org/
> > BSDCan - The Technical BSD Conference - http://www.bsdcan.org/
> >
> >
> >
> > -------------------------------------------------------
> > SF email is sponsored by - The IT Product Guide
> > Read honest & candid reviews on hundreds of IT Products from real 
> > users.
> > Discover which products truly live up to the hype. Start reading now.
> > http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
> > _______________________________________________
> > ht://Dig Developer mailing list:
> > htd...@li...
> > List information (subscribe/unsubscribe, etc.)
> > https://lists.sourceforge.net/lists/listinfo/htdig-dev
> >
> 
> 
> 
> -------------------------------------------------------
> SF email is sponsored by - The IT Product Guide
> Read honest & candid reviews on hundreds of IT Products from real users.
> Discover which products truly live up to the hype. Start reading now.
> http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
> _______________________________________________
> ht://Dig Developer mailing list:
> htd...@li...
> List information (subscribe/unsubscribe, etc.)
> https://lists.sourceforge.net/lists/listinfo/htdig-dev
> 
> 


-- 
Dan Langille : http://www.langille.org/
BSDCan - The Technical BSD Conference - http://www.bsdcan.org/

Re: [htdig-dev] Release this code! 3.2 is done!??

[Neal R. <ne...@ri...>]

> Do we have anyone for Linux... any Linux?

 I can do the RPMs for RedHat.

 Just Curious:
  Is everyone else getting hit by the flu?  A big chunk of my office was 
in the last few days.

Thanks

-- 
Neal Richter
Knowledgebase Developer
RightNow Technologies, Inc.
Customer Service for Every Web Site
Office: 406-522-1485

Re: [htdig-dev] Release this code! 3.2 is done!??

[Gustave T. Stresen-R. <ted...@ma...>]

So, do we have a final version I can test and package for Mac OS X? If 
so, where do I get it? If not, what can i do to help?

Ted Stresen-Reuter

PS: Curious that I got exactly zero replies to my request for 
comparison between htdig and MS indexing server

On Mar 9, 2005, at 5:33 PM, Neal Richter wrote:

>
>> Do we have anyone for Linux... any Linux?
>
>  I can do the RPMs for RedHat.
>
>  Just Curious:
>   Is everyone else getting hit by the flu?  A big chunk of my office 
> was
> in the last few days.
>
> Thanks
>
> -- 
> Neal Richter
> Knowledgebase Developer
> RightNow Technologies, Inc.
> Customer Service for Every Web Site
> Office: 406-522-1485
>
>
>
>
> -------------------------------------------------------
> SF email is sponsored by - The IT Product Guide
> Read honest & candid reviews on hundreds of IT Products from real 
> users.
> Discover which products truly live up to the hype. Start reading now.
> http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
> _______________________________________________
> ht://Dig Developer mailing list:
> htd...@li...
> List information (subscribe/unsubscribe, etc.)
> https://lists.sourceforge.net/lists/listinfo/htdig-dev
>

Re: [htdig-dev] Release this code! 3.2 is done!??

[Dan L. <da...@la...>]

On 11 Apr 2005 at 18:21, Gustave T. Stresen-Reuter wrote:

> So, do we have a final version I can test and package for Mac OS X? If 
> so, where do I get it? If not, what can i do to help?

Personally, I won't have time to do anything until at least May 15th.
-- 
Dan Langille : http://www.langille.org/
BSDCan - The Technical BSD Conference - http://www.bsdcan.org/
   NEW brochure available at http://www.bsdcan.org/2005/advocacy/

Re: [htdig-dev] Release this code! 3.2 is done!??!

[Geoff H. <ge...@ge...>]

On Mar 8, 2005, at 6:44 AM, Dan Langille wrote:

> If the "Pre-Release Checklist" has not been done, I have no clues
> about LeakTester, checker, purify, gprof.  Anyone?

I can vouch that essentially everything in the pre-release checklist 
has been done. The utilities you mention are used for finding memory 
leaks and generating profiling/performance data.

Yes, I think it'd be helpful to know that some Linux packages would be 
available around the same time as the release.

-Geoff

Re: [htdig-dev] Release this code! 3.2 is done!??!

[Dan L. <da...@la...>]

On 9 Mar 2005 at 11:06, Geoff Hutchison wrote:

> On Mar 8, 2005, at 6:44 AM, Dan Langille wrote:
> 
> > If the "Pre-Release Checklist" has not been done, I have no clues
> > about LeakTester, checker, purify, gprof.  Anyone?
> 
> I can vouch that essentially everything in the pre-release checklist 
> has been done. The utilities you mention are used for finding memory 
> leaks and generating profiling/performance data.

OK, so we can skip the pre-release stage.  That's a huge set of tasks 
gone from the process.

> Yes, I think it'd be helpful to know that some Linux packages would be 
> available around the same time as the release.

What I need (or rather, our clients need) is packages from from their 
vendor (in this case, RedHat).  ;)

cheers
-- 
Dan Langille : http://www.langille.org/
BSDCan - The Technical BSD Conference - http://www.bsdcan.org/