######################################################################
# Name of the service and group that is responsible for it
######################################################################
serviceGroup=org.openlmis
serviceName=openlmis-referencedata
######################################################################
# Current version of the service
# Only a Release Manager should update this
# See https://openlmis.atlassian.net/wiki/display/OP/Rolling+a+Release
######################################################################
serviceVersion=3.0.1-SNAPSHOT
Given a version number MAJOR.MINOR.PATCH, increment the:
MAJOR version when you make incompatible API changes,
MINOR version when you add functionality in a backwards-compatible manner, and
PATCH version when you make backwards-compatible bug fixes.
I like the plan Josh suggests. As we release our components this week, the component leads should help coordinate which snapshots we will be working towards next.
Here is the draft CHANGELOG that we are compiling to prepare for the 3.1.0 release of Requisition service (probably releasing this component Tuesday):
https://github.com/OpenLMIS/openlmis-requisition/blob/master/CHANGELOG.md
(It has a simple Markdown format. For the simple tickets, I copied from the Git commit history. For more complex tickets, I summarized what changed in the Requisition component.)
-Brandon
--
You received this message because you are subscribed to the Google Groups "OpenLMIS Dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to
openlmis-dev...@googlegroups.com.
To post to this group, send email to
openlm...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/openlmis-dev/6ad4945d-4bb9-446b-9b49-347a7d991dcd%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
To view this discussion on the web visit https://groups.google.com/d/msgid/openlmis-dev/EF996AA1-E727-4A6F-BCED-9DD356109C78%40villagereach.org.
For more options, visit https://groups.google.com/d/optout.
Paweł Gesek
Technical Project Manager
pge...@soldevelo.com / +48 690 020 875
SolDevelo Sp. z o. o. [LLC]
Office: +48 58 782 45 40 / Fax: +48 58 782 45 41 Al. Zwycięstwa 96/98 81-451, Gdynia
http://www.soldevelo.com
Place of registration: Regional Court for the City of
Gdansk KRS: 0000332728, TAX ID:
PL5862240331, REGON: 220828585, Share capital:
60,000.00 PLN
PATCH version when you make backwards-compatible bug fixes.
Beyond these tools and process, there is a tension underlying our decisions:
At this point I feel that while we need to demonstrate to the broader community that we can release stable software, it's also the point in time to make breaking changes as we don't yet have a lot of implementations building clients off of our public API. That said these decisions can't be made in the depths of a ticket, so again I'm calling for us to start having these discussions here in the dev forum.
Are we in agreement about the immediate next steps?
- Component leads should check to ensure that their current working version, is the version they intend to release in time for the 3.0.1 Reference Distribution release in a few days time.
- Developers should check the serviceVersion of their component, and verify that any work they're working on, or have committed, is appropriate according to the next component release version and the rules of Semantic Versioning. If there's work that needs to be done that doesn't agree with the serviceVersion, notify the component lead by posting to the developer forum (this one).
To unsubscribe from this group and stop receiving emails from it, send an email to openlmis-dev+unsubscribe@googlegroups.com.
To post to this group, send email to openlm...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/openlmis-dev/6ad4945d-4bb9-446b-9b49-347a7d991dcd%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups "OpenLMIS Dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to openlmis-dev+unsubscribe@googlegroups.com.
To post to this group, send email to openlm...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/openlmis-dev/EF996AA1-E727-4A6F-BCED-9DD356109C78%40villagereach.org.
For more options, visit https://groups.google.com/d/optout.
Hello,
yes, I believe the component leads have done that. We will move
discussions about this to the forum and away from channels such as
Slack. I will assist them with these new responsibilities of
controlling the component versions.
As for the approach, I believe this will now require more
communication between the component leads and the product owner.
The versioning approach is sound, however holding off some tickets
until a PATCH version is completed and dev forum discussion about
versions end, might impact when these tickets are be able to get
completed - and these tickets might have been marked as *MUST* for
the ref distro release that is coming at the end of the sprint.
I still think think that we would want to know the potential backward compatibility issues a bit sooner and avoid finding them half-way through a sprint - there is overhead in time with these discussions on the dev forum and rolling out a patch release, and our release cycle is relatively short nowadays. I think we are at fault for not recognizing these issues during planning - we will pay more attention to them in the future and try to act on them sooner.
Regards,To unsubscribe from this group and stop receiving emails from it, send an email to openlmis-dev...@googlegroups.com.
To post to this group, send email to openlm...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/openlmis-dev/e14c46b8-afbb-49d4-a71b-52f66ce01f55%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
I suggest on the Grooming wiki pages—where the Product Owner prioritizes tickets for upcoming sprints—that we add a note about which component version we are working towards.
For Requisition component I’ve added this at the top for the coming sprint:
https://openlmis.atlassian.net/wiki/display/OP/Backlog+Grooming+Sprint+23
“Requisition
We expect version 3.1.0 will already have been released around Tuesday, March 28. After that, we will proceed with 3.1.1-SNAPSHOT to do bug fixes, performance, security, & refactoring.”
That way there will be awareness as we conduct group planning activities. That would have helped us catch the mis-match that Josh described.
-Brandon
To unsubscribe from this group and stop receiving emails from it, send an email to openlmis-dev...@googlegroups.com.
To post to this group, send email to openlm...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/openlmis-dev/6ad4945d-4bb9-446b-9b49-347a7d991dcd%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups "OpenLMIS Dev" group.
To view this discussion on the web visit https://groups.google.com/d/msgid/openlmis-dev/12fe4e5f-2398-33a8-b005-e02bab258356%40soldevelo.com.