[prev in list] [next in list] [prev in thread] [next in thread]
List: inprotect-devel
Subject: Re: [Inprotect-devel] [Inprotect-users] Upgrade svn versions
From: "Rob Notaro" <rnotaro () nframe ! com>
Date: 2008-05-08 14:22:33
Message-ID: 053E179161004E4C91C8613916AA37B903D15684 () nframemail01 ! nframe ! local
[Download RAW message or body]
--===============1254052087==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
boundary="----_=_NextPart_001_01C8B116.F50115D2"
This is a multi-part message in MIME format.
Can I do anything to help?
Sent by Good Messaging (www.good.com)
-----Original Message-----
From: Heath Hendrickson [mailto:heath@mindache.com]
Sent: Thursday, May 08, 2008 10:21 AM Eastern Standard Time
To: Inprotect Users : General questions & announcements
Cc: Inprotect Development
Subject: Re: [Inprotect-users] Upgrade svn versions
The main things that are holding up release of a 1.0.0 (at least from
my perspective) are:
1) Installer script updates (most of this is done, we just need
testers and feedback)
2) Creation of an upgrade script to go from 0.22.5 -> 1.0.0 and
testing of it
3) Additional testing of the latest back-end code (sched2.pl,
nessus_scan2.pl)
We can probably release without #2 and just include a doc to help
users manually upgrade, but #3 is the killer. Without enough testing
of the new back-end code, I'm hesitant to release it as stable.
heath
On May 7, 2008, at 12:43 AM, Rob Notaro wrote:
> Is there a new stable version due out soon?
>
> Sent by Good Messaging (www.good.com)
>
>
> -----Original Message-----
> From: Heath Hendrickson [mailto:heath@mindache.com]
> Sent: Wednesday, May 07, 2008 12:09 AM Eastern Standard Time
> To: Inprotect Users : General questions & announcements
> Subject: Re: [Inprotect-users] Upgrade svn versions
>
> I guess it depends on what version you are starting from. There are
> some schema upgrade files that add the necessary new elements to the
> DB automatically. I recommend backing up the DB before the upgrade,
> just in case.
>
> I don't think we're going to have an automated upgrade until a final
> 1.0.0 release is ready. It's still a sorta moving target, and I'd
> rather focus on the code changes than constantly updating an upgrade
> script, if you know what I mean.
>
> While running the SVN version isn't extremely risky, upgrading isn't
> as straight forward as I'd like either.
>
> What version are you currently running, and I'll let you know what I
> think you need to do to upgrade to the current HEAD.
>
> heath
>
> On Apr 25, 2008, at 3:36 PM, Richard Witt wrote:
>
> > What would be the best process to upgrade the svn versions? Would
> > backing up the database then wiping the current version out and
> > installing a "fresh" version from the current svn then restoring
> > the database work?
> > STATEMENT OF CONFIDENTIALITY: This message and any attachments are
> > intended solely for the person or entity to which it is addressed
> > and may contain confidential or privileged information. If the
> > recipient of this message is not the addressee or a person
> > responsible for delivering the message to the addressee, such
> > recipient is prohibited from reading or using this message in any
> > way. If you have received this message in error, please call the
> > sender of this message immediately and delete the message from any
> > computer.
> >
> >
> ----------------------------------------------------------------------
> > ---
> > This SF.net email is sponsored by the 2008 JavaOne(SM) Conference
> > Don't miss this year's exciting event. There's still time to save
> > $100.
> > Use priority code J8TL2D2.
> > http://ad.doubleclick.net/clk;198757673;13503038;p?http://
> > java.sun.com/javaone_______________________________________________
> > inprotect-users mailing list
> > inprotect-users@lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/inprotect-users
>
>
> ----------------------------------------------------------------------
> ---
> This SF.net email is sponsored by the 2008 JavaOne(SM) Conference
> Don't miss this year's exciting event. There's still time to save
> $100.
> Use priority code J8TL2D2.
> http://ad.doubleclick.net/clk;198757673;13503038;p?http://
> java.sun.com/javaone_______________________________________________
> inprotect-users mailing list
> inprotect-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/inprotect-users
[Attachment #3 (text/html)]
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<TITLE>Re: [Inprotect-users] Upgrade svn versions</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/plain format -->
<P><FONT SIZE=2>Can I do anything to help?<BR>
<BR>
Sent by Good Messaging (www.good.com)<BR>
<BR>
<BR>
-----Original Message-----<BR>
From: Heath Hendrickson [<A \
HREF="mailto:heath@mindache.com">mailto:heath@mindache.com</A>]<BR> Sent: \
Thursday, May 08, 2008 10:21 AM Eastern Standard Time<BR> To: \
Inprotect Users : General questions & announcements<BR> \
Cc: Inprotect Development<BR> \
Subject: Re: [Inprotect-users] Upgrade svn \
versions<BR> <BR>
The main things that are holding up release of a 1.0.0 (at least from <BR>
my perspective) are:<BR>
<BR>
1) Installer script updates (most of this is done, we just need <BR>
testers and feedback)<BR>
2) Creation of an upgrade script to go from 0.22.5 -> 1.0.0 and <BR>
testing of it<BR>
3) Additional testing of the latest back-end code (sched2.pl, <BR>
nessus_scan2.pl)<BR>
<BR>
We can probably release without #2 and just include a doc to help <BR>
users manually upgrade, but #3 is the killer. Without enough testing <BR>
of the new back-end code, I'm hesitant to release it as stable.<BR>
<BR>
heath<BR>
<BR>
On May 7, 2008, at 12:43 AM, Rob Notaro wrote:<BR>
<BR>
> Is there a new stable version due out soon?<BR>
><BR>
> Sent by Good Messaging (www.good.com)<BR>
><BR>
><BR>
> -----Original Message-----<BR>
> From: Heath Hendrickson [<A \
HREF="mailto:heath@mindache.com">mailto:heath@mindache.com</A>]<BR> > \
Sent: Wednesday, May 07, 2008 12:09 AM Eastern Standard Time<BR> > \
To: Inprotect Users : General questions & \
announcements<BR> > Subject: Re: \
[Inprotect-users] Upgrade svn versions<BR> ><BR>
> I guess it depends on what version you are starting from. There are<BR>
> some schema upgrade files that add the necessary new elements to the<BR>
> DB automatically. I recommend backing up the DB before the upgrade,<BR>
> just in case.<BR>
><BR>
> I don't think we're going to have an automated upgrade until a final<BR>
> 1.0.0 release is ready. It's still a sorta moving target, and I'd<BR>
> rather focus on the code changes than constantly updating an upgrade<BR>
> script, if you know what I mean.<BR>
><BR>
> While running the SVN version isn't extremely risky, upgrading isn't<BR>
> as straight forward as I'd like either.<BR>
><BR>
> What version are you currently running, and I'll let you know what I<BR>
> think you need to do to upgrade to the current HEAD.<BR>
><BR>
> heath<BR>
><BR>
> On Apr 25, 2008, at 3:36 PM, Richard Witt wrote:<BR>
><BR>
> > What would be the best process to upgrade the svn versions? Would<BR>
> > backing up the database then wiping the current version out and<BR>
> > installing a "fresh" version from the current svn then \
restoring<BR> > > the database work?<BR>
> > STATEMENT OF CONFIDENTIALITY: This message and any attachments are<BR>
> > intended solely for the person or entity to which it is addressed<BR>
> > and may contain confidential or privileged information. If the<BR>
> > recipient of this message is not the addressee or a person<BR>
> > responsible for delivering the message to the addressee, such<BR>
> > recipient is prohibited from reading or using this message in any<BR>
> > way. If you have received this message in error, please call the<BR>
> > sender of this message immediately and delete the message from any<BR>
> > computer.<BR>
> ><BR>
> > <BR>
> ----------------------------------------------------------------------<BR>
> > ---<BR>
> > This SF.net email is sponsored by the 2008 JavaOne(SM) Conference<BR>
> > Don't miss this year's exciting event. There's still time to save<BR>
> > $100.<BR>
> > Use priority code J8TL2D2.<BR>
> > <A HREF="http://ad.doubleclick.net/clk;198757673;13503038;p?http://">http://ad.doubleclick.net/clk;198757673;13503038;p?http://</A><BR>
> > java.sun.com/javaone_______________________________________________<BR>
> > inprotect-users mailing list<BR>
> > inprotect-users@lists.sourceforge.net<BR>
> > <A HREF="https://lists.sourceforge.net/lists/listinfo/inprotect-users">https://lists.sourceforge.net/lists/listinfo/inprotect-users</A><BR>
><BR>
><BR>
> ----------------------------------------------------------------------<BR>
> ---<BR>
> This SF.net email is sponsored by the 2008 JavaOne(SM) Conference<BR>
> Don't miss this year's exciting event. There's still time to save <BR>
> $100.<BR>
> Use priority code J8TL2D2.<BR>
> <A HREF="http://ad.doubleclick.net/clk;198757673;13503038;p?http://">http://ad.doubleclick.net/clk;198757673;13503038;p?http://</A><BR>
> java.sun.com/javaone_______________________________________________<BR>
> inprotect-users mailing list<BR>
> inprotect-users@lists.sourceforge.net<BR>
> <A HREF="https://lists.sourceforge.net/lists/listinfo/inprotect-users">https://lists.sourceforge.net/lists/listinfo/inprotect-users</A><BR>
<BR>
</FONT>
</P>
</BODY>
</HTML>
[Attachment #4 (--===============1254052087==)]
-------------------------------------------------------------------------
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference
Don't miss this year's exciting event. There's still time to save $100.
Use priority code J8TL2D2.
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
_______________________________________________
inprotect-devel mailing list
inprotect-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/inprotect-devel
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic