On 27.01.2007 09:15:00 Cameron McCormack wrote: > 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.)
Yep, we just have to make sure we don't forget about it. > > 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? 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. Jeremias Maerki --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
