[jira] [Commented] (SOLR-14497) Move the project to become Apache TLP
[ https://issues.apache.org/jira/browse/SOLR-14497?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17203798#comment-17203798 ] Dawid Weiss commented on SOLR-14497: I've started working on separating the builds on master. > Move the project to become Apache TLP > - > > Key: SOLR-14497 > URL: https://issues.apache.org/jira/browse/SOLR-14497 > Project: Solr > Issue Type: Task >Reporter: Dawid Weiss >Priority: Major > > This issue is about the process of moving Solr to become an Apache TLP. > Se > [https://cwiki.apache.org/confluence/display/LUCENE/Solr+TLP+needed+changes] > for a tabular view of possible changes. > *TODO*: Add sub tasks. > h4. Preparation > # Figure out formal steps to be taken with Apache Board to set up TLP > project for Solr. > # Figure out the initial committership, PMC members, chair. > # Separate the code (and build) from Lucene so that Solr can be built > independently. This applies to 8.x and master (9.x). > # Determine what happens with mailing lists (and their archives). Are new > mailing lists going to be set up or the existing ones aliased somehow? > # Determine what happens with CI and build servers. > # Determine how to split web site > # [add more here] > h4. Execution > # Code: clone Lucene/Solr git to Solr TLP, add a TLP marking tag. > # Web Site: clone lucene/solr-site Git Repo, add a TLP marking tag > # Send an information about any potential mailing list changes, etc. to > previous addresses. > # Add redirects from old Solr site/ javadoc/ any other addresses to TLP > locations. > # [add more here] > h4. Post-transition > # Proceed with LUCENE-9375. > # [add more here] -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org For additional commands, e-mail: issues-h...@lucene.apache.org
[jira] [Commented] (SOLR-14497) Move the project to become Apache TLP
[ https://issues.apache.org/jira/browse/SOLR-14497?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17203795#comment-17203795 ] Ishan Chattopadhyaya commented on SOLR-14497: - bq. Are we still aiming to setup the Solr PMC before 9.0 so that Lucene can release 9.0 alone, followed by an independent Solr 9.0 release? +1 How should I (or anyone just watching from the sidelines till now) proceed to help with this effort? Would parallely working on the tasks in the "Preparation" section help? > Move the project to become Apache TLP > - > > Key: SOLR-14497 > URL: https://issues.apache.org/jira/browse/SOLR-14497 > Project: Solr > Issue Type: Task >Reporter: Dawid Weiss >Priority: Major > > This issue is about the process of moving Solr to become an Apache TLP. > Se > [https://cwiki.apache.org/confluence/display/LUCENE/Solr+TLP+needed+changes] > for a tabular view of possible changes. > *TODO*: Add sub tasks. > h4. Preparation > # Figure out formal steps to be taken with Apache Board to set up TLP > project for Solr. > # Figure out the initial committership, PMC members, chair. > # Separate the code (and build) from Lucene so that Solr can be built > independently. This applies to 8.x and master (9.x). > # Determine what happens with mailing lists (and their archives). Are new > mailing lists going to be set up or the existing ones aliased somehow? > # Determine what happens with CI and build servers. > # Determine how to split web site > # [add more here] > h4. Execution > # Code: clone Lucene/Solr git to Solr TLP, add a TLP marking tag. > # Web Site: clone lucene/solr-site Git Repo, add a TLP marking tag > # Send an information about any potential mailing list changes, etc. to > previous addresses. > # Add redirects from old Solr site/ javadoc/ any other addresses to TLP > locations. > # [add more here] > h4. Post-transition > # Proceed with LUCENE-9375. > # [add more here] -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org For additional commands, e-mail: issues-h...@lucene.apache.org
[jira] [Commented] (SOLR-14497) Move the project to become Apache TLP
[ https://issues.apache.org/jira/browse/SOLR-14497?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17176255#comment-17176255 ] Jan Høydahl commented on SOLR-14497: I created two sub tasks here already, which is probably a good place to detail the independent tasks. I guess the split could happen at any point in time, even before an 8.x release, but once the split has started it triggers a lot of work before the next release can be done, so it needs to be planned carefully. > Move the project to become Apache TLP > - > > Key: SOLR-14497 > URL: https://issues.apache.org/jira/browse/SOLR-14497 > Project: Solr > Issue Type: Task >Reporter: Dawid Weiss >Priority: Major > > This issue is about the process of moving Solr to become an Apache TLP. > Se > [https://cwiki.apache.org/confluence/display/LUCENE/Solr+TLP+needed+changes] > for a tabular view of possible changes. > *TODO*: Add sub tasks. > h4. Preparation > # Figure out formal steps to be taken with Apache Board to set up TLP > project for Solr. > # Figure out the initial committership, PMC members, chair. > # Separate the code (and build) from Lucene so that Solr can be built > independently. This applies to 8.x and master (9.x). > # Determine what happens with mailing lists (and their archives). Are new > mailing lists going to be set up or the existing ones aliased somehow? > # Determine what happens with CI and build servers. > # Determine how to split web site > # [add more here] > h4. Execution > # Code: clone Lucene/Solr git to Solr TLP, add a TLP marking tag. > # Web Site: clone lucene/solr-site Git Repo, add a TLP marking tag > # Send an information about any potential mailing list changes, etc. to > previous addresses. > # Add redirects from old Solr site/ javadoc/ any other addresses to TLP > locations. > # [add more here] > h4. Post-transition > # Proceed with LUCENE-9375. > # [add more here] -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org For additional commands, e-mail: issues-h...@lucene.apache.org
[jira] [Commented] (SOLR-14497) Move the project to become Apache TLP
[ https://issues.apache.org/jira/browse/SOLR-14497?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17176236#comment-17176236 ] Dawid Weiss commented on SOLR-14497: Getting rid of ant is very likely a prerequisite since it'll be hard to push things forward without it... Erick filed a Jira issue for that. I have to think about what exact steps are needed myself. But thanks for nagging - it is motivating. :) > Move the project to become Apache TLP > - > > Key: SOLR-14497 > URL: https://issues.apache.org/jira/browse/SOLR-14497 > Project: Solr > Issue Type: Task >Reporter: Dawid Weiss >Priority: Major > > This issue is about the process of moving Solr to become an Apache TLP. > Se > [https://cwiki.apache.org/confluence/display/LUCENE/Solr+TLP+needed+changes] > for a tabular view of possible changes. > *TODO*: Add sub tasks. > h4. Preparation > # Figure out formal steps to be taken with Apache Board to set up TLP > project for Solr. > # Figure out the initial committership, PMC members, chair. > # Separate the code (and build) from Lucene so that Solr can be built > independently. This applies to 8.x and master (9.x). > # Determine what happens with mailing lists (and their archives). Are new > mailing lists going to be set up or the existing ones aliased somehow? > # Determine what happens with CI and build servers. > # Determine how to split web site > # [add more here] > h4. Execution > # Code: clone Lucene/Solr git to Solr TLP, add a TLP marking tag. > # Web Site: clone lucene/solr-site Git Repo, add a TLP marking tag > # Send an information about any potential mailing list changes, etc. to > previous addresses. > # Add redirects from old Solr site/ javadoc/ any other addresses to TLP > locations. > # [add more here] > h4. Post-transition > # Proceed with LUCENE-9375. > # [add more here] -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org For additional commands, e-mail: issues-h...@lucene.apache.org
[jira] [Commented] (SOLR-14497) Move the project to become Apache TLP
[ https://issues.apache.org/jira/browse/SOLR-14497?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17176229#comment-17176229 ] Jan Høydahl commented on SOLR-14497: Yea, lots of things to do there. I wonder if it makes sense to start working on the split in a branch, or if there is just too much other stuff going on in master these days? Should probably get rid of ant in master and a few other things before starting a branch.. Do you want to lay out somewhere, which steps are needed to do the actual git and build transition? Perhaps in [https://cwiki.apache.org/confluence/display/LUCENE/Solr+TLP+needed+changes] ? Hopefully you'll get plenty of assistance! > Move the project to become Apache TLP > - > > Key: SOLR-14497 > URL: https://issues.apache.org/jira/browse/SOLR-14497 > Project: Solr > Issue Type: Task >Reporter: Dawid Weiss >Priority: Major > > This issue is about the process of moving Solr to become an Apache TLP. > Se > [https://cwiki.apache.org/confluence/display/LUCENE/Solr+TLP+needed+changes] > for a tabular view of possible changes. > *TODO*: Add sub tasks. > h4. Preparation > # Figure out formal steps to be taken with Apache Board to set up TLP > project for Solr. > # Figure out the initial committership, PMC members, chair. > # Separate the code (and build) from Lucene so that Solr can be built > independently. This applies to 8.x and master (9.x). > # Determine what happens with mailing lists (and their archives). Are new > mailing lists going to be set up or the existing ones aliased somehow? > # Determine what happens with CI and build servers. > # Determine how to split web site > # [add more here] > h4. Execution > # Code: clone Lucene/Solr git to Solr TLP, add a TLP marking tag. > # Web Site: clone lucene/solr-site Git Repo, add a TLP marking tag > # Send an information about any potential mailing list changes, etc. to > previous addresses. > # Add redirects from old Solr site/ javadoc/ any other addresses to TLP > locations. > # [add more here] > h4. Post-transition > # Proceed with LUCENE-9375. > # [add more here] -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org For additional commands, e-mail: issues-h...@lucene.apache.org
[jira] [Commented] (SOLR-14497) Move the project to become Apache TLP
[ https://issues.apache.org/jira/browse/SOLR-14497?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17176165#comment-17176165 ] Dawid Weiss commented on SOLR-14497: > Are we still aiming to setup the Solr PMC before 9.0 so that Lucene can > release 9.0 alone, followed by an independent Solr 9.0 release? I'm +1 for this but it'll require some build-system work to get the stand-alone source distribution ready (among other things). This is fun stuff to do but it takes me away from my regular job and there's not much time left. I'll see what I can do to push it forward though. > Move the project to become Apache TLP > - > > Key: SOLR-14497 > URL: https://issues.apache.org/jira/browse/SOLR-14497 > Project: Solr > Issue Type: Task >Reporter: Dawid Weiss >Priority: Major > > This issue is about the process of moving Solr to become an Apache TLP. > Se > [https://cwiki.apache.org/confluence/display/LUCENE/Solr+TLP+needed+changes] > for a tabular view of possible changes. > *TODO*: Add sub tasks. > h4. Preparation > # Figure out formal steps to be taken with Apache Board to set up TLP > project for Solr. > # Figure out the initial committership, PMC members, chair. > # Separate the code (and build) from Lucene so that Solr can be built > independently. This applies to 8.x and master (9.x). > # Determine what happens with mailing lists (and their archives). Are new > mailing lists going to be set up or the existing ones aliased somehow? > # Determine what happens with CI and build servers. > # Determine how to split web site > # [add more here] > h4. Execution > # Code: clone Lucene/Solr git to Solr TLP, add a TLP marking tag. > # Web Site: clone lucene/solr-site Git Repo, add a TLP marking tag > # Send an information about any potential mailing list changes, etc. to > previous addresses. > # Add redirects from old Solr site/ javadoc/ any other addresses to TLP > locations. > # [add more here] > h4. Post-transition > # Proceed with LUCENE-9375. > # [add more here] -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org For additional commands, e-mail: issues-h...@lucene.apache.org
[jira] [Commented] (SOLR-14497) Move the project to become Apache TLP
[ https://issues.apache.org/jira/browse/SOLR-14497?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17176162#comment-17176162 ] Jan Høydahl commented on SOLR-14497: What's the status here? Last I recall was [~dsmiley] working on an email to send to committers in order to prepare the board resolution? Are we still aiming to setup the Solr PMC before 9.0 so that Lucene can release 9.0 alone, followed by an independent Solr 9.0 release? > Move the project to become Apache TLP > - > > Key: SOLR-14497 > URL: https://issues.apache.org/jira/browse/SOLR-14497 > Project: Solr > Issue Type: Task >Reporter: Dawid Weiss >Priority: Major > > This issue is about the process of moving Solr to become an Apache TLP. > Se > [https://cwiki.apache.org/confluence/display/LUCENE/Solr+TLP+needed+changes] > for a tabular view of possible changes. > *TODO*: Add sub tasks. > h4. Preparation > # Figure out formal steps to be taken with Apache Board to set up TLP > project for Solr. > # Figure out the initial committership, PMC members, chair. > # Separate the code (and build) from Lucene so that Solr can be built > independently. This applies to 8.x and master (9.x). > # Determine what happens with mailing lists (and their archives). Are new > mailing lists going to be set up or the existing ones aliased somehow? > # Determine what happens with CI and build servers. > # Determine how to split web site > # [add more here] > h4. Execution > # Code: clone Lucene/Solr git to Solr TLP, add a TLP marking tag. > # Web Site: clone lucene/solr-site Git Repo, add a TLP marking tag > # Send an information about any potential mailing list changes, etc. to > previous addresses. > # Add redirects from old Solr site/ javadoc/ any other addresses to TLP > locations. > # [add more here] > h4. Post-transition > # Proceed with LUCENE-9375. > # [add more here] -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org For additional commands, e-mail: issues-h...@lucene.apache.org
[jira] [Commented] (SOLR-14497) Move the project to become Apache TLP
[ https://issues.apache.org/jira/browse/SOLR-14497?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17118539#comment-17118539 ] Jan Høydahl commented on SOLR-14497: I removed the last "Nutch" mentions and added myself to the initial list. I also added a text above the resolution "If you are a Lucene committer and want to be part of the new Solr PMC, please add your name to the draft resolution below:". I don't see any reason to add 80 names to that list, of which some have no interest in Solr and others are inactive. Every Lucene committer who wants to join the new Solr project can add themselves to the list. In this way the Solr members list will reflect the actual community. Solr will still have a public history as a Lucene sub project and CHANGES.txt is carried over, so no credit is lost. We can even promise that any current Lucene committer will be given Solr committer bit later simply by asking the Solr PMC. > Move the project to become Apache TLP > - > > Key: SOLR-14497 > URL: https://issues.apache.org/jira/browse/SOLR-14497 > Project: Solr > Issue Type: Task >Reporter: Dawid Weiss >Priority: Major > > This issue is about the process of moving Solr to become an Apache TLP. > Se > [https://cwiki.apache.org/confluence/display/LUCENE/Solr+TLP+needed+changes] > for a tabular view of possible changes. > *TODO*: Add sub tasks. > h4. Preparation > # Figure out formal steps to be taken with Apache Board to set up TLP > project for Solr. > # Figure out the initial committership, PMC members, chair. > # Separate the code (and build) from Lucene so that Solr can be built > independently. This applies to 8.x and master (9.x). > # Determine what happens with mailing lists (and their archives). Are new > mailing lists going to be set up or the existing ones aliased somehow? > # Determine what happens with CI and build servers. > # Determine how to split web site > # [add more here] > h4. Execution > # Code: clone Lucene/Solr git to Solr TLP, add a TLP marking tag. > # Web Site: clone lucene/solr-site Git Repo, add a TLP marking tag > # Send an information about any potential mailing list changes, etc. to > previous addresses. > # Add redirects from old Solr site/ javadoc/ any other addresses to TLP > locations. > # [add more here] > h4. Post-transition > # Proceed with LUCENE-9375. > # [add more here] -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org For additional commands, e-mail: issues-h...@lucene.apache.org
[jira] [Commented] (SOLR-14497) Move the project to become Apache TLP
[
https://issues.apache.org/jira/browse/SOLR-14497?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17118519#comment-17118519
]
Dawid Weiss commented on SOLR-14497:
Jan - that resolution still has Nutch bits in it. For some reason I'm unable to
edit it (insufficient karma?).
{quote}bq. Don't know whether we need a PMC vote on the text before submitting
it?
{quote}
I don't think we have to have a formal vote but it'd be good for PMC members to
at least eyeball it.
{quote}bq. I also want to propose that we start off with every committer who
signs up will be on the initial Solr PMC
{quote}
I am not against but I think this proposal makes more sense for projects that
are materializing out of no prior history. Solr has an established structure
and it seems reasonable to have the same PMC at the moment of becoming TLP as
it just prior to that. Then new PMC members can be voted in using the new
project's infrastructure. I don't mind either way though - just expressed my
opinion.
> Move the project to become Apache TLP
> -
>
> Key: SOLR-14497
> URL: https://issues.apache.org/jira/browse/SOLR-14497
> Project: Solr
> Issue Type: Task
>Reporter: Dawid Weiss
>Priority: Major
>
> This issue is about the process of moving Solr to become an Apache TLP.
> Se
> [https://cwiki.apache.org/confluence/display/LUCENE/Solr+TLP+needed+changes]
> for a tabular view of possible changes.
> *TODO*: Add sub tasks.
> h4. Preparation
> # Figure out formal steps to be taken with Apache Board to set up TLP
> project for Solr.
> # Figure out the initial committership, PMC members, chair.
> # Separate the code (and build) from Lucene so that Solr can be built
> independently. This applies to 8.x and master (9.x).
> # Determine what happens with mailing lists (and their archives). Are new
> mailing lists going to be set up or the existing ones aliased somehow?
> # Determine what happens with CI and build servers.
> # Determine how to split web site
> # [add more here]
> h4. Execution
> # Code: clone Lucene/Solr git to Solr TLP, add a TLP marking tag.
> # Web Site: clone lucene/solr-site Git Repo, add a TLP marking tag
> # Send an information about any potential mailing list changes, etc. to
> previous addresses.
> # Add redirects from old Solr site/ javadoc/ any other addresses to TLP
> locations.
> # [add more here]
> h4. Post-transition
> # Proceed with LUCENE-9375.
> # [add more here]
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org
For additional commands, e-mail: issues-h...@lucene.apache.org
[jira] [Commented] (SOLR-14497) Move the project to become Apache TLP
[ https://issues.apache.org/jira/browse/SOLR-14497?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17118498#comment-17118498 ] Jan Høydahl commented on SOLR-14497: We need to draft a board resolution for you (chair) to submit for the next board meeting agenda. I added a first draft of a board resolution at the bottom of [https://cwiki.apache.org/confluence/display/LUCENE/Solr+TLP+needed+changes]. Don't know whether we need a PMC vote on the text before submitting it? Wrt the initial Solr PMC, perhaps each committer who wants to can add their own names to the list on that Wiki page? I also want to propose that we start off with every committer who signs up will be on the initial Solr PMC, even if they are not currently a Lucene PMC member, to simplify things? WDYT? > Move the project to become Apache TLP > - > > Key: SOLR-14497 > URL: https://issues.apache.org/jira/browse/SOLR-14497 > Project: Solr > Issue Type: Task >Reporter: Dawid Weiss >Priority: Major > > This issue is about the process of moving Solr to become an Apache TLP. > Se > [https://cwiki.apache.org/confluence/display/LUCENE/Solr+TLP+needed+changes] > for a tabular view of possible changes. > *TODO*: Add sub tasks. > h4. Preparation > # Figure out formal steps to be taken with Apache Board to set up TLP > project for Solr. > # Figure out the initial committership, PMC members, chair. > # Separate the code (and build) from Lucene so that Solr can be built > independently. This applies to 8.x and master (9.x). > # Determine what happens with mailing lists (and their archives). Are new > mailing lists going to be set up or the existing ones aliased somehow? > # Determine what happens with CI and build servers. > # Determine how to split web site > # [add more here] > h4. Execution > # Code: clone Lucene/Solr git to Solr TLP, add a TLP marking tag. > # Web Site: clone lucene/solr-site Git Repo, add a TLP marking tag > # Send an information about any potential mailing list changes, etc. to > previous addresses. > # Add redirects from old Solr site/ javadoc/ any other addresses to TLP > locations. > # [add more here] > h4. Post-transition > # Proceed with LUCENE-9375. > # [add more here] -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org For additional commands, e-mail: issues-h...@lucene.apache.org
[jira] [Commented] (SOLR-14497) Move the project to become Apache TLP
[ https://issues.apache.org/jira/browse/SOLR-14497?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17118451#comment-17118451 ] Anshum Gupta commented on SOLR-14497: - I'm +1 with [~uschindler] on this. Let's more slow but steadily towards the end goal. I think we might need to officially tell the board about the proposal to split, and then take it from there. I don't think a new project can be created without board approval. If someone has better idea on the rules here, please let me know and I can send out the email. > Move the project to become Apache TLP > - > > Key: SOLR-14497 > URL: https://issues.apache.org/jira/browse/SOLR-14497 > Project: Solr > Issue Type: Task >Reporter: Dawid Weiss >Priority: Major > > This issue is about the process of moving Solr to become an Apache TLP. > Se > [https://cwiki.apache.org/confluence/display/LUCENE/Solr+TLP+needed+changes] > for a tabular view of possible changes. > *TODO*: Add sub tasks. > h4. Preparation > # Figure out formal steps to be taken with Apache Board to set up TLP > project for Solr. > # Figure out the initial committership, PMC members, chair. > # Separate the code (and build) from Lucene so that Solr can be built > independently. This applies to 8.x and master (9.x). > # Determine what happens with mailing lists (and their archives). Are new > mailing lists going to be set up or the existing ones aliased somehow? > # Determine what happens with CI and build servers. > # Determine how to split web site > # [add more here] > h4. Execution > # Code: clone Lucene/Solr git to Solr TLP, add a TLP marking tag. > # Web Site: clone lucene/solr-site Git Repo, add a TLP marking tag > # Send an information about any potential mailing list changes, etc. to > previous addresses. > # Add redirects from old Solr site/ javadoc/ any other addresses to TLP > locations. > # [add more here] > h4. Post-transition > # Proceed with LUCENE-9375. > # [add more here] -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org For additional commands, e-mail: issues-h...@lucene.apache.org
[jira] [Commented] (SOLR-14497) Move the project to become Apache TLP
[ https://issues.apache.org/jira/browse/SOLR-14497?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17111312#comment-17111312 ] Dawid Weiss commented on SOLR-14497: Well, a patch will still apply (even if stripped prefix is required). I'm not concerned too much about Github integration: if we can't move things reasonably on github then so be it. Pull requests can be filed with relative ease against new repository (on github as well). > Move the project to become Apache TLP > - > > Key: SOLR-14497 > URL: https://issues.apache.org/jira/browse/SOLR-14497 > Project: Solr > Issue Type: Task > Security Level: Public(Default Security Level. Issues are Public) >Reporter: Dawid Weiss >Priority: Major > > This issue is about the process of moving Solr to become an Apache TLP. > Se > [https://cwiki.apache.org/confluence/display/LUCENE/Solr+TLP+needed+changes] > for a tabular view of possible changes. > *TODO*: Add sub tasks. > h4. Preparation > # Figure out formal steps to be taken with Apache Board to set up TLP > project for Solr. > # Figure out the initial committership, PMC members, chair. > # Separate the code (and build) from Lucene so that Solr can be built > independently. This applies to 8.x and master (9.x). > # Determine what happens with mailing lists (and their archives). Are new > mailing lists going to be set up or the existing ones aliased somehow? > # Determine what happens with CI and build servers. > # Determine how to split web site > # [add more here] > h4. Execution > # Code: clone Lucene/Solr git to Solr TLP, add a TLP marking tag. > # Web Site: clone lucene/solr-site Git Repo, add a TLP marking tag > # Send an information about any potential mailing list changes, etc. to > previous addresses. > # Add redirects from old Solr site/ javadoc/ any other addresses to TLP > locations. > # [add more here] > h4. Post-transition > # Proceed with LUCENE-9375. > # [add more here] -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org For additional commands, e-mail: issues-h...@lucene.apache.org
[jira] [Commented] (SOLR-14497) Move the project to become Apache TLP
[ https://issues.apache.org/jira/browse/SOLR-14497?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17111309#comment-17111309 ] Jan Høydahl commented on SOLR-14497: Agree with Uwe we should set some conditions for when to split the main git repo. Removing ant from master could be one such condition. We also need to think hard and long about how to treat open PRs and patches. PRs belong to the 'lucene-solr' repo, and I wonder if we could bulk move lucene-PRs to the new 'lucene' github repo and all solr-PRs to the new 'solr' github repo? Also, PRs and patches will likely not apply once we start moving things around in the repos post-split... > Move the project to become Apache TLP > - > > Key: SOLR-14497 > URL: https://issues.apache.org/jira/browse/SOLR-14497 > Project: Solr > Issue Type: Task > Security Level: Public(Default Security Level. Issues are Public) >Reporter: Dawid Weiss >Priority: Major > > This issue is about the process of moving Solr to become an Apache TLP. > Se > [https://cwiki.apache.org/confluence/display/LUCENE/Solr+TLP+needed+changes] > for a tabular view of possible changes. > *TODO*: Add sub tasks. > h4. Preparation > # Figure out formal steps to be taken with Apache Board to set up TLP > project for Solr. > # Figure out the initial committership, PMC members, chair. > # Separate the code (and build) from Lucene so that Solr can be built > independently. This applies to 8.x and master (9.x). > # Determine what happens with mailing lists (and their archives). Are new > mailing lists going to be set up or the existing ones aliased somehow? > # Determine what happens with CI and build servers. > # Determine how to split web site > # [add more here] > h4. Execution > # Code: clone Lucene/Solr git to Solr TLP, add a TLP marking tag. > # Web Site: clone lucene/solr-site Git Repo, add a TLP marking tag > # Send an information about any potential mailing list changes, etc. to > previous addresses. > # Add redirects from old Solr site/ javadoc/ any other addresses to TLP > locations. > # [add more here] > h4. Post-transition > # Proceed with LUCENE-9375. > # [add more here] -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org For additional commands, e-mail: issues-h...@lucene.apache.org
[jira] [Commented] (SOLR-14497) Move the project to become Apache TLP
[ https://issues.apache.org/jira/browse/SOLR-14497?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17111295#comment-17111295 ] Dawid Weiss commented on SOLR-14497: Thanks Jan, very clear. > Move the project to become Apache TLP > - > > Key: SOLR-14497 > URL: https://issues.apache.org/jira/browse/SOLR-14497 > Project: Solr > Issue Type: Task > Security Level: Public(Default Security Level. Issues are Public) >Reporter: Dawid Weiss >Priority: Major > > This issue is about the process of moving Solr to become an Apache TLP. > Se > [https://cwiki.apache.org/confluence/display/LUCENE/Solr+TLP+needed+changes] > for a tabular view of possible changes. > *TODO*: Add sub tasks. > h4. Preparation > # Figure out formal steps to be taken with Apache Board to set up TLP > project for Solr. > # Figure out the initial committership, PMC members, chair. > # Separate the code (and build) from Lucene so that Solr can be built > independently. This applies to 8.x and master (9.x). > # Determine what happens with mailing lists (and their archives). Are new > mailing lists going to be set up or the existing ones aliased somehow? > # Determine what happens with CI and build servers. > # Determine how to split web site > # [add more here] > h4. Execution > # Code: clone Lucene/Solr git to Solr TLP, add a TLP marking tag. > # Web Site: clone lucene/solr-site Git Repo, add a TLP marking tag > # Send an information about any potential mailing list changes, etc. to > previous addresses. > # Add redirects from old Solr site/ javadoc/ any other addresses to TLP > locations. > # [add more here] > h4. Post-transition > # Proceed with LUCENE-9375. > # [add more here] -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org For additional commands, e-mail: issues-h...@lucene.apache.org
[jira] [Commented] (SOLR-14497) Move the project to become Apache TLP
[ https://issues.apache.org/jira/browse/SOLR-14497?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17111285#comment-17111285 ] Jan Høydahl commented on SOLR-14497: I started a WIKI page at [https://cwiki.apache.org/confluence/display/LUCENE/Solr+TLP+needed+changes] with a table view of where I think we'll end up after the move. It makes it easier to visualize the changes needed, at least for me. Feel free to expand on the table in any way you see fit, or to discuss. > Move the project to become Apache TLP > - > > Key: SOLR-14497 > URL: https://issues.apache.org/jira/browse/SOLR-14497 > Project: Solr > Issue Type: Task > Security Level: Public(Default Security Level. Issues are Public) >Reporter: Dawid Weiss >Priority: Major > > This issue is about the process of moving Solr to become an Apache TLP. > Elements to handle (as sub-tasks)? > h4. Preparation > # Figure out formal steps to be taken with Apache Board to set up TLP > project for Solr. > # Figure out the initial committership, PMC members, chair. > # Separate the code (and build) from Lucene so that Solr can be built > independently. This applies to 8.x and master (9.x). > # Determine what happens with mailing lists (and their archives). Are new > mailing lists going to be set up or the existing ones aliased somehow? > # Determine what happens with CI and build servers. > # Determine how to split web site > # [add more here] > h4. Execution > # Code: clone Lucene/Solr git to Solr TLP, add a TLP marking tag. > # Web Site: clone lucene/solr-site Git Repo, add a TLP marking tag > # Send an information about any potential mailing list changes, etc. to > previous addresses. > # Add redirects from old Solr site/ javadoc/ any other addresses to TLP > locations. > # [add more here] > h4. Post-transition > # Proceed with LUCENE-9375. > # [add more here] -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org For additional commands, e-mail: issues-h...@lucene.apache.org
[jira] [Commented] (SOLR-14497) Move the project to become Apache TLP
[ https://issues.apache.org/jira/browse/SOLR-14497?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17111085#comment-17111085 ] Uwe Schindler commented on SOLR-14497: -- As already discussed on Mailing list, I'd suggest to not move too fast forward with that. I'd suggest to focus on master branch and leave 8.x alone. I'd also wait for the Gradle migration to be finalized: I don't want to be disturbed in this process yet. As this is/was infrastructure affecting both projects, we should start with a "stable state". > Move the project to become Apache TLP > - > > Key: SOLR-14497 > URL: https://issues.apache.org/jira/browse/SOLR-14497 > Project: Solr > Issue Type: Task > Security Level: Public(Default Security Level. Issues are Public) >Reporter: Dawid Weiss >Priority: Major > > This issue is about the process of moving Solr to become an Apache TLP. > Elements to handle (as sub-tasks)? > h4. Preparation > # Figure out formal steps to be taken with Apache Board to set up TLP > project for Solr. > # Figure out the initial committership, PMC members, chair. > # Separate the code (and build) from Lucene so that Solr can be built > independently. This applies to 8.x and master (9.x). > # Determine what happens with mailing lists (and their archives). Are new > mailing lists going to be set up or the existing ones aliased somehow? > # Determine what happens with CI and build servers. > # Determine how to split web site > # [add more here] > h4. Execution > # Code: clone Lucene/Solr git to Solr TLP, add a TLP marking tag. > # Web Site: clone lucene/solr-site Git Repo, add a TLP marking tag > # Send an information about any potential mailing list changes, etc. to > previous addresses. > # Add redirects from old Solr site/ javadoc/ any other addresses to TLP > locations. > # [add more here] > h4. Post-transition > # Proceed with LUCENE-9375. > # [add more here] -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org For additional commands, e-mail: issues-h...@lucene.apache.org
