Thanks Daniel – these will
be included as part of the 1.0.1 release. Can you do me a favor and create
Bugzilla tickets for each of the below items and we can formally process them
as being fixed as part of 1.0.1?
Regards…Brian
From:
higgins-dev-bounces@xxxxxxxxxxx [mailto:higgins-dev-bounces@xxxxxxxxxxx] On
Behalf Of Daniel Sanders
Sent: Friday, March 21, 2008 6:15 PM
To: Higgins (Trust Framework) Project developer discussions
Subject: Re: [higgins-dev] Higgins Release 1.0.1 Updates and Actions
I
have checked in several bug fixes to the B-1-0-0 branch that did not have
bugzilla defect numbers. At the time I was just told to go ahead and
check them in. They fixes were for the following defects:
1.
STS was not encrypting tokens when there was an AppliesTo element in the RST.
2.
The XML File IdAS Context Provider was crashing if someone deleted the file
after it had opened the context. It should have been detecting that the
file was deleted and then re-initializing it.
3.
The XML File IdAS Context Provider was not making sure that updates made using
an IContext in one thread were visible to IContext objects in other threads.
Will
the fact that they were checked into the B-1-0-0 branch cause them to be taken
for the 1.0.1 bug fix release?
>>> Brian Walker <BWalker@xxxxxxxxxxxxx> 3/21/2008 12:15 PM
>>>
All - as discussed on Thursday's call , we are planning to
issue a Higgins 1.0.1 bug fix release on 28-Mar-08. Wanted to provide some
advance notice and planning leading up to this release. Below are some status
and actions of note in preparation of this bug fix release:
1.
Status:
a. Per
the outline on the wiki (here)
we are going to label this as T1-0-1 and it will be a tagged version on the
R1-0-0 branch.
b. We
currently have 16 candidate bugs targeted for this release. Please see the
location here
for the detail list.
c. We
will send out an email in advance of when we are actually going to do the
T1-0-1 build - but for planning purposes, I would propose we plan on having any
bugs submitted by Thur 27-Feb end-of-business Pacific Time zone. This will give
us time on Friday to tag the build as T1-0-1.
2.
Actions - we need the following actions to support this
bug release:
a. Review
and update the list of candidate bugs for this bug fix release. Would like to
have this list finalized in terms of what we are going to commit to by end of
business Tue 25-Mar. If you feel it will not be fixed - just let me know and we
will move it to another scheduled release. Based on the current list,
the following people need to review and update the tickets as to their commit
status for 1.0.1:
i.
Mike M. - 214048, 218044, 218045, 219638
ii.
Valery - 216743, 223063, 223441, 223442, 223443, 223444
iii.
Paul - 218923
iv.
Tom D. - 223260
v.
Tie L - 223367, 223369
vi.
Mary - 223368
b. Peter
K - will send out an email to Higgins Dev to alert them before he plans to do
the 28-Mar-08 T1-0-1 tag build.
Please let me know if we overlooked anything with this
release plan.
Regards.Brian
Brian J. Walker
=brian.walker
VP of Engineering
Parity Communications
cell: 781-801-0254