This would have been the next version. The manifest is always updated after
a new release.
On May 13, 2014 7:19 PM, "Arsenij E Solovjev" <xeper...@gmail.com> wrote:
> But in the MANIFEST.MF it says 14.1.31 o.O
>
> On 05/13/2014 06:26 PM, Zieris, Franz wrote:
>
> Small amendment: The last Saros version released was 13.12.6 (not
> 14.1.31), so the next version number would be 14.0.0 (not 15.0.0).
>
>
>
> Franz
>
>
>
> *From:* Arsenij E Solovjev [mailto:xeper...@gmail.com <xeper...@gmail.com>]
>
> *Sent:* Tuesday, May 13, 2014 6:09 PM
> *To:* dpp-devel@lists.sourceforge.net
> *Subject:* [DPP-Devel] Feature Request: Semantic Versioning for Saros
>
>
>
> Hi everyone,
>
> Franz and myself just had a discussion about using Semantic Versioning for
> Saros.
> This idea has been pitched previously by other devs, but making this
> change would have
> made updates impossible for users for reasons I will not touch here.
>
> So, basics first: Semantic Versioning is a prescription on how to version
> your software
> and can be summed up in this simple rule:
>
> Given a version number MAJOR.MINOR.PATCH, increment the:
>
> 1. MAJOR version when you make incompatible API changes,
> 2. MINOR version when you add functionality in a
> backwards-compatible manner, and
> 3. PATCH version when you make backwards-compatible bug fixes.
>
> Quelle: http://semver.org/
>
>
> The current version of Saros is 14.1.31. This tells us that the latest
> version has been released
> on January 31st 2014. Besides being meaningless (and somewhat ugly), this
> versioning also
> forces us to hardcode our check for version-compatibility.
>
> So we came up with a solution for this. On each release we would increment
> MAJOR.MINOR.PATCH
> in the following manner:
>
> 1. MAJOR when the release is not backwards-compatible with the
> previous Saros version
> 2. MINOR when it is backwards-compatible and new features have been
> added
> 3. PATCH when it's a backwards compatible bugfix-only release (if that
> were ever to happen)
>
> So the next Saros release would be 15.0.0 and would use this new scheme.
> We would need to update
> the documentation of our release process, and simplify the
> version-compatibility check implementation.
>
> So, any thoughts? Any volunteers? Should I make this into an Feature
> Request on Sourceforge?
>
> Cheers,
> Arsenij
>
>
>
>
> ------------------------------------------------------------------------------
> "Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE
> Instantly run your Selenium tests across 300+ browser/OS combos.
> Get unparalleled scalability from the best Selenium testing platform
> available
> Simple to use. Nothing to install. Get started now for free."
> http://p.sf.net/sfu/SauceLabs
> _______________________________________________
> DPP-Devel mailing list
> DPP-Devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/dpp-devel
>
>
------------------------------------------------------------------------------
"Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE
Instantly run your Selenium tests across 300+ browser/OS combos.
Get unparalleled scalability from the best Selenium testing platform available
Simple to use. Nothing to install. Get started now for free."
http://p.sf.net/sfu/SauceLabs
_______________________________________________
DPP-Devel mailing list
DPP-Devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dpp-devel
