Initial non-experimental PropertyGraph Release

[rlratzel]

As a user, I would like to be able to load my data as a property graph and manipulate it as a property graph

Tasks

Beta Give feedback

1. Create new PropertyGraph source dir under cugraph/python #10
   0 of 2
   +0
2. Create new conda/pip package for PropertyGraph #11
   0 of 5
   +0
3. rapidsai/graph_dl#200
4. rapidsai/graph_dl#199
5. Adding vector columns twice fails in PG cugraph#3010
   bug +1
   
6. PropertyGraph test_property_graph_mg.py::test_add_edge_data_with_ids seg faults when restricted to a single-GPU #13
   bug +1

Scaling Tasks

Beta Give feedback

1. [FEA]: Allow data added to PropertyGraph to have IDs already as the index cugraph#3111
   feature request +1
   
2. Allow host memory to be used for property data #17
   0 of 1
   +0
3. [FEA] Explore saving property graph for each type in different dataframes cugraph#2424
   feature request +1
   
4. Allow users to specify values for non-applicable properties cugraph#3429
   1 of 2
   Story +1
   
5. [FIX]: MGPropertyGraph renumber_vertices_by_type fails when type is unspecified ('') cugraph#3058
   bug +1
   
6. [FEA]: Support creating a subgraph as a Property graph from an existing Property Graph cugraph#3158
   feature request +1
   
7. Get PG test case for MAG240 scale use case written and running cugraph#2720
   +0
   
8. Support additional data loading procedures in PropertyGraph #7
   improvement +1
   
9. Update MG PropertyGraph tests to have coverage at least equal to SG PropertyGraph tests #8
   feature request +1
   
10. [FEA]: Allow Vertex Properties to be Type-Specific cugraph#2942
    feature request +1
    
11. Research supporting storing some PropertyGraph properties on GPU, some on CPU #14
    +0

BLOG and Marketing Tasks

Beta Give feedback

1. [DOC] BLOG on Property Graph #16
   doc +1