Le lun. 31 oct. 2022 à 07:34, Hervé Boutemy a
écrit :
> if pushing the tag is an additional manual step after the vote, experience
> shows that it will be forgotten
>
Well it worked well for multiple projects so I'm sure it can work for maven.
Dist is another deal and we can also invest automati
if pushing the tag is an additional manual step after the vote, experience
shows that it will be forgotten
and even if we check its existence in dist-tool and publish what is missing,
people will have to look at the report:
https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven-dist-tool/
+1 post-release tagging is the easiest (plus the fact a tag is a hash in
git, not a name ;))
Le dim. 30 oct. 2022 à 21:40, Olivier Lamy a écrit :
> +1
>
> Exactly if the problem is the tag, we simply don’t push the tag.
> m-release-p has options for that (don’t push and local clone).
> The tag i
+1
Exactly if the problem is the tag, we simply don’t push the tag.
m-release-p has options for that (don’t push and local clone).
The tag is not needed as we are supposed to vote sources tarball.
This even make the release process faster as you avoid some extra network
operations such another clo
I don't see the point of burning releases. Imho, this has a negative
impact on users for no benefits.
If the problem is just about not rewriting the git history, we could simply
tag manually once the vote has succeeded (or find a way to delay pushing
the tag even if the tag has been created in you
Am 2022-10-30 um 20:32 schrieb Elliotte Rusty Harold:
On Sun, Oct 30, 2022 at 6:53 PM Michael Osipov wrote:
Am 2022-10-30 um 19:39 schrieb Elliotte Rusty Harold:
IMO A failed release should not burn an external facing version
number. If it does, then the release process is flawed and needs to
On Sun, Oct 30, 2022 at 6:53 PM Michael Osipov wrote:
>
> Am 2022-10-30 um 19:39 schrieb Elliotte Rusty Harold:
> > IMO A failed release should not burn an external facing version
> > number. If it does, then the release process is flawed and needs to be
> > fixed.
>
> Why? This I don't understand
Am 2022-10-30 um 19:39 schrieb Elliotte Rusty Harold:
IMO A failed release should not burn an external facing version
number. If it does, then the release process is flawed and needs to be
fixed.
Why? This I don't understand. From ASF PoV only the source release ZIP
file is relevant. Everythin
On Sun, Oct 30, 2022 at 2:40 PM Elliotte Rusty Harold
wrote:
> IMO A failed release should not burn an external facing version
> number. If it does, then the release process is flawed and needs to be
> fixed.
>
Big old +1 on that! :-)
Gary
>
> On Sun, Oct 30, 2022 at 11:05 AM Slawomir Jaranow
IMO A failed release should not burn an external facing version
number. If it does, then the release process is flawed and needs to be
fixed.
On Sun, Oct 30, 2022 at 11:05 AM Slawomir Jaranowski
wrote:
>
> Hi,
>
> Current procedure of releases is unclear in case of restart releases. [1]
>
> I see
Am 2022-10-30 um 12:04 schrieb Slawomir Jaranowski:
Hi,
Current procedure of releases is unclear in case of restart releases. [1]
I see two cases:
- technical problem during release ... something goes wrong after SMC tag
was created
- canceled vote
Technically we have many solutions:
1.
- dr
Hi,
Current procedure of releases is unclear in case of restart releases. [1]
I see two cases:
- technical problem during release ... something goes wrong after SMC tag
was created
- canceled vote
Technically we have many solutions:
1.
- drop old tag and restart with the same version
- no need
Am 2022-10-30 um 11:24 schrieb Slawomir Jaranowski:
niedz., 30 paź 2022 o 11:16 Michael Osipov napisał(a):
Am 2022-10-30 um 11:02 schrieb Slawomir Jaranowski:
Hi,
We solved 42 issues:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317820&version=12344367
There are sti
niedz., 30 paź 2022 o 11:16 Michael Osipov napisał(a):
> Am 2022-10-30 um 11:02 schrieb Slawomir Jaranowski:
> > Hi,
> >
> > We solved 42 issues:
> >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317820&version=12344367
> >
> > There are still a couple of issues left in JIR
Am 2022-10-30 um 11:02 schrieb Slawomir Jaranowski:
Hi,
We solved 42 issues:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317820&version=12344367
There are still a couple of issues left in JIRA:
https://issues.apache.org/jira/issues/?jql=project%20%3D%20MPLUGIN%20AND%20res
Hi,
We solved 42 issues:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317820&version=12344367
There are still a couple of issues left in JIRA:
https://issues.apache.org/jira/issues/?jql=project%20%3D%20MPLUGIN%20AND%20resolution%20%3D%20Unresolved%20ORDER%20BY%20key
Staging
16 matches
Mail list logo
