db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kristian Waagan (JIRA)" <j...@apache.org>
Subject [jira] Created: (DERBY-3707) STATUS file changes June 2008
Date Wed, 04 Jun 2008 14:21:45 GMT
STATUS file changes June 2008

                 Key: DERBY-3707
                 URL: https://issues.apache.org/jira/browse/DERBY-3707
             Project: Derby
          Issue Type: Improvement
          Components: Documentation
    Affects Versions:
            Reporter: Kristian Waagan
            Assignee: Kristian Waagan
            Priority: Minor
             Fix For:

I posted the following mail to derby-dev, see full thread here: http://www.nabble.com/Changes-to-the-STATUS-file-td17617479.html

- - - - - - - -

I was looking at the STATUS file we have in the SVN repository, and I
would like to suggest the following changes:

 1) Add the release to the release list.

 2) Mismatch between release date for
    The STATUS file says it was release on the 26th of April, whereas
    the download page says the 24th of April.
    BTW: Was there ever an [ANNOUNCE] mail for this release?

 3) Specify the dates in the release list using the international
    standard date notation (YYYY-MM-DD). See:

 4) Indent the list of committers in a consistent way.

 5) Clarify what the sentence below means, and possibly remove it.
    "The Derby sub-project's modules will be available as distinct and
    discrete downloads".

 6) Remove extra dot character.
    "full-fledged Apache DB project.."

If the feedback for these changes are positive, I can create a Jira and
attach some patches for review. I guess change 1 has to go in anyway.

It is not entirely clear to my how often the STATUS file should be
updated, or if there is anyone who is more responsible than the
community in general to do it.

- - - - - - - -

There won't be patches attached for all commits, please consult the "Subversion commits" tab
as well.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message