we'll need to clarify what projects are guinea pigs, to stress test the issues
history copy
and releases/milestones
I see 3 cited:
- ARCHETYPE
- MCLEAN
- MJLINK
MNGSITE does not have any release, then not really something key IMHO for
testing
migration
I see also MPOM, but it seems it has be
Please start by filing an issue describing what the intended rule will
do. It's easier to understand in prose than code.
On Tue, Jan 7, 2025 at 10:02 PM Andy Law wrote:
>
> All,
>
> I’ve written some code to extend the enforcer plugin to include a “mutually
> exclusive profiles” rule. I’m ready
All,
I’ve written some code to extend the enforcer plugin to include a “mutually
exclusive profiles” rule. I’m ready to submit a Pull Request, but I’m not quite
sure of the correct procedure.
In my own projects, I tend to work primarily off a develop branch, folding
features into that and then
Ok be to on track I was created a wiki site -
https://cwiki.apache.org/confluence/display/MAVEN/JIRA+to+GitHub+switching
As for our ASF MAven initiatives we use wiki to document progress and
so on ... so in this case it should be the same.
On Tue, 7 Jan 2025 at 17:41, Sandra Parsick wrote:
>
> >
No manual work ...
I thought about not migrate issues at all for this repo - MNGSITE
Ah, thanks for clarifying. I misunderstood it.
We have voted about switching to GitHub ...
https://lists.apache.org/thread/h42ls1ccc1flhk2yrkwc6rz05m8rjq6r
I'm not going to do about 100 votes ... for each re
On Tue, 7 Jan 2025 at 16:56, Sandra Parsick wrote:
>
> I created migration configuration for the following projects :
>
> - MCLEAN [1]
> - MJLINK [2]
> - MNGSITE with a filter, so that only open issues are migrated [3]
>
> @Slawomir: I know that you want to migrate the issues of MNGSITE
> manually
I created migration configuration for the following projects :
- MCLEAN [1]
- MJLINK [2]
- MNGSITE with a filter, so that only open issues are migrated [3]
@Slawomir: I know that you want to migrate the issues of MNGSITE
manually. The configuration should demonstrate a possibility to migrate
o
Le 2025-01-07 14:25, Elliotte Rusty Harold a écrit :
I'd like to propose that we simply stop using Slack for project wide
communications. Discussion about Maven related things can take place
in the mailing list or the issue tracker. Between that, communication
is well covered. Thoughts?
Having
On 1/7/25 8:25 AM, Elliotte Rusty Harold wrote:
All third party proprietary systems not owned by the Apache Project
come with risks, Github and Jira included. However Slack strikes me as
particularly bad.
I'll weigh in as a lurker (largely a contributor to Maven through third
party integration
One more thing I just noticed. When I use the Github editor to make
small changes to a file directly in my browser as I did in
https://github.com/apache/maven-site/pull/629 and many other PRs,
especially ones focused on docs, it offers me the option to edit
master directly or create a branch, not a
+1 any abandonment of a commercial tool.
+1 to the analysis as well.
I am a big believer in the truth of the immutable record (mailing list
archive)
On Tue, Jan 7, 2025 at 1:26 PM Elliotte Rusty Harold
wrote:
> All third party proprietary systems not owned by the Apache Project
> come with risk
All third party proprietary systems not owned by the Apache Project
come with risks, Github and Jira included. However Slack strikes me as
particularly bad.
1. It breaks the web architecture with unstable URLs.
2. The privacy practices are unclear, unstable, and user hostile.
Using Slack requires
After a discussion with Gerd Aschemann, I moved the migration list from
the Github Issue to the repository of the migration tool [1]. I adjusted
the list according to already provided feedback.
If someone wants to have write permission to this repository, please let
me know it, I will assign i
13 matches
Mail list logo
