You are viewing a plain text version of this content. The canonical link for it is here.
Posted to batik-dev@xmlgraphics.apache.org by Vincent Hardy <vi...@eng.sun.com> on 2000/11/29 19:34:24 UTC
[code/admin] IMPORTANT : CODE FREEZE TOMOROW
Hello,
Our release being Monday, I propose we freeze everything by tomorow
Noon GMT (i.e., no code fixes in California on Thursday). Then, each
of us can work locally on their pet bugs, but not do any commit.
After the freeze, we need to finish reviewing the web site and the
distribution.
Here is the schedule I propose:
a. Code freeze Thursday noon GMT.
b. Thursday night, PST : Version of the Web site up for review. This
will not yet be publicly available.
c. Friday. Review the web site and distribution. Corrections to the
web site.
d. Sunday or Monday. Links added from xml.apache.org and the mailing
list page to Batik. This is handled oustide the team by Pier, cced
on this email.
The remaining bug fixes or changes I am aware of coming before the
freeze are:
1. [Thierry] Some more error handling code.
2. [Bill] Text selection adjustments: traces removal and modal
selection.
3. [Vincent] Implement primitiveUnits on filter parameters.
Please let the list know if there is any additional change you
expect to commit before tomorow.
Thanks.
V.
Re: [code/admin] IMPORTANT : CODE FREEZE TOMOROW
Posted by Vincent Hardy <vi...@eng.sun.com>.
I am ok with comment only changes. I think we will take a snapshot of
the code base on Friday afternoon, PST.
V.
Bill Haneman wrote:
>
> Hi:
>
> As I have mentioned to Vincent already, I'd like to do a "comments-only"
> commit after the official freeze, maybe tomorrow. The intent is
> to CHANGE NO CODE but only clean up and expand javadoc comments, since I
> have not been as disciplined in some parts of the code as I feel I
> should in this regard. Perhaps others feel the same way, and we can
> "preschedule" time slots for these commits (one commit per site)
> tomorrow.
>
> (I think this should be a "vetoable" suggestion :-)
>
> I agree that even comment changes probably should stop
> before Monday :-)
>
> -Bill
>
> --------------
> Bill Haneman
> +1 353 1 849 0495
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: batik-dev-unsubscribe@xml.apache.org
> For additional commands, e-mail: batik-dev-help@xml.apache.org
Re: [code/admin] IMPORTANT : CODE FREEZE TOMOROW
Posted by Stephane Hillion <St...@sophia.inria.fr>.
Bill Haneman wrote:
> Can we please fix the build complaint about
> class NullOp needing to be in NullOp.java? I know it's
> nitpicking but I hate seeing warnings on a "dot release"
> build.
There are also a lot of javadoc warnings.
--
Stephane.
Re: [code/admin] IMPORTANT : CODE FREEZE TOMOROW
Posted by Vincent Hardy <vi...@eng.sun.com>.
>
> P.S. - Vincent, maybe you can do this as part of your
> last "packaging" pass through the code.
OK. It is on my todo for today.
V.
Re: [code/admin] IMPORTANT : CODE FREEZE TOMOROW
Posted by Bill Haneman <bi...@ireland.sun.com>.
One more little thing:
Can we please fix the build complaint about
class NullOp needing to be in NullOp.java? I know it's
nitpicking but I hate seeing warnings on a "dot release"
build.
I keep thinking someone else is going to do it ;-)
-Bill
P.S. - Vincent, maybe you can do this as part of your
last "packaging" pass through the code.
----------------
Bill Haneman
+1 353 1 849 0495
Re: [code/admin] IMPORTANT : CODE FREEZE TOMOROW
Posted by Bill Haneman <bi...@ireland.sun.com>.
Hi:
As I have mentioned to Vincent already, I'd like to do a "comments-only"
commit after the official freeze, maybe tomorrow. The intent is
to CHANGE NO CODE but only clean up and expand javadoc comments, since I
have not been as disciplined in some parts of the code as I feel I
should in this regard. Perhaps others feel the same way, and we can
"preschedule" time slots for these commits (one commit per site)
tomorrow.
(I think this should be a "vetoable" suggestion :-)
I agree that even comment changes probably should stop
before Monday :-)
-Bill
--------------
Bill Haneman
+1 353 1 849 0495
Re: [code/admin] IMPORTANT : CODE FREEZE TOMOROW
Posted by Stephane Hillion <St...@sophia.inria.fr>.
Vincent Hardy wrote:
> 1. [Thierry] Some more error handling code.
> 2. [Bill] Text selection adjustments: traces removal and modal
> selection.
> 3. [Vincent] Implement primitiveUnits on filter parameters.
>
> Please let the list know if there is any additional change you
> expect to commit before tomorow.
Thomas has implemented enable-background at the GVT level and has tested
it for <g> elements. I will complete the other container bridges.
--
Stephane.
[code/admin] IMPORTANT : CODE FREEZE TOMOROW
Posted by Thomas E Deweese <th...@kodak.com>.
>>>>> "VH" == Vincent Hardy <vi...@eng.sun.com> writes:
VH> Hello, Our release being Monday, I propose we freeze everything by
VH> tomorow Noon GMT (i.e., no code fixes in California on
VH> Thursday).
VH> The remaining bug fixes or changes I am aware of coming before the
VH> freeze are:
VH> 1. [Thierry] Some more error handling code.
VH> 2. [Bill] Text selection adjustments: traces removal and modal
VH> selection.
VH> 3. [Vincent] Implement primitiveUnits on filter parameters.
VH> Please let the list know if there is any additional change you
VH> expect to commit before tomorow.
I'm planning on committing a flushed out implementation of
enable-background (some bugs with coordinate systems, and new with
bounds worked out, as well as a pretty good test case), also Stephane
was going to add enable-background support to the remaining container
elements (right now it's only supported on 'g').
I'm planning on committing as soon as I finish integrating with
the current CVS (still don't have direct CVS access).