what i would like to move towards is a ticket is created, then before we schedule something for the next release we check for outstanding tickets.

So in this case if steve wants to schedule auth for a minor release, we review auth for outstanding tickets first. I'm not saying that all outstanding tickets must be resolved before a minor release, just that we review them and let that influence our decision to put auth on the release schedule.

Thoughts?

On Apr 29, 2013, at 1:35 PM, Nomi Harris <nlharris@lbl.gov> wrote:

Agreed.

Nomi

On Apr 29, 2013, at 11:33 AM, Michael Sneddon <mwsneddon@lbl.gov> wrote:

The problem is probably an out-of-date makefile.  I assume we'll soon start to fail such modules that don't update to conform to the documentation standards as they are rereleased, and give owners a couple days during build week to make the fix.  If it is critical to get auth running now though, then for this round it probably shouldn't be a deal beaker for deployment of auth.

On Mon, Apr 29, 2013 at 9:47 AM, Nomi Harris <nlharris@lbl.gov> wrote:

Weren't there other modules that deployed their docs into non-standard directories as well? Not that I think that's a good thing; I'm just saying I don't think auth is the only culprit.
        Nomi

On Apr 29, 2013, at 9:45 AM, Dan Olson <dolson@mcs.anl.gov> wrote:

> This has been deployed onto the clients instance.
>
> Maybe this hasn't come up before, but the documentation appears to deploy to the authorization_server
> service_dir instead of auth.  Is that by design, or did something fail to deploy properly?
>
> ----- Original Message -----
>> From: "Thomas Brettin" <brettin@mcs.anl.gov>
>> To: "Dan Olson" <dolson@mcs.anl.gov>
>> Cc: release-team@lists.kbase.us
>> Sent: Monday, April 29, 2013 10:04:50 AM
>> Subject: auth
>>
>> Hi Dan,
>>
>> Can you deploy this into testing this morning?
>>
>> Tom
>>

_______________________________________________
Release-team mailing list
Release-team@lists.kbase.us
https://lists.kbase.us/mailman/listinfo/release-team