Timeline for What are the really use of the ancient Project Application issue queue now that you can promote your own sandbox projects?
Current License: CC BY-SA 3.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Apr 13, 2017 at 12:46 | history | edited | CommunityBot |
replaced http://drupal.stackexchange.com/ with https://drupal.stackexchange.com/
|
|
| Mar 20, 2017 at 14:15 | comment | added | Adrian Cid Almaguer | Finally the project was approved and I see the shield now after I think 2 or 3 days. | |
| Mar 15, 2017 at 12:03 | history | edited | Pierre.Vriens | CC BY-SA 3.0 |
added 212 characters in body
|
| Mar 14, 2017 at 19:33 | comment | added | mpdonadio♦ | I am 90% sure this answer is incorrect and tangential to the actual question, which is about the Project Applications queue being repurposed to the Drupal.org security advisory coverage applications queue. This has to do with what gets called the "git vetted" role, which is being repurposed to opt-in to security coverage. I don't have the full details yet, so I don't want to give out bad info (technically, I am a review admin, but inactive the last few months). | |
| Mar 14, 2017 at 17:40 | comment | added | Pierre.Vriens | Maybe not an answer to your previous comment, but that's indeed a good question. And it confuses me too. Maybe worth another (separated) question here on D.A? BTW: I just discovered other "changes" to the behavior of project pages of project pages for some of my modules for which I last updated their project page about a year ago ... more fun on the way about that ... | |
| Mar 14, 2017 at 17:26 | comment | added | Adrian Cid Almaguer | Maybe I'm a little confused, If I can get the shield only with the project release why we need a issue queue named: Drupal.org security advisory coverage applications drupal.org/project/projectapplications | |
| Mar 14, 2017 at 17:11 | history | answered | Pierre.Vriens | CC BY-SA 3.0 |