Hey Jeremy, I didn't intend to imply anything. If it felt that way then I apologise, my comment was a genuine attempt to try to be understanding when there are other issues more pressing than disseminating your knowlege. Thanks for the IRC chat by the way. I really am just trying to do the right thing in a busy time.
Best Regards, Kelvin. On 04/10/06, Jeremy Boynes <[EMAIL PROTECTED]> wrote:
Kelvin I'm confused - I've tried in this thread to explain /what/ we were voting on and why we needed to release these dependencies first as background for an informed decision. Obviously I've failed. In light of that, do you have any specific questions that could be answered? -- Jeremy PS I feel it's unfair to imply that I "don't feel in a position to share your expertise right now" - I responded with this thread, I've asked on IRC if anyone had any questions, and I've offered to reply to specific questions here. What more do you want? On Oct 4, 2006, at 11:45 AM, kelvin goodson wrote: > Hi Jeremy, > > My question on the VOTE thread was not /why/ we are voting, but > rather > would it be possible to help me equip myself to be in a position to > vote. I > was aking for some help to understand the content of what we are > voting on. > It seems the vote currently has the 3 +1s necessary, and no -1s to > carry > it. I still don't feel in a position to cast an informed critical > eye over > the content, so at the moment I must abstain. It's a busy time, so I > understand if you don't feel in a position to share your expertise > right > now, but if that's the case then perhaps you would be prepared to > contribute a section to the release guidelines. > > Best Regards, Kelvin. > > On 04/10/06, Jeremy Boynes <[EMAIL PROTECTED]> wrote: >> >> Kelvin asked about why we should vote on the parent pom artifacts and >> buildtools separately rather than have a single vote for all >> artifacts. It is due to the modular nature of our build and the >> dependencies between the different distributions that we were looking >> to produce. It's kind of like Axis2 where doing a release means they >> need to coordinate releases of several other WS projects such as >> axiom, neethi, XmlSchema, etc. and have stable versions of those >> available before doing their own release. >> >> In our development, we typically build from the root, covering all >> sub-projects in Tuscany. In doing so we treat all of Tuscany as one >> big codebase that gets built together. This includes not just the >> main sub-projects but also other minor projects that support those >> main sub-projects - specifically maven POMs and plugin that they >> depend on, and also the buildtools project that is used to configure >> the sourcecheck profile in the build. >> >> We are producing separate source distributions for sdo, das, sca and >> we want a user to be able to build any one of those independently. >> The build of any one of those depends on the parent pom (which is the >> parent of the sub-project's pom) and the buildtools module. To have a >> stable build for those projects, we must have a stable version of the >> dependency just like we need to have a stable version of dependent >> projects (e.g. wanting a stable version of EMF for SDO rather than a >> SNAPSHOT). >> >> We don't need a separate distro for those artifacts as that isn't >> actually useful. What need is to have a version of the dependency >> available from a release Maven repo so that Maven can resolve/ >> download the artifact during the build. In our case that is the m2- >> incubating-repository where they were published. >> >> I have been publishing versions of these to the SNAPSHOT repo to >> allow the unstable sub-project builds to run. That's not considered >> releasing and does not require a vote. However, in prep for the >> actual release of sdo etc. we want to publish a stable release and >> that requires a vote just like we would vote on a distro going into >> the mirror system. >> >> -- >> Jeremy >> >> >> --------------------------------------------------------------------- >> 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]
