[dev] [cvs] commit: horde/docs RELEASE_NOTES

[Jan Schneider]

Zitat von Michael M Slusarz <slusarz at horde.org>:

> Quoting Michael Rubinsky <mrubinsk at horde.org>:
>
>> Quoting Michael M Slusarz <slusarz at horde.org>:
>>
>>> slusarz     2009-08-07 13:33:06 EDT
>>>
>>> Modified files:        (Branch: FRAMEWORK_3)
>>>   docs                 RELEASE_NOTES
>>> Log:
>>> First pass at 3.3.5 release notes.
>>
>> Just an FYI - the new freshmeat site and API no longer use the  
>> release_focus data. They *do* allow for tagging of individual  
>> releases with keywords.  So, do we want to tag our releases in lieu  
>> of the release_focus data? I'm thinking something like 'stable',  
>> 'security', 'RC' etc... ?
>
> Do we just want to reuse the descriptions already in the  
> RELEASE_NOTES files?  e.g.
>
> Initial announcement
> Documentation
> Minor feature enhancements
> Major feature enhancements
> Minor bugfixes
> Major bugfixes
> Minor security fixes
> Major security fixes

Since the old release_focus data had been converted to those tags for  
the existing releases, I already did that for the releases that I had  
to add manually.

Jan.

-- 
Do you need professional PHP or Horde consulting?
http://horde.org/consulting/
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: Digitale PGP-Unterschrift
URL: <http://lists.horde.org/archives/dev/attachments/20090808/80e75921/attachment.bin>