https://issues.apache.org/SpamAssassin/show_bug.cgi?id=6638
Bug #: 6638
Summary: The 3.3.2 release notes file has not been committed to
svn
Product: Spamassassin
Version: 3.3.2
Platform: All
OS/Version: All
Status: NEW
Severity: normal
Priority: P2
Component: Documentation
AssignedTo: [email protected]
ReportedBy: [email protected]
Classification: Unclassified
Created attachment 4939
--> https://issues.apache.org/SpamAssassin/attachment.cgi?id=4939
3.3.2 release announcement from the announcement email that was sent
There is no 3.3.2.txt file in build/announcements directory. As far as I can
see from previous releases it ought to be committed to trunk as well as branch
3.3.
I'm attaching a 3.3.2.txt file with the text copied from the release
announcement that was mailed out for the 3.3.2 release and To and Subject lines
in the same format as the 3.3.1.txt file.
I'm also committing it to branch without a vote as it is documentation and the
link to it on our main page is currently broken. Am I correct that this can be
done as C-T-R even to branch?
Where is the release manager checklist? We should add this step to it if it is
not already there.
Is it too minor to worry about not having release notes in the 3.3.2
distribution tarball or do we need to do something about that?
--
Configure bugmail:
https://issues.apache.org/SpamAssassin/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
