[Evergreen-dev] Please No Pushes Until Monday

[Morgan, Michele]

Jason,

Yes, ready to go with both the email and blog post.

Shall we say 11:00?

Michele

--
Michele M. Morgan, Systems Support Specialist
North of Boston Library Exchange, Danvers Massachusetts
mmorgan at noblenet.org



On Mon, Jul 24, 2023 at 10:33 AM Jason Stephenson <jason at sigio.com> wrote:

> Michele,
>
> I like the announcement, short and to the point.
>
> Do you plan to send an email, too?
>
> I'm ready to go whenever you are. Just let me know.
>
> Jason
>
> On 7/24/23 08:56, Morgan, Michele wrote:
> > Another FYI, I have a draft release announcement on evergreen-ils.org
> > <http://evergreen-ils.org> ready to be published when the time is
> right.
> > If anyone wants to make changes, please feel free.
> >
> > Email announcement will be similar, also when the time is right.
> >
> > --
> > Michele M. Morgan, Systems Support Specialist
> > North of Boston Library Exchange, Danvers Massachusetts
> > mmorgan at noblenet.org <mailto:mmorgan at noblenet.org>
> >
> >
> >
> > On Sun, Jul 23, 2023 at 8:49 AM Jason Stephenson via Evergreen-dev
> > <evergreen-dev at list.evergreen-ils.org
> > <mailto:evergreen-dev at list.evergreen-ils.org>> wrote:
> >
> >     Just a FYI: I updated the 3.9.4 release notes for the things that
> were
> >     missed yesterday.
> >
> >     I pushed it to the rel_3_9, rel_3_9_4, and main branches listed in
> the
> >     quote below.
> >
> >     I also updated the tarball, MD5 sum file, and release notes for the
> >     downloads page.
> >
> >     On 7/22/23 14:01, Jason Stephenson wrote:
> >      > Hello, all.
> >      >
> >      > Given that we're trying to get security releases actually
> >     released on
> >      > Monday, I'm going to ask that no one push to the main Evergreen
> >      > repository until the release branches have been pushed on Monday.
> >      >
> >      > The branches should be pushed around the time that the release
> >      > announcement is made.
> >      >
> >      > I've got an appointment for a filling on Monday morning, so if I
> >     do it
> >      > it won't be until after noon.
> >      >
> >      > If someone wants to merge the branches before I can, they are
> here:
> >      >
> >      > rel_3_9: security/release/rel_3_9_2023_07
> >      > rel_3_10: security/release/rel_3_10_2023_07
> >      > rel_3_11: security/release/rel_3_11_2023_07
> >      > main: security/release/main_2023_07
> >      > rel_3_10_3: working/collab/blake/tags/rel_3_10_3
> >      > rel_3_11_1: working/collab/blake/tags/rel_3_11_1
> >      > rel_3_9_4: security/release/tags/rel_3_9_4
> >      >
> >      > They should all be up to date with the database upgrades forward
> >     ported,
> >      > etc.
> >      >
> >      > Owing to certain circumstances, the downloads page has already
> been
> >      > updated with the new tarballs.  (Well, I'm going to add 3.9.4
> right
> >      > after hitting send.)
> >      >
> >      > Cheers,
> >      > Jason Stephenson
> >     _______________________________________________
> >     Evergreen-dev mailing list
> >     Evergreen-dev at list.evergreen-ils.org
> >     <mailto:Evergreen-dev at list.evergreen-ils.org>
> >     http://list.evergreen-ils.org/cgi-bin/mailman/listinfo/evergreen-dev
> >     <
> http://list.evergreen-ils.org/cgi-bin/mailman/listinfo/evergreen-dev>
> >
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://list.evergreen-ils.org/pipermail/evergreen-dev/attachments/20230724/b66c82bc/attachment-0001.htm>