[Building Sakai] 2.9: How to cut a custom release

[David Horwitz]

Hi Steve,


On 11/17/2012 11:11 AM, Steve Swinsburg wrote:
> Hi David,
>
> Could you just get your local Samigo to not inherit from master,
So in effect recreate pure-pom (or at least one of them)?

>   and just roll whatever it needs from master into the samigo pom?
Tried that it seems the inherited distribution management overides any 
local DM or defined versions


D
> cheers,
> Steve
>
>
> On 17/11/2012, at 6:51 PM, David Horwitz <david.horwitz at uct.ac.za> wrote:
>
>> Hi All,
>>
>> Here is the case we run a custom msub branch of Samigo - effectively we
>> msub a later version (in 2.8 we ran sam 2.9 and in 2.9 it will likely be
>> based on 2.10) that include new features we're contributing back. We
>> reversion this (2.10.0-UCT) and cut regular releases from our jenkins
>> build. The reversioning and cutting stable releases are required parts
>> of our deployment in order to ensure that the correct code is deployed
>> and to track changes etc.
>>
>>
>> OK now in 2.9 we have to inherit from master - this causes problems
>> because the released master defines versions for samigo api jars that
>> are incorrect causing the build to fail. I can see no reliable way round
>> this other than having a UCT release of master for every Samigo build (a
>> master that would only be used for release purposes) am I missing
>> something here?
>>
>> D
>> _______________________________________________
>> sakai-dev mailing list
>> sakai-dev at collab.sakaiproject.org
>> http://collab.sakaiproject.org/mailman/listinfo/sakai-dev
>>
>> TO UNSUBSCRIBE: send email to sakai-dev-unsubscribe at collab.sakaiproject.org with a subject of "unsubscribe"
>