[tei-council] Upcoming 2.4.0 release
James Cummings
James.Cummings at it.ox.ac.uk
Thu Jul 4 02:32:56 EDT 2013
On 03/07/13 22:24, Lou Burnard wrote:
> A list of SF tickets (with links) acted on since last release has also
> featured in previous release notes sfaicr
Yes, those have been merged with items from SVN previously, and
if the new SF system allows me to do so I'll have a go at adding
_some_ of them to the release notes today. (The release notes
have never been exhaustive, only pointing to highlights.) And if
we can do so I'll include a link to a list on SF.
-James
>
>
> n 02/07/13 21:19, James Cummings wrote:
>> On 02/07/13 19:43, Lou Burnard wrote:
>>> I usually find that the best way of preparing the release notes is to
>>> edit the subversion log.
>> Yes, and I will go through that, but since the last release was
>> way back in January I thought It might be beneficial to give
>> people a chance to highlight those things they had worked on or
>> felt were important to mention to the community.
>>
>> Trying to open things up...
>>
>> -James
>>
>>>
>>> On 02/07/13 19:41, James Cummings wrote:
>>>> Just a reminder that we should be freezing on the 2.4.0 release
>>>> in subversion in preparation for this Friday, so no more changes
>>>> generally to P5/ or Stylesheets/ folders. If you notice typos,
>>>> email the council list and get at least couple people to agree
>>>> with you that it is release-blocking before making any changes.
>>>>
>>>> However, edits *are* allowed to P5/ReleaseNotes/readme-2.4.0.xml
>>>> to add items you've worked on, or think are important, to the
>>>> release notes for this version.
>>>>
>>>> So far Gabby and Martin have added items for the usage of <app>
>>>> with no <lem>, simplified table of contents, hundreds of typos,
>>>> and the @sex change.
>>>>
>>>> Surely you can think of more! Either edit the file (this file is
>>>> exempt from the repository freeze) or email them to me and I'll
>>>> do so.
>>>>
>>>> -James
>>>>
>>
>
--
Dr James Cummings, James.Cummings at it.ox.ac.uk
Academic IT Services, University of Oxford
More information about the tei-council
mailing list