Component Migration

2019-01-03 Thread Benedict Elliott Smith
Following the vote for JIRA workflow changes, I have introduced the new 
Components and migrated any that were relatively easy*.  I have retained the 
old Component values with the prefix Legacy/.

I have also introduced the proposed Feature field into Component for now, until 
we can establish if it is possible to achieve an editable multi-select list. I 
have a ticket filed with Infra you can follow for progress on this and other 
changes: https://issues.apache.org/jira/browse/INFRA-17528 

To complete the migration of Component, it would be appreciated if we could all 
chip-in.  The filter below will list all of those tickets your jira user has 
been associated with as either reporter, assignee or reviewer, that is also 
associated with one of the legacy component types.  It would be appreciated if 
you could slowly work through your own (perhaps starting with reporter and 
assignee, then moving onto reviewer if the tickets remain un-migrated in a week 
or two)

project = CASSANDRA AND component in ("Legacy/Coordination", "Legacy/Core", 
"Legacy/CQL", "Legacy/Distributed Metadata", "Legacy/Documentation and 
Website", "Legacy/Local Write-Read Paths", "Legacy/Observability", 
"Legacy/Streaming and Messaging", "Legacy/Testing", "Legacy/Tools") AND 
(assignee = currentUser() OR reviewer = currentUser() OR reviewers = 
currentUser() OR reporter = currentUser())

Disappointingly, the majority of tickets have *no* Component associated with 
them.  Perhaps we could have a similar cleanup effort for those lacking 
Component at a later date.

* there are some remaining bulk migrations I may be able to perform using fuzzy 
string searches, but they won’t go very far
-
To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org
For additional commands, e-mail: dev-h...@cassandra.apache.org



[NOTICE] Mandatory migration of git repositories to gitbox.apache.org

2019-01-03 Thread Apache Infrastructure Team
Hello, cassandra folks.
As stated earlier in 2018, all git repositories must be migrated from
the git-wip-us.apache.org URL to gitbox.apache.org, as the old service
is being decommissioned. Your project is receiving this email because
you still have repositories on git-wip-us that needs to be migrated.

The following repositories on git-wip-us belong to your project:
 - cassandra-dtest.git
 - cassandra.git
 - cassandra-builds.git


We are now entering the mandated (coordinated) move stage of the roadmap,
and you are asked to please coordinate migration with the Apache
Infrastructure Team before February 7th. All repositories not migrated
on February 7th will be mass migrated without warning, and we'd appreciate
it if we could work together to avoid a big mess that day :-).

Moving to gitbox means you will get full write access on GitHub as well,
and be able to close/merge pull requests and much more.

To have your repositories moved, please follow these steps:

- Ensure consensus on the move (a link to a lists.apache.org thread will
  suffice for us as evidence).
- Create a JIRA ticket at https://issues.apache.org/jira/browse/INFRA

Your migration should only take a few minutes. If you wish to migrate
at a specific time of day or date, please do let us know in the ticket.

As always, we appreciate your understanding and patience as we move
things around and work to provide better services and features for
the Apache Family.

Should you wish to contact us with feedback or questions, please do so
at: us...@infra.apache.org.


With regards,
Apache Infrastructure


-
To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org
For additional commands, e-mail: dev-h...@cassandra.apache.org