Do we know when a new build will be released for 25R1? It seems the original from about a month ago is the only one available. 25.100.0054
Answer
New build for 25R1
Best answer by Robert Sternberg
Elena, Thanks for the response! I have been reviewing this which is partly why I posted here. I was expecting a new build to be released but have not seen it yet. I am hoping that we will still see the available builds for download. It seems it would be required for anyone wanting to do a local install.
Hi
This question is a bit tricky to answer! Excuse my monologue of current understanding and I hope it helps answer the question.
In the past, I’ve heard builds and updates used interchangeably... understandably so. While builds have always technically been internal to Acumatica by definition, we only saw one public-facing build per update number. Because of that, it was natural to refer to the update as a “build” in everyday use.
With the introduction of the new versioning schema, I need to be more specific in how I answer separating those concepts:
-
Builds remain internal to Acumatica and importantly, a single build may serve as the foundation for multiple public releases in the form of patches.
-
Service Packs (SPs) and Patches now represent the public-facing release milestones:
-
Service Packs are for major, non-breaking updates.
-
Patches, which are a newer addition to the schema, cover minor, cumulative fixes for issues related to stability, performance, or security.
-
To answer your question:
-
With the new terminology: The next public build number will be released with Service Pack 1.
-
With the old terminology: What we once referred to as a “build” is now more accurately defined as either a Service Pack or a Patch, depending on the scope of the release.
For 2025 R1:
-
The next major milestone is Service Pack 1, which will include a new build number under the updated schema.
-
The next minor milestone is Patch #2. Patch #1 has already been released and is scheduled to roll out to SaaS environments this week, with standards set in the FAQ. Patch #1 reused the prior build number and I expect that to continue through all patches until SP1 is released.
If a member helped you, please *Like* their post. If a member provided an answer to your question, please mark it as *Best Answer*.
Hi
This topic might give some information about situation with builds:
Elena, Thanks for the response! I have been reviewing this which is partly why I posted here. I was expecting a new build to be released but have not seen it yet. I am hoping that we will still see the available builds for download. It seems it would be required for anyone wanting to do a local install.
If a member helped you, please *Like* their post. If a member provided an answer to your question, please mark it as *Best Answer*.
+7Elena, Thanks for the response! I have been reviewing this which is partly why I posted here. I was expecting a new build to be released but have not seen it yet. I am hoping that we will still see the available builds for download. It seems it would be required for anyone wanting to do a local install.
Hi
This question is a bit tricky to answer! Excuse my monologue of current understanding and I hope it helps answer the question.
In the past, I’ve heard builds and updates used interchangeably... understandably so. While builds have always technically been internal to Acumatica by definition, we only saw one public-facing build per update number. Because of that, it was natural to refer to the update as a “build” in everyday use.
With the introduction of the new versioning schema, I need to be more specific in how I answer separating those concepts:
-
Builds remain internal to Acumatica and importantly, a single build may serve as the foundation for multiple public releases in the form of patches.
-
Service Packs (SPs) and Patches now represent the public-facing release milestones:
-
Service Packs are for major, non-breaking updates.
-
Patches, which are a newer addition to the schema, cover minor, cumulative fixes for issues related to stability, performance, or security.
-
To answer your question:
-
With the new terminology: The next public build number will be released with Service Pack 1.
-
With the old terminology: What we once referred to as a “build” is now more accurately defined as either a Service Pack or a Patch, depending on the scope of the release.
For 2025 R1:
-
The next major milestone is Service Pack 1, which will include a new build number under the updated schema.
-
The next minor milestone is Patch #2. Patch #1 has already been released and is scheduled to roll out to SaaS environments this week, with standards set in the FAQ. Patch #1 reused the prior build number and I expect that to continue through all patches until SP1 is released.
Robert Sternberg, Crestwood Associates -- If a community member helped you, please *Like* their post/reply. If they provided an answer to your question, please mark it as *Best Answer*.
Is a link available to allow us to obtain the 25.100.0054.1 patch so I can update our local instance?
+7Is a link available to allow us to obtain the 25.100.0054.1 patch so I can update our local instance?
Not yet
Robert Sternberg, Crestwood Associates -- If a community member helped you, please *Like* their post/reply. If they provided an answer to your question, please mark it as *Best Answer*.
If a member helped you, please *Like* their post. If a member provided an answer to your question, please mark it as *Best Answer*.
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.