I notice this from an earlier email: "We are now finalizing the third milestone of 4.0.0 release."
So perhaps there is some confusion. If this is intended to be a release, then there is a problem. Releases need to be done in source form, and there needs to be a vote. If this is not intended to be a release, then there needs to be a clearer explanation of what it is. i.e. Are people expected to test this? Are we soliciting feedback? When will the final vote be called? On 27 November 2013 18:45, Noah Slater <[email protected]> wrote: > Can you explain what a "milestone" is? > > At Apache, we only do source releases, but there is no source archive > here, and I notice that have not used the term. > > But I find it quite irregular to be announcing the availability of > binary "milestones" without a primary source archive. > > On 26 November 2013 17:28, Imesh Gunaratne <[email protected]> wrote: >> Hi All, >> >> The third milestone of the Apache Stratos (incubtaing) 4.0.0 release is now >> ready. >> >> Please find the binary packages of this milestones at: >> https://dist.apache.org/repos/dist/dev/incubator/stratos/4.0.0-incubating-m3/ >> >> Source code could be fetched using git tag 4.0.0-incubating-m3: >>>git clone https://git-wip-us.apache.org/repos/asf/incubator-stratos.git >>>cd incubator-stratos >>>git checkout 4.0.0-incubating-m3 >> >> The installation guide could be found attached with this mail. >> >> Features Included: >> >> Load Balancer >> - Introduced load balance statistics publishing interface. >> - A reference implementation of the above interface was done for HAProxy >> extension. >> - Added support for dedicated load balancing for services. This applies to >> both Stratos load balancer and HAProxy extension. >> - Added support for dedicated load balancing for subscriptions. This also >> applies to both Stratos load balancer and HAProxy extension. >> - Fixed failover logic: Support for retrying requests on all members of a >> given cluster if the selected member did not respond for a request. >> >> Auto-Scaler >> - Introduced partition group model. This functionality could be used for >> applying autoscaling algorithms on separate partition sets. >> - Divided policies into two main types: Autoscaling & Deployment. Here the >> autoscaling policies define how autoscaling logic is executed and deployment >> policies define in which partition the next member is spawned. >> >> Stratos Manager >> - Cleaned up and enhanced artifact synchronization, so that both repository >> initial checkout (git clone) and repository updates (git pull) are done >> through the java based deployment synchronization client. git.sh script is >> not used anymore. >> - Git repo credentials are encrypted/decrypted using a key, which is >> generated per cartridge subscription. >> >> Cartridge Agent >> - Publish health statistics periodically to CEP (load average and memory >> consumption). >> >> CEP Extension >> - Analyze health statistics sent by cartridge agent and publish inactive >> member information (faulty members) to heath-stat topic in message broker. >> >> Please feel free to report any issues you find with this milestone in JIRA >> under 4.0.0-M3 version tag: >> https://issues.apache.org/jira/browse/STRATOS/fixforversion/12325284 >> >> >> Many Thanks >> Apache Stratos Team > > > > -- > Noah Slater > https://twitter.com/nslater -- Noah Slater https://twitter.com/nslater
