Thanks for the feedback.
I collected it as issues in the migration tool repository [1], so I can
go through the issues step-by-step.
I will inform you about my progress.
Sandra
[1] https://github.com/support-and-care/jira-to-gh-issues/issues
Am 11.12.24 um 03:00 schrieb Olivier Lamy:
Hi,
+1
Arnaud Héritier
Twitter/GitHub/... : aheritier
Le mar. 10 déc. 2024 à 23:16, Slawomir Jaranowski
a écrit :
> Hi,
>
> It is the last release before retire
>
> We solved 5 issues:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317622&version=12342770
>
> There are stil
The Apache Maven team is pleased to announce the release of the Maven Fluido
Skin, version 2.0.1.
https://maven.apache.org/skins/maven-fluido-skin/
You should specify the version in your project's site configuration:
org.apache.maven.skins
maven-fluido-skin
2.0.1
Import: This release requ
+1
On Wed, 11 Dec 2024 at 08:15, Slawomir Jaranowski
wrote:
>
> Hi,
>
> It is the last release before retire
>
> We solved 5 issues:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317622&version=12342770
>
> There are still a couple of issues left in JIRA:
> https://issues.a
Hi,
The vote has passed with the following result:
+1 : Sylwester, Tamás, Sławomir, Michael
PMC quorum was reached.
I will promote the source release zip file to Apache distribution area and the
artifacts to the central repo.
Thanks for voting,
Konrad
> On 6. Dec 2024, at 17:11, Konrad Winds
Fix link for site:
https://maven.apache.org/plugins-archives/maven-patch-plugin-LATEST/
On Tue, 10 Dec 2024 at 23:15, Slawomir Jaranowski
wrote:
>
> Hi,
>
> It is the last release before retire
>
> We solved 5 issues:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317622&ver
+1
On Tue, Dec 10, 2024 at 11:15 PM Slawomir Jaranowski
wrote:
>
> Hi,
>
> It is the last release before retire
>
> We solved 5 issues:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317622&version=12342770
>
> There are still a couple of issues left in JIRA:
> https://issue
+1
wt., 10 gru 2024 o 23:16 Slawomir Jaranowski
napisał(a):
> Hi,
>
> It is the last release before retire
>
> We solved 5 issues:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317622&version=12342770
>
> There are still a couple of issues left in JIRA:
>
> https://issue
On Wed, 11 Dec 2024 at 12:16, Elliotte Rusty Harold wrote:
>
> Do we have any estimate how many people/projects still use this?
>
> The three remaining issues in the repo look not too difficult to fix
> if anyone would actually care.
I don't see anybody who wants to take care of it ... so it is
Moving would exactly make things faster. This thread diverged quite a
bit, but AFAIR the opener of this thread (or the other mail referenced
by opener of this thread) is exactly about problems _with_ JIRA.
And I also say leave them opened (migrate, leave them as they were
left in JIRA). Not to clo
Non PMC committees certainly can close jira issues. I do this all the time.
Also if we want to conserve volunteer time we should not spend time moving
to GitHub. That’s extra work compared to simply continuing with jira.
Leaving a bug open costs nothing until someone is ready to address it.
On We
Are you all sure this is how _an open source project having
volunteers-only is supposed to work?_ (maybe better as: "spend it's
scarce resources"?)
As if we'd all be in some company, working on some company product,
then yes, I agree wholeheartedly, this is "how things should be done".
But in rea
On 11/12/2024 12:29, Elliotte Rusty Harold wrote:
On Tue, Dec 10, 2024 at 5:10 PM Slawomir Jaranowski
wrote:
On Tue, 10 Dec 2024 at 17:42, Sylwester Lachiewicz
wrote:
Michale proposed closing all issues that have not been active for more
than 3 years, so there will be less to maintain/migra
Le 2024-12-11 12:29, Elliotte Rusty Harold a écrit :
Please press the button. However, this needs to be done issue by
issue, not as a bulk close of all issues older than some arbitrary
date.
+1 to this.
Ideally, even closed issues should be migrated to make it possible to
search for past val
On Tue, Dec 10, 2024 at 5:10 PM Slawomir Jaranowski
wrote:
>
> On Tue, 10 Dec 2024 at 17:42, Sylwester Lachiewicz
> wrote:
> >
> > Michale proposed closing all issues that have not been active for more
> > than 3 years, so there will be less to maintain/migrate.
>
> Maybe we can limit the age dur
Do we have any estimate how many people/projects still use this?
The three remaining issues in the repo look not too difficult to fix
if anyone would actually care.
On Tue, Dec 10, 2024 at 10:16 PM Slawomir Jaranowski
wrote:
>
> Hi,
>
> It is the last release before retire
>
> We solved 5 issues
16 matches
Mail list logo
