Version number for next stable release

[ikedas]

For example, rpm versioning system judges that 6.2.17 is older than 6.2.17b.1 by default. There may be any other systems alike.

1. What version number should we give to the next stable release?
   Either of 6.2.17 (problematic), 6.2.18, 6.3.0 ...and so on.
2. What kind of policy should we adopt to update version numbers?
   How may we determine development and stable releases by version numbers?

[racke]

On 06/08/2017 04:02 AM, IKEDA Soji wrote: For example, rpm versioning system judges that |6.2.17| is older than |6.2.17b.1| by default. There may be any other systems alike. 1. What version number should we give to the next stable release? Either of |6.2.17| (problematic), |6.2.18|, |6.3.0| ...and so on.

We don't have a big change set, so I would say we skip .17 and release as .18.

2. What kind of policy should we adopt to update version numbers? How may we determine development and stable releases by version numbers?

Some version that is handled gracefully by RPM :-). Regards Racke

…

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#21>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAIxPjm6dEGHL8R60KU_YtQwmM8U_N7cks5sB1ZMgaJpZM4NzfUB>.

-- Ecommerce and Linux consulting + Perl and web application programming. Debian and Sympa administration.

[ikedas]

@racke, thanks for suggesting.

1. What version number should we give to the next stable release?
   Either of |6.2.17| (problematic), |6.2.18|, |6.3.0| ...and so on.

We don't have a big change set, so I would say we skip .17 and release as .18.

I agree.

If there are no objection, the next stable release will be 6.2.18.