[tei-council] Release guidelines

[Martin Holmes]

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
>
>
>