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:[EMAIL PROTECTED] ▪ ICQ 26955922 ▪ MSN [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
