Create a new release (7.x-2.0-alpha1 ?) [#2109157]

It's been a while since the last release and there have been lots of improvements. I think it's about time to do a new stable release of Project and project_issue. I just tested out the upgrade path and found a new issue. There's also an old issue dww had assigned to me to figure out. I think in both cases that the best answer is to just provide guidance to the potential need for manual configuration rather than an automated upgrade.

The issues are:

#2108693: Node changes field settings need to be updated during upgrade from unstable
#1955726: Provide unstable1 -> unstable2 upgrade path documentation for #1836934: Entityreference selection handler for project behaviors

Are there any issues in the queue that should be fixed prior to a release? Here are some criticals/majors, although it's not 100% clear they need to be fixed before the next release:

Comments

Comment #1

MustangGB CreditAttribution: MustangGB commented 5 November 2013 at 14:24

None of these seem like release blockers.

Comment #2

greggles

he/him

English

Denver, Colorado, USA

CreditAttribution: greggles commented 12 November 2013 at 16:46

@akamustang - Thanks for the feedback. Can you clarify if you mean they don't seem like blockers before the next unstable release or before the final release. I don't think they need to be fixed before the next unstable release, but #1890906: Information disclosure: Project* is not properly allowing node_access to work on listing queries in D7 should definitely be fixed before a final release.

Comment #3

MustangGB CreditAttribution: MustangGB commented 15 November 2013 at 08:39

To clarify, I was going by the issue title, so 7.x-2.0-unstable2 is what I was referring to.

Comment #4

greggles

he/him

English

Denver, Colorado, USA

CreditAttribution: greggles commented 5 May 2014 at 20:26

Issue summary:

View changes

I just upgraded to the current tip of project and project_issue dev branches and the upgrade went smoothly!

I think we can just link to all the issues in the original post from the unstable2 release node. In my opinion, that is documentation enough for anyone who uses these modules.

I plan to do that in a week or so.

Comment #5

drumm

he/him

NY, US

CreditAttribution: drumm commented 5 May 2014 at 20:49

Should we name it alpha1?

Comment #6

greggles

he/him

English

Denver, Colorado, USA

CreditAttribution: greggles commented 5 May 2014 at 20:59

Title:

Create a new release (7.x-2.0-unstable2 ?)

» Create a new release (7.x-2.0-alpha1 ?)

Sure, alpha1 makes sense.

The biggest concern is the node access issue. We need to resolve that before deploying it on s.d.o, though, which should be soon.

Comment #7

BarisW CreditAttribution: BarisW commented 7 June 2014 at 06:14

Yes please, I am about to start a new website with the project module, would love to have a release instead of using dev.

Comment #8

dww

we/he/they

CreditAttribution: dww commented 7 June 2014 at 16:45

Issue summary:

View changes

Yeah, alpha1 seems good. +1 to that.

Sorry I've been MIA and out of the loop for a while. Things seem relatively stable. If folks are basically happy with the ends of the branches these days, let's do it.

I did a quick look through majors/criticals and updated the list in the summary. I definitely think #1890906: Information disclosure: Project* is not properly allowing node_access to work on listing queries in D7 is the most critical. The rest can probably wait. Even #1890906 isn't necessarily a blocker for an alpha1, I suppose.

Thanks,
-Derek