I totally agree, our enemy is regression and we should be very sure to avoid it.
Le 07/05/2024 à 17:19, Pranay Pandey a écrit :
Hi Daniel,
I am in favor of creating a new release.
After we create a new release, IMO we shouldn't be committing any new
features there.
This is critical that we
Ha sorry Pranay,
I did not get your point, I guess you were discussing before frezzing the
release branch, right?
Then of course we can't guarantee to have fixed all known bugs.
Only blocker bugs (decided by the reporter and discussed if needed) and of
course security bugs are blocking a
Le 07/05/2024 à 17:01, Daniel Watford a écrit :
Hi Jacques,
I'm sorry, but I can't quite parse your question, 'What is the
difference...'. Could you restate it another way?
Simple, what is the process so far?
We freeze the trunk into a release branch, says 24.xx in our case
.05 seems short
Hi Pranay,
OK, but then only that? So far we backported any bug. So we would release a
branch with bugs in?
Le 07/05/2024 à 16:42, Pranay Pandey a écrit :
Hi Jacques,
what is a blocker bug, only security?
I think it should also include anything broken on the UI or at the process
level.
Best
Hi Daniel,
I am in favor of creating a new release.
After we create a new release, IMO we shouldn't be committing any new
features there.
This is critical that we limit the scope of release with ongoing
development in the trunk.
Best regards,
Pranay Pandey
On Tue, 7 May 2024 at 20:31, Daniel
Hi Jacques,
I'm sorry, but I can't quite parse your question, 'What is the
difference...'. Could you restate it another way?
Are you asking what the difference is between enforcing a feature-freeze on
trunk versus continuing to allow all changes to trunk whilst having a
feature-freeze on a
Hi Jacques,
what is a blocker bug, only security?
I think it should also include anything broken on the UI or at the process
level.
Best regards,
Pranay Pandey
On Tue, 7 May 2024 at 19:48, Jacques Le Roux
wrote:
> What is the difference between freezing the trunk in a release-24.xx where
>
What is the difference between freezing the trunk in a release-24.xx where the rule is no improvements but if a consensus agrees with? In other words,
apart exceptions only bugs and not only blockers,as we did so far and the "new" proposition? Do we really wants to backport only blockerbugs? And
Hi Jacopo,
I see only KEYS
TIA
Jacqued
Le 07/05/2024 à 11:41, Jacopo Cappellato a écrit :
The vote is successful with seven positive votes (all binding) and no
negative votes.
I am going to publish and announce the release soon.
Jacopo
On Tue, Apr 30, 2024 at 5:06 PM Jacopo Cappellato
Dear Daniel,
Thank you for outlining the proposed release strategy for OFBiz. I liked
the idea of creating a new branch from trunk named 'release-24.05' to
address blockers for the upcoming release.
I agree with Michael's proposal that targeting a release while working on
the trunk is worth
The Apache OFBiz community is pleased to announce the new release "Apache
OFBiz 18.12.13".
Apache OFBiz® is an open source product for the automation of enterprise
processes that includes framework components and business applications.
http://ofbiz.apache.org/
"Apache OFBiz 18.12.13" is the
The vote is successful with seven positive votes (all binding) and no
negative votes.
I am going to publish and announce the release soon.
Jacopo
On Tue, Apr 30, 2024 at 5:06 PM Jacopo Cappellato
wrote:
>
> This is the vote thread to publish "Apache OFBiz 18.12.13", the thirteenth
> release
+1
Jacopo
On Tue, Apr 30, 2024 at 5:06 PM Jacopo Cappellato
wrote:
>
> This is the vote thread to publish "Apache OFBiz 18.12.13", the thirteenth
> release from the release18.12 branch.
>
> The release files can be downloaded from here:
> https://dist.apache.org/repos/dist/dev/ofbiz/
> and are:
Hello all,
I'm a little confused by what the differences in opinions actually are in
this thread. I think this is because the differences are minor and we are
probably close to an agreement on how to proceed.
Although there are not many of us involved in this conversation, it seems
there is a
14 matches
Mail list logo