Until we are at least RC quality, we shouldn't set PLATFORM_RELEASE to the final date. Also keep in mind that this value should never go backwards. So I want to leave some wiggle room, just in case (however unlikely) we move the release date forward (perhaps 19.03). Scott On 18-12-12 03:17 PM, Khalil, Ghada wrote:
Scott was going to put the final release version (19.05) a little closer to milestone-3 / RC1. Do you prefer to have it set from now?
Ghada
-----Original Message----- From: Jones, Bruce E [mailto:bruce.e.jones@intel.com] Sent: Wednesday, December 12, 2018 3:11 PM To: Little, Scott; starlingx-discuss@lists.starlingx.io Subject: Re: [Starlingx-discuss] changing PLATFORM_RELEASE
This makes sense to me. Should we set the value to the next planned release date?
brucej
-----Original Message----- From: Scott Little [mailto:scott.little@windriver.com] Sent: Wednesday, December 12, 2018 11:41 AM To: starlingx-discuss@lists.starlingx.io Subject: [Starlingx-discuss] changing PLATFORM_RELEASE
Or master branch builds are still reporting PLATFORM_RELEASE=18.10. This value is also known as the SW_VERSION.
To avoid confusion, I propose the following. After we cut a release branch, should always advance the master branch value by at least +1 month beyond that release, but never greater than -1 month to the next projected release date.
I propose changing the current master branch to PLATFORM_RELEASE=19.01
Scott
_______________________________________________ Starlingx-discuss mailing list Starlingx-discuss@lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss@lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss