Re: 3.0 M5?

From: Andrus Adamchik (andru..bjectstyle.org)
Date: Wed Aug 20 2008 - 11:49:41 EDT

  • Next message: Andrus Adamchik (JIRA): "[jira] Commented: (CAY-1094) CM DataNode panel reorg - pull the password encoding options into a tab"

    A tag implies committing code to two places. We do that for stable
    branches (to allow development to go ahead when we are in the code
    freeze for a particular release). With milestones we do not implement
    code freeze, so tagging the release until all the serious known issues
    are fixed will only create overhead. So I suggest we fix the class
    generator issue(s) (which I consider a serious bug) on trunk, and then
    create a tag.

    Andrus

    On Aug 20, 2008, at 6:38 PM, Aristedes Maniatis wrote:
    > On 21/08/2008, at 1:29 AM, Andrus Adamchik wrote:
    >
    >> BTW, I am also in favor of M5.
    >
    > Should we (I don't seem to have rights) create an M5 tag under 3.0
    > and assign specific tasks there so we can track progress on what is
    > left? The full list for 3.0 is quite long:
    >
    > https://issues.apache.org/cayenne/secure/BrowseVersion.jspa?id=10000&versionId=10091&showOpenIssuesOnly=true
    >
    > Ari
    >
    >
    >
    > -------------------------->
    > ish
    > http://www.ish.com.au
    > Level 1, 30 Wilson Street Newtown 2042 Australia
    > phone +61 2 9550 5001 fax +61 2 9550 4001
    > GPG fingerprint CBFB 84B4 738D 4E87 5E5C 5EFA EF6A 7D2E 3E49 102A
    >
    >
    >

    This archive was generated by hypermail 2.0.0 : Wed Aug 20 2008 - 11:50:15 EDT