Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [] OCL End User SDK feature

Hi Adolfo

I think that is what we originally planned, but some timestamping issue got in the way. But if it now works great.

To minimize disruption I guess we contribute:

+1 Core (final contribution)
+1 Tools (preliminary contribution based on I-builds of other +1/+2/+3 projects)
+3 Tools (final contribution)



On 03/04/2012 16:03, Adolfo Sánchez-Barbudo Herrera wrote:
Hello team,

During the last M6 build I realized about a potential problem concerning our release train contribution, which could impact to downstream project .

As you know we have to separate builds which are expected to contribute Eclipse OCL project artifacts at different time frames. Currently:

At +1, the Core SDK and its included  features are built and published in our milestones repository
At +3, the remaining features (including OCL End User SDK and Examples) are built and published in our milestones repository.

On the other hand, the features which we contribute to the release train are "OCL End User SDK" and "Examples". This means that we are not really contributing any content to the release train until +3... which could be very dangerous.

Our releng infrastructure makes sense and all should be fine as long as our downstream projects use our milestones repository to do their milestones builds. However, there do exist a potential problem since they could be using a different repository, i.e the release train staging one, to do the their builds, so that they may be making a contribution, let's say at +2, which could be broken when we do our +3 contribution.

So in order to avoid future problems with our downstream projects and giving that the OCL End User SDK doesn't have any dependency on a +2 project I suggest moving such a feature back to our Core (+1) build.

Comments ?

Best regards,
Open Canarias, S.L.
Adolfo Sánchez-Barbudo Herrera
C/Elías Ramos González, 4, ofc. 304
Tel.: +34 922 240231

_______________________________________________ mailing list

No virus found in this message.
Checked by AVG -
Version: 2012.0.1913 / Virus Database: 2114/4910 - Release Date: 04/02/12

Back to the top