On 05/29/2013 05:23 PM, Russell E. Owen wrote:
> In article <51a51603.5030...@stsci.edu>,
> Michael Droettboom
> wrote:
>
>> I am going to hold off one more day on making the release candidate.
>> There are three blocker bugs that were discovered over the weekend and
>> I'd like to give them a
In article <51a51603.5030...@stsci.edu>,
Michael Droettboom
wrote:
> I am going to hold off one more day on making the release candidate.
> There are three blocker bugs that were discovered over the weekend and
> I'd like to give them a chance for review first:...
Thanks for the update.
T
I am going to hold off one more day on making the release candidate.
There are three blocker bugs that were discovered over the weekend and
I'd like to give them a chance for review first:
#854 and #2061: These both have to do with problems with ignoring limits
and can be fixed by the same cha
I've gone ahead and created the 1.3.x branch on master. This means that
the feature freeze on master is effectively lifted. Any PRs for 1.3.x
should be milestoned as such before merging (and can be merged to either
master or the 1.3.x branch). That milestone will indicate to me what
needs to
The 1.3.0 release candidate tagging is scheduled for this coming Monday,
May 27. Unfortunately, due to an oversight on my part, I forgot that is
a holiday, so I'm going to postpone it one day to Tuesday, May 28. I
will be hoping to tag the release by 23:00 UTC that day.
I think we're in reall
