-
Notifications
You must be signed in to change notification settings - Fork 50
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
v0.5.8 release to master #411
Comments
A release would be good. I'd like to verify that the reporting
functionality is working first though.
…On Tue, Mar 20, 2018 at 5:50 PM, Chris Murray ***@***.***> wrote:
@elplatt <https://github.com/elplatt> @ramgarden
<https://github.com/ramgarden> I've merged the 2 PRs (#407
<#407> & #410
<#410>) into dev & created a
tag/release. Are we happy to do a PR into master as per the previous
release process -
- deploy a fresh build & DB of dev & test functionality
- (blow away if needed)
- deploy a fresh build & DB of master & test functionality
- deploy dev build over top of master & test functionality
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#411>, or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAS0WKgGfk4o5WbPty_DK3uiQmAElPKMks5tgXmOgaJpZM4SytWd>
.
--
Edward L. Platt
https://elplatt.com | @elplatt | [email protected]
Tips for stopping email overload:
https://hbr.org/2012/02/stop-email-overload-1
|
@elplatt can't log into the demo instance to test it as per https://groups.google.com/d/topic/seltzercrm-dev/XnFA3OagQPY/discussion, the credentials may have changed |
Also, thoughts on having the registration and profile picture modules enabled by default? Do we also want to have Amazon payments enabled by default? What about PayPal? |
We're using the PayPal module exclusively since we started it.
Not sure if they should be enabled by default because every space is
different.
…On Sat, Mar 24, 2018, 4:23 PM Chris Murray ***@***.***> wrote:
Also, thoughts on having the registration and profile picture modules
enabled by default?
Do we also want to have Amazon payments enabled by default? What about
PayPal?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#411 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ACnBzShFPNE1tbMzntfvJj5GbKtGDa5Bks5thqtKgaJpZM4SytWd>
.
|
@ramgarden What do you think of it? Are there any things you'd want changed with it? |
The only thing that would make the PayPal module better would be if it
could pull the csv directly instead of us having to go log in and grab it
then import it manually. But that's a limitation in the PayPal side I
think, right?
…On Sat, Mar 24, 2018, 6:06 PM Chris Murray ***@***.***> wrote:
@ramgarden <https://github.com/ramgarden> What do you think of it? Are
there any thigns you'd want changed with it?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#411 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ACnBzV0-OyGajiy1cSZkERDXal_qPQa8ks5thsNggaJpZM4SytWd>
.
|
Well partly the PayPal side, partly my lack of ability to get #253 sorted :P |
As part of the testing, I've realised there's a blocking issue on doing a fresh install, created #413 to track it :) |
I'd say yes it might be time for the next release. I still haven't upgraded
our official install we've been using in production for 3 years now at
Melbourne Makerspace in Florida. I'm so lazy and worried it will break our
front door lock relies on it.
…On Mon, Mar 11, 2019, 8:33 PM Chris Murray ***@***.***> wrote:
@elplatt <https://github.com/elplatt> only a year late, but do we want to
do this release? I believe the reporting function was fixed in 370351c
<370351c>
by @adamundefinied;also demo install is still not workign & needs SSL-ified
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#411 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ACnBzTNILPtPvex-fBP_F2Ymdht7ypk8ks5vVwP4gaJpZM4SytWd>
.
|
@ramgarden well at least we know that version of code was reasonable stable ;) we should definitely set up a skype call or soemthing to chat about it when you have time & I'll see if I can walk you though it :) is the code that's there currently what's on your github repo? |
It might be a tad different because I made that fork at a slightly
different time after we already had it in place. But since the releases
are so far apart it's a good chance it is the same version.
…On Mon, Mar 11, 2019 at 8:51 PM Chris Murray ***@***.***> wrote:
@ramgarden <https://github.com/ramgarden> well at least we know that
version of code was reasonable stable ;) we should definitely set up a
skype call or soemthing to chat about it when you have time & I'll see if I
can walk you though it :) is the code that's there currently what's on your
github repo?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#411 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ACnBzTRyw6pI1ErX-jytiETZI2HPuv5Mks5vVwghgaJpZM4SytWd>
.
|
An new release would be great! How confident is everyone about the new install / upgrade process not breaking? Would anyone be willing to do a systematic test of the features? I may have some time this summer (May?) to put a little work into tidying up the code and merging in changes from i3 and other contributors. |
@elplatt - I'm reasonably confident of the install/upgrade process working, based on the tests in my first post. I do a basic test of
Haven't done much with the key/metadata/mentor/email list modules I've run this comparison and it seems to mostly be
So I'm fairly certain that doing a pull of elplatt:master onto your dev branch & deploying should be ok; the dev branches are a little trickier as there's greater diverengce of the code, and once you do elplatt:master > melbourneMkaerSpace:dev, elplatt:dev > melbounreMakerSpace:dev should be a lot simpler. Your branches for issues 375 & 376 can be pruned, the fixes will be in the new master branch |
v0.5.7 - update copyright year & enable additional modules #411
@elplatt @ramgarden so I've done the following successfully, just need to find out what's going on with billing in #425 now!
By testing fucntionality I mean the following
|
@elplatt on an aside, while I remember - is it worth getting rid of the 0.4.x-dev branch, as it's fairly stale now! |
PR #440 has been opened for this release @elplatt @ramgarden can yous review & let me know if it's OK to merge? |
Checking now...
…On Sun, May 3, 2020 at 7:49 PM Chris Murray ***@***.***> wrote:
PR #440 <#440> has been opened for
this release
@elplatt <https://github.com/elplatt> @ramgarden
<https://github.com/ramgarden> can yous review & let me know if it's OK
to merge?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#411 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAU4DTM6JFIL4F2L65L44C3RPX7IJANCNFSM4EWK2WOQ>
.
|
@elplatt @ramgarden I've merged the 2 PRs (#407 & #410) into dev & created a tag/release. Are we happy to do a PR into master as per the previous release process -
The text was updated successfully, but these errors were encountered: