Re: Ready for release?

Hi All,

thomas.deweesekodak.com wrote on 01/22/2007 07:35:15
PM:

>    There are a few I'd like to try and tackle, I'm
working on a list
> (most are ones with patches already in bugzilla).

   Here is my list, I'm applying them locally (any opinions
on 41216).

        40681 - Patch already provided (thanks to Archie).
        41205 - Patch already provided (thanks to Herve).
        41216 - Patch is available, (thanks to Trejkaz) I
don't think 
              we have a CLA but the patch is basically just
adding 
              all the other charsets.
        41234 - We should try and make sure the resource
files
                  for errors can be found (this has popped
up in a few 
places). 
              The simple fix may be to just replicating the

              Messages.properties to the new directory. I
actually 
              think our whole messaging system needs some
work.


------------------------------------------------------------
---------
To unsubscribe, e-mail: batik-dev-unsubscribexmlgraphics.apache.org
For additional commands, e-mail: batik-dev-helpxmlgraphics.apache.org

Thomas DeWeese:
>    Here is my list, I'm applying them locally (any
opinions
> on 41216).
> 
>         40681 - Patch already provided (thanks to
Archie).
>         41205 - Patch already provided (thanks to
Herve).

I didn’t review the patches, but if you’re happy with
them that’s fine.

>         41216 - Patch is available, (thanks to Trejkaz)
I don't think 
>               we have a CLA but the patch is basically
just adding 
>               all the other charsets.

Yeah I’m a bit worried the patch is too large to accept
without a CLA.
Did you contact Trejkaz about it?

>         41234 - We should try and make sure the
resource files
>                   for errors can be found (this has
popped up in a few 
> places). 
>               The simple fix may be to just replicating
the 
>               Messages.properties to the new directory.
I actually 
>               think our whole messaging system needs
some work.

I’m happy with that as a stop-gap solution.  (I guess
Jeremias could do
that too for FOP’s related problem, before a proper
solution is made.)


So after these changes, I guess we’re done, and a release
candidate can
be made.  I’ll collate the bugs in Bugzilla that have been
closed since
the 1.6 release so that they can be included in the README
file in the
distribution directory.

I read through some messages before 1.6’s release, and
noted that even
a RC must go through the formal process of getting a vote
from the PMC.
That’d be the next step then?

-- 
Cameron McCormack, http://mcc.id.au/
	xmpp:heycamjabber.org  ▪  ICQ 26955922  ▪  MSN cammcc.id.au

------------------------------------------------------------
---------
To unsubscribe, e-mail: batik-dev-unsubscribexmlgraphics.apache.org
For additional commands, e-mail: batik-dev-helpxmlgraphics.apache.org

Hello,
Any chance you also want to apply this one : 35515 ?
(Problem with 
converting WMF files to SVG Documents). This problem is not
specific to 
WMF Files transcoding, and will happen any time
SVGGraphics2D is used. I 
already provided a patch, and I can / will add soon (today
or tomorrow) 
some code to test it.

But I agree that this is not a big problem...

Herve

thomas.deweesekodak.com wrote:
> Hi All,
>
> thomas.deweesekodak.com wrote on 01/22/2007 07:35:15
PM:
>
>   
>>    There are a few I'd like to try and tackle, I'm
working on a list
>> (most are ones with patches already in bugzilla).
>>     
>
>    Here is my list, I'm applying them locally (any
opinions
> on 41216).
>
>         40681 - Patch already provided (thanks to
Archie).
>         41205 - Patch already provided (thanks to
Herve).
>         41216 - Patch is available, (thanks to Trejkaz)
I don't think 
>               we have a CLA but the patch is basically
just adding 
>               all the other charsets.
>         41234 - We should try and make sure the
resource files
>                   for errors can be found (this has
popped up in a few 
> places). 
>               The simple fix may be to just replicating
the 
>               Messages.properties to the new directory.
I actually 
>               think our whole messaging system needs
some work.
>
>
>
------------------------------------------------------------
---------
> To unsubscribe, e-mail: batik-dev-unsubscribexmlgraphics.apache.org
> For additional commands, e-mail: batik-dev-helpxmlgraphics.apache.org
>
>  
>
>
>   

------------------------------------------------------------
---------
To unsubscribe, e-mail: batik-dev-unsubscribexmlgraphics.apache.org
For additional commands, e-mail: batik-dev-helpxmlgraphics.apache.org

Cameron McCormack:
> > I read through some messages before 1.6’s
release, and noted that even
> > a RC must go through the formal process of getting
a vote from the PMC.
> > That’d be the next step then?

Jeremias Maerki:
> As long as you call it RC, don't make it known beyond
batik-dev and
> don't distribute it through the standard mirrors, no.
See:
> http://www.apache.org/dev/release.html#release-typeso
> 
> If you target a wider audience, then yes. In that case,
build the
> release files and put them on your
~/public_html/<something> (-->
> people.apache.org/~<uid>/<something>) and
then start a vote (on general,
> cc batik-dev) referencing the files, ideally with MD5s.
When the vote
> passes the artifacts are pushed into the distribution
space.

Hmm, I guess I would like something in between these.  I
don’t really
want to keep the RC in the distribution archive, since
it’s really just
a temporary thing.  But I do want to have it tested by the
wider SVG
community.  Any way this could happen?  Or should I just
accept that an
RC is just like any other release? 

-- 
Cameron McCormack, http://mcc.id.au/
	xmpp:heycamjabber.org  ▪  ICQ 26955922  ▪  MSN cammcc.id.au

------------------------------------------------------------
---------
To unsubscribe, e-mail: batik-dev-unsubscribexmlgraphics.apache.org
For additional commands, e-mail: batik-dev-helpxmlgraphics.apache.org