Hello Raphael!
Am 10.10.2017 um 17:10 schrieb Raphael Bircher:
> I understand this, I have just an idea. We keep the 4.1.4 as is and
> release a patch for the bug. Then we make just new community builds
> with > the patch. Like this we avoid to make a 4.1.5 and we stick
> within the ASF policy.
A patch for *all* platforms must also be tested in all ways. So I think,
this way isn't an easy and good way.
Simply let 4.1.4 as is but don't let it (official) free.
Create a 4.1.5-RC1 (or maybe 4.1.4-RC5 if possible) with this patch, and
if no further errors announce 4.1.5.
Regards Mathias
Regards Raphael
Am .10.2017, 16:35 Uhr, schrieb Jim Jagielski <j...@jagunet.com>:
Once something is tagged it is public. It is official. Removing and/or
adjusting tags is something that we cannot and should not do. It is
really against ASF policy since it destroys an accurate representation
of our history and IP provenance.
If someone wishes to take over as RM, I am fine with that. I will
still produce the required builds. But as long as I'm RM, I can't
abide by "rewriting" history re: 4.1.4... But like I said, I'm OK
w/ someone taking over as RM and will follow their direction
whatever it is.
On Oct 10, 2017, at 9:38 AM, Andrea Pescetti <pesce...@apache.org>
wrote:
Jim Jagielski wrote:
Considering this issue, this means that 4.1.4 is also DOA. I will
wait for
a few more hours, for West Coast to get online but my plan is to
start the process for AOO-415
We are still in time for retiring 4.1.4-RC4 (not 4.1.4 altogether).
Builds are on SourceForge but they've never been distributed and they
can be replaced by new builds.
4.1.4 is tagged but SVN tags can be deleted and recreated. Not best
practice, but surely feasible.
Remember that the amount of code changes needed to produce something
named 4.1.5 is quite significant and very much error-prone. Take a
look at the relevant issues in case, but for a "quick fix" I would
definitely stick to 4.1.4, produce 4.1.4-RC5 and vote on RC5, while
undoing what we did for 4.1.4-RC4.
Note: I'm writing all of the above without having had the time to
look at the patch or test. I'll do that this evening, European time.
I have still to understand the importance of this bug too - I assume
this affects potentially many users, otherwise we can go the slippery
way of "fix just another small bug" for ages.
Regards,
Andrea.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org
