TC Meetings Communications

Hi Please note revised time I had forgotten the mainland Europe is still ahead
by an hour.

Colin

Hi All,
There will be aTC meeting today at 16:00 CET
I have one main agenda item.

  1. Upcoming 3.2 release planning

Best,
Colin


The title of this topic originally was "TC Meeting Today 15-02-2017 17:00 CET"
Edited to allow publishing of short notes about the meetings.
~rugyada

Am I the only one confused by talk of a 3.2 release? We haven’t released 3.1 yet shouldn’t that get done first?

3.1 was xmas release :slight_smile:

Colin was probably talking about 3.02, the isos currently produced in ABF

Sorry, 3.1 > 3.01.
Yes, 3.1 or 3.2 is an oversight :wink:

Seems like naming them 3.01 and 3.02 was a terrible idea. Colin consistently keeps calling them 3.1 and 3.2. If the president of the association can’t get the naming right…

Meeting logs here.

The president is only human and may make mistakes like everyone. There is a reason behind the 3.01, 3.02, …, 3.10, etc. pattern decision. You can see by yourself, isn’t it? :wink:

2 Likes

Guys and Gals if you look here http://abf-downloads.openmandriva.org/ I’m
assuming that the Christmas release was 3.1 so the next will be 3.2.
Reaonable?
Best,
Colin

2 Likes

There is still nothing in 3.1/

1 Like

The Christmas release was OMLx 3.01
https://blog.openmandriva.org/2016/12/openmandriva-lx-3-01-our-holidays-gift/
3.01 - Wiki [en] OpenMandriva

Next upcoming release will be OMLx 3.02
3.02 - Wiki [en] OpenMandriva

Example:
https://abf.openmandriva.org/platforms/3.0/products/38/product_build_lists/834
OpenMandrivaLx.3.02-PLASMA.x86_64.iso

version=3.02

2 Likes

Here’s what TPG (on Cooker ML) says:

Next stable release will be 3.02
Next unstable release will be 3.1

With all due and well deserved respect for Colin my observation was that he wasn’t making a mistake as he repeatedly uses 3.1 and 3.2 only in spite of what our release notice and our wiki say. Therefore I was requesting to have the topic discussed at the next TC meeting.

Or am I being to picky or to pedantic? Is it OK to call our releases whatever?

1 Like

Well I am confused as you are; devs have referred to on some occasions as 3.1
and 3.2 and this would be much more consistent with our previous secondary
releases of 2014 i.e. 2014.1…2014.2 and the unreleased 2014.3. To me the 0 is
superfluous and I really don’t know how it crept in.
Anyway to clarify it did mean 3.20----------- ha only joking 3.02:0
Best,
Colin

1 Like

Please ask TPG. I think he’s the one who did this and is still Release Manager. Again his most recent word this past week on Cooker ML:

Next stable release will be 3.02
Next unstable release will be 3.1

And the Christmas release is clearly called 3.01 in the release announcement and in our wiki.

Full disclosure. I don’t even like this damn discussion :confounded: as I thought then and still do that naming it 3.0x was an invitation to naming confusion. But on the other hand I feel I’d be remiss in not bringing it up as you can see from what TPG our Release Manager says we will have things called both 3.01-3.02 and 3.1… Arggghhh… :persevere:

All of which adds up to something to either discuss in TC-meeting or let TPG tell us how it is and follow that. At at this point in time I think the later is maybe the better course. The opportunity to avoid confusion has unfortunately passed.

There is nothing to be confused.

3.* is the series.
3.xx are the “respins” (or call it what you like best).
The pattern X.0x > X.1x > X.2x > until X.99 is to be free to exceed the 9th release - if ever one needs to.

Of course we may be superficial and just look at the next 10 cm from our nose, why bother to think in perspective? Who cares?

2 Likes

Well it seems to me then that 3.01 ands 3.02 should not be called releases but
updates but hell what do I know!! :slight_smile: The notion that 3.01 or indeed 3.02 are
“stable”, well, all I can say that they certainly aren’t here. Yesterdays
update broke my system and I will have to reinstall because the lockup that
occurred during update completely broke the rpm database so I will have to
re-install. As far as I can see this rolling release system is just resulting
in continuous breakage of what is supposed to be a stable system.

2 Likes

Hi All,
There will be a TC meeting at the usual place and time this afternoon.
Here’s an agenda>

  1. Clarification of release naming
  2. QA Next release. ISO testing
  3. Discussion rpm update to 5.4.18. Suggestion is to conduct debate in GitHub
    (Jeff Johnson)

Apologies for the late mail dentist this morning.

Best,
Colin

1 Like

Hi All,
There will be no TC meeting today. Bero is at a conference and I am preparing
for the OpenMandriva meet in Budapoest.
Normal service will resume next week.
Best,
Colin

Hi Everyone,
There will be no official TC meeting today. Normal service will resume next week
on my return from holiday.
Please feel free to meet informally if you wish.
Best,
Colin

You do realize that this thread is for February 15, 2017? :sleeping: