Get our code in sync with drupal.org cvs
Bug #439044 reported by
Stuart Metcalfe
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Drupal OpenID module |
Confirmed
|
Low
|
Stuart Metcalfe | ||
Drupal Teams module |
Confirmed
|
Low
|
Stuart Metcalfe | ||
Drupal/Launchpad login module |
Confirmed
|
Low
|
Stuart Metcalfe |
Bug Description
Drupal.org's CVS is the system mandated by drupal in order to get a project listed under /projects/ on the main site. We should get our latest revisions into drupal's CVS system and keep them in sync. Is there a better way to manage/automate this?
Changed in drupal-launchpad: | |
status: | New → Confirmed |
Changed in drupal-openid: | |
status: | New → Confirmed |
Changed in drupal-teams: | |
status: | New → Confirmed |
importance: | Undecided → Medium |
importance: | Medium → Wishlist |
Changed in drupal-openid: | |
importance: | Undecided → Wishlist |
Changed in drupal-launchpad: | |
importance: | Undecided → Wishlist |
To post a comment you must log in.
Is there any timeline that you intend to do this? It sucks, but it would be very helpful to me if you could make a sync.