Re: [Proftpd-user] Thoughts on using semver for future version labels?

Thomas Spicer <[email protected]>
Newsgroups gmane.network.proftpd.user
Message-ID <CAM6ZBGq+g=roQYJMRoEjUL47wcCaXxVee6_d4RG7UCQLcjvd=Q@mail.gmail.com>
My vote would be to drop the RC and use incrementing numbering. If you look
at the master commit branch the amount of work/updates/fixes/patches occurs
with great frequency. It will require thinking about how your branches are
working though, so that might be the biggest change in a switch.

On Sun, Apr 23, 2017 at 9:23 PM, TJ Saunders <[email protected]> wrote:

> I've been thinking/wondering whether it would make sense for ProFTPD to
> use semver[1] semantics for its versioning.  Thus rather than:
>
>   1.3.7rc1
>
> we'd have:
>
>   1.3.7-rc1
>
> Or maybe we'd move away from the RC process, and instead start to
> increase the patch number more frequently, incrementing that number
> instead of using RC labels:
>
>   1.3.7
>   1.3.8
>   1.4.0
>
> And so the "stable" releases would start be more of incrementing the
> minor or major versions.
>
> Thoughts?
> TJ
>
> [1] http://semver.org/
>
> ------------------------------------------------------------
> ------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> _______________________________________________
> ProFTPD Users List   <[email protected]>
> Unsubscribe problems?
> http://www.proftpd.org/list-unsub.html
>

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot

_______________________________________________
ProFTPD Users List   <[email protected]>
Unsubscribe problems?
http://www.proftpd.org/list-unsub.html
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.