Another idea: have the release PR contain the checklist. Then it would all
be in one place.
David
On Wed, Aug 19, 2020 at 4:40 PM Fabricio Aguiar
wrote:
>
>
>
> On Wed, Aug 19, 2020 at 12:02 PM David Davis
> wrote:
>
>> A separate github repo might make sense. Right now our release scripts
>>
On Wed, Aug 19, 2020 at 12:02 PM David Davis wrote:
> A separate github repo might make sense. Right now our release scripts
> live inside our .travis folders in repo. I don't know that they are project
> specific so perhaps we could move them to this new repo?
>
The script just get the plugin na
August 19th Agenda
- archive https://github.com/pulp/pulp_rpm_prerequisites
- done on galaxy
- Brian to archive on gh
- done: https://github.com/pulp/pulp_rpm_prerequisites
- look into
https://github.com/ansible-collections/overview/blob/master/collection_requirem
I suggest that we re-use the pulp_packaging github repo since it has a
related purpose and already exists :)
Also, for what it's worth, HackMD supports markdown checklists as well. I
lean more towards the github issue approach personally but it's worth
mentioning.
On Wed, Aug 19, 2020 at 11:03 A
A separate github repo might make sense. Right now our release scripts live
inside our .travis folders in repo. I don't know that they are project
specific so perhaps we could move them to this new repo?
David
On Wed, Aug 19, 2020 at 5:57 AM Tatiana Tereshchenko
wrote:
> Would a separate githu
+1 to have one Y release with depreciation warnings before actually
removing the code or introduce any backward incompatible change.
Tanya
On Wed, Aug 19, 2020 at 10:09 AM Matthias Dellweg
wrote:
> This sounds pretty much the same as i had in mind. Thank you for writing
> it up!
> One concern i
Would a separate github repo with issues enabled make sense?
One place for all templates if we need many (I can think of at least Y and
Z releases).
One place for all release tracking, one can see what is released, and what
is not, without going from repo to repo (or from one redmine project to
ano
This sounds pretty much the same as i had in mind. Thank you for writing it up!
One concern inline:
On Tue, Aug 18, 2020 at 10:31 PM Brian Bouterse wrote:
>
> Here's a problem statement(s) and some brainstorming ideas about what could
> be done to resolve them. This was discussed today at open f
