Skip Menu | Logged in as guest | Logout
 
Ticket metadata
Id: 5247
Status: resolved
Priority: -3/0
Queue: vdt-support

Fixed in: 1.10.1w
Fix scheduled: CUR

Owner: Scot Kronenfeld
Requestors: burt@fnal.gov
Cc:
AdminCc:

More about burt@fnal.gov
Comments about this user:
No comment entered about this user
This user's 10 highest priority tickets:
Groups this user belongs to:
  • Everyone

New reminder:

Created: Fri May 01 13:49:05 2009
Starts: Not set
Started: Not set
Last Contact: Mon Jun 01 11:23:19 2009
Due: Not set
Closed: Mon Jun 01 11:23:32 2009
Updated: Mon Jun 01 11:23:33 2009 by kronenfe



History Brief headersFull headers
Subject: GIP 1.1.1 released
Date: Fri, 01 May 2009 13:48:14 -0500
To: vdt-support@OPENSCIENCEGRID.ORG, OSG GIP <osg-gip@OPENSCIENCEGRID.ORG>
From: Burt Holzman <burt@fnal.gov>
Download (untitled) / with headers
text/plain 401b
Hi Scot and VDT friends,

Based on feedback from the OSG 1.0.1 release, we have a new bugfix GIP
release, located in the usual place:

http://home.fnal.gov/~burt/gip_1_1_1.tgz

== 1.1.1 ==
* allow old-style storage config again (GIP stanza)
* BeStMan: correctly determine SE space when no space tokens exist
* BeStMan: improved logging
* Parse updated srm-ping output
* Fix crashing LSF provider

- B
Download smime.p7s
application/x-pkcs7-signature 3.8k
CC: vdt-support@OPENSCIENCEGRID.ORG, OSG GIP <osg-gip@OPENSCIENCEGRID.ORG>
Subject: Re: GIP 1.1.1 released
Date: Fri, 01 May 2009 13:48:51 -0500
To: Burt Holzman <burt@fnal.gov>
From: Burt Holzman <burt@fnal.gov>
Download (untitled) / with headers
text/plain 282b
Burt Holzman wrote:
> Hi Scot and VDT friends,
>
> Based on feedback from the OSG 1.0.1 release, we have a new bugfix GIP
> release, located in the usual place:
>
> http://home.fnal.gov/~burt/gip_1_1_1.tgz

Sorry, that URL should be:

http://home.fnal.gov/~burt/gip/gip_1_1_1.tgz
Download smime.p7s
application/x-pkcs7-signature 3.8k
Subject: [vdt-support #5247] SVN commit, rev 9123
To: vdt-support@cs.wisc.edu
From: kronenfe@cs.wisc.edu
Download (untitled) / with headers
text/plain 163b
Commit comment:
Updated GIP from 1.1.0 to 1.1.1


Changed files:
U vdt/branches/vdt-1.10.1/defs

To generate a diff:
svn diff -c 9123 file:///p/vdt/workspace/svn
Download (untitled) / with headers
text/plain 118b
Hi Burt,
This will go into our next VDT 1.10.1 lettered update, which we expect
to release in 1-2 weeks.

Thanks,
scot
Subject: Re: [vdt-support #5247] GIP 1.1.1 released
Date: Wed, 06 May 2009 11:39:20 -0500
To: vdt-support@OPENSCIENCEGRID.ORG
From: Burt Holzman <burt@fnal.gov>
Download (untitled) / with headers
text/plain 269b
Scot Kronenfeld via RT wrote:
> Hi Burt,
> This will go into our next VDT 1.10.1 lettered update, which we expect
> to release in 1-2 weeks.

Great. Especially because I just got at least one important 1.1.1
bugfix, so I'll send you a 1.1.2 before that release.

- B
Download smime.p7s
application/x-pkcs7-signature 3.8k
Download (untitled) / with headers
text/plain 466b
Hi Burt,
We plan to release VDT 2.0.0 this Thursday. Currently this contains GIP
1.1.1. You mentioned that you had an important bug fix and will release
1.1.2 soon. Will it be ready by Wednesday? If not, is it safe to
release GIP 1.1.1 as part of VDT 2.0.0?


Note: VDT 2.0.0 is independent of the next VDT 1.10.1 lettered update
that was previously mentioned in this ticket. That is still
forthcoming, but we're concentrating our efforts on the 2.0.0 release.
Subject: Re: [vdt-support #5247] GIP 1.1.1 released
Date: Mon, 18 May 2009 17:26:40 -0400
To: vdt-support@OPENSCIENCEGRID.ORG
From: burt <burt@fnal.gov>
Download (untitled) / with headers
text/plain 402b
Scot Kronenfeld via RT wrote:
> Hi Burt,
> We plan to release VDT 2.0.0 this Thursday. Currently this contains GIP
> 1.1.1. You mentioned that you had an important bug fix and will release
> 1.1.2 soon. Will it be ready by Wednesday? If not, is it safe to
> release GIP 1.1.1 as part of VDT 2.0.0?

Hey Scot,

I'm on vacation and won't be back at work until Thursday. Can we delay
by a day?

- B
Subject: Re: [vdt-support #5247] GIP 1.1.1 released
Date: Mon, 18 May 2009 16:39:42 -0500
To: vdt-support@OPENSCIENCEGRID.ORG
From: Alain Roy <roy@cs.wisc.edu>
Download (untitled) / with headers
text/plain 722b
On May 18, 2009, at 4:28 PM, burt@fnal.gov via RT wrote:
> Scot Kronenfeld via RT wrote:
>> Hi Burt,
>> We plan to release VDT 2.0.0 this Thursday. Currently this
>> contains GIP
>> 1.1.1. You mentioned that you had an important bug fix and will
>> release
>> 1.1.2 soon. Will it be ready by Wednesday? If not, is it safe to
>> release GIP 1.1.1 as part of VDT 2.0.0?
>
> Hey Scot,
>
> I'm on vacation and won't be back at work until Thursday. Can we
> delay
> by a day?

We won't delay the VDT 2.0.0 release for you, sorry. But we will
gladly update the GIP after the release.

It's going to go through a long VTB and ITB process, so there will be
time for us to get any needed bug fixes released.

-alain
Subject: Re: [vdt-support #5247] GIP 1.1.1 released
Date: Mon, 18 May 2009 17:59:19 -0400
To: vdt-support@OPENSCIENCEGRID.ORG
From: burt <burt@fnal.gov>
Download (untitled) / with headers
text/plain 817b
Alain Roy via RT wrote:
> On May 18, 2009, at 4:28 PM, burt@fnal.gov via RT wrote:
>> Scot Kronenfeld via RT wrote:
>>> Hi Burt,
>>> We plan to release VDT 2.0.0 this Thursday. Currently this
>>> contains GIP
>>> 1.1.1. You mentioned that you had an important bug fix and will
>>> release
>>> 1.1.2 soon. Will it be ready by Wednesday? If not, is it safe to
>>> release GIP 1.1.1 as part of VDT 2.0.0?
>> Hey Scot,
>>
>> I'm on vacation and won't be back at work until Thursday. Can we
>> delay
>> by a day?
>
> We won't delay the VDT 2.0.0 release for you, sorry. But we will
> gladly update the GIP after the release.
>
> It's going to go through a long VTB and ITB process, so there will be
> time for us to get any needed bug fixes released.

We'll get it to you when we get it to you then.

- B
Download (untitled) / with headers
text/plain 151b
Hello Burt,
GIP 1.1.1 was released today in VDT 1.10.1w.

Let us know whenever the next release with the aforementioned bug fix is
ready.

Thanks,
scot