[tei-council] Release guidelines

[Martin Holmes]

Hi Peter,

Ah, I see what you mean -- that is bad. We need to add a step to the 
release process which corrects the schema pointer to point to the one in 
the release package itself. I would definitely want to keep the 
lastSuccessfulBuild pointer in trunk, though; since it's now quite 
complicated to build the Guidelines yourself, it's important that people 
working on the code can validate against the latest version of the schema.

Cheers,
Martin

On 13-12-06 06:15 AM, Peter Stadler wrote:
> Hi Martin,
>
> sorry for skipping some relevant parts:
> The XML files within [1] include <?xml-model href="http://tei.oucs.ox.ac.uk/jenkins/job/TEIP5/lastSuccessfulBuild/artifact/release/xml/tei/odd/p5.nvdl“ …
>
> So, the current release process simply tags those files with the release number and zips them for convenient download. Hence, within [2] (and the bundled release!) you’ll find these references and all these files don’t validate anymore due to the changes in the meantime.
>
> Anyway, I think it’s a very good idea to freeze the repo and not continue work in any branch (if possible) during release preparations. I’m not proposing a branching philosophy à la gitflow, but simply
>
> 1. copy trunk to branches/release (and freeze trunk)
> 2. modify necessary stuff for the release in the release branch
> 3. create tags/release-x.x.x and the zip archive from the release branch
> 4. release the lock on trunk and delete branches/release
>
> Regrettably I do not have any experience with Jenkins and can’t tell how to tell Jenkins to build from branches/release rather than trunk
>
> Best
> Peter
>
> [1] https://sourceforge.net/p/tei/code/HEAD/tree/trunk/P5/Source/Specs/
> [2] https://sourceforge.net/p/tei/code/HEAD/tree/tags/P5_release_2.5.0/Source/Specs/
>
> Am 06.12.2013 um 14:48 schrieb Martin Holmes <mholmes at UVIC.CA>:
>
>> HI Peter,
>>
>> I'm not sure I understand this bit:
>>
>>> the
>>> schema reference in the tagged release specs pointing at
>>> „lastSuccessfulBuild“. This makes all the current 2.5.0 specs invalid
>>
>> Could you say where you're seeing the pointer to lastSuccessfulBuild?
>>
>> Like James, I don't see any advantage at the moment in creating a branch
>> prior to release, but I'm happy to be convinced. I presume you're
>> imagining situations such as the work which will considerably modify
>> chapter 10, but which isn't intended for the 2.6 release; we could be
>> working on that in trunk right now, rather than holding off till after
>> the release. However, that's not very common, and we could actually work
>> on the chapter changes in a branch, and merge them back into trunk.
>>
>> Cheers,
>> Martin
>>
>>
>>
>> On 13-12-06 01:03 AM, Peter Stadler wrote:
>>> Dear all,
>>>
>>> if I understand
>>> http://www.tei-c.org/Activities/Council/Working/tcw22.xml correctly,
>>> all the work for creating a release is done in trunk. I know, never
>>> touch a running system, but wouldn’t it be more elegant to have a
>>> separate release branch? E.g., one thing I find annoying is the
>>> schema reference in the tagged release specs pointing at
>>> „lastSuccessfulBuild“. This makes all the current 2.5.0 specs invalid
>>> … With a release branch one could modify this reference to point at
>>> the respective release schema while not tainting trunk.
>>>
>>> Well, I guess this proposal has come up before and there are good
>>> reasons not to do it.
>>>
>>> Best Peter
>>>
>>> PS: Enough for now, I’ll be off for some hours but looking forward to
>>> any replies
>>>
>>>
>>>
>> --
>> tei-council mailing list
>> tei-council at lists.village.Virginia.EDU
>> http://lists.village.Virginia.EDU/mailman/listinfo/tei-council
>>
>> PLEASE NOTE: postings to this list are publicly archived
>
>
>

-- 
Martin Holmes
University of Victoria Humanities Computing and Media Centre
(mholmes at uvic.ca)