Start work on VOTable 1.6

[mbtaylor]

Changes mostly from running make new-release, but did some manual adjustment of the \previousversion URLs.

[msdemlei]

Seems harmless enough. (you're aware of ivoatex's make new-release?)

[mbtaylor]

Thanks @msdemlei but it looks like I still can't merge this since neither you nor I have write access. I think either @andamian or @bsipocz has to approve?

If I'm acting as editor does it make sense for me to acquire Maintainer status? I'm not sure what's normal procedure.

[msdemlei]

On Mon, Feb 02, 2026 at 02:40:28AM -0800, Mark Taylor wrote: mbtaylor left a comment (ivoa-std/VOTable#74) If I'm acting as editor does it make sense for me to acquire Maintainer status? I'm not sure what's normal procedure.

Oh, and dear Apps chairs, can I have write access, please, so I can approve?

[tomdonaldson]

A fine start.

[tomdonaldson]

I don't think we have consistent access policies across the repos and it is important to limit access. That said, when I was editor, I had maintainer access so I've gone ahead and added @mbtaylor as maintainer. I also added @msdemlei with write permissions to allow timely reliable reviews. I'm happy to back off these positions as needed pending further discussions with @andamian, @bsipocz and @molinaro-m.

[bsipocz]

I think it's right to have the editors write access. Long term, maybe those access rights should be done via appropriate github teams rather than directly going to individuals, but that's an extreme level of nitpicking and way beyond the scope of the individual repo.

Thanks @msdemlei but it looks like I still can't merge this since neither you nor I have write access.

However, I very much wonder how @mbtaylor didn't have write access as being an org owner?