Hi, In my personal opinion, for normal (non-Incubating) projects, if you can't get a real release from your dependency (that's the ideal goal, is Jukka pointed out), you have to get at least an SVN tag or a labelled nightly build. There has to be a way to get at the dependency code outside of the dependant package. I would ask the dependency to at least create an SVN tag (e.g. MINA_20061116_QPID_0.1) for this purpose.
For Incubating projects, I'm very hesitant about the above. The reason is that we've been paying a lot of attention to podling releases and validation thereof. If the dependency podling, MINA in this case, has never had an ASF-approved release, we're getting into dicey territory, and I would say, reluctantly, that its binaries shouldn't be included in another project. Yoav On 11/17/06, Paul Fremantle <[EMAIL PROTECTED]> wrote:
Jukka As a general point, there may be a significant delay in getting a release with a given patch in it. For example, the Synapse incubator relies on Axis2. Axis2 is a fairly significant project and they would be unlikely to be willing or able to create a release with a few minor patches outside of their planned release cycle. I would not expect them to either. So while that is one answer, I don't think it will always apply in every case. Paul On 11/17/06, Jukka Zitting <[EMAIL PROTECTED]> wrote: > Hi, > > On 11/17/06, Cliff Schmidt <[EMAIL PROTECTED]> wrote: > > The Qpid community has been debating whether or not they should > > include an unreleased snapshot version of MINA within their upcoming > > Qpid release, and whether they would even be allowed to do so by > > "Apache rules". > > Did you already consider working with the MINA community to have a > proper release as your dependency? I don't think it should be too hard > to do, the main issues being: > > 1) Technical: Is the code good enough for a release? You already think > the code is good. > > 2) Community: Is there a release manager? If no-one in the MINA > community is interested, there's no stopping one of you from > volunteering. > > 3) Oversight: Is the PMC ready to approve the release? This should > really be up to the MINA PMC to decide. > > BR, > > Jukka Zitting > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- Paul Fremantle VP/Technology, WSO2 and OASIS WS-RX TC Co-chair http://bloglines.com/blog/paulfremantle [EMAIL PROTECTED] "Oxygenating the Web Service Platform", www.wso2.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
