Page 2 of 3 FirstFirst 123 LastLast
Results 11 to 20 of 27

Thread: Release Policy Update

  1. #11
    Sencha Premium User
    Join Date
    Sep 2009
    Posts
    311

    Default

    the release will be one per month? (minor)
    and major every three months?

  2. #12
    Sencha User edspencer's Avatar
    Join Date
    Jan 2009
    Location
    Palo Alto, California
    Posts
    1,939

    Default

    Our version numbers look like MAJOR.MINOR.PATCH, so 3.1.0 breaks down like:

    Major: 3
    Minor: 1
    Patch: 0

    Major releases (e.g. 4.0) occur roughly every 12 - 18 months, minors (e.g. 3.2) roughly every 3 - 4 months, patches (e.g. 3.1.1) roughly once per month.

    The numbers above are typical but we don't have a policy strictly defining that - releases happen when it makes most sense.
    Ext JS Senior Software Architect
    Personal Blog: http://edspencer.net
    Twitter: http://twitter.com/edspencer
    Github: http://github.com/edspencer

  3. #13
    Sencha User jay@moduscreate.com's Avatar
    Join Date
    Mar 2007
    Location
    DC Area =)
    Posts
    16,364

    Default

    It's nice to see this process in place for both branches.

  4. #14
    Sencha User
    Join Date
    Sep 2008
    Posts
    63

    Default

    Quote Originally Posted by Jamie Avins View Post
    We are updating our policies so that the first patch release for major or minor releases are going to be made available for public download. In addition, we're planning to release early public beta / release candidates on the forums so we can get more feedback before release.
    Just wondering, if big bugs are found in version 3.1.1 (considering how much you are changing this is likely to happen), what will we have to do? We will have to wait for 3.2 to see them fixed?

  5. #15
    Sencha User edspencer's Avatar
    Join Date
    Jan 2009
    Location
    Palo Alto, California
    Posts
    1,939

    Default

    Quote Originally Posted by TizianoF View Post
    Just wondering, if big bugs are found in version 3.1.1 (considering how much you are changing this is likely to happen), what will we have to do? We will have to wait for 3.2 to see them fixed?
    The point of the first patch release is to address any bugs in the major or minor before it. The idea with 3.1.1 is to fix bugs, not introduce new ones. We will be releasing 3.1.2 to support subscribers as usual and currently have no plans to issue it as a general release.
    Ext JS Senior Software Architect
    Personal Blog: http://edspencer.net
    Twitter: http://twitter.com/edspencer
    Github: http://github.com/edspencer

  6. #16

    Default

    I would suggest that you should "GA" release whatever x.y.z release turns out to be "the most stable." Whatever that turns out to be.

    For instance: I'm passing over 3.1.0 "as a routine matter of course." (I waited four months to upgrade my iPhone, and I'll be putting Snow Leopard on my Mac sometime in late March ... and after carefully checking the label on the bottom of the box.)

    Am I chompin' therefore to get 3.1.1? Not particularly; not if it's unstable. I'm going to be listening very attentively for a month or two after whatever incremental GA release comes anyhow, just to see if it is stable, and if it isn't I'll never budge from 3.0. (Perhaps, ever.)

    So... when the pay-as-you-go people are ecstatic with a release, then release it. The very worst thing that you could do is this: "We released before its time, and then we released an interim that was also before its time (not intending to do so), and we finally fixed the bugs but ... you can't have those fixes."

  7. #17

    Default

    What about subsequent releases?
    Are those only only available to those with commercial licenses?
    What about open source projects?
    What about cachefly? It's not really useful if only old/buggy releases are available there?

  8. #18
    Sencha User edspencer's Avatar
    Join Date
    Jan 2009
    Location
    Palo Alto, California
    Posts
    1,939

    Default

    Quote Originally Posted by togetyourexlove View Post
    I was hoping to see some more examples. May be if you could create some more and show us mortals some tricks
    We added 7 new examples in 3.2, giving us 100 in total...

    Which examples would you like to see? I'm usually amenable to adding more
    Ext JS Senior Software Architect
    Personal Blog: http://edspencer.net
    Twitter: http://twitter.com/edspencer
    Github: http://github.com/edspencer

  9. #19
    Sencha User mystix's Avatar
    Join Date
    Mar 2007
    Location
    Singapore
    Posts
    6,232

    Default

    @ed, that looks like signature spam to me.

  10. #20
    Sencha User edspencer's Avatar
    Join Date
    Jan 2009
    Location
    Palo Alto, California
    Posts
    1,939

    Default

    Quote Originally Posted by mystix View Post
    @ed, that looks like signature spam to me.
    lol I do believe you're right. I killed it
    Ext JS Senior Software Architect
    Personal Blog: http://edspencer.net
    Twitter: http://twitter.com/edspencer
    Github: http://github.com/edspencer

Page 2 of 3 FirstFirst 123 LastLast

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •