perfsonar-dev - perfsonar bundle versioning
Subject: perfsonar development work
List archive
- From: Loukik Kudarimoti <>
- To: "" <>
- Subject: perfsonar bundle versioning
- Date: Thu, 19 Oct 2006 19:16:54 +0100
Hi,
I would like to briefly mention the versioning scheme for perfsonar that I have in mind. I wish to bring up this topic so that we can have more discussions on it.
The idea is to have
1) Major Releases (ex: 1.0, 2.0, 3.0 , etc)
- Releases which include schema changes, major features and enhancements. Can also include critical bug fixes. Users are strongly suggested to update to new versions.
2) Minor Releases (1.1, 1.2, 1.3)
- Updates to services, new features, fixes to major bugs (which qualify for a new minor version, etc). Users are suggested to update to these versions but this might not be a critical update.
3) Bug fixes or extra minor releases (1.1.0, 1.1.2, etc)
- Minor bug fixes - affected ones will be required to update but maybe not all.
We also need to see how NMWG versioning can be incorporated (if needed, I am not so sure right now)
Based on the above terminology, I think the next release that we are working on, qualifies to be called 2.0 (because release codes mean schema changes)
Any thoughts, suggestions?
Loukik.
- perfsonar bundle versioning, Loukik Kudarimoti, 10/19/2006
- Re: [pS-dev] perfsonar bundle versioning, Martin Swany, 10/19/2006
- Re: [pS-dev] perfsonar bundle versioning, Loukik Kudarimoti, 10/19/2006
- Re: [pS-dev] perfsonar bundle versioning, Jochen Reinwand, 10/20/2006
- Re: [pS-dev] perfsonar bundle versioning, Martin Swany, 10/19/2006
Archive powered by MHonArc 2.6.16.